Think back to that second pass I mentioned. This is the moment the decision is reached, the final
checkpoint ahead of an interview. The recruiter slows down and works through it more closely, and even so
your current role still accounts for 95% of the screen.
And that makes sense: your current role is the clearest view into the level you work at, what you
actually ship, and how your weeks run. To win the "yes", this entry must span the
full role profile for a UX Researcher, giving each area you named under Domain
Expertise in the Profile Summary a dedicated bullet.
1
Research Planning & Study Design
Plenty of research resumes halt at "ran some studies" and call it done. What a hiring
manager is really after is planning judgment: the research questions you scoped, the method you picked and why, a
sampling plan that held up, and a study plan that earned stakeholder buy-in. Name the question you framed
and the decision your design de-risked.
Techniques
Research questions
Method selection
Study plans
Sampling
Tools
Research briefs
Notion, Confluence
Dovetail
Metrics
Studies scoped
Study turnaround
Decisions informed
2
Qualitative Research
Qual is the spot where mid-level researchers get vague. Show that you draw real meaning from people instead of just logging quotes:
interviews you moderated and synthesized, a usability session you ran, contextual inquiry you did in the field, and a
diary study you fielded over weeks. Name the behavior you uncovered along with
the decision it shifted.
Techniques
User interviews
Usability testing
Contextual inquiry
Diary studies
Tools
Dovetail, UserTesting
Zoom, Lookback
Maze
Metrics
Sessions moderated
Themes surfaced
Decisions influenced
3
Quantitative & Survey Research
Vague lines like "sent out a survey" fall flat here; the manager wants a real measurement
story. Point to the instrument you designed and the question it answered (a survey you wrote clean enough to trust, a
behavioral analysis you ran across segments, not just "pulled some numbers"). A finding tied to significance lands
hard, since the figure carries the argument for you.
Techniques
Survey design
Behavioral analytics
Statistics
Segmentation
Tools
Qualtrics, Typeform
Amplitude, Mixpanel
GA, SPSS
Metrics
Sample size
Statistical significance
4
Recruiting & Research Ops
This area rides on two things: how reliably you source the right participants and how smoothly you keep the research
machine running. Walk the manager through the panel you assembled, the screeners and incentives you set, and one ops win that held
(a recruiting pipeline you accelerated, a repository you launched so studies became reusable). Dropping
"recruited participants" onto the page on its own, with nothing behind it, leads nowhere.
Techniques
Participant recruiting
Panels & screening
Incentives
Repository
Tools
User Interviews
Respondent, Ethnio
Dovetail
Metrics
Recruit time
Panel size
No-show rate
5
Synthesis & Insight Generation
Hardly any signal tells a mid-level researcher apart from a senior this clearly. Point to the affinity map you built, the coding scheme you ran over raw
transcripts, and the framework or journey map that pulled scattered notes into one coherent story. An insight wired to a decision, or
a finding that reshaped the roadmap, beats "wrote up some notes" every time.
Techniques
Affinity mapping
Coding & tagging
Frameworks
Journey maps
Tools
Dovetail
Miro, FigJam
Notion
Metrics
Insights shipped
Decisions influenced
Research adoption
6
Evaluative & Usability Testing
This is the area where the strongest research candidates pull ahead of the pack. Show the moderated test you ran or the
unmoderated study you fielded, the benchmark you set, and a usability problem you flagged early so it never shipped (a flow you measured, a SUS
score you watched release over release). Listing "did usability testing" on its own, with nothing supporting it, wins
you nothing on a skills line.
Techniques
Moderated testing
Unmoderated testing
Benchmarking
SUS
Tools
Maze, UserTesting
Lookback
Hotjar
Metrics
Task success rate
Time-on-task
SUS score
7
Stakeholder Influence & Storytelling
Almost nothing separates mid from senior as cleanly as this. The readout you delivered, the report you wrote so it actually got read, and the
highlight reel you cut, each one carrying evidence into the room so the team moves on data instead of opinion. A study nobody acted on barely helps you; name the decision you swung, the team you brought along,
or the research practice you opened up to others.
Techniques
Readouts
Reports
Driving decisions
Democratization
Tools
Dovetail, Notion
Slides, Figma
Confluence
Metrics
Decisions influenced
Research adoption
Readouts delivered
Stakeholder reach
8
Strategic & Continuous Research
Researchers earn the promotion when they lift the whole team's evidence base, not just close their own tickets. A foundational study you
ran ahead of the roadmap, a generative program you stood up, a research roadmap you set with leadership, and a real example where a
whole class of product questions stopped being guesswork because continuous research was always running.
Techniques
Foundational research
Generative research
Research roadmap
ResearchOps
Tools
Dovetail repository
Notion, Jira
Continuous discovery
Metrics
Roadmap bets de-risked
Research cadence
Repository reuse