UX Designer CV Example

Why a UX designer CV is read differently

Design hiring has its own priorities, and they explain every choice below. A design lead or UX recruiter skims fast for evidence you solve user problems with a real process, not a gallery of pretty screens:

• Process beats polish: a beautiful screen proves nothing on its own, but a screen you can explain — the research that shaped it, the trade-off you made, the metric it moved — is exactly the signal a hiring manager screens for first
• The portfolio is the real CV: your document exists to earn a click, so a clear, working portfolio link is non-negotiable and carries more weight than any adjective on the page
• Outcomes matter as much as craft: 'redesigned checkout' says little, but 'redesigned checkout and lifted completion 14%' proves you design for the business, not just the aesthetic
• Research signals seniority: any evidence you talked to users, ran usability tests, and let findings change your design separates a real UX designer from a visual designer with a UX title
• Collaboration is the daily job: your bullets should show you worked with product, engineering, and research to ship — not that you handed off a pretty Figma file and walked away

Read your CV the way a design lead will: not 'does this look nice?' but 'can I trust this person to own a problem, research it, design a solution, and ship something that works?' Every section below answers that with evidence — and points to a portfolio that proves it.

The structure that works for a UX CV

Keep it to a clean one to two pages and make the portfolio link impossible to miss. For most UX designer applications this order works best:

Design hiring rewards clarity, so keep the CV itself plain and let the portfolio carry the visual weight — a heavily 'designed' CV that mangles in an ATS helps no one. Lead with real shipped product work if you have it; if you're breaking in, move projects, a bootcamp capstone, and self-initiated redesigns up the page.

The summary: domain, process, and one headline outcome

Three or four lines under your name — the most-read part of the CV, and the nudge toward your portfolio. For a UX designer it should answer: what you've designed, how you work, and one outcome worth leading with:

• Open with domain and level: 'Product designer with 5 years designing B2B SaaS interfaces, owning end-to-end UX from research to shipped design'
• Name the domains you genuinely worked in: fintech, health, e-commerce, or enterprise tooling — pick what your portfolio backs up, not a list of every industry
• Lead with one hard outcome: 'redesigned onboarding and raised task-completion from 61% to 84%' says more than 'user-centred, detail-oriented designer' ever could
• Signal your process: mention research, usability testing, or design systems so a reader sees a designer who validates, not one who only pushes pixels
• Cut the empty filler: 'passionate, pixel-perfect team player' says nothing — replace it with a domain, a process, and a usability or conversion number that proves it

A strong UX summary reads like someone a design lead could hand a messy problem to tomorrow. If yours could describe any designer, add the specific detail — a domain, a process, a task-success or conversion number — that makes it unmistakably yours and makes the reader want to open your portfolio.

The skills section: research, design, and tools

Group your skills so a hiring manager scans them in seconds, and only list what your portfolio can back up. For a UX designer they fall into clear buckets:

Be honest about your level — if you list usability testing or a design system, expect the portfolio review to probe it. A short, accurate, process-focused skills list beats a long generic one, because a design lead can immediately picture the kind of problem you'd own.

The portfolio and case studies: what a design lead opens first

For a UX role the portfolio isn't a supporting document — it's the main event, and the CV exists to get it opened. A design lead judges you almost entirely on how you present your thinking in two or three deep case studies:

• Show the whole arc: problem, research, the decisions you made and why, what you shipped, and the result — a case study that jumps straight to final screens reads as decoration, not design
• Go deep, not wide: two or three thorough case studies beat ten thumbnail galleries, because depth is where a lead sees how you actually think and handle trade-offs
• Make your own contribution clear: on team projects, say exactly what you did — 'led the research and interaction design; a colleague owned the visual system' — vague 'we' hides your real skill
• Include the messy middle: an early wireframe you rejected, a usability finding that changed your direction, or an idea you killed shows judgement far better than a clean highlight reel
• End each case study with impact: the metric that moved, the problem you removed, or what the team learned — so the reader leaves seeing outcomes, not just artefacts

Treat your CV and portfolio as one system: every strong line on the CV should have a case study behind it that tells the full story. If a bullet claims a redesign lifted conversion, the case study should show the research, the design, and the number — that consistency is what turns a portfolio click into an interview.

Experience bullets: tie every design decision to an outcome

The strongest UX bullets tie a design decision to a usability or business outcome. Compare a vague line with one that gives a hiring manager real evidence:

• Weak: 'Designed screens and created wireframes in Figma for the mobile app' — no problem, no research, no outcome, and nothing that separates you from any other designer
• Strong: 'Redesigned the checkout flow after usability tests revealed a drop-off at address entry, lifting completion from 68% to 82% and cutting support tickets about payment by 24%'
• Strong: 'Ran 12 moderated usability sessions on the dashboard, then reworked the information architecture and raised task-success on the core report from 55% to 88%'
• Strong: 'Built and documented a component library adopted by three squads, cutting design-to-dev handoff time and keeping the product visually consistent across 40+ screens'
• Pattern to apply: action verb + the problem or research + the design decision + the outcome (task success, drop-off, conversion, tickets, consistency)

The numbers don't need to be huge — they need to be real and tied to a design decision. 'Improved sign-up completion 9% by simplifying the form to four fields' is a strong bullet, because it proves exactly what a design lead wants: a decision, grounded in research, that moved a metric that matters.

Breaking into UX from graphic design, front-end, or research

Most UX designers arrive from an adjacent field, and hiring managers know it — they hire junior and crossover designers on process, a strong portfolio, and evidence you think from the user in. An empty UX title is not a problem if you fill the page and portfolio with the right proof:

• Reframe adjacent experience in UX terms: a graphic designer who ran client research, a front-end dev who shaped interactions, or a researcher who influenced design is doing UX-adjacent work — describe it that way
• Lead with self-initiated projects: a redesign of a product you use daily, complete with research and testing, proves process far better than any 'aspiring UX designer' summary line
• Show a bootcamp capstone with substance: if you retrained, present the capstone as a full case study — problem, research, iterations, outcome — not just the final screens
• Target the on-ramps: junior UX, product design internships, and UX-research assistant roles exist for switchers, so tailor the CV and portfolio to how they screen
• Lead with process, not apologies: never open with the experience you lack — open with a real problem you researched, the design decision you made, and what it improved

A career-change UX CV wins on process and a portfolio that proves it, not years with the title. Fill the page with reframed wins and one or two deep, self-initiated case studies, and you'll stand out from switchers who send a generic CV and a thumbnail gallery that hides how they actually think.

ATS, keywords, and the recruiter screen

UX roles at larger companies usually run applications through software and a fast recruiter screen before a design lead sees them, so keep the CV itself clean and matched to the spec — and never rely on a heavily designed PDF to carry your keywords:

• Mirror the job spec's language: if it says 'user research', 'design systems', 'prototyping', or 'usability testing', use those exact phrases where they're true for you
• Include the tool and method keywords: Figma, user research, usability testing, WCAG, information architecture, and prototyping help both the parser and the recruiter place you fast
• Use a clear role title: putting 'UX Designer' or 'Product Designer' as your headline helps the software and the skim-reading recruiter category you correctly
• Keep the CV parser-safe: put your creativity in the portfolio, not in a multi-column CV with graphics and text-in-images that an ATS silently drops
• Make the portfolio link machine- and human-readable: a plain, clickable URL beats a QR code or a link buried in an image the parser can't see

The test is simple: could someone read your CV top to bottom in a plain text editor and still see your process, your tools, and your portfolio link? If yes, the parser can too. Keep the CV clean and let the portfolio be where your design skill shows.

Common mistakes on a UX CV

Most UX CVs are rejected for fixable reasons rather than a lack of talent. Avoid these and you immediately stand out:

• No portfolio link, or a broken one: nothing sinks a UX application faster — test the link, and lead it toward deep case studies, not a thumbnail wall
• All craft, no process: a CV and portfolio full of final screens with no research or reasoning reads as visual design, not UX — show how you got there
• No metrics anywhere: a UX CV with zero outcomes reads as someone who designs in a vacuum, so attach a real usability or business figure to your strongest bullets
• Hiding your contribution: on team projects, unclear 'we' language makes a lead assume you did the least — say exactly what you owned
• One generic CV and portfolio for every role: a UX researcher, a product designer, and a design-systems specialist are different jobs — tailor the summary, skills, and featured case studies to the role

Run the design-lead test: in 30 seconds and one portfolio click, can they see process, real research, a design decision, and an outcome you moved? If yes, you're ahead of most of the stack. The fixes are nearly always the same — add a working portfolio link, show process, attach numbers, and tailor to the role.