A UX designer resume should show outcomes and process, not just screens. Pair a strong portfolio with bullets that prove your research and design decisions moved a usability or business metric — task success, conversion, retention.
Hiring managers look for end-to-end product thinking: research, interaction design, prototyping, testing, and iteration — and evidence the work shipped and improved something. The strongest resumes link a case-study portfolio and quantify impact (higher task-completion, lower drop-off, improved SUS or conversion). Collaboration with PM and engineering and fluency in Figma plus a research method or two round it out.
UX resumes split into two kinds: ones that describe deliverables ("created wireframes and prototypes") and ones that describe outcomes ("redesigned checkout, cutting drop-off 19%"). Hiring managers strongly prefer the second, because deliverables are assumed and outcomes prove your design judgment was right. The portfolio should show the process; the resume should lead with what changed because of your work.
“UX designer with 5 years on B2C and SaaS products. Redesigned a checkout flow that cut drop-off 19% and led the research behind a navigation overhaul that lifted task-success from 72% to 91%. Figma-native, comfortable running my own usability studies.”
The single fastest way to lift a ux designer resume is rewriting weak, duty-based bullets into specific, quantified outcomes. Three worked examples:
Created wireframes and prototypes for the product.
Redesigned the checkout flow through 3 rounds of usability testing, cutting drop-off 19% and adding an estimated $220K in annual recovered revenue.
Why it works: Lead with the outcome; wireframes are assumed.
Conducted user research for the team.
Ran 18 user interviews and 2 unmoderated studies that reframed a navigation redesign, lifting task-success from 72% to 91%.
Why it works: Quantify the research and the usability metric it moved.
Worked on the design system.
Built and documented a Figma component library adopted by 3 squads, cutting design-to-dev handoff time roughly 40% and improving UI consistency.
Mirror the terms a job description actually uses. Include the ones below that match the posting:
Outcomes on the resume, process in the portfolio. Deliverables like wireframes and prototypes are assumed; what differentiates you is the usability or business metric your design moved. Lead each bullet with the result and let the portfolio show how you got there.
Match the posting. UX-leaning roles want research, information architecture, and testing with outcome metrics; UI-leaning roles want visual craft, design systems, and a polished portfolio. Many roles blend both, so lead with whichever the job description weights and show range in your case studies.
Start from a clean, ATS-friendly template and apply these examples to your own experience. No sign-up to try the editor.
Open the resume editor