UX Designer CV Guide: What Recruiters Actually Look For in 2026

If you have ever wondered why your UX portfolio gets compliments but your CV gets silence, you are not alone. UX design sits at an unusual intersection: you need to prove a creative, visual skillset inside a document that is, by nature, mostly text. The recruiter reading your CV probably cannot evaluate your Figma skills directly — they are scanning for the right keywords, the right framing, and evidence that you think like a product person, not just a visual artist.

That tension shapes everything about how a strong UX CV is written. This guide will walk you through exactly what hiring managers look for, how to frame your experience, and the specific mistakes that quietly kill applications every day.

What Recruiters Scan For

UX roles attract enormous volumes of applicants. A senior recruiter at a mid-size tech company might receive 200 applications for a single IC position. Here is what they are actually doing in the first 10 seconds:

1. A portfolio link above the fold. This is non-negotiable. If your portfolio URL is buried in the footer or missing entirely, many recruiters will not scroll further. It belongs directly under your name and contact details, formatted cleanly and prominently.

2. Evidence of process, not just output. Hiring managers want to see that you use a structured design process — research, ideation, prototyping, testing, iteration. "Designed mobile onboarding flow" tells them nothing. "Led end-to-end redesign of onboarding flow, reducing drop-off by 34% based on usability testing with 12 participants" tells them everything.

3. Cross-functional collaboration language. Modern UX does not happen in isolation. Phrases like "partnered with engineering," "facilitated stakeholder workshops," and "aligned design decisions with product roadmap" signal that you understand how design fits inside an organisation.

4. Tool fluency without being a spec sheet. Figma, Miro, Maze, Hotjar, Amplitude — these should appear in context, not as a bulleted list of every tool you have ever touched. Mentioning Figma auto-layout in the context of a design system project is more convincing than listing it under "Skills."

5. Domain familiarity. B2C, B2B SaaS, fintech, health tech, e-commerce — these are distinct design contexts. If the role is for a fintech product, recruiters will look for any experience working within regulated, data-heavy, or trust-sensitive interfaces.

Key Skills to Highlight

Technical skills worth naming explicitly:

• Figma (especially components, variables, and auto-layout — these signal production-quality work)
• Prototyping tools: ProtoPie, Principle, or Framer for complex interactions
• Research methods: moderated usability testing, card sorting, tree testing, diary studies
• Accessibility: WCAG 2.1/2.2 AA compliance, inclusive design principles
• Design systems: creation, documentation, adoption metrics
• Analytics: Hotjar, FullStory, Amplitude, Mixpanel — any tool that connects design to behaviour

Soft skills that actually land (when evidenced, not just claimed):

• Stakeholder facilitation — run the workshops, own the alignment meetings
• Async communication — especially relevant for distributed teams
• Prioritisation frameworks — MoSCoW, RICE, effort-impact matrices

Never write "strong communicator" or "detail-oriented" without a sentence immediately after that proves it. Claims without evidence are filler.

Strong vs Weak Bullets

This is where most CVs lose the plot. Weak bullets describe tasks. Strong bullets describe outcomes and demonstrate thinking.

Weak: Redesigned the checkout flow for a retail client. Strong: Redesigned a 6-step checkout flow into a 3-step progressive disclosure pattern, validated through A/B testing with 8,000 users — conversion rate increased by 18% and cart abandonment dropped by 12%.

Weak: Conducted user research for a new mobile app. Strong: Led generative research with 20 target users across three countries to identify pain points in expense tracking; synthesised findings into a jobs-to-be-done framework that directly shaped the MVP feature set for a Series A fintech startup.

Weak: Worked with developers to implement design. Strong: Embedded with a cross-functional squad of 4 engineers and 1 PM during a 3-month design system migration; authored component documentation in Storybook and reduced design-to-dev handoff time by an estimated 30%.

The formula is not complicated: action verb + specific context + measurable result. If you do not have a percentage, use a concrete number — users interviewed, components documented, sessions facilitated, screens delivered. Numbers that feel small still beat vague language.

Common Mistakes That Cost You Interviews

1. Treating the CV as a portfolio substitute. Your CV and portfolio are different documents doing different jobs. The CV signals keywords and credibility to get you past the first filter; the portfolio does the heavy lifting in the interview. Do not try to describe your design process in exhaustive detail on the CV — save depth for the portfolio case studies and link to them clearly.

2. Listing responsibilities instead of contributions. "Responsible for UX research" is a job description, not an achievement. Ask yourself: what was different because you were there? What decision changed because of your research? What shipped because of a prototype you built?

3. Burying the portfolio link or making it click-unfriendly. If you are applying through LinkedIn or an ATS, make sure your portfolio URL is a plain-text clickable link, not just a brand name. "www.janedoe.design" is fine; "portfolio (available on request)" is not.

4. Skipping the summary. A two-to-three sentence professional summary at the top — specific, achievement-forward, not generic — significantly increases read time. "UX Designer with 5+ years building B2C products in fintech, specialising in high-stakes transactional flows" is immediately useful to a recruiter.

How to Tailor Your CV for Each Application

The job description is your cheat sheet. Copy the language the hiring team used. If they say "user journeys," use "user journeys" — not "user flows" or "experience mapping." Applicant tracking systems often do literal keyword matching, and even human reviewers subconsciously favour language that mirrors their own.

Identify the top three responsibilities in the posting and check that each has a direct, evidence-backed counterpart in your CV. If the role emphasises accessibility but your CV has no WCAG mention, add it — if you have done the work, name it explicitly.

This is exactly where NextCV removes friction. Paste the job description, and the AI reshapes your existing profile to surface the experience most relevant to that role, mirror the language the employer uses, and prioritise the right achievements. For UX roles across different verticals — agency vs. in-house, startup vs. enterprise — the tailoring makes a measurable difference in response rates.

Closing Thoughts

A UX designer CV is ultimately a design problem. Your audience (the recruiter) has limited time, defined goals, and specific information needs. Apply the same user-centred thinking to the document that you bring to your products: reduce cognitive load, surface the most important information first, and make the next step (clicking your portfolio) effortless.

Get that right, and the portfolio can do the rest.