UX Designer Resume Template & Examples (2026)

Entry-level / Junior UX Designer

Early-career UX designer with three end-to-end case studies showing the full process — research through tested prototype — including one shipped project with real usage data. Strong Figma craft; hungry for research reps.

• Redesigned a nonprofit’s volunteer signup against 8 usability sessions, cutting drop-off 40% after launch — full case study from research plan to shipped metrics.
• Completed 3 end-to-end case studies (research, flows, tested prototypes, iteration rationale) documented at [portfolio URL].
• Ran 15 moderated tests across projects, personally recruiting participants and synthesizing findings into prioritized changes.

Why this works: One shipped project with a real post-launch number beats three fictional app concepts. Junior portfolios fail on process gaps, not craft gaps — show the research and the iteration, including what tested badly.

Senior UX / Product Designer

Senior product designer owning outcomes across a product area: discovery through shipped metrics, design-system governance, and the research practice that keeps a roadmap honest. Comfortable presenting to executives and pairing with engineers.

• Owned UX for the payments area (3 squads): shipped work moved activation 12 points and cut support contacts 35% year over year.
• Governed the design system through 2 major product rebrands with zero squad-blocking migrations, chairing the weekly systems council.
• Built the continuous-discovery practice (weekly touchpoints, insight repository) that PMs now staff roadmap reviews from.

Why this works: Senior design postings buy outcomes and organizational leverage: metrics owned, systems governed, practices installed. Craft is assumed; judgment and influence are the screen.

Graphic / Visual Designer transitioning to UX

Visual designer (5 years, brand and marketing) moving into UX: already redesigned two client web products with measured conversion wins, now with formal research training and a documented end-to-end case study. Visual craft most UX-first peers lack.

• Redesigned a client’s e-commerce checkout (research-informed, 6 usability sessions), lifting conversion 18% — the project that reframed my practice around evidence.
• Completed NN/g UX certification and applied it: one full case study from discovery interviews to a tested, iterated prototype.

Why this works: The transition evidence is process, not pixels: show research you ran and decisions it changed. Your visual strength stays on display in the artifacts themselves — spend the words proving the evidence habit.

Read the title dialect: UX, product designer, or UX/UI

Titles encode expectations. "Product designer" postings (most product companies) want end-to-end ownership: discovery, flows, visuals, shipped metrics. "UX designer" at enterprises often sits beside separate research and UI functions — process depth matters more. "UX/UI" postings (agencies, smaller companies) want strong visual execution with usable process. Mirror the posting’s own title in your summary line — keyword matching is literal, and "product designer" does not match "UX designer" in an ATS.

Then re-weight the same source CV: research bullets lead for UX-titled roles, outcome-owned bullets for product-designer roles, craft-plus-speed evidence for UX/UI. This per-posting re-emphasis is exactly what snipecv automates.

Pair the resume with the portfolio — each has a different job

UX is a two-document hire: the resume gets you past ATS and the recruiter scan; the portfolio wins the design review. The resume carries keywords, metrics, and scope ("owned UX for 3 squads"); the portfolio carries process and craft. Do not make the resume do portfolio work — a resume full of process narrative and thin on outcomes fails the 7-second scan that decides whether anyone opens the portfolio at all.

Link the portfolio in the header, and make sure the case studies it leads with match the roles you are targeting — a resume tailored to fintech pointing at three e-commerce case studies wastes the tailoring.

Attach a product metric to every design story you can

Design hiring has swung hard toward outcome evidence: completion rates, conversion, adoption, support-contact reduction, task success. "Lifted onboarding completion from 47% to 74%" is legible to the recruiter, the PM, and the design director alike — and rare enough on design resumes to differentiate immediately. Get the numbers from your PM or analytics partner before you leave a project; they are much harder to recover later.

When the metric was a team outcome, claim your part honestly ("design lead on the redesign that lifted..."). And when a project shipped without measurement, say what you validated instead — prototype test results are metrics too ("killed the tab concept after 2 rounds tested below benchmark").

Show research as decisions changed, not methods listed

A methods list ("usability testing, interviews, card sorting") is the design equivalent of a tool wall — every resume has it. The differentiating evidence is research that changed something: the diary study that found what two redesigns missed, the prototype test that killed a concept before a sprint was spent, the field study that re-sequenced a roadmap. State the method, the sample, and the decision it drove.

