UX Researcher Resume Example & Template (2026)

The U.S. Bureau of Labor Statistics classifies UX researchers under the broader “User Experience Designers” category, which earned a median annual wage of $80,730 in May 2024, with 16 percent employment growth projected through 2034 — nearly four times the average for all occupations. That growth is real, but it hasn’t made the hiring process easier. Most UX researcher roles at mid-size and large companies attract hundreds of applications, and the first filter is an Applicant Tracking System scanning for a specific vocabulary of methods, tools, and deliverables.

A UX researcher resume needs to speak two languages simultaneously: the precise methodological terminology that satisfies ATS keyword matching, and the outcome-oriented narrative that convinces a hiring manager you can move a product team from assumptions to evidence. This page gives you a complete sample resume built on both principles, a section-by-section explanation of every decision, ATS keyword guidance drawn from current job descriptions, and the five mistakes that most reliably knock UX researcher candidates out of the funnel early.

Full Sample Resume

Jordan Mack San Francisco, CA · jordan.mack@email.com · linkedin.com/in/jordanmack · portfolio: jordanmackresearch.com

UX Researcher

Mixed-methods UX Researcher with 5 years of experience at a B2B SaaS company, specializing in qualitative research synthesis and translating findings into product roadmap decisions. Conducted 200+ user interviews and usability tests across desktop and mobile; research directly informed three major product redesigns that reduced user-reported task failure rates by an average of 34%. Proficient in Figma, Dovetail, UserTesting, and Maze. Experienced running research ops for teams of up to 12 designers and PMs.

Experience

Senior UX Researcher | Fieldnote Technologies, San Francisco, CA | January 2022 – Present

• Planned and executed a 6-week discovery study using contextual inquiry and semi-structured interviews (n=28) to map the end-to-end workflow of enterprise project managers; findings surfaced 11 unmet needs that fed directly into the Q3 2024 roadmap, resulting in a new feature set that drove a 19% increase in weekly active users within 90 days of launch.
• Designed and deployed a survey to 1,400 active users to measure satisfaction with a redesigned onboarding flow; combined CSAT scores with session-recording analysis in FullStory to identify three drop-off points, enabling the product team to reduce onboarding abandonment from 41% to 24% over two sprint cycles.
• Ran 14 moderated usability tests per quarter in UserTesting, synthesized findings in Dovetail using affinity mapping, and delivered research reports that reduced design iteration cycles by an estimated 2 weeks per release by front-loading failure modes before engineering handoff.
• Built and maintained a research repository in Dovetail covering 3 years of studies (180+ sessions tagged); the repository cut time-to-insight for cross-functional stakeholders by 60% and reduced duplicated research requests by roughly 30% in the first year of use.

UX Researcher | Arcadia Digital, Oakland, CA | June 2019 – December 2021

• Conducted diary studies (n=12, 3-week duration) to capture in-context behavior of small business owners using an invoicing tool; insights from the study prompted a homepage redesign that increased feature discovery by 27% as measured by click-tracking data.
• Partnered with a data analyst to combine qualitative interview themes with quantitative funnel data in Mixpanel, producing a mixed-methods report that identified why a 22% conversion drop in the free-to-paid upgrade funnel was driven by trust concerns rather than pricing — redirected a proposed A/B pricing test toward social proof improvements instead.
• Facilitated monthly “Research Readout” sessions with product, design, and engineering leads; standardized a one-page findings brief template adopted by three other researchers on the team.

Skills

Usability Testing · User Interviews · Contextual Inquiry · Survey Design · Diary Studies · Journey Mapping · Affinity Mapping · Qualitative Research · Quantitative Research · Mixed Methods · Figma · UserTesting · Dovetail · Maze · FullStory · Mixpanel · WCAG 2.2 · Accessibility Research · Research Operations (ResearchOps) · Stakeholder Presentations

Education

B.S. in Cognitive Science | University of California, San Diego | 2019

Why This Resume Works: Section by Section

Summary

The summary does four things that matter to ATS systems and hiring managers at the same time. First, it names the research mode (“mixed-methods”) — a phrase that appears verbatim in a high percentage of UX researcher job postings. Second, it quantifies scope: “200+ user interviews” gives a recruiter a concrete signal of experience level without requiring them to do math across five bullet points. Third, it names specific tools (Figma, Dovetail, UserTesting, Maze) in a natural sentence rather than a disconnected list — both humans and parsers reward this. Fourth, it closes with a capability statement that scales up: “research ops for teams of up to 12” signals that this candidate can operate beyond individual contributor work.

The summary deliberately avoids generic openers like “passionate about users” or “dedicated professional.” A hiring manager reading 80 resumes in a day skips those phrases on reflex. Opening with a job title and a specific scope forces the reader to engage with substance immediately.

Experience Bullets

Each bullet follows a consistent architecture: what was done (method and scope), what was produced (deliverable or synthesis output), and what happened as a result (outcome tied to a number). This structure satisfies three separate audiences in the hiring process.

The ATS sees method names (“contextual inquiry,” “semi-structured interviews,” “diary studies,” “usability tests”) and tool names (“Dovetail,” “UserTesting,” “FullStory,” “Mixpanel”) distributed naturally across bullets rather than crammed into a skills section.

The recruiter doing the first human screen sees numbers — 19% increase in weekly active users, abandonment reduced from 41% to 24%, 60% reduction in time-to-insight — that distinguish this candidate from one who describes identical activities without outcomes.

The hiring manager or research lead sees research maturity: the candidate knows how to pair qualitative and quantitative methods, can run a research repository, and has experience presenting to cross-functional stakeholders. The diary study bullet is a particularly strong signal because diary studies are logistically complex and appear far less often than usability tests on junior researcher resumes.

Bullet lengths vary intentionally. The longer bullets (2–3 lines) are used for the most complex or high-impact studies where context is required to understand the outcome. One-line bullets would undersell the work and lose the ATS keyword density that longer, structured bullets provide.

Skills Section

The skills section is formatted as a flat, comma-or-dot-separated list rather than a column grid. Some ATS parsers (especially older Taleo implementations) misread multi-column layouts and either scramble the order or drop items entirely. A single-line format with clear separators is the safest ATS-compatible structure.

The list is deliberately split between hard-method terms (usability testing, contextual inquiry, diary studies), tool names (Dovetail, Maze, FullStory), and emerging high-value terms (ResearchOps, WCAG 2.2) that appear with increasing frequency in 2025–2026 job postings, particularly at companies with product accessibility mandates.

Soft skills (“communication,” “collaboration”) are excluded from the skills section entirely. They are demonstrated through bullet point context instead — “facilitated monthly research readout sessions” shows stakeholder communication; it doesn’t just claim it.

Education

The degree is in Cognitive Science, one of the three most common educational backgrounds for UX researchers alongside Human-Computer Interaction and Psychology. The section is kept minimal: degree name, institution, graduation year. A GPA line is omitted because the candidate has 5 years of experience — at that point, employers are evaluating work output, not academic record.

If the candidate held certifications (Nielsen Norman Group UX Research, Google UX Design Certificate), those would appear as a brief “Certifications” subsection here, not as a separate top-level section, to avoid fragmenting the resume’s visual flow.

ATS Keyword Guidance for UX Researcher Roles

UX researcher job descriptions in 2025–2026 cluster around three vocabulary groups. Missing any one of these groups entirely is usually enough to drop below the threshold score in a competitive applicant pool.

Research Methods — These are non-negotiable and must appear verbatim, not paraphrased. The most common terms across postings: usability testing, user interviews, contextual inquiry, survey design, diary studies, journey mapping, affinity mapping, card sorting, tree testing, concept testing. Recruiters will search for the specific methods they need for the role; if your resume says “talked to users” instead of “conducted semi-structured user interviews,” it will score lower even if the activities were identical.

Tools — The specific tool ecosystem varies by company, but the names that appear most consistently across postings are: Figma, UserTesting, Dovetail, Maze, Lookback, Optimal Workshop, Miro, SPSS, and Qualtrics. Match your resume to the tools named in each target posting. If you’ve used a lesser-known equivalent (e.g., a homegrown panel tool instead of UserTesting), note the equivalent in context: “managed participant panels using an internal scheduling tool, equivalent workflow to UserTesting.”

Emerging High-Value Terms — Three areas are appearing in a growing share of 2026 postings that weren’t common two years ago: ResearchOps (the systems and infrastructure around research, not just running studies), mixed methods (the ability to triangulate qualitative and quantitative data rather than operating in only one mode), and WCAG 2.2 / accessibility research (particularly at companies with compliance obligations or public-sector clients). Including these signals research maturity to senior researchers on hiring panels.

Placement Strategy — Put the highest-priority keywords in the summary (where they appear early in the document and weight heavier in some parsers) and in experience bullets (where they appear in natural context). The skills section provides a comprehensive sweep of remaining terms. Avoid listing 40+ skills in a single block — modern ATS implementations including Workday and Greenhouse apply density penalties above roughly 25–30 keywords, and it reads as padding to human reviewers.

5 Common UX Researcher Resume Mistakes

1. Describing process without describing impact

The most pervasive mistake on UX researcher resumes is writing bullets that end at the deliverable: “Conducted 12 usability tests and synthesized findings into a report.” What did the report change? Which design decisions were made differently because of it? How many users were affected? Research that doesn’t connect to product outcomes looks like research for its own sake. Hiring managers at product-led companies specifically screen for researchers who can drive decisions, not just document observations. Every bullet should have an explicit downstream effect, even an estimated one.

2. Omitting quantitative methods

Many UX researchers default to leading with qualitative work because it’s where they spend most of their time. But listing only interviews, usability tests, and diary studies signals a potential gap to teams who expect mixed-methods capability. Even if you’ve only run surveys or pulled basic analytics as a secondary source, those count — include them. Phrases like “combined qualitative interview themes with Mixpanel funnel data” or “triangulated usability test findings with session recordings” demonstrate methodological range that purely qualitative bullets don’t.

3. Listing tools as logos rather than in context

A skills section that reads “Figma, Dovetail, Maze, UserTesting, Lookback, Optimal Workshop, SPSS, Qualtrics, Miro, Notion, Confluence, Slack” tells a recruiter you’ve heard of these tools. Experience bullets that show you used Dovetail to synthesize 180 sessions over three years, or used Maze to run unmoderated tests at a sample size that produced statistical significance, tell them you actually know the tool. Put the most important tools in bullets first; let the skills section sweep up the rest.

4. Ignoring accessibility-related keywords

WCAG 2.2 and accessibility research appear in a measurably higher share of UX researcher postings in 2026, driven by EU Accessibility Act enforcement timelines and growing product accessibility requirements in US enterprise and government contracts. Candidates who don’t include any accessibility-related terminology are invisible to ATS filters on those postings, and they appear less current to senior researchers who consider accessibility fluency baseline in 2026. If you’ve done any screen-reader testing, color contrast evaluation, or inclusive design research, make it explicit on the resume.

5. Using a visually complex template

UX researchers are, reasonably, tempted to demonstrate design sensibility through their resume layout — sidebar columns, icon grids, color-coded sections. These formats consistently underperform in ATS parsing. Multi-column layouts cause Taleo and some Workday implementations to read column two as a continuation of column one, producing garbled text that drops keywords entirely. Icon-based skills sections are invisible to parsers. A single-column, clean document with standard section headers (Summary, Experience, Skills, Education) will always outperform a designed template in the 98% of large-company applications that route through ATS first. Save the visual craft for your portfolio.

Ready to build your own UX Researcher resume? OfferFlow’s resume builder formats your experience into clean, ATS-optimized layouts and checks your content against the keywords from your target job description — so you know before you apply whether your resume will clear the first filter.