UX Researcher CV Example and Writing Guide for 2026
Updated 25 June 2026
A strong UX researcher CV connects research activity with the decisions and improvements that followed. This guide shows how to structure that evidence, sharpen your personal statement and turn routine duties into convincing achievement bullets.
Ux Researcher CV examples
Junior UX Researcher
JuniorJunior UX Researcher with experience supporting mixed-method studies for digital services. Comfortable defining research questions, conducting interviews and usability tests, analysing survey data and turning findings into practical recommendations for product and design teams.
Why it works: This example connects early-career research experience to clear study methods, practical findings and measurable product decisions.
Mid-level UX Researcher
Mid-levelUX Researcher with four years of experience planning qualitative and quantitative studies for digital products and services. Skilled in study design, interviews, usability testing, surveys and synthesis, with a record of turning evidence into practical decisions for product managers, designers and developers.
Why it works: This example connects mixed-method research to product decisions, accessibility improvements and measurable delivery outcomes without overstating leadership seniority.
Senior UX Researcher
SeniorSenior UX Researcher with nine years of experience planning mixed-method studies, turning complex evidence into clear product decisions and building practical research standards. Works closely with product managers, designers, developers and data specialists, with particular strengths in inclusive research, stakeholder readouts, mentoring and research repository ownership.
Why it works: Shows research leadership, mixed-method expertise, inclusive practice and clear evidence that findings changed product decisions at scale.
How to write an ux researcher CV
Use a clear, reverse-chronological CV with simple headings and restrained formatting. Two pages usually gives an experienced candidate enough room, while a recent graduate may need only one. Put contact details first, followed by your personal statement, skills, experience, education and any relevant extras. Avoid a photo, date of birth, graphics and rating bars.
| Section | What to include |
|---|---|
| Personal statement | Your level, strongest research methods, product context and one credible outcome |
| Skills | Research methods first, followed by the tools you can use confidently |
| Experience | Studies conducted, participants or product areas covered, decisions influenced and measured results |
| Education | Award, institution and dates, plus relevant project detail if you have limited experience |
| Extras | Relevant volunteering, languages, talks or publications only |
Keep the personal statement to a compact paragraph. Mention only a handful of tools you use regularly; place the fuller tool list in a dedicated skills section. For experience, lead each bullet with an action and explain what changed after the research. UX researchers commonly define research questions, choose suitable data-collection methods and combine qualitative and quantitative approaches, so make the evidence specific rather than listing "user research" repeatedly.
Tailor the skills section to the vacancy's language where it truthfully matches your background. Present education briefly once professional experience carries more weight. Recent graduates can give more space to a dissertation, placement or portfolio study, but should explain their own contribution and the research decision it supported. Extras belong at the end and should earn their space.
Personal statement examples
UX researcher with four years' experience planning mixed-method studies for digital services, from research-question definition and participant recruitment through synthesis and stakeholder readouts. Led 18 moderated interviews and a 420-response survey that helped a product team simplify onboarding, contributing to a verified 12% reduction in first-session abandonment.
Hard-working UX researcher looking for an exciting new role. I am a good communicator, enjoy working with people and have experience with many research methods and tools. I work well independently or in a team and always deliver excellent results.
Writing your experience
Treat every experience bullet as a small piece of evidence. Start with what you did, add the scope, then state the decision or result that followed. A useful pattern is: action + research scope + finding or decision + defensible metric. The metric does not have to be commercial. Participant numbers, study cadence, product areas covered, recruitment time, adoption of recommendations and frequency of stakeholder briefings can all show scale.
| Duty-led wording | Evidence-led rewrite |
|---|---|
| Conducted user interviews | Planned and moderated 16 user interviews across two customer groups, identifying three onboarding barriers that informed the next design iteration |
| Presented research findings | Delivered fortnightly research readouts to 14 product, design and engineering stakeholders, securing agreement on five prioritised usability fixes |
| Carried out usability testing | Tested two checkout prototypes with 12 participants, uncovering four recurring issues before launch and helping reduce task completion time by 18% in the validated revision |
The stronger versions show ownership and a consequence. They also separate the research activity from the result, which makes the candidate's contribution easier to understand. UX research work may cover participant recruitment, interviews, surveys, contextual inquiry, workshops and usability testing. Choose the methods that genuinely match each role rather than cramming every technique into one bullet.
Use verbs that describe the work precisely: planned, scoped, recruited, moderated, interviewed, surveyed, observed, tested, analysed, synthesised, mapped, prioritised, presented, influenced and mentored. Reserve "led" for work where you owned direction or delivery. Senior candidates should show how research shaped priorities, established practice or helped colleagues develop; junior candidates can draw on placements, academic projects and adjacent work if they make their own role clear.
Numbers need context. "Improved completion by 20%" is weaker if the reader cannot tell what was tested or how the change relates to your research. Link the figure to a named task, product stage or team decision. Never estimate a result after the fact. If no outcome was measured, report the verified scale and concrete decision instead.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
List education in reverse-chronological order with the exact award, institution and completion year. A recent graduate can add one or two lines on a relevant dissertation or project, especially where it demonstrates research planning, method selection, analysis or usability testing. Experienced candidates should usually keep this section shorter because their employment evidence carries more weight.
For the Level 6 integrated degree route, the BA Digital User Experience (UX) degree or BSc Digital User Experience (UX) degree is listed as a mandatory qualification within that specific route. This is conditional route information, not a universal entry requirement for every UX researcher role. If it applies to you, record the exact degree title and route without implying that every employer asks for it.
Short courses in Optimal Workshop, Lookback or SPSS may be useful, but they are optional. Include one only when you completed it and it supports the vacancy or work shown elsewhere in the CV. Give the course name, provider and completion year accurately. Do not describe tool familiarity as a certification, and do not pad the section with unrelated online courses.
Common mistakes to avoid
Listing research methods without showing why each method was chosen or what decision it informed.
Connect the research question, chosen method and resulting decision. For example, explain whether interviews clarified motivations, a survey tested the reach of a pattern or usability sessions exposed problems before launch.
Describing studies as activities rather than showing what changed after the findings were shared.
Write each experience bullet around an outcome. State the scope of the study, the insight produced and the product, design or service decision that followed. Add only figures you can defend.
Packing the personal statement with every platform and technique used across a career.
Mention only a small selection of research tools used regularly in the personal statement. Put the fuller, clearly grouped inventory in a dedicated technical skills section.
Treating participant recruitment as an administrative footnote.
Show the audience, recruitment scope and study context where these details are safe to disclose. This helps the reader understand whether the sample matched the research question.
Writing only about collaboration, with no evidence of communicating findings clearly enough to shape decisions.
Name the audiences who received the findings and explain what they did next. Where relevant, quantify the cadence of readouts or the number of stakeholder groups briefed.
Using broad claims about empathy or being user centred without evidence of inclusive research practice.
Give a compact example of how the research considered different user needs and how the findings helped improve the accessibility or inclusiveness of a digital service.
Junior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with transferable research experience, the methods practised through study, placements or projects, and the type of product question you can investigate. | Lead with research leadership, the scale of decisions influenced, regular research readouts, mentoring and ownership of shared research knowledge. |
| Study ownership | Show that you can turn a focused question into a sensible study plan, recruit suitable participants and carry out the selected method with care. | Show ownership of a research programme across several product areas, including how priorities were agreed and how mixed methods answered connected questions. |
| Methods evidence | Use a few well-explained examples of interviews, surveys, contextual inquiry or usability testing. Depth is more convincing than a long unproven list. | Demonstrate judgement across qualitative and quantitative approaches, including why methods were combined and how the evidence resolved uncertainty. |
| Impact | Trace findings to a specific prototype revision, usability fix or clearer understanding of user behaviour. Use modest figures that can be verified. | Connect research to decisions made across teams, repeated improvements or changes in product direction. Quantify study reach, stakeholder communication or adoption where defensible. |
| Collaboration | Describe productive work with designers, product managers, developers or other researchers and make your own contribution easy to identify. | Show how you set priorities with several disciplines, handled competing research needs and helped teams act on findings rather than merely receiving them. |
| Leadership | Include peer support, workshop facilitation or careful documentation when these are genuine, but keep the emphasis on sound research delivery. | Give evidence of mentoring junior researchers, running research reviews and improving access to reusable findings through stewardship of a research repository. |
Frequently asked questions
Keep it long enough to prove method choice, study scope and research impact without repeating yourself. Most readers will get more value from a selective reverse-chronological account than from a catalogue of every project, tool or workshop.
Use university work, placements, volunteering or self-directed projects that involved a genuine research question. Explain the method, participants, analysis and resulting recommendation, while labelling project evidence honestly and using only figures you can support.
No. A British-style CV does not need a photo or date of birth. Use the space for a concise personal statement, research skills and evidence of how your work informed a decision.
Prioritise the methods and analytical abilities you can demonstrate through experience, such as study design, interviews, surveys, contextual inquiry, usability testing, synthesis and communication of actionable insights. Match the wording to the vacancy without claiming experience you do not have.
Translate earlier work into research evidence: defining questions, interviewing people, analysing qualitative or quantitative data, facilitating workshops, presenting findings or working with stakeholders. Then show how those abilities apply to a user or product question rather than relying on a generic claim of transferable skills.
No. In the personal statement, name only a handful of tools or tool categories used in day-to-day research. Put the fuller list in a technical skills section, group it by purpose and remove software you could not discuss confidently in an interview.