Volume adds credibility at the practice level: "60+ moderated sessions run" tells a hiring manager you personally do the work. But volume without a changed-decision story reads as process theater — always anchor to consequence.

Make accessibility and system fluency concrete

Two competencies now separate shortlists. Accessibility: state the standard and the movement — "60 audit violations to zero, WCAG 2.1 AA" — not "passionate about inclusive design". Regulated industries and enterprise buyers audit now, and hiring managers need someone who has done the remediation work, including the engineering partnership it requires (focus management, contrast tokens).

Design systems: contribution or governance, with adoption numbers — "120 components, 4 squads, handoff time cut 50%". Systems work signals you design for leverage and for engineers, and pairing it with even basic HTML/CSS literacy ("developer handoff fluency") answers the collaboration question every panel quietly asks.

Entry-level

• Redesigned [flow] against N usability sessions, cutting drop-off N% after launch — full case study at [URL].
• Completed N end-to-end case studies (research plan, flows, tested prototype, iteration rationale).
• Ran N moderated tests, recruiting participants and synthesizing findings into prioritized changes.

Mid-level

• Lifted [product metric] from N% to N% by redesigning [flow] from N moderated sessions.
• Built the design system (N components, tokens synced to code) adopted by N squads, cutting handoff time N%.
• Cut support contacts N% via a [method] study that surfaced [the insight previous redesigns missed].
• Brought [product] from N audit violations to zero (WCAG 2.1 AA), partnering with engineering on remediation.

Senior

• Owned UX for [product area] (N squads): shipped work moved [metric] N points year over year.
• Governed the design system through N rebrands/migrations with zero squad-blocking breaks.
• Built the continuous-discovery practice (cadence, insight repository) that roadmap reviews now staff from.

Does my UX resume matter if my portfolio is strong?

Yes — the portfolio never gets opened if the resume fails the screen. ATS parsing and the recruiter’s first pass run on the resume alone: matching title, tool keywords, outcome numbers, scope statements. Treat the resume as the distribution layer for the portfolio: it must earn the click in 7 seconds. The most common failure is a beautifully designed resume PDF that parses badly — multi-column layouts and text-in-graphics break ATS extraction, so keep the resume file boringly parseable and spend the craft budget on the portfolio.

Should I use "UX designer" or "product designer" on my resume?

Mirror each posting — the titles are dialects, not different careers, and ATS matching is literal. Your summary line ("Product designer with 6 years...") is among the heaviest-weighted text an ATS reads, so switching it per application measurably changes match scores. Keep your actual past job titles truthful; the summary and skills framing are where the dialect adjustment happens.

What metrics can a designer honestly claim, since outcomes are team results?

Claim the metric with your role stated: "design lead on the redesign that lifted onboarding completion 27 points" is honest and strong. Metrics you can own more directly: usability-test task-success improvements between iterations, audit-violation counts you drove to zero, handoff-time and consistency gains from systems you built, and prototype-test results that changed decisions. What reads false is a lone designer claiming revenue numbers with no mechanism — always keep the causal chain visible.

How do I write a UX resume with agency experience only?

Convert project variety into range evidence and pick your 2-3 deepest engagements for full bullets — "20+ client products" is context, but the hospital portal with the 28% abandonment cut is the story. Product companies worry agency designers ship and leave; counter it with any evidence of post-launch measurement, renewals won by your work, or an engagement where you iterated after real usage data. Research you personally ran matters double, since agencies often skip it.

Is AI-tool fluency worth listing on a design resume in 2026?

Briefly, with an outcome, in the skills block — not as a headline. Design hiring assumes AI-assisted production now; what it screens for is the judgment layer tooling does not supply: research instinct, taste, systems thinking, and the ability to tell when generated output is wrong. One honest line ("AI-assisted prototyping integrated into discovery cadence") suffices. A resume that leads with AI tools reads as junior regardless of years.

How long should a UX designer resume be?

One page for most of a career; two only when senior scope genuinely needs it. Design hiring managers are the most layout-sensitive readers you will face — density, hierarchy, and restraint on your own resume are read as craft evidence. Summary with title dialect, best outcome number, and portfolio link; 3-5 outcome bullets for the current role; older projects compressed hard. If it needs 9pt type to fit one page, it needs editing, not smaller type.