How to write a UX designer resume that gets past ATS and into the portfolio review (2026)

UX designer resumes have a structural problem ATS engines don't help with: design hiring is portfolio-driven, but ATS scoring is keyword-driven. The portfolio is what gets you to interview; the resume is what gets the recruiter to look at the portfolio. Both have to land for the application to convert.

This post covers the resume side specifically — the pattern that gets past ATS filters and into the portfolio-review queue, the research vocabulary that signals modern UX practice, and the design-system + tooling language that distinguishes senior designers from mid-level.

Why UX designer resumes are uniquely tricky

Three structural challenges:

1. The portfolio is the real artifact. Hiring managers care about your case studies more than your resume. But the recruiter screening the application stack rarely opens portfolios; they make the cut from resumes alone. The resume has to do enough work to motivate the portfolio click.
2. Visual design tools produce ATS-hostile PDFs. Designers often build resumes in Figma, Canva, or InDesign — tools that produce visually beautiful but parser-hostile PDFs (multi-column layouts, image-only sections, tight kerning, custom fonts). The ATS extracts garbled text or none at all.
3. Research vs craft tension. Senior UX roles weight research methodology AS HIGH as visual craft. Resumes that lead with deliverable types ("wireframes, mockups, prototypes") rank below ones that lead with research methods ("interviews, usability testing, journey mapping") — even though the work might be identical.

The good news: ATS parsing for UX roles is more forgiving on keyword density than for engineering roles, but more punishing on layout traps. Get the layout right and the keywords just need to be reasonably present.

The portfolio link goes in the page header

Non-negotiable. Recruiters look for it in the same location they look for email and phone. If they have to hunt for the portfolio URL, they often don't.

JANE CHEN
Senior Product Designer · San Francisco
jane.chen@email.com  ·  (555) 555-0142  ·  janechen.design  ·  linkedin.com/in/janechen

Notes:

• Use a clean URL. "janechen.design" reads better than "www.janechen.com/portfolio". Custom domains > behance.net or dribbble.com URLs.
• Hyperlink text should be the URL or the domain name. Don't write "Portfolio" as a hyperlink — recruiters want to see the URL before they click. Plus ATS parsers extract URL text but not link metadata.
• If your portfolio is on Notion/Webflow and looks unpolished, fix THAT first. A bad portfolio kills more interviews than a bad resume.

Section 1 — The summary that lands

Pattern that works for senior UX:

[Role] with [years] designing [domain/product type], most recently leading [specific high-impact work]. [Optional: where my work has shipped at scale].

Examples:

• "Senior Product Designer with 7 years designing B2B SaaS interfaces, most recently led the design system rebuild at Stripe used by 40+ engineering teams."
• "Lead UX Designer with 9 years in consumer mobile, shipped flows used by 200M+ users at Pinterest and Discord."
• "Senior UX Researcher + Designer with 6 years in healthcare. Designed and validated patient-facing flows now serving 4M+ patients at Athenahealth."

What works:

• Combines role + tenure + domain + scale
• Names visible products / scale of users when honest
• Distinguishes design-system / IC / management track if relevant

What doesn't work:

• "Passionate user-centered designer with experience across multiple industries" — generic
• "Designer who loves solving complex problems" — vague
• 4-paragraph "About me" — recruiter reads first sentence, skips rest

Section 2 — Experience bullets that show the practice

The pattern that consistently lands at senior UX roles:

[Verb] [research or design activity] [scope] [outcome with measurable impact OR named artifact]

Strong examples:

• "Led discovery research for new payments flow: 18 customer interviews, 3-week diary study, 2 rounds of usability testing on prototypes — validated 3 of 5 hypothesized friction points and informed final shipping spec"
• "Owned end-to-end design for B2B onboarding flow, reducing time-to-first-value from 14 days to 4 days; rolled out to 12K customers via gradual experiment"
• "Built and maintained component library used by 6 engineering teams (~140 engineers); achieved 92% adoption across new feature surfaces in 6 months"
• "Co-designed accessibility audit and remediation across product surface; raised WCAG 2.1 AA compliance from 67% to 94%"

What works:

• Names the research method explicitly (interviews, diary study, usability testing — not just "user research")
• Names the design artifact when relevant (component library, design system, accessibility audit)
• Quantifies scope (number of users, teams, customers) and outcome (time reduction, adoption rate)
• Names the cross-functional partners when relevant (engineering, PM, research)

What to avoid:

• "Designed beautiful interfaces" — meaningless. Every designer claims this; recruiters skip past.
• "Worked on the design system" — what specifically? Component library? Token system? Documentation? Adoption?
• "Created wireframes and mockups" — describes deliverables, not impact. Junior framing.
• "Collaborated with cross-functional teams" — vague. Name the function (engineering, PM, research) and the scope (squad of 8 / org-wide).

Section 3 — Skills section that signals the breadth

Group skills into 3-4 categories so the parser and human reader both get clean structure:

