How to read this UX researcher resume example
The sample above is not a template to copy word for word - copied resumes read as copied. It is here to show the shape of a page that gets past a first screen: one column, standard headings, and bullets that end in an outcome rather than a duty. Research that changed a roadmap, with the decision named.
- Every bullet opens with a verb and carries a number. That is the pattern, not a coincidence.
- The summary makes a claim and then supports it in the first bullet underneath.
- Skills are named tools, not adjectives, and each one appears again in the experience section.
- The earlier role is short. Recent work carries the weight of the page.
The numbers in a UX researcher resume
The most common thing missing from a UX researcher resume is a number. Not because the work had none, but because nobody wrote them down at the time. These are the measures a UX researcher can usually reach for, and the example uses them.
- Ran the study that reframed the roadmap: the top-requested feature was solving a problem users did not have.
- Built a continuous research programme of 8 sessions a month that every product team now recruits from.
- Uncovered the pricing confusion behind 30% of sales objections, which led to a repackaging that lifted conversion 9%.
Before and after: rewriting a weak bullet
Most UX researcher resumes are one edit away from being much stronger, and the edit is the same every time: replace the description of the job with the result of doing it. The pairs below are the same work, written twice.
- Weak: "Responsible for usability testing and related tasks." Strong: "Ran the study that reframed the roadmap: the top-requested feature was solving a problem users did not have."
- Weak: "Worked on interviews projects across the team." Strong: "Built a continuous research programme of 8 sessions a month that every product team now recruits from."
- Weak: "Helped improve processes and supported UX researcher initiatives." Strong: "Uncovered the pricing confusion behind 30% of sales objections, which led to a repackaging that lifted conversion 9%."
Adapting the example to your own history
Work backwards from the posting. Find the two or three things it actually screens for, then make sure the top third of your page answers them. Everything below that is supporting evidence.
- Reorder your bullets so the one closest to the posting comes first in each role.
- Rewrite the summary for the specific job. It is the only part a human reliably reads.
- Cut any skill you would not want to be asked about for ten minutes.
- Keep Usability testing, Interviews, Survey design visible in context, not stranded in a list.