A UX designer resume has one job: get a hiring manager to open your portfolio. That is the real screen — the resume is the trailer, the portfolio is the film. So the resume needs to do two things well. First, it has to carry a working portfolio link at the top, because a UX resume without one is dead on arrival. Second, its bullets have to read like outcomes, not deliverables: not 'designed wireframes and prototypes,' but 'redesigned checkout, lifting task success from 61% to 88% and cutting support tickets 30%.' Recruiters skim for that signal in seconds, and an applicant tracking system scans the same page for the tools and methods named in the posting. One page for under ten years, single column, no graphics — yes, even for a designer.
The resume is the trailer; the portfolio is the film
Hiring for design works differently from most fields. The portfolio decides almost everything, and the resume's entire purpose is to earn the click that opens it. That reframes what a good UX resume is: not a self-contained pitch, but a fast, credible argument that your case studies are worth ten minutes. Two failures kill that argument before it starts — no portfolio link, and bullets that list deliverables instead of results.
So put the link where it cannot be missed: top of the page, next to your name, on a clean URL. Then make every line below it answer the only question a design hiring manager cares about — when you touched this product, what got better, and how do you know?
Rewrite your bullets around outcomes
Designers default to describing artifacts — wireframes, prototypes, flows, mockups. Those are inputs. The reviewer is scanning for evidence that your design work moved a number a user or the business cares about. Same project, same person; only the framing changes, and the second version is the one that gets the portfolio opened.
Designed wireframes and high-fidelity prototypes for the checkout flow.
Redesigned the three-step checkout in Figma after usability testing exposed a confusing address step, lifting task success from 61% to 88% and reducing checkout support tickets by 30%.
Names the method, the problem found, and two outcomes — one usability, one business.
Conducted user research and created personas for a new mobile app.
Ran 14 moderated interviews and 2 unmoderated tests that reframed the core flow around a habit users actually had, cutting onboarding drop-off from 47% to 29% at first launch.
Research that changed a decision and moved a funnel metric — not research as a deliverable.
Built and maintained the design system in Figma.
Built a 40-component Figma design system with tokens and usage docs, cutting average design-to-handoff time by ~40% and eliminating the spec-drift that had caused repeated visual-QA reopens.
Quantifies the leverage of the system and the pain it removed for the team.
Worked with product and engineering to ship new features.
Partnered with PM and 4 engineers to ship a redesigned dashboard, raising weekly active use of the feature 22% and lifting its task-level SUS score from 68 to 81.
Shows cross-functional shipping plus a satisfaction metric, not vague collaboration.
Send the right tool and method signal
Design hiring is tool- and method-sensitive. A role built around Figma and a mature design system wants to see Figma and design systems — not "proficient in modern design tools." Two rules:
- Keep a plain-text skills line near the top, grouped lightly. Design & Prototyping (Figma, FigJam); Research (usability testing, interviews, surveys, card sorting); Systems (design tokens, component libraries, accessibility/WCAG). Use the exact spellings the posting uses, since that is what the ATS matches.
- Prove the method inside your bullets. "Figma" in a list is a claim; "ran a card sort that restructured the navigation" or "built the token system in Figma" is evidence. List broadly, but make sure the methods that matter for the role show up in your actual accomplishments.
Resist dumping every tool you have ever opened. A skills block with twenty programs reads as filler and invites questions you cannot answer in a critique. List what you can defend.
Frame scope to the level you are targeting
What a reviewer weights shifts as you climb. Junior resumes prove you can execute clean interaction and visual work end to end on a feature. Senior resumes prove ownership — driving research, making tradeoffs, and shipping work with measurable reach across a product area. Staff and lead resumes prove influence beyond your own screens: design systems adopted across teams, research practices you established, or product direction you shaped. A resume that tries to read as senior-but-also-fine-with-junior lands as neither, so pick one rung and frame your scope to match it.
The honest summary
A strong UX designer resume is single column, parseable, and built to get your portfolio opened. Put a working portfolio link at the top, lead every bullet with an outcome metric rather than a deliverable, name your real tools and methods in the recruiter's vocabulary, and frame your scope to the level you are targeting. For demand and salary context, the BLS Occupational Outlook for web developers and digital designers is a solid baseline, and the Nielsen Norman Group's articles are the reference for the research methods you will be cite-checking your bullets against. Do this well on a handful of well-matched roles and the resume stops being a filter and starts being the thing that gets your work seen.
Common questions
- Should a UX designer resume be visually designed?
- No. This is the trap most designers fall into. The resume is a parsing document, not a portfolio piece — your visual skill belongs in the portfolio, which is where it actually gets judged. A two-column layout with icons and a skills sidebar reads worse to an ATS and signals you confused the artifact with the work. Single column, plain text, generous whitespace. Save the craft for the case studies.
- Do I really need a portfolio link on the resume?
- Yes — at the top, next to your name and email, and it must work. A UX resume without a portfolio link gets discarded faster than any bullet can save it, because no one hires a designer sight unseen. Make it a clean URL on your own domain or a polished portfolio host, and confirm it loads, is not password-walled by default, and shows three to five case studies before any decoration.
- What metrics can I use if my work was never measured?
- Use the ones you can defend honestly. Task success rate, time on task, error rate, and SUS or NPS scores come straight from usability testing you can run or cite. Business metrics — conversion, activation, support-ticket volume, retention — usually exist somewhere even if you did not own the dashboard. Ask your PM or analytics partner. A defensible range ("cut drop-off by roughly a third") beats no number, and you will be asked about it.
- How do I show UX versus UI versus product design on a resume?
- Mirror the title in the posting. If the role says "Product Designer," frame your scope end to end — research, interaction, visual, and shipping with engineering. If it says "UX Designer," lead with research and interaction; if "UI Designer," lead with visual systems and design-system work. The underlying experience can be the same; what changes is which parts you foreground for that specific role.
Sources
Keep reading
What does an ATS-friendly resume look like?
An ATS-friendly resume is single-column and plain-text, with standard headings, readable dates, and no tables or graphics. Here is the exact anatomy.
How long should a resume be?
Most resumes should be one page; two pages once you have ~10+ years of relevant experience. The real rule: every line has to earn its place.
Why is my resume getting rejected by ATS?
ATS rejection has two causes: parse failures from bad formatting and keyword gaps against the job description. Here is how to diagnose and fix yours.
Software engineer resume tips
A strong software engineer resume leads with measurable impact, names the exact stack, fits one page, and parses cleanly through any ATS. Here is how.