Research: customer interviews, usability testing, surveys, diary studies,
          journey mapping, JTBD, competitive analysis, persona development

Design: information architecture, interaction design, visual design, prototyping,
        design systems, design tokens, accessibility (WCAG 2.1 AA), motion design

Tools: Figma, FigJam, Framer, Principle, Lottie, Maze, UserTesting, Dovetail,
       Notion, Linear, Storybook

Domains: B2B SaaS, fintech, healthcare, developer tools

Notes:

• Lead with Research. Senior UX roles weight research practice over deliverable types. "Research" first signals you ARE a researcher, not just a wireframe-maker.
• Name accessibility specifically. "WCAG 2.1 AA" is a credible token. "Accessibility (a11y)" is acceptable. Just "accessibility" without context is weak.
• Name design-system specifics. "Design tokens" / "component library" / "Storybook" are specific signals. "Design systems" alone is generic.

Section 4 — Case studies inline (optional but powerful)

For mid-career designers without a dense work history, consider adding 2-3 brief case studies inline:

Selected case studies

Stripe Payments Flow Redesign · janechen.design/stripe-payments
Reduced abandonment 23% in 4-week shipping cycle. Research: 12 customer
interviews + 3 prototype tests. Designed across mobile + web.

Athenahealth Patient Portal Onboarding · janechen.design/athena-onboarding
Lifted activation 38% by restructuring 14-step flow into 4. Co-designed
with cardiology + GP customer panels.

Each case study: name + URL (deep-link to that specific case) + 1-line outcome + 1-line method. The URL is what the recruiter actually clicks; the inline summary motivates the click.

Tools and methodology vocabulary in 2026

Research methods (still high-signal):

• Customer interviews, usability testing, A/B testing
• Diary studies, contextual inquiry, ethnographic research
• Card sorting, tree testing
• Surveys, NPS analysis
• Jobs to be done (JTBD), journey mapping
• Synthesis: affinity mapping, opportunity mapping

Design vocabulary:

• Information architecture, interaction design
• Design systems, component libraries, design tokens
• Accessibility (WCAG 2.1 AA, screen-reader testing, contrast ratios)
• Responsive design, adaptive design
• Motion design, micro-interactions

Tools (signal hands-on practice):

• Figma + FigJam (table-stakes in 2026)
• Framer (high-signal — production-style prototyping)
• Storybook (signals you ship to engineering)
• Maze, UserTesting, Dovetail (research tools)
• Lottie (motion design output)
• Notion / Linear (project management with engineering)

What's becoming dated in 2026:

• Sketch (still acceptable but Figma has won)
• Adobe XD (largely abandoned)
• Photoshop / Illustrator for screen design (signals print background)
• "Wireframes" as a primary deliverable (low-fidelity work is now usually direct in Figma)

The full curated keyword list is at /resume-keywords/ux-designer.

The PDF that survives ATS parsing

Most UX designer resume parsing failures come from the PDF itself, not the content. The most common issues:

1. Image-only PDF. Designed in Figma → exported as image → wrapped in PDF. Test: open the PDF in any reader and try to copy-paste the body text. If you can't, the file is image-only and ATS extracts ZERO content.
2. Multi-column layout. Beautiful for human reading, parser-hostile. Stick to single column.
3. Custom fonts that don't embed. PDFs with non-standard fonts sometimes lose all text formatting. Embed fonts on export, or use system fonts.
4. Decorative elements rendered as text. Bullets, dividers, icons that look like Unicode glyphs sometimes break extraction. Stick to standard ASCII characters in the text body.

If you want to keep a portfolio-piece visual resume for human review (it's beautiful and signals craft), submit a separate ATS-friendly version to applications. Two versions: portfolio resume for recruiters who'll see the whole thing, ATS resume for online application forms.

Common failure modes

1. No portfolio link or non-clickable URL — the single most common UX-resume failure. Portfolio link in the header, plain URL text.
2. Generic "user-centered design" without research methods — name what you actually do (interviews, usability testing, journey mapping).
3. Listing only visual tools without research tools — Figma + Sketch in skills but no Maze, Dovetail, UserTesting reads as "I make screens, not insights."
4. Image-only PDF from a design tool — invisible to ATS. Test by copy-pasting from your PDF.
5. Bullet content that describes deliverables, not outcomes — "designed wireframes" vs "designed onboarding flow that lifted activation 38%."
6. Missing accessibility signal — WCAG / a11y is increasingly expected on senior designer resumes; absent it reads as a gap.

Test your UX designer resume

The free LSI Resume Analyzer scores against the curated UX designer keyword library and runs the 5 ATS engine simulators. For UX resumes, the most common findings are: image-only PDF (catastrophic — fix immediately), multi-column layout (Workday-fatal), missing research methodology vocabulary, generic "designed beautiful interfaces" bullet language.

For the deeper context on how each ATS engine reads designer resumes, see How an ATS Reads Your Resume and the engine-specific Workday and Greenhouse posts.