UX Researcher ATS Checklist for Tech Companies (2026)
UX Researcher (UXR) resumes get filtered by the same ATS engines as IC product-design resumes — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but the failure modes are inverted. Where a designer resume gets rejected for a thin tools/craft surface, a UXR resume gets rejected for reading like a UX/UI portfolio with "researcher" in the title: methods are vague, sample sizes are missing, deliverables aren't named, decisions are unmentioned, and the cross-functional partnership signal is generic. This 22-item checklist walks every UXR through the pre-submission audit specific to research roles at tech companies — format, structure, methods specificity, artifact ownership, decision-impact framing, portfolio coordination, and verification — and names the UXR-specific failure modes that take down even strong candidates [1][2][3][4].
Key Takeaways
- Most Fortune 500 companies route resumes through ATS engines before any human review, and the UXR keyword target is fundamentally different from the UX/UI designer target — methods specificity, study artifacts, cross-functional partnership, and decision-impact replace the designer craft / tools scan [1][2].
- The single most common UXR resume failure is the "designer-with-research-curiosity" pattern: 70% of bullets are UI craft work, 30% are vague "research" — recruiters configured to filter for named methods auto-reject these [3][4].
- Sample size and recruit criteria are non-negotiable on every recent study. "Ran user research" without numbers reads as designer-touching-research; "9 moderated usability sessions with mid-market admins via dscout" passes [3][4].
- Per Erika Hall's Just Enough Research, the UXR craft sits in the question definition and the decision linkage, not in method volume — and the resume bullets must reflect that through named-method-plus-decision phrasing rather than method-stuffing [3].
- BLS does not publish a UX-Researcher-specific occupational code; the closest official proxies are SOC 19-3032 Industrial-Organizational Psychologists ($109,840 median, May 2024) and SOC 15-1255 Web and Digital Interface Designers ($98,540 median, May 2024) [5][6]. levels.fyi tracks UXR comp at top-tier tech companies separately and consistently above the BLS proxies because BLS does not isolate the role [7].
- The portfolio link is increasingly expected at senior-and-up UXR roles. Per Tomer Sharon's It's Our Research framing of research as a craft surface, study writeups are where hiring managers verify research judgment that the resume bullets only summarize [8].
Stage 1 — Format and File Prep (Items 1–5)
1. Single-column layout, no exceptions.
Greenhouse and Workday inconsistently parse two-column resumes; the parsed-text version recruiters see often appends the right column after the left, scrambling experience bullets [1][2]. UXR resumes are particularly vulnerable because many "research-flavored" templates use a sidebar for methods icons or a methods cloud. Use single-column with vertical sections: Header → Summary → Skills → Experience → Education → Optional (Publications, Speaking). Verify by copy-pasting into a plain-text editor; if the order is wrong there, it's wrong in the ATS.
2. Submit as .docx or PDF — both work, with caveats.
.docx is the safer default across Workday and Taleo. PDF works on Greenhouse, Lever, and Ashby with high parse fidelity. The trap most relevant for UXR: PDFs exported from Figma or design tools sometimes embed text as glyphs or vectorized paths rather than parseable characters, breaking ATS extraction [2]. Build the resume in Word, Google Docs, or a plain-text-first tool — not in Figma. If you do export from a design tool, verify the output by running pdftotext or by copy-pasting from a reader to confirm the extracted text matches the rendered document.
3. Keep file size under 2 MB.
UXR resumes typically run 1–2 pages and don't include images, so this is rarely an issue. Watch for embedded company logos, headshot photos (skip these — not standard in US tech), or thumbnail screenshots of research artifacts (those belong in the portfolio, not the resume). Pure-text UXR resumes should be 50–200 KB. Anything over 2 MB has embedded media that should come out and live in the portfolio link instead.
4. Use system fonts only — Calibri, Arial, Helvetica, Georgia, or Times New Roman.
Custom fonts get substituted during ATS parsing, sometimes shifting line breaks and section boundaries unpredictably [2]. UXR resumes don't need typographic personality on the document — the research signal is in the words, and the typographic personality (if any) belongs in the portfolio site. Save the custom font for your portfolio cover, your conference-talk template, or your case-study deck.
5. Avoid headers/footers, text boxes, columns, and tables.
Document headers/footers on Workday and older Greenhouse parsers can be ignored entirely [1][2]. UXR resumes sometimes use tables to lay out a methods inventory ("Moderated usability | Generative interviews | Surveys | Card sorting | RITE") — this fails ATS parsing universally because the table tokenizer scrambles the cells. The fix: write the same methods inventory as a single line of text inside an experience bullet, e.g., "Methods on the consumer-product team across 4 quarters: moderated usability (12 studies), generative interviews (18), surveys (4), card sorts (3), 2 RITE rounds."
Stage 2 — Structure and Section Order (Items 6–10)
6. Standard section headers — exactly these names.
Use: "Summary" (or "Professional Summary"), "Skills" (or "Research Methods and Tools"), "Experience" (or "Professional Experience"), "Education," "Publications" or "Speaking" (optional, only if substantial). ATS parsers — especially Taleo and older Workday — pattern-match on exact section names [1][2]. Creative section names ("Where I've Listened," "What I've Learned," "How I Research") cause the parser to skip those sections. UXR resumes that lean rebellious here lose ATS points without compensating gain. Save creative section naming for the portfolio site.
7. Header line: name, location, contact, LinkedIn, portfolio (or Google Scholar) — and that's it.
Format: "Name | City, ST | email | (xxx) xxx-xxxx | linkedin.com/in/firstname-lastname | portfolio-or-scholar-url." A portfolio URL is increasingly expected at senior+ UXR levels for the research-judgment check. If you publish, a Google Scholar or ResearchGate link works in the same slot. Skip GitHub (rarely relevant unless you've done open-source UXR tooling), headshot, address line, and "Open to Work" banner — these read as junior-resume conventions.
8. Lead with a 3–4 line Professional Summary that names methods, scope, and partnership.
The summary gets the highest scan-weight per word [1][2]. For UXR, pack 5–7 Tier-1 keywords. Example: "Senior UX Researcher with 7 years of mixed-methods experience — owned end-to-end study work across moderated usability, generative interviews, and surveys for B2B SaaS surfaces; partnered with PM, design, and data science on quarterly research roadmaps; comfortable presenting to VP-level stakeholders. Recent: led the segmentation study that drove the H2 prioritization shift on the consumer-product team." That's 7 Tier-1 UXR keywords (mixed methods, moderated usability, generative interviews, surveys, partnered with PM/design/DS, research roadmap, segmentation study) plus 2 Tier-2 (B2B SaaS, prioritization) in 4 lines.
9. Skills section organized for UXR, not for designer.
UXR skills sections should NOT be a 15-item UI-tools dump — that's the most common failure mode. Recommended grouping (4 categories, 18–22 items): Methods (moderated usability, generative interviews, contextual inquiry, surveys, card sorting, A/B partnership, RITE, JTBD, mixed methods), Tools (Dovetail, Maze, dscout, Qualtrics, Optimal Workshop, R, SQL — 8–10 named tools), Deliverables (research plan, screener, discussion guide, synthesis report, insights repository), Cross-functional (PM partnership, design partnership, data-science partnership, executive communication, narrative). The UI-tools dump triggers spam-detection on Greenhouse and Ashby and reads as designer-not-yet-transitioned [1][9].
10. Experience section: reverse-chronological, 5–7 bullets per recent role.
Reverse-chronological is the ATS expectation. For senior+ UXR, 5–7 bullets at the most recent role, 4–5 at recent prior roles, 3 at older roles. UXR bullets carry more signal density than most generic resumes because each bullet should reference a method, a sample size or recruit, and a decision the study informed. Don't skimp on bullet count for the most recent role — recency-weighted scoring on Lever and Greenhouse pushes the recent role to the top of recruiter screens [1][10].
Stage 3 — UXR-Specific Content Audit (Items 11–16)
11. Every recent study bullet names the method, sample size, and recruit.
This is the single highest-leverage check on the entire UXR checklist. For each role in the last 5 years, the bullet cluster must include studies with: method named (moderated usability vs. generative interview vs. survey vs. card sort), sample size (n=9, 18 interviews, 320-respondent survey), and recruit method (dscout panel, internal panel, in-house recruit, screener criteria). Pattern: "9 moderated usability sessions with mid-market admins, dual-screener for tenure (6+ months) and tool-stack (Slack, Notion, Zendesk), recruited via dscout." Vague phrasing ("ran usability tests") fails the screen because the recruiter is calibrating method maturity on the specifics, not the method label [3][4].
12. Every recent role names study artifacts the researcher owned.
Artifact ownership is the rarest UXR-specific signal because designers and PMs don't produce these [3][4]. For each UXR role, name what you authored: research plans, screeners, discussion guides, synthesis reports, insight-repository taxonomies, study-design rubrics. Pattern: "Authored 9 research plans, 12 discussion guides, and 9 synthesis reports across the year; owned the insights-repository taxonomy in Dovetail across 230 atomic insights and 14 studies." If you've outsourced one of these (e.g., screener written by the recruit vendor), don't claim it. The interview probes artifacts.
13. Every recent study names the decision the study informed.
UXR bullets without a downstream decision are the second-most-common failure mode. Decision-impact framing is what distinguishes mature UXR resumes from study-execution-only resumes [3][12]. Patterns that pass: "synthesis surfaced 4 task-failure patterns that drove the team to delay launch one sprint and rebuild the role-assignment flow," "segmentation study identified 3 latent segments that the PM and design partners adopted as the H2 prioritization unit," "diary study insights led the team to falsify the original feature hypothesis and pivot the roadmap." If a study bullet has no downstream decision, ask whether it deserves to be on the resume at all. Per the editorial-truth bar: empty space beats fabrication. If you don't have a clear decision linkage, lean on a different study bullet that does.
14. Bullets show range across qualitative and quantitative work.
Mid-and-senior UXR resumes need range across qualitative and quantitative methods in each recent role [3][4]: Generative qual (interviews, contextual inquiry, ethnographic observation), Evaluative qual (moderated usability, RITE, heuristic evaluation), Survey / quant (survey design, segmentation, statistical analysis, factor analysis), Experimental partnership (A/B test design or review, hypothesis authoring, triangulation with experiment results). All-qual or all-quant resumes get filtered for senior-and-up roles where mixed-methods range is expected. The senior signal is balance — at least one bullet in each domain across the recent 2 years, with depth concentrated in the candidate's strongest method.
15. The UX/UI vs. UXR split is intentional and explicit.
If your background is UX/UI design with a research stretch, the resume should make the split explicit and lead with research. Pattern: 4 study-execution bullets, then 1 closing bullet like "Maintained ~20% IC design capacity on research-artifact stimuli — built study prototypes in Figma and partnered with the staff designer on visual representation of insights." If you've been a pure researcher (no design work), don't fake design bullets — own the research focus. The mistake is mixing UX/UI craft framing with UXR study framing without intentionality, which reads as conflated identity [3][4][5].
16. Education compressed; portfolio link prominently retained.
UXRs more than 5 years out of school should compress Education to 1–2 lines. Degree, school, year. Cut: GPA (irrelevant for UXR regardless of value), coursework, dean's list, undergrad clubs. PhDs in HCI, cognitive science, behavioral economics, sociology, anthropology, and psychology are common on UXR resumes and add legitimate signal — keep the dissertation title in 1 line if relevant. Master's degrees (MHCI, MS in Human Factors) are similarly common; add the program name. The portfolio (or Scholar profile) URL stays at the top of the document. Per Tomer Sharon's It's Our Research framing, the portfolio is where hiring managers verify the researcher still has the craft — study design, synthesis quality, narrative — that the resume bullets only summarize [8].
Stage 4 — UXR Keywords and Mechanics (Items 17–19)
17. Mirror the JD's exact phrasing — title, methods, and tools.
If the JD says "Senior UX Researcher," use that exact title in your summary even if your formal title is different. If the JD says "Quantitative UX Researcher" or "Mixed-Methods Researcher," use those exact phrases somewhere in the resume to pass strict-match Workday and Taleo screens [2][10]. If the JD names specific methods ("contextual inquiry," "diary studies," "RITE"), tools ("Dovetail," "dscout," "Optimal Workshop"), or frameworks ("JTBD," "continuous discovery"), mirror them. The fix: read the JD twice, list the 12–18 highest-frequency methods/tools/process terms, and verify each appears in your resume in canonical form. Tools like Jobscan or Resume Worded automate this comparison [11].
18. Don't claim methods or tools you can't defend in a 30-minute interview.
The ATS rewards method claims; the UXR work-sample punishes false claims hard. UXR hiring loops include questions about study design, recruit criteria, synthesis approach, hypothesis framing, and specific incidents you led through [3][4]. A candidate who lists "diary studies" without ever having run one fails the work-sample interview within five minutes. Limit method and tool claims to what you've actually done. If your sample sizes are 6–9 per study, say so. If your survey work is descriptive-stats only, don't claim factor analysis. The methods don't have to be exotic — they have to be true.
19. Avoid the "kitchen sink methods" dump.
UXR Skills sections should not list every method that exists. A skills line that reads "Usability testing, contextual inquiry, ethnography, diary studies, surveys, card sorting, tree testing, eye tracking, biometrics, MaxDiff, conjoint, Kano, JTBD, RITE, RTE, GOMS, KLM, ..." triggers spam-detection on Greenhouse and Ashby and reads as buzzword-stuffing [1][9]. Pick the 8–12 methods you actually run and ship them deep in experience bullets, not as a flat list.
Stage 5 — Verification and Submission (Items 20–22)
20. Run your resume through Jobscan or Resume Worded against the UXR JD.
Both tools simulate ATS parsing and produce a match score against the specific JD [11]. UXR matches are typically harder than designer matches because the keyword surface is narrower (named methods + named tools + decision language) and level distinctions (UXR vs. Senior UXR vs. Staff UXR vs. Quant UXR) are tighter — target 75%+ match score for UXR roles, with most missing keywords being legitimate method-specificity gaps you can fix by adding sample size and decision linkage to bullets. Under 65% match means the resume needs structural rework before submitting. The 10 minutes of running this check is the single highest-ROI step in the entire submission process.
21. LinkedIn and portfolio match the resume on title, methods, and tenure.
Recruiters at every modern tech company cross-reference both LinkedIn and the portfolio during pre-screen [3][10]. The four checks before submitting: (a) every job title on the resume matches the LinkedIn title exactly (or differs only in a clarifying-prefix way you can defend), (b) every sample size and study count on the resume is consistent with what LinkedIn says about your role and the company headcount, (c) every dated study on the resume falls within your LinkedIn employment dates, (d) the portfolio's case studies are dated within roles where the resume claims you owned them. Inconsistency between resume, LinkedIn, and portfolio reads as a trust failure, and recruiters are explicitly trained to look for it.
22. Final manual parse-test by copying into a plain-text editor.
Open your .docx in Word or Google Docs, select all, copy, paste into TextEdit (Mac), Notepad (Windows), or a plain-text editor. The result approximates what the ATS sees post-parse. Verify: section order is right, bullets aren't scrambled, sample sizes and study counts are intact and correctly attached to their roles, percentage and dollar signs render correctly (no "%" → "â%" artifacts), all links — including the portfolio URL — are still readable as text. If anything looks wrong here, it'll look wrong in the ATS. Fix the source until the plain-text version reads cleanly.
Bonus — UXR Resume Failure Modes Beyond the ATS
Even resumes that pass the ATS can fail the recruiter and hiring-manager screens that follow. Six failure modes specific to UXR resumes:
- The "designer-with-research-curiosity" resume. The candidate has been a UX/UI designer for 4 years and ran a few research projects. The resume blends UI craft and "research" without separating them, so neither identity reads cleanly. Fails the recruiter screen because UXR recruiters at companies with separate research functions filter against the conflation pattern. Fix: pick UXR or designer for the resume identity and frame the other side as context, not as parallel work.
- UX/UI conflation in title or skills. Listing "UX/UI/Research Lead" as a title or "UX/UI Design + User Research" as a skill cluster reads as confused identity. UXR recruiters at top-tier tech companies separate the roles deliberately; resumes that blend them at the title level get filtered. Fix: pick a primary role, frame any cross-discipline work in experience bullets.
- "User researcher" vs. "UX researcher" mismatch with the role. Some companies use "User Researcher" as the canonical title; others use "UX Researcher" or "Design Researcher." Workday and Taleo strict-match on the canonical title. Fix: read the JD, mirror the company's title language in your summary line and (where defensible) in your most recent role title parenthetical.
- No method specifics. "Conducted user research to inform product decisions" appears once and is treated as decoration; appears in every bullet and the resume reads generic. Fix: name the method, name the sample size, name the recruit, name the decision in every recent study bullet.
- No quantitative depth (or no qualitative depth) framing for mixed-methods roles. Pure-qual or pure-quant resumes get filtered for senior+ mixed-methods JDs. Fix: name the partnership pattern (paired with quant UXR on triangulation; paired with qual UXR on synthesis) honestly so the recruiter knows what mixed-methods looks like for this candidate.
- No decision linkage. The resume describes 8 studies but never names a downstream decision. Reads as study-execution without business connection — and decision-influenced is one of the highest-signal phrases for senior+ UXR. Fix: for every recent study bullet, append the decision it informed (delayed launch, killed feature, repriortized roadmap, falsified hypothesis, validated direction).
BLS Context and Honest Disclosure
BLS does not publish a UX-Researcher-specific occupational code. The closest official proxies are SOC 19-3032 Industrial-Organizational Psychologists ($109,840 median annual, May 2024) for the qualitative-research / human-factors lineage, and SOC 15-1255 Web and Digital Interface Designers ($98,540 median annual, May 2024) for the digital-product lineage [5][6]. Both undershoot what mid-and-senior UXR roles pay at top-tier tech companies; levels.fyi tracks UXR and Quantitative UXR comp at Meta, Google, Stripe, Airbnb, and Atlassian separately and consistently above the BLS proxies [7]. Cite levels.fyi for tech-comp realism and BLS for the official occupational framing — and don't fabricate a "median UXR salary" number. There isn't an authoritative one.
FAQ
How do I handle a UX/UI-to-UXR pivot on my resume?
Frame the design stretch as deliberate background and recent UXR work as primary identity. Pattern: "UX/UI Designer (2018–2022) on the consumer-product team, with growing research ownership in the last 18 months — moved into a dedicated UXR role in 2023 as the team established a research function." Lead the recent role with study-execution bullets; cite the design background once in the summary as context. Recruiters at modern tech companies (Stripe, Notion, Linear, Anthropic) read deliberate pivots as senior-curiosity signal, not as a red flag — but only when framed as deliberate and when recent UXR work carries the weight.
I'm applying to my first UXR role from a related field — what goes on the resume?
Surface every proto-research element from your prior work, framed in UXR-resume language. Adjacent fields that translate well: psychology research (named studies, IRB experience, qualitative coding), market research (segmentation work, panel management, survey design), data analytics (experimental design, A/B test analysis, descriptive vs. inferential framing), service design (contextual inquiry, journey mapping). Erika Hall's Just Enough Research Chapter 1 is the canonical scaffolding for the framing shift [3]. Then run the resume through Jobscan against a UXR JD; aim for 70%+ match by adjusting bullets to mirror the JD's method and tool language.
How many years of UXR experience do I need for "Senior UXR" titles?
The honest range is 4+ years of sustained mixed-methods UXR work for "Senior," with at least 6 end-to-end studies that influenced documented product decisions and at least one cross-team or roadmap-influencing study. Below that mark, "Senior UXR" reads as inflated even if the company gave you the title. Above 6 years with one stretch of cross-org research-portfolio ownership, "Staff UXR" becomes the next step. levels.fyi tracks these tenure expectations across top-tier tech companies clearly [7].
Should I list sample sizes for every study on the resume?
Yes, when the numbers are real and you can defend them. "9 moderated usability sessions" or "320-respondent survey" or "18 generative interviews" are all strong bullets when the underlying numbers are accurate. The editorial bar: cite numbers you can defend in a hiring-manager interview, and skip the metric if the underlying data is shaky. An unsourced sample-size claim that a hiring manager probes and you can't substantiate damages the entire resume's credibility — empty space beats fabrication.
Do I need a portfolio as a UX researcher?
Increasingly yes for senior-and-up roles, especially at top-tier tech companies. The portfolio is where hiring managers verify research craft — study design, synthesis quality, narrative ability, decision-impact framing. 2–4 deep study writeups (anonymized as needed) is plenty; depth beats breadth. Tomer Sharon's It's Our Research framing of the research-as-craft surface is a useful reference for what to include [8]. Without a portfolio, the resume needs to carry more weight on every bullet — and the work-sample stage of the interview becomes the gating signal.
How do I handle a layoff on my UXR resume?
Don't put "laid off" on the resume itself — that's interview-conversation context, not resume copy. Instead, end the role at the layoff date and let the date do the work. If the gap is more than 6 months, name what you did during the gap (consulting, research advisory, writing, panel work, sabbatical) in 1 line. Recruiters at modern tech companies read 2022–2024 research-team layoff gaps as market signal, not candidate signal, especially when the layoff coincided with widely-reported research-org reductions at the company. The framing matters more than the gap length.
Should I list academic publications on a UXR industry resume?
Yes, briefly, if you have CHI, CSCW, or peer-reviewed publications in HCI or behavioral fields. A "Selected Publications" section with 2–4 entries (full citation, link to Scholar) signals research depth that industry-only candidates can't match. Don't list every poster or workshop submission — pick the strongest peer-reviewed work. For PhDs transitioning to industry, this section often does the heaviest lifting on the resume.
How do I show research-democratization or ResearchOps leadership on a UXR resume?
Democratization and ResearchOps work are senior signals because they indicate the researcher has thought about scale, governance, and research-quality maintenance — not just study execution [14]. Patterns: "Owned the research democratization program (workshops + templates + study-design rubric) for 18 PMs and designers, with documented gate criteria for when a question warrants UXR-led versus self-serve," or "Built the ResearchOps function (panel, recruit vendor management, repository taxonomy, NDA workflow) across 4 product teams." Pair with metrics: program participants, self-serve study count, repository tagging volume. Kate Towsey's Research That Scales is the canonical reference for this work [14].
References
[1] Greenhouse Software. "Sourcing and Filtering Best Practices — Greenhouse Help Center." https://support.greenhouse.io/hc/en-us/articles/360051506331-Sourcing-best-practices
[2] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html
[3] Erika Hall. Just Enough Research (A Book Apart, 2nd ed. 2019). https://muleshq.com/just-enough-research
[4] Nielsen Norman Group. "When to Use Which User-Experience Research Methods." https://www.nngroup.com/articles/which-ux-research-methods/
[5] U.S. Bureau of Labor Statistics. "Industrial-Organizational Psychologists (SOC 19-3032)." https://www.bls.gov/oes/current/oes193032.htm
[6] U.S. Bureau of Labor Statistics. "Web and Digital Interface Designers (SOC 15-1255)." https://www.bls.gov/oes/current/oes151255.htm
[7] levels.fyi. "UX Researcher Compensation by Level." https://www.levels.fyi/t/user-experience-researcher
[8] Tomer Sharon. It's Our Research: Getting Stakeholder Buy-in for User Experience Research Projects (Morgan Kaufmann, 2012). https://tomersharon.com/its-our-research/
[9] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing
[10] LinkedIn Talent Solutions. "Recruiter Search Best Practices." https://business.linkedin.com/talent-solutions/recruiter
[11] Jobscan. "ATS Resume Test — Run Your Resume Through Our Free Scanner." https://www.jobscan.co/
[12] Maze. "UX Research Methods and How to Choose Them." https://maze.co/guides/ux-research/methods/
[13] Nielsen Norman Group. "User Experience (UX) vs. UI: What's the Difference?" https://www.nngroup.com/articles/ux-vs-ui/
[14] Kate Towsey. Research That Scales: The Research Operations Handbook (Rosenfeld Media, 2024). https://rosenfeldmedia.com/books/research-that-scales/
