12 min read
You've spent weeks on case-study layouts, and Greenhouse still shows two employers instead of four. You're not failing on craft. You're uploading the wrong file type. A UX designer resume that passes ATS is a plain Word doc for the portal, with your portfolio link in bullet three, not a designed PDF that doubles as your case-study deck.
Check your resume for free with the posting pasted in before you swap fonts again. You're confirming employer order and whether Figma and user research still sit next to the job that used them, not chasing a magic keyword list on a file parsers cannot read.
Most UX candidates I talk to already have the methods the posting wants. What's missing is a boring upload file Greenhouse and Workday can chunk into employer blocks before a recruiter opens your profile. Your portfolio still wins the screen. It just doesn't belong in the attachment field.
Below you'll get five steps to split upload from portfolio, before/after pairs for common UX templates, two edge cases for researchers and career changers, where designed resumes still break after flattening, and a copy-paste header block you can use tonight. Job hunting while you're polishing pixels is draining enough without a sidebar pretending to be your first job.
And when the portal asks for a cover letter, don't paste lines that repeat a scrambled import. Generate a cover letter from the corrected resume text so employer names match what Greenhouse finally read.
Quick Wins
- Upload plain Word for the application. Save the designed PDF for humans after the screen.
- Portfolio URL on line three under email, case study named in bullet three.
- Spell Figma and usability testing in dated bullets, not icon grids.
- Paste the export into Notepad once and read employer order top to bottom.
Why your designed UX resume fails Greenhouse before anyone opens Figma
Greenhouse and Workday do not score taste. They extract text into employer, title, date, and bullet fields. UX resumes often arrive with skill rails, process diagrams, and portfolio spreads that parsers read before Experience. Your current product role drops to row six while Figma and user research become a fake first employer.
The bar your upload file must clear: plain-text export reads name, contact, Experience with Month Year dates, Education, then Skills. Each employer line stays attached to its title and bullets. Methods and tools appear next to the job that used them, not in a left-column icon grid.
UX portfolios train you to lead with visuals. ATS uploads punish that instinct. A composite product designer applied to twelve Greenhouse reqs with a case-study PDF exported from a design tool. Preview showed one employer block and a skills blob. She rebuilt in Word using the header below, linked portfolio.com in bullet three, and the preview matched her timeline. Same case studies. Different file for upload.
I've screened UX files where the Greenhouse preview showed wireframe thumbnails as empty lines and dropped the usability metric from bullet one entirely. The recruiter never reached the portfolio link because the parsed profile looked like a junior generalist with no dated research work.
Edge case: UX researcher vs product designer on the same team. Researchers should lead bullet one with method, sample, and finding. Product designers lead with shipped flow, metric, and handoff. Both use the same single-column skeleton. Only bullet language shifts per posting.
Edge case: career changer from graphic design. Keep agency client names on plain employer lines, not inside nested tables. Write Agency Name (Client: Retail Brand) as text. Parsers treat table cells as separate jobs. Recruiters ctrl-f the product domain they hire for, not your old logo grid.
Edge case: contract UX via agency then in-house conversion. List agency months on their own employer line with Month Year dates, then the in-house title on a separate block when you converted. Do not merge both into one undated row because the designed template made dates hard to fit. Honest labels parse cleaner than creative spacing.
Hiring managers still want proof you can think in systems. That proof belongs in bullets with methods and outcomes, not in margin diagrams. A plain file with strong research bullets gets forwarded. A pretty file with scrambled import gets closed before anyone clicks your portfolio link.
For how parsers match posting language after layout is clean, read how ATS matches resumes to job descriptions . File choice comes first. Keyword tailoring second.
Build a UX designer resume that passes ATS in five steps
Work top to bottom. Run the Notepad paste test after each step so you catch flattening before you tailor keywords for the posting.
Step 1: Split the upload file from your portfolio
Before: One designed PDF with case-study spreads, full-bleed images, and a process diagram on page one.
After: Plain Word file for Greenhouse upload. Portfolio lives at portfolio.com on line three under email. Case study referenced in bullet three under current role, not embedded as images.
The application field wants employer history parsers can chunk. Your portfolio wants scroll and interaction. Those are two deliverables, not one export.
Step 2: Flatten sidebars and skill rails
Before: Left rail holds Skills with Figma, Sketch, and Miro icons. Right column holds Experience. Colored header band with contact in a text box.
After: Single column, 11-point Calibri or Arial. Tools appear inside dated bullets: Stack: Figma, Miro, usability testing on the employer line that used them. Contact sits under your name in the body.
Parsers often read the left rail first. Your design tools become the opening job. Fix the column, not the keyword list.
Step 3: Put portfolio proof in bullet three
Posting wants end-to-end product design with research and prototyping for a Greenhouse employer in Austin.
Before: Portfolio link in footer on every page. Case study titles only on a Projects page with no dates.
After: Flowline Health, Austin. Product Designer | January 2022 to Present. Bullet one names method and outcome. Bullet two names handoff and metric. Bullet three: Led onboarding redesign; usability tests with 22 participants cut drop-off 14%; full case study at portfolio.com/onboarding.
Recruiters click when the link sits next to a bullet that names the study they care about. Footer QR codes often parse as garbage or attach to the wrong employer.
Step 4: Write research and design proof in plain bullets
Before: Skills section lists user research, wireframing, prototyping, accessibility with no dates. Experience bullets read Responsible for design tasks.
After: Ran moderated usability tests on checkout flow with 18 participants; identified 6 friction points that drove a 12% lift in completion. Built hi-fi prototypes in Figma for 3 sprint cycles; cut dev rework tickets 9 in Q2 2025.
One outcome per line. Method, scope, tool, and one number each. Parsers weight dated Experience higher than undated Skills clouds.
Step 5: Tailor bullet one, then export DOCX
Open the job description. Highlight three must-have terms: method, tool, and domain if listed. Rewrite bullet one under your current role so one term lands in the first eight words. Export DOCX when Greenhouse allows choice. Otherwise PDF from Word only, never from a design export.
Research-heavy posting example: Led generative interviews with 16 enterprise buyers; synthesized findings into 4 journey maps that shaped Q3 roadmap. Product-heavy posting example: Shipped mobile settings redesign in Figma; cut support tickets on account changes 11% in 90 days post-launch.
Before: Summary paragraph lists design thinking, empathy, and collaboration with no employer attached.
After: Drop the summary or keep three plain sentences. Move every method into a dated bullet. Collaboration belongs next to the squad you shipped with, not as a floating value statement above Experience.
Accessibility is a common posting term. Do not list WCAG only under Skills. Write one bullet that names the standard and the user outcome you moved: Remediated checkout contrast and focus order to WCAG AA; cut accessibility-related support tags 7% in one release cycle.
Copy-paste UX resume header block
Copy-paste this at the top of a blank Word doc and replace bracketed lines:
[Full Name]
[City, ST] · [Phone] · [[email protected]]
portfolio.com/[handle] · linkedin.com/in/[handle]
[Optional one-line summary with title level and domain]
Experience
[Month Year] to [Month Year or Present] · [Employer] · [Job Title]
[Bullet one: method or shipped flow with metric]
[Bullet two: cross-functional scope with tool names]
[Bullet three: case study link tied to this employer]
Education
[Degree], [Institution], [Year]
Skills
[Comma-separated tools also named in Experience]
Export PDF from this file only when the portal requires PDF. Open the Greenhouse or Workday preview if offered. If employers scramble, switch to DOCX upload from the same source.
See Greenhouse parsing fixes for scrambled uploads when you're comparing how different employers configure import previews.
When a plain UX resume still breaks after you flatten layout
Uploading the portfolio PDF because it looks more you. Case-study spreads are not employer history. Parsers read images as blanks and reorder text boxes. Build a separate upload file even when the portfolio PDF is gorgeous.
Stuffing keywords into a sidebar after a failed upload. More text in the wrong column makes parse order worse. Flatten first, then tailor bullets.
Using builder templates with invisible tables. Many online resume shops hide grid lines. Greenhouse still reads the grid. Your wireframe skills row can import before your current title.
Leaving section headers creative. My Design Journey and Process Overview do not map to Experience and Skills in most parsers. Standard labels are boring on purpose.
Repeating contact info in header, footer, and body. Duplicates fight for the same fields. Pick one body block and delete the rest.
Applying fixes only to page one. A clean first page with a two-column page two still scrambles the full profile. Scroll the entire doc before export.
Skipping the preview because you're applying on mobile. Wait until you can open the desktop preview once. A scrambled upload is harder to fix after submit on some reqs.
Trusting the PDF because it looked fine on your laptop. Recruiters may open the parsed profile first. Your current role already sits under Skills while a sidebar full of tools became a fake employer.
Verify UX resume parse order before you hit submit
Run the export through the free ATS checker with the job description pasted in. You're confirming employer-title pairing and whether research terms landed in Experience, not chasing a perfect score on a designed file.
Then score your job match on the same plain-text order. Keywords only help after Greenhouse or Workday can attach them to the right job line. A high match on a scrambled file still loses to a readable lower score.
Upload plain tonight
A UX designer resume that passes ATS (no design resume needed) comes down to two files: boring Word for upload, portfolio for proof. Single-column layout with standard headers passes Greenhouse and Workday import. Designed case-study PDFs scramble employers before a recruiter opens your profile. Flatten layout, put your portfolio link in bullet three, and read a plain-text paste once.
Pick the next UX req on your list. Paste the copy-paste header block. Run a free ATS check. Open the preview if the portal shows one. Upload when employer lines stay paired with the right titles and your case study link sits in the body.
This won't turn your portfolio site into a parser-friendly file without edits. It does stop qualified designers from losing screens because their best research bullet landed under Skills while a sidebar full of Figma icons became their fake first job.
Save one Word master file with the header block above. Duplicate it per application, tailor bullet one to the posting, and re-run the plain-text paste before every Greenhouse or Workday upload. Same skeleton every time beats exporting a new pretty PDF each week.
Read more
Frequently asked questions
No. Portfolio PDFs carry grids, case-study spreads, and image blocks parsers cannot read as employer history. Upload a plain single-column Word or text-based PDF for the application file. Put your portfolio URL on line three under your email and again in bullet three under your current role. Recruiters click after the file imports cleanly.
Not on the ATS file. Spell Figma, Sketch, and Adobe XD in plain text inside dated Experience bullets. Icons and skill bars often import as empty cells or reorder your contact block above your current job. Save visual hierarchy for your portfolio site, not the Greenhouse upload.
Line three under email for your main portfolio URL. Bullet three under your current employer for the case study that matches the posting: Led checkout redesign; usability tests with 24 participants cut task time 18%; case study at portfolio.com/checkout. Parsers drop footer links and QR codes. Body text survives import.
Yes when both pages stay single column with Month Year dates on every role. Page count is not the failure mode. Sidebars, process diagrams in tables, and designed headers are. A dense two-page Word file with research methods in bullets imports cleaner than a one-page Canva export.
Same skeleton, different bullet one. Researchers lead with study design, sample size, and method names in the first eight words. Product designers lead with shipped flows, metrics, and handoff scope. Both roles lose screens when wireframe thumbnails replace employer lines or when Skills holds every tool with no dated proof.