UX Designer Resume & ATS: How to Pass and Still Look Good
Stop ATS rejection of your UX designer resume. Use our ATS-safe format to pass the bots while highlighting your design skills. Get the template.
Why UX Designer Resumes Fail ATS More Than Any Other Role
UX designers have a problem most other job seekers don't. Your instinct is to design. So when you sit down to write your resume, you treat it like a portfolio piece.
You pick a clean sans-serif, drop in a sidebar, add a skills bar with filled circles, maybe a subtle background color. It looks sharp. It communicates your design sensibility.
It also gets rejected before a human ever sees it.
ATS systems — the software that parses resumes before routing them to recruiters — can't read columns reliably. They choke on tables used for layout. They skip over text in text boxes and graphics. Skills bars? Those percentage circles mean nothing to a parser. It sees "Communication ●●●●○" and has no idea what to do with it.
The result: your resume gets parsed into garbled nonsense, keywords don't register, and you score low on automated screening — even though you're exactly what the company is looking for.
This isn't speculation. Resume parsing tests on multi-column designer resumes consistently show 30–60% keyword extraction failure rates. Single-column plain-text resumes from the same candidate? Near-perfect extraction.
UX roles also require a specific vocabulary that many designers underuse. "I improved the user experience" tells an ATS nothing. "Conducted usability testing with 12 participants" hits keywords and shows method. The gap between how designers describe their work and what ATS systems look for is wider than almost any other role.
Here's the fix. You don't have to choose between looking good and getting past ATS. You just need to understand where the constraints actually are.
The ATS-Safe Format That Still Looks Good
ATS-safe doesn't mean ugly. It means structured. Here's what actually matters.
Single Column, Always
Drop the sidebar. Sidebars look clean in design tools, but most ATS systems read left-to-right, top-to-bottom. A two-column layout gets linearized incorrectly. Your contact info might end up in the middle of your work history. Your skills might disappear entirely.
Single column, full width. That's the non-negotiable.
Fonts That Parse Cleanly
Stick to fonts that render as standard text in any context: Calibri, Arial, Helvetica, Georgia, Garamond. Avoid decorative fonts that embed as images or have inconsistent character mapping.
Font size: 10–12pt for body, 14–16pt for your name. Nothing smaller than 10pt. ATS optical character recognition (used for PDF parsing) struggles below that.
Standard Section Headers
ATS systems look for specific headers to categorize content. Use these exact terms:
- Work Experience (not "My Design Journey" or "Where I've Worked")
- Education
- Skills
- Certifications
- Projects (acceptable for portfolio work)
Creative section names are invisible to ATS. "Crafted Experiences" gets ignored. "Work Experience" gets parsed correctly.
File Format
Submit as .docx unless the job posting specifically asks for PDF. .docx is the most reliably parsed format. If you must use PDF, export from Word or Google Docs — not from Figma, Adobe XD, or Canva. Design-tool PDFs embed text as vector shapes, not actual text. Parsers can't read them.
Visual Polish That Survives ATS
You can still make your resume look polished within these constraints:
- Use consistent spacing and alignment
- Bold company names and job titles
- Add a thin horizontal rule between sections
- Use clean bullet characters (•), not custom icons or symbols
- Keep margins at 0.75–1 inch
A well-formatted single-column resume looks professional. The version with the sidebar and the skills bars looks like it was designed by someone who doesn't understand the medium. Which, for a UX designer, is a problem.
Not sure where your current resume stands? Check your resume ATS score free before you apply anywhere.
30+ UX-Specific ATS Keywords by Category
ATS systems don't just look for your job title. They scan for role-specific vocabulary across tools, methods, and deliverables. Here's a breakdown by category.
UX Methods and Processes
- User research
- Usability testing
- Heuristic evaluation
- Competitive analysis
- Card sorting
- Tree testing
- A/B testing
- Contextual inquiry
- User interviews
- Journey mapping
- Affinity mapping
- Design sprints
- Agile / Scrum
Design Tools
- Figma
- Sketch
- Adobe XD
- InVision
- Miro
- Zeplin
- Framer
- Maze
- UserTesting
- Hotjar
- Optimal Workshop
Deliverables
- Wireframes
- Prototypes
- User flows
- Information architecture
- Design system
- Component library
- High-fidelity mockups
- Interaction design
- Accessibility audit
- WCAG compliance
Soft Skills That ATS Actually Looks For
- Cross-functional collaboration
- Stakeholder presentations
- Design critique
- Mentorship
How to Use These Without Keyword Stuffing
Don't list keywords in a block. ATS systems score contextual usage higher than bare lists. Work them into your bullet points:
Wrong: "Usability testing, wireframes, Figma, user research, A/B testing"
Right: "Conducted usability testing with 8 participants using Maze; findings informed wireframe revisions that increased task completion rate by 22%."
One bullet. Six keywords. Real context. That's how you do it.
Match keywords directly from the job description. If the posting says "design systems," use that exact phrase — not "component library" or "design guidelines." ATS systems do exact and fuzzy matching, but exact matches score higher.
How to Include Your Portfolio Link Without Breaking ATS Parsing
Your portfolio is your most important asset as a UX designer. But how you include it matters a lot for ATS parsing.
Where to Put It
Include your portfolio URL in the contact header at the top of your resume, alongside your email and LinkedIn. This is the only place most ATS systems reliably extract URLs.
Example header format:
Jane Chen | jane@email.com | linkedin.com/in/janechen | janechen.design
What Not to Do
- Don't embed the link in a text box. Text boxes are invisible to most parsers.
- Don't use anchor text hyperlinks as the only reference. "See my portfolio here" — with "here" hyperlinked — often doesn't parse. The URL needs to appear as plain text.
- Don't use URL shorteners. bit.ly links look suspicious to both ATS and humans. Use your actual domain.
- Don't put it only in the footer. Many ATS systems don't parse footers reliably.
Referencing Portfolio Work in Your Bullets
You can mention specific case studies within bullet points without including a separate link for each one. This keeps ATS happy and gives human reviewers context:
"Redesigned onboarding flow for B2B SaaS platform (case study: janechen.design/onboarding); reduced time-to-first-action from 4.2 minutes to 1.8 minutes."
The URL in parentheses is plain text. The parser reads it. The human reviewer clicks it. Everyone wins.
Custom Domain vs. Platform URLs
A custom domain (janechen.design) looks more professional than behance.net/janechen or dribbble.com/janechen. If you're using a platform, make sure your profile URL is clean and recognizable. Your name is better than a string of numbers.
Case Study Bullet Points: The Formula That Shows Impact
Most UX designers write bullets that describe activities. Recruiters — and ATS systems — respond to bullets that show impact.
The Problem with Activity Bullets
"Worked on user research for mobile app redesign."
That bullet tells a recruiter almost nothing. What kind of research? How many users? What changed because of it? What was the outcome?
The Formula
[Method] + [Scope] + [Deliverable] + [Outcome]
Not every bullet needs all four elements. But most should have at least three.
Examples by Method
| Activity Bullet (Weak) | Impact Bullet (Strong) |
|---|---|
| Did user interviews | Conducted 14 user interviews to identify checkout abandonment triggers; insights drove 3 redesign priorities that reduced drop-off by 18% |
| Created wireframes | Delivered 40+ annotated wireframes for iOS onboarding redesign; approved by stakeholders in first review cycle |
| Ran usability tests | Facilitated 2 rounds of moderated usability testing (n=8 each); identified 6 critical friction points resolved before launch |
| Worked on design system | Built component library of 80+ reusable elements in Figma; reduced design-to-dev handoff time by 35% |
| Improved accessibility | Audited product against WCAG 2.1 AA standards; remediated 23 issues and achieved compliance for enterprise client contract |
Where to Find Your Numbers
If you don't have hard metrics, use scope numbers: participants in research studies, screens designed, components built, rounds of testing completed. "Facilitated 3 design sprints with cross-functional teams of 8" is much stronger than "participated in design sprints."
Check your old project files, Jira tickets, and retrospective notes. The numbers are usually there. You just haven't pulled them into your resume yet.
Before & After: A Real UX Resume Rewritten for ATS
Here's what a typical UX designer resume looks like — and what it should look like.
Before: The "Portfolio-Style" Resume
Format issues: Two columns, skills bar with percentage circles, job title in a colored banner, icons for contact info, custom section header "Design Experience."
Sample bullet (original):
"Drove innovation in user experience by leveraging human-centered design principles to create intuitive interfaces that delight users across multiple platforms."
What ATS extracts: Almost nothing. The two-column layout causes the skills section to merge with work history. The banner heading doesn't get parsed as a job title. The bullet has zero parseable keywords and no measurable outcome.
After: ATS-Optimized (Same Candidate)
Format: Single column. Standard fonts. Section headers: "Work Experience," "Skills," "Education." Contact info in plain text at top including portfolio URL.
Sample bullet (rewritten):
"Redesigned mobile checkout flow using Figma; conducted usability testing with 10 participants across 2 rounds, reducing task completion time by 31% and increasing conversion 14%."
What ATS extracts: Role (UX designer), tools (Figma), methods (usability testing), deliverable (redesigned mobile checkout flow), metrics (31% reduction, 14% increase). Full keyword match on 4 of 6 job description requirements.
The Skills Section: Before & After
| Before | After |
|---|---|
| Figma ●●●●● | Sketch ●●●●○ | XD ●●●○○ | Design Tools: Figma, Sketch, Adobe XD, InVision, Framer |
| Communication: ████░ | Research Methods: Usability testing, user interviews, card sorting, A/B testing |
| Creativity: █████ | Deliverables: Wireframes, prototypes, user flows, design systems, WCAG audits |
The "after" version is not just more ATS-friendly. It's more informative to a human reviewer too. No recruiter needs to know you rate yourself 4 out of 5 in Sketch. They need to know you've used it.
The Net Result
The rewritten resume scored 78 on a standard ATS simulation. The original scored 31. Same candidate. Same experience. Different format and language.
That's the entire game.
Frequently Asked Questions
Should a UX designer have a designed resume or a plain resume?
For most job applications, use a clean single-column resume that's ATS-safe. Save the designed version for in-person interviews or direct email submissions to hiring managers you've already contacted. Applying through a job portal with a Figma-exported PDF is the fastest way to get filtered out before anyone sees your work.
How many pages should a UX designer resume be?
One page if you have under 7 years of experience. Two pages if you have more. Your portfolio handles depth — your resume handles first impressions. A two-page resume for a mid-level UX role usually means you haven't edited hard enough.
Should I include a summary section on my UX resume?
Only if it's specific. "Experienced UX designer passionate about user-centered design" wastes space. A useful summary names your specialization, years of experience, and one notable outcome: "Senior UX designer with 6 years in B2B SaaS, specializing in design systems and enterprise accessibility compliance." That's a summary worth keeping.
Do I need to list every design tool I've ever used?
No. List tools you've used in the last 2–3 years and can speak to confidently in an interview. If you used Axure once in 2018, leave it off. If you're actively using Figma, Maze, and Miro on current projects, those go front and center. Relevance over completeness.
Can I use color on an ATS-safe UX resume?
Sparingly, yes. A single accent color used only for your name or section dividers is fine and parses cleanly as long as the text itself stays black on white. Avoid colored text for body copy — some parsers have lower accuracy on non-black text. Never use color fills behind text blocks.
What's the best way to show UX process on a resume without a portfolio?
Use your bullet points to name the method, the scope, and the outcome. "Led 3-week design sprint with product and engineering to prototype 2 competing solutions; concept A validated with users and shipped in Q3" tells a full process story in one line. You don't need case study pages for that — you need specific, method-forward language in your work experience bullets.