How to Write UX Researcher Resume Bullets That Prove Research Impact

Example output

Illustrative examples only — not real candidate achievements or testimonials.

• Designed and moderated 22 remote usability sessions in UserTesting, measuring task completion rate across 5 core flows; findings drove a navigation redesign that lifted task success from 61% to 83% in follow-up prototype testing.

  UserTesting · task success rate: 61% → 83%

• Built a centralized research repository in Dovetail tagging 400+ interview clips across 14 studies; repository adopted by 5 product squads, reducing duplicated research requests by an estimated 30% over two quarters.

  Dovetail · 30% reduction in duplicate research requests; 5 squads served

• Ran an unmoderated concept validation study in Maze with 210 participants, measuring preference and comprehension scores across 3 homepage variants; highest-scoring variant shipped and increased new-user activation by 18%.

  Maze · 18% increase in new-user activation; 210 participants

• Facilitated 8 co-design workshops using FigJam with cross-functional stakeholders (PM, engineering, customer success), synthesizing 60+ sticky-note clusters into a prioritized opportunity map that anchored the Q3 roadmap.

  FigJam · 60+ insight clusters; 1 roadmap anchored

• Conducted a 6-week diary study with 30 participants tracking daily app interactions, coding 900+ entries in Dovetail; surfaced 4 unmet needs that led to 2 net-new features scoped into the following product cycle.

  Dovetail · 900+ diary entries coded; 2 net-new features scoped

• Ran 12 assistive-technology usability sessions with screen-reader users against a Figma prototype, identifying 9 WCAG 2.1 AA barriers; all 9 resolved before engineering handoff, reducing accessibility-related bug reports by 40% post-launch.

  Figma · 9 WCAG barriers resolved; 40% fewer accessibility bug reports

• Designed a 500-respondent survey in Notion-tracked research plan, applying chi-square analysis to segment satisfaction scores by user cohort; results reframed the PM team's prioritization, moving 2 features from backlog to active sprint.

  Notion · 500 respondents; 2 features reprioritized

The UX Researcher Bullet Formula

Every bullet should answer four questions a hiring manager has when they scan your resume: What research method did you use? How many participants or data points were involved? What did the team learn or change? Which tool supported the work?

A weak bullet reads: 'Conducted user interviews to improve the onboarding flow.' A strong bullet reads: 'Ran 18 moderated interviews in Dovetail, surfacing 3 critical drop-off moments that led the PM team to redesign the onboarding checklist — reducing reported confusion by 34% in follow-up Maze prototype tests.'

Notice the difference: method (moderated interviews), scope (18 participants), insight (3 drop-off moments), stakeholder action (PM redesign), outcome metric (34% reduction), and tool (Dovetail + Maze). Every element earns its place.

Patterns for Study Design and Participant Recruitment Bullets

UX researchers are often the only person on a team who owns participant recruitment and study design end-to-end. Your bullets should reflect that ownership explicitly — not just 'conducted research' but who you recruited, how many sessions you ran, and what screener criteria you set.

For usability studies, name the task completion rate or error rate you measured. For diary studies or longitudinal research, name the duration and cadence. For survey work, name the sample size and the statistical significance or confidence interval if you calculated one.

Example pattern: '[Study type] with [N] participants recruited via [channel], measuring [metric], using [tool].'

If you partnered with a PM or engineer to scope the research question, say so — cross-functional collaboration is a core competency hiring managers look for in this role, and it differentiates a researcher who influences roadmaps from one who just delivers reports.

Synthesis and Insight Delivery Bullets

Many researchers undersell the synthesis half of their work. Collecting data is table stakes; turning it into a decision is the value. Bullets about synthesis should name the affinity mapping or tagging approach, the number of themes or insights surfaced, and — critically — what the team did differently because of those insights.

Dovetail is the dominant repository tool for tagging and clustering qualitative data; if you used it, name it. If you built a research repository that other teams could query, quantify its reach (e.g., 'used by 4 product squads across 2 quarters').

For usability test synthesis, name the severity ratings you applied and how many issues were triaged into the sprint backlog. For survey data, name the analysis method (e.g., regression, thematic coding) and the sample size. Avoid vague verbs like 'shared findings' — replace them with 'presented to,' 'briefed,' or 'co-authored a product brief with' to show the insight landed with a named stakeholder group.

Accessibility and Inclusive Research Bullets

Accessibility is a named skill in this role's competency profile, and it shows up in research work in specific ways: recruiting participants with disabilities, running assistive-technology usability sessions, and auditing prototypes against WCAG criteria before engineering handoff.

If you have this experience, it deserves its own bullet — not a parenthetical. Name the assistive technologies participants used (screen readers, switch access), the WCAG level you tested against, and the number of barriers identified and resolved.

Example pattern: 'Facilitated [N] usability sessions with participants using [assistive technology], identifying [X] WCAG [level] barriers; findings informed [specific design change] before engineering handoff in Figma.'

This type of bullet is rare on researcher resumes and signals both methodological range and values alignment — two things that matter to teams building products for broad audiences.

Frequently asked questions