11 min read
Answer first: Your UX designer resume should be a boring, single-column Word or text PDF for ATS upload, with your portfolio link as plain text and all visual design saved for case studies on your site. Fancy layouts fail parsing before any recruiter opens your Dribbble.
You've spent years learning visual hierarchy. Then Workday reads your two-column template and thinks your Figma skills are your current employer. That's not a taste problem. It's an upload-order problem. Before you redesign bullet icons, check your resume for free against the posting and confirm parsers can read your job titles in order.
Below: why plain wins for US ATS, the exceptions (when a human-only PDF is fine), what to change tonight, and bullets that prove UX work without a designed grid. You're not dumbing down your career. You're splitting parser file from portfolio file.
If you're applying tonight, don't start in Figma or Canva for the upload version. Start in Word with a blank doc. Paste your current bullets in plain text. Strip icons. Add dates. Export. Then open your portfolio in a second tab and make sure the case study dates match.
Contract UX roles and agency benches see the same parsers as product companies. A staffing agency uploading your file to a client req will not manually fix a scrambled Greenhouse import. They'll move to the next candidate whose profile fields populated correctly.
Quick Wins
- Export one plain single-column PDF from Word; save the designed version for humans only.
- Put portfolio URL as text on line three, not inside a header graphic.
- Move Figma and research tools into bullets under dated employers.
- Paste the PDF into Notepad once and read employer order top to bottom.
Why a UX designer resume needs a no-fancy layout for US ATS
US corporate UX roles on Workday, Greenhouse, and Lever still start with the same parser every other function hits. The system extracts text into profile fields. It does not admire your spacing system. Columns, skill bars, and icon grids reorder or drop content before a recruiter searches "user research" or "design systems."
Your portfolio proves craft. The upload file proves employment history, methods, and outcomes in a order machines can map. When those jobs split, you stop losing screens to layout while your case studies never get clicked.
I've passed UX files where the PDF attachment was gorgeous but the parsed profile showed Skills as the first employer. The hiring manager never opened the portfolio because the profile already looked confused.
Read resume rejected by ATS for the wider filter stack. This page is the UX-specific split between parser file and portfolio.
The exception: A referral or in-person portfolio review can use a designed PDF because a human chose to open it. Cold applications through corporate portals should never use that file as the upload. Keep two versions with clear filenames: Lastname_UX_Resume_ATS.pdf and Lastname_Portfolio_CaseStudies.pdf.
Agency and in-house reqs both run the same parsers. A startup posting on Greenhouse cares about readable employers as much as a bank on Workday. The split between boring upload and beautiful portfolio applies across company size.
Accessibility work belongs in bullets, not only in a portfolio case study. WCAG audits, screen reader testing, and contrast remediation are searchable terms when they sit under a dated role. Parsers cannot click your a11y project thumbnail in the margin.
What to do now: plain UX designer resume file
Step 1: Build a parser master in Word
11-point Calibri or Arial. Single column. Headers: Summary (optional), Professional Experience, Education, Skills. No text boxes, no tables for skills, no Canva export for the upload version.
Before: Two-column resume with tool icons in a left rail and case study thumbnails in the margin.
After: Name and contact in body lines one to three, portfolio URL as behance.net/handle text, employers with Month Year dates and standard bullets.
Step 2: Write bullets that sound like UX work, not adjectives
Name the method, artifact, and outcome. User interviews, usability tests, wireframes, design systems, accessibility audits. Skip "passionate about user-centric design" without a shipped example.
Product designer example:
Before: "Created intuitive interfaces and collaborated with cross-functional teams."
After: "Ran 12 moderated usability sessions on checkout; shipped Figma prototypes that cut error rate 18% in A/B test Q3 2025."
UX researcher example:
Before: "Conducted user research to inform product decisions."
After: "Synthesized 24 diary studies into journey maps for mobile onboarding; findings drove 3 priority fixes in Jira for eng sprint 42."
Step 3: Mirror posting language in bullets, not sidebars
If the req says design systems, Figma, and WCAG 2.1, those terms belong in dated bullets under the employer where you did the work. A keyword column that parses first makes you look like your job title is "Sketch Adobe XD."
Step 4: Keep portfolio and resume roles aligned
Case study titles should match employer names and rough dates on the resume. Recruiters cross-check. A 2024 banking app case study under a resume that only lists agency work from 2021 raises questions.
Step 5: Run Notepad test before every batch apply
Copy all text from your upload PDF. Paste into Notepad. Employers in order? Dates intact? Portfolio link readable? If not, flatten layout before tailoring keywords.
Copy-paste UX resume bullet skeleton
[Verb] [artifact/method] for [product/flow]; [tool] with [metric or scope].
Example: Redesigned account settings IA after card sort with 9 participants; shipped in Figma and React, support tickets down 22% in 60 days.
Swap in your real projects. Illustrative metrics inside bullets are fine. They show shape, not market research.
Edge case: career changer from graphic design
Lead with UX-titled roles or freelance projects with dates. Put visual design work under one employer block with bullets reframed toward research and prototyping, not only brand guidelines.
Edge case: staff or principal UX
Two pages is acceptable. Page one: last two roles with system-level outcomes. Page two: earlier IC work and education. Still single column. No executive infographic timelines.
Pair 3: Design systems lead
Before: Logo grid of component libraries in a sidebar. Bullets say "maintained design system" with no adoption metric.
After: "Scaled Figma design system to 40+ product surfaces; cut design-dev handoff time 30% after token rollout Q1 2025." Tools live inside the bullet, not in icons.
Pair 4: Contract or freelance UX
Before: One block titled Freelance with no client names or dates.
After: Each client as its own employer line with Month Year range, NDA-safe project description, and method named in bullet one.
What to do in the next ten minutes
Open your current upload PDF. Paste into Notepad. If your first line of parsed text is a tool name instead of your name, stop and flatten. Export a plain version from Word before you tailor one more posting. Link your portfolio on line three as text. Run the checker on that file only.
See Microsoft Word resume settings for US ATS success when you rebuild the parser master from scratch in Word tonight.
Where UX designer resumes break in US ATS
Uploading the portfolio PDF as your resume. Case study spreads are not employment history. Parsers see images and blank fields.
Skill bars and star ratings. Greenhouse and Workday flatten them into nonsense strings or skip the section.
Listing tools without proof bullets. Figma in a sidebar does not beat Figma in a bullet with a shipped flow and metric.
Creative section names. My Design Journey does not map to Experience. Use boring headers parsers expect.
One designed file for every channel. Email a plain PDF to a hiring manager after a referral; keep the designed deck for in-person portfolio reviews only.
Hiding employment gaps behind designed timeline graphics. Parsers read gaps as blank rows. Address gaps with one honest line in the summary or a dated contract role, not a curved timeline image.
Duplicating case study copy in the summary. The summary should state level, domain, and top proof in three lines. Save the long narrative for the portfolio URL you link on line three.
Verify the plain file before you apply
Run your upload version through the free ATS checker with the UX posting pasted in. You're checking parse order and must-have terms, not chasing a perfect score on a designed PDF.
Use job match score to see whether research-heavy or systems-heavy reqs fit your bullet proof before you spend an hour on portfolio tweaks.
Need a clean base? Build your resume in single-column format, then add UX bullets. Pair top targets with a short note from the cover letter generator.
Split upload from portfolio tonight
A UX designer resume that passes US ATS is deliberately plain. Single column, standard headers, portfolio as text, proof in bullets. Save the layout craft for case studies recruiters click after your file parses cleanly.
Flatten tonight's upload file, run a free check, and apply with the boring version. Your portfolio still shows you're a designer. The parser just needs to know where you worked and what you shipped.
Pick the next UX req on your list. Duplicate your parser master. Tailor three bullets. Upload the plain PDF. Send the portfolio link when a human replies, not before the parser can read your current job title.
Read more
Frequently asked questions
Not on the ATS upload file. Save grids, color blocks, skill bars, and custom icons for your portfolio site or PDF you hand to a human after a screen. The file you submit through Workday or Greenhouse should be a single-column Word or text-based PDF that parses like any other corporate resume. Your design taste belongs in case studies, not in the parser's first read.
Upload what the portal accepts, then check the preview if one exists. A text-based PDF exported from a plain Word doc usually works when the source has no tables or sidebars. Scanned portfolio PDFs and Canva exports often fail. If preview scrambles your employers, try DOCX from the same flattened file before you assume the problem is keywords.
List tools in a short Skills line or inside dated bullets under each role. Example: Led usability tests in UserTesting; shipped checkout redesign in Figma with 14% fewer drop-offs in Q2. Do not put tools in a graphic sidebar that parses before your current job title. The bullet that proves you used Figma matters more than a logo row.
Yes, as plain text in the body under your email, not inside a header graphic. Recruiters will click through after the file parses. A broken upload with a pretty portfolio button in the footer still loses to a plain file with github.com or behance.net written as text on line three.
One page through mid-level, two pages max for senior IC or lead roles with multiple shipped products. Parsers do not reward length. They reward readable employer blocks with Month Year dates, standard section headers, and bullets that name methods, tools, and outcomes. Cut old unrelated jobs before you shrink font to fit a designed layout.
No for US corporate ATS uploads. Photos add parsing noise and can trigger bias filters at some employers. Your portfolio headshot page is the right place for a photo. The upload file should be text only with a plain portfolio link.