UX Designer resume example
A UX designer is hired to reduce the cost of using a product. That means finding out where people get stuck, proposing a flow that removes the sticking point, and getting it built. Hiring managers read a UX resume looking for evidence that you worked with real users and real engineers, not only with Figma files.
The resume has to show three things clearly: research you ran yourself, design work that shipped, and a number that moved after it shipped. Completion rate, support tickets, time on task, drop-off at a step, error rate. If a project never shipped, say what you learned and what changed because of it. Screeners skip resumes that describe wireframes and personas with no outcome attached.
Also show how you work with other people. Mid-level UX roles sit between product managers, engineers and often a content or brand team. Name the rituals you took part in, the design system you maintained or contributed to, and the handoff practices that kept rework low. A portfolio link near your name is expected; a resume that says "portfolio available on request" gets passed over.
The example
Jordan Avery is a placeholder, and every employer on this page is fictional. The numbers are illustrative.
What makes it work
The same bullets as people usually write them, and what changed.
Before
Responsible for creating wireframes and mockups for the mobile app.
After
Redesigned the mobile account setup across six screens, cutting the drop-off between steps two and three from 34% to 19%.
The weak version lists deliverables. The strong one names the flow, the scope and the number that moved.
Before
Conducted user research to understand customer pain points.
After
Ran 22 moderated sessions with small-business users and found that three of five could not locate the export function.
Specific counts and a specific finding show research you actually did, not a phrase copied from a course.
Before
Worked closely with engineering and product teams in an agile environment.
After
Joined engineering refinement each sprint and wrote state specs for empty, loading and error cases, which cut design rework tickets by about a third.
Names the ritual and the artifact instead of claiming collaboration in the abstract.
Before
Helped maintain the company design system.
After
Added 14 form and table components to the shared library and documented usage rules, so three product teams stopped rebuilding inputs.
Shows the size of the contribution and who benefited from it.
Before
Improved accessibility across the platform.
After
Audited the checkout flow against WCAG 2.1 AA, fixed contrast and focus order on 20 screens, and cleared all blocking issues before launch.
Names the standard, the scope and the finish line rather than a vague improvement.
Before
Presented designs to stakeholders and got approval.
After
Ran a two-hour prioritization workshop with product, support and sales that settled a six-month roadmap disagreement over navigation.
A presentation is a task; the rewrite shows a decision you unblocked.
Keywords a ux designer resume needs
| Keyword | Why it matters | Where to put it |
|---|---|---|
| user research | Most UX postings ask for someone who can talk to users, not only interpret someone else's findings. | Skills list and at least one bullet in your most recent role |
| usability testing | It is the single most named UX method in job descriptions and proves you validate before shipping. | A bullet with the number of sessions and what changed as a result |
| Figma | The default design and handoff tool at most companies; recruiters filter on it by name. | Tools group in skills |
| design system | Mid-level designers are expected to work inside one and extend it rather than draw from scratch. | Skills list and a bullet describing components you added or maintained |
| wireframes | Shows you work at low fidelity early instead of jumping to polished screens. | Skills list or a bullet about early exploration |
| prototyping | Interactive prototypes are how ideas get tested and sold internally. | Skills list and a testing bullet |
| information architecture | Navigation and content structure work is a distinct skill screeners look for on larger products. | A bullet about restructuring navigation or taxonomy |
| accessibility WCAG | Many teams now require AA compliance and will ask how you check for it. | Skills list, plus a bullet about audits or fixes |
| interaction design | Distinguishes you from a visual-only designer and matches common job titles. | Summary or headline |
| design handoff | Engineers judge designers on how clean the spec and states are. | A bullet about working with engineering |
| A/B testing | Shows you can defend a design with data rather than taste. | A bullet with the metric and the result |
| journey mapping | Common request for roles that span more than one screen or channel. | Skills list or a research bullet |
| stakeholder workshops | Signals you can run a room of non-designers and leave with decisions. | A bullet in a recent role |
| design QA | Checking the built version against the design is real work teams want covered. | Skills list or an engineering collaboration bullet |
Common mistakes
- Listing tools and methods with no shipped work or metric attached to any of them.
- Leaving off a portfolio link, or linking to a site that needs a password with no note about how to get it.
- Describing team outcomes in the plural throughout so a reader cannot tell what you personally designed.
- Filling the page with personas and empathy maps while never mentioning a build, a launch or a release.
- Using screenshots or a two-column layout that breaks when parsed by an applicant tracking system.
- Calling yourself a UX/UI designer without saying which parts of the work you actually own.
- Skipping accessibility entirely when the posting names WCAG or Section 508.
- Writing a summary about your design philosophy instead of the products and users you have worked with.
Questions people ask
- Do I need a portfolio if I already have a strong resume?
- Yes. For UX roles the portfolio decides the interview and the resume decides whether anyone opens the portfolio. Put the URL in the header next to your email. If your best work is under NDA, include one case study you can discuss and say so plainly.
- How many projects should I put on a UX resume?
- Cover two or three roles with three to five bullets each, and let each bullet stand for one project or one flow. Depth beats a long list. Pick the projects where you can name the user problem, your contribution and a result.
- What if my work never shipped?
- Say what it was, why it stopped, and what came out of it anyway. Research that changed a roadmap decision counts. Prototypes that killed a bad feature before engineering spent a quarter on it count too. Just be honest about the state.
- Should I list Figma, Sketch and Adobe XD all together?
- List what you actually use now and one or two others you know. Figma is the one most teams screen for. Padding the list with every tool you opened once makes the rest of the skills section less believable.
- How do I show research skills if a researcher ran the studies?
- Describe what you did inside those studies: writing the task script, taking notes, synthesizing clips, running the debrief. Then show what you changed in the design because of a finding. Teams without a dedicated researcher want to know you can carry the lighter version alone.
- Does a UX resume need a metric in every bullet?
- No, and forcing one produces numbers nobody believes. Aim for two or three real metrics across the whole resume and let the other bullets carry scope: how many screens, how many teams, how many sessions.
- Should I include visual design and front-end code?
- Include them if they are real. Knowing HTML and CSS well enough to read a component and talk to engineers is a plus at most companies. Do not claim engineering ability you cannot show in an interview.
- How long should a mid-level UX resume be?
- One page is still fine at five to nine years, two pages if you have a lot of shipped work. Either way the first third of page one should carry your strongest outcome. Do not push education and coursework above your experience.
More resume examples
Now do it with your own resume
Paste a job description and your resume. It rewrites your own lines for the job, never invents a fact, and asks you when something is missing.
Start from this example