Every other profession's CV has to carry the whole argument on its own. A UX designer's does not — it arrives attached to a portfolio, and the portfolio will do most of the persuading. That changes the CV's job in a way most UX resume advice misses entirely.
The CV is not a compressed portfolio. It is the document that decides whether the portfolio gets opened, and then the document a hiring manager returns to for the things a portfolio is bad at showing.
What the CV is actually for
Portfolios are excellent at demonstrating craft and process on two or three projects. They are poor at communicating three things a hiring manager needs to know:
- Scope and level. Did you own a product area or execute assigned screens? Were you the only designer or one of twelve? A beautiful case study rarely makes this clear.
- Context and constraint. Agency or in-house. B2B or consumer. Regulated or not. Startup ambiguity or enterprise process. These change what your experience is worth for a given role.
- Breadth over time. The portfolio shows three projects. The CV shows the shape of a career.
Write the CV to answer those, and let the portfolio do craft.
The summary line does real work here
UX is a wide title covering research-heavy roles, interaction and systems work, visual and brand-adjacent design, and product design that is nearly product management. Hiring managers screen for fit within that range, and a summary that says "passionate about user-centred design" tells them nothing.
State the specialism, the level, and the domain in one sentence. "Product designer, seven years, B2B SaaS — mostly complex data workflows for enterprise operations teams, with a design systems background" is immediately placeable. Someone hiring for a consumer mobile role will pass, correctly, and someone hiring for enterprise tooling will open the portfolio.
Being filtered out fast by roles that were never a fit is a feature.
Outcomes, when you can get them
Designers face a genuine measurement problem that engineers largely do not. You rarely own the metric, the metric often moves for reasons beyond the design, and in enterprise or early-stage contexts it may not be instrumented at all.
The honest hierarchy, best to worst:
- A business or product metric you can defend. "Redesigned the onboarding flow; activation rose from 34% to 51% over the following quarter." Only use this if you can explain the measurement and what else was changing at the time — you will be asked.
- A usability or research metric. Task completion, time on task, error rate, support ticket volume for a specific flow. Often more directly attributable to your work than a revenue number, and more defensible.
- Scale and adoption. "Design system adopted by four product teams, covering roughly 80% of the app surface." Real, checkable, and it demonstrates influence rather than output.
- Decision and outcome, stated qualitatively. "Research with twelve operations users showed the proposed dashboard solved a problem nobody had; the team redirected the quarter to queue management instead." No number, genuinely impressive, and it demonstrates the thing senior designers are actually hired for.
The fourth is far better than an invented version of the first. Fabricated design metrics collapse under one follow-up question.
What hiring managers screen out on
- "We" throughout. The most common fault in design CVs and portfolios both. Collaborative work is the norm and nobody expects you to claim the whole thing, but a document where every sentence is "we" hides what you personally did. Say what you owned.
- Tool lists as a proxy for skill. Figma is assumed. Listing it alongside eleven other tools with proficiency bars consumes space and communicates nothing. Name tools once, briefly, and spend the space on what you did with them.
- Process described as a deliverable. "Conducted user research, created personas, built wireframes, delivered high-fidelity mockups" is a list of artefacts. It does not say what you learned or what changed as a result. Artefacts are means.
- Unsolicited redesigns as the lead experience. Fine as a portfolio piece early on. On the CV, real constrained work outranks a self-directed redesign of a famous app every time.
- No portfolio link, or a broken one. Trivially avoidable and it happens constantly. Put the link in the header, check it, and if it is password-protected put the password next to it.
What has changed recently
Two shifts are worth reflecting on the CV if they are genuinely true of you.
The first is AI-adjacent design work. Designing for non-deterministic systems — confidence states, error recovery, trust, streaming responses — is a specialism most designers have not practised, and it is being actively hired for. If you have shipped it, name it specifically rather than adding "AI" to a skills list.
The second is designers who build. Fluency with modern prototyping and code-adjacent tooling, enough to ship working prototypes rather than mockups, compresses team iteration loops. Where it is real, it belongs on the CV.
Both are genuine differentiators and both are easy to overclaim, which means both get probed in interviews.
Format and parsing
Design CVs suffer more parsing damage than any other profession's, for the obvious reason: designers design them. Multi-column layouts, contact details in a styled header, skill rating bars, and portfolio links embedded in an image are all common and all break extraction.
Your CV is a work sample, so it should look considered — but a well-set single-column document with clear typography, generous spacing and one accent colour looks better than most two-column CVs anyway, and it parses. Keep the visual ambition in the portfolio, where it belongs and where it is actually assessed.
Paste your PDF into a plain text editor to check the reading order, or run it through the free ATS checker. For role-specific interview preparation, see our UX designer interview guide.