UX Designer resume example
UX resumes are read alongside a portfolio, and the portfolio decides. The resume’s job is to get it opened: a working link near the top, the outcomes your design work produced, and enough about process to show you did research rather than decoration.
The full example
Fictional example shown in the Classic template. Every design on this site is free to use.
Summary example
UX designer with 6 years on B2B and consumer products, currently the sole designer on a platform with 200K monthly users. Cut checkout abandonment from 68% to 41% through a five-round research and testing programme, and built the design system now used across four product teams.
Notice the shape: years of experience, then one specific result with a number in it, then what you are known for. Three sentences is enough.
Bullet points that work
Adapt these to work you have genuinely done — the numbers must be yours.
- Cut checkout abandonment from 68% to 41% across five rounds of research and usability testing.
- Built the design system now used by 4 product teams, halving design-to-development handoff time.
- Ran 60+ moderated usability sessions and 12 rounds of unmoderated testing.
- Redesigned the onboarding flow, raising completion from 44% to 79%.
- Introduced an accessibility audit that brought the product to WCAG 2.1 AA across core journeys.
- Facilitated 8 cross-functional design sprints with product, engineering and support.
Tips specific to this role
- 1
Put your portfolio link on its own line near the top, and check it works from a private window.
- 2
Give outcomes, not artefacts. "Abandonment 68% to 41%" beats "created wireframes and prototypes".
- 3
Keep the resume itself single-column and plainly formatted. Creative layouts fail parsers most often in this field.
Mistakes to avoid on a ux designer resume
-
A portfolio of screens with no problem behind them. The work is the reasoning; polished final frames with no research or constraint read as decoration.
-
No mention of research. Designers who have spoken to users and designers who have not are easy to tell apart, and the resume usually reveals which.
-
Outcome-free case studies. Say what changed — task completion, error rate, support contacts, conversion.
-
Listing Figma as a skill. Assumed. Design systems, accessibility standards and research methods are not.
How the summary changes with experience
The same role, written two ways. Take whichever is closer to where you are now.
Entry level
UX designer with two years on an internal tools team, redesigning the claims-entry flow after eight contextual interviews with handlers. Cut average task completion from 4m 20s to 2m 45s and halved validation errors. Portfolio at [link].
Senior
Senior UX designer with 10 years in regulated fintech, owning the design system used across six product teams and taking it to WCAG 2.2 AA. Ran the research programme that reframed the onboarding problem as identity verification rather than form length, cutting drop-off by 31%. Portfolio at [link].
Certifications worth listing
Put these in their own section with the awarding body and, where one applies, the expiry date.
- Nielsen Norman Group UX Certification
- Google UX Design Professional Certificate
- IAAP Certified Professional in Accessibility Core Competencies (CPACC)
Questions
What should a ux designer put on a resume?
Lead with a summary that names your years of experience and your single strongest result. Then work experience with one measurable achievement per bullet, followed by skills using the exact terms from the job advert. For this role, employers screen most often for: user experience, ux design, user research, wireframes, prototyping.
What should a UX resume say that the portfolio does not?
Product context, user scale, your exact role in team projects, and constraints. Case studies show polished outcomes; the resume establishes whether you led the research, shipped against a deadline, or worked within someone else’s design system.
How do I show research changed something?
Name the finding and the decision it overturned. "Five usability sessions killed an onboarding flow already built" proves influence in one line. Listing methods you know reads as coursework — what matters is research that altered what shipped.