The UX hiring paradox
UX designers are hired for their portfolio. Hiring managers, design leads, and PMs who interview you are evaluating your case studies, your process artifacts, your thinking about tradeoffs. The resume is almost secondary to the work.
Except: your resume has to exist before anyone sees the portfolio. At companies of any scale, resumes go through an ATS before a human ever sees them. And even when a recruiter opens your resume, they're making a 15-second decision about whether to click your portfolio link — based entirely on what the resume says.
The real job of a UX resume: Pass the ATS filter, give the recruiter enough signal to believe you're worth clicking into, and make sure the portfolio link is impossible to miss. The resume doesn't need to tell your whole story — the portfolio does that. The resume just needs to get you to the portfolio stage.
What UX hiring managers actually screen for
Before a design lead or hiring manager sees your portfolio, a recruiter typically does an initial screen. Here's what that recruiter is checking for on your resume:
UX title history
Titles matter more in design than people expect. 'UX Designer,' 'Product Designer,' 'UX Researcher,' 'Interaction Designer,' 'UI Designer' — these aren't interchangeable to recruiters at larger companies. If your title was 'Web Designer' but you did UX work, your bullets need to make that explicit.
Tool fluency
Figma is now the standard. If your resume doesn't mention Figma, recruiters at modern product companies will notice. Secondary tools depend on the role: prototyping (ProtoPie, Framer), research (Maze, UserTesting), handoff (Zeplin, Storybook), systems (design tokens, Figma variables).
Cross-functional evidence
UX designers who can describe collaboration with engineering and product — not just design deliverables — read as more embedded in the product development process. Bullets that mention engineers, PMs, or stakeholders by function signal someone who operates as a partner, not a service provider.
Portfolio link
The most basic thing. Recruiters see resumes without portfolio links from UX designers constantly. If you don't have a public link, you're filtering yourself out.
Company / product context
Working on consumer products, enterprise SaaS, fintech, or healthcare each requires different UX knowledge. Your bullets should establish what kind of product you designed for — scale, domain, user type.
Before and after: how UX resume bullets actually differ
Most UX resume bullets describe deliverables. Strong UX bullets describe the problem you were solving, the decisions you made, and what changed as a result.
Product Designer (Mid-Level)
Before
After
Why it works: The 'before' describes a deliverable. The 'after' gives context (why it was redesigned), explains the design decision (what changed and why), and connects it to a measurable outcome.
UX Researcher
Before
After
Why it works: Research bullets need to show the method, the scale, and — critically — what happened with the findings. Research that doesn't change anything doesn't demonstrate impact. Research that shifted a roadmap decision does.
UX Designer (Career Changer from Engineering)
Before
After
Why it works: Career changers need to show the UX process explicitly — not assume the reader understands that they used it. Naming the artifacts (journey map, prototype, usability test) proves the methodology.
Senior Product Designer / Design Lead
Before
After
Why it works: Senior designers need to show scale (team size, product scope, client count) and influence (design system adoption, systems thinking) — not just individual craft. The 'before' could describe any designer anywhere.
UX resume structure: what goes where
Header
RequiredName, location (city/state), email, LinkedIn, portfolio URL. The portfolio link should be the full URL in plain text — some ATS systems strip hyperlinks. If your portfolio is password-protected, include the password. Don't overthink the format: clarity beats creativity here.
Summary (optional but useful for UX)
Optional2–3 sentences. Useful when you need to establish your UX specialty quickly — especially for career changers, UX researchers (vs. designers), or designers targeting a specific domain (fintech, healthcare, enterprise). Template: '[X years] [specialization] designer with background in [relevant domain]. Work spans [product types]. Strongest in [2–3 differentiating skills].' Skip it if your title history already tells the story.
Skills
RequiredGroup by category. Design tools (Figma, Sketch, ProtoPie), Research methods (moderated usability testing, card sorting, tree testing, diary studies), Cross-functional tools (Jira, Confluence, Notion), Additional (basic HTML/CSS if applicable, data analysis if relevant). Lead with what you use daily.
Experience
RequiredReverse chronological. For each role: 3–5 bullets that follow the format [what you designed/researched] + [your decision or process] + [what changed]. Don't list every project — pick the 3–5 that best show range, scale, and impact. Senior designers: show team leadership and systems thinking, not just craft.
Education
RequiredDegree, school, graduation year. If you did a UX bootcamp, include it here or in a separate 'Certifications' section — but don't try to hide it. If it was a reputable program (General Assembly, Springboard, CareerFoundry, IDEO U), name it clearly. Bootcamp + strong portfolio beats a design degree + weak portfolio at most companies.
Portfolio / Projects (optional second section)
OptionalSome UX designers add a brief 2–3 line summary of their top 2 portfolio projects directly on the resume — company, problem, your role, and the outcome. This is optional and works best when the portfolio link might not be clicked immediately (like in a recruiter screening pass). It's not a substitute for the portfolio itself.
ATS keywords for UX designers
UX job descriptions vary significantly by company and role type. Use keywords from the specific job posting — but make sure they reflect your actual experience. These are the most commonly scanned terms by UX ATS systems and recruiters:
Core UX methods
Design tools
Design systems & collaboration
Role-specific signals
The 5 most common UX resume mistakes
✗ No portfolio link (or a broken one)
This is the most common filter-out. Check that your portfolio link works from an incognito window. If it's Notion, make sure it's publicly shared. If it's password-protected, include the password.
✗ Bullets describe deliverables, not decisions
'Designed the checkout flow' tells the reader what you made. 'Redesigned checkout after discovering 40% abandonment at the payment step, reducing drop-off by 22%' tells them what you solved and why it mattered.
✗ Missing Figma or listing outdated primary tools
If your skills section leads with Sketch or XD but doesn't mention Figma, recruiters at modern product companies notice. Figma has been the industry standard since ~2021 for most product work.
✗ Over-designed resume format
A resume with custom typography, multi-column layouts, and inline graphics may not parse correctly through ATS. Design it clean, single-column, with standard section headers. The portfolio is where you show your visual range.
✗ No evidence of cross-functional work
UX designers who list only design deliverables read as execution-oriented. Bullets that describe working with engineers, PMs, and researchers read as embedded, collaborative, and more senior.
Common questions
Should I include my portfolio link on my resume?
Yes — put it prominently in your header, next to your name and contact info. Don't bury it. Some ATS systems strip hyperlinks, so write the full URL (not just 'portfolio'). If your portfolio is password-protected, include the password in the header too, or note it next to the link.
Do UX resumes need to be one page?
For early-career UX roles (0–3 years), one page is the standard. For senior designers and design leads with 5+ years and multiple notable projects, two pages is acceptable — but the second page should be adding meaningful content, not padding. Recruiters at top companies read hundreds of resumes; one tight page often reads better than two loose ones.
Should I include every design tool I know?
List the tools you'd be comfortable being tested on in an interview. A skills section that includes 'Figma, Sketch, Adobe XD, Axure, InVision, Miro, Notion, Jira, Confluence, HTML/CSS, Python' looks credible if you genuinely use them; it looks like keyword stuffing if you listed half of them hoping no one asks. Lead with your primary tools, then list secondary ones more briefly.
What if my best work is under NDA?
This is common. Your resume bullets can still describe the problem, your process, and the measurable outcome — without sharing the actual designs. In your portfolio, add a case study that describes the work at a conceptual level, with wireframes replaced by process diagrams. Most hiring managers understand NDA constraints; what they're evaluating is your thinking, not the pixels.
I'm transitioning into UX from another field. What do I emphasize?
Your transferable signals: user empathy from a customer-facing role, systems thinking from engineering or operations, storytelling from marketing, domain expertise that makes your UX work more credible. Pair each transferable signal with a concrete UX artifact (a case study, a redesign project, a bootcamp capstone) that proves you can execute. The combination of domain knowledge + UX craft is genuinely differentiating.
Get your UX resume ATS-optimized
Zari analyzes your UX resume against the job description — identifies keyword gaps, flags weak bullets, and rewrites them to show design thinking and impact. Plus LinkedIn optimization and interview prep for design roles.
Optimize my UX resume →