Research synthesis Resume Bullet Points for a UX Researcher
A weak-to-strong rewrite and three fill-in templates for turning research synthesis into a bullet that actually proves it, not just claims it.
Weak vs strong
Responsible for research synthesis as part of daily duties.
Conducted 40+ user interviews across 3 research studies, with findings directly informing 2 shipped product changes
The difference isn't length — it's that the strong version names a scope and a result. "Responsible for X" tells a hiring manager nothing they couldn't guess from the job title.
Fill-in-the-blank templates
- [Action verb] research synthesis for [scope — team size / volume / timeframe], resulting in [measurable outcome].
- Used research synthesis to [specific problem you solved], reducing/improving [metric] by [amount].
- Trained/led [number] people on research synthesis, [specific context or standard achieved].
Pick the one closest to what you actually did, then fill it in with your own real numbers — don't force a template that doesn't fit your actual experience.
Where this fits on a ux researcher resume
Under your most relevant role, in the experience section — not in a skills list, where it can't carry the specificity that makes it convincing. See the full research synthesis skill page for how to also list it for ATS matching.
Frequently asked questions
What if I don't have a hard number for my research synthesis bullet?
Use scale instead — team size, frequency, volume, or timeframe. "Applied research synthesis across a 40-person shift rotation" is still concrete without inventing a metric you don't have.
How many research synthesis bullets should I include?
One strong bullet beats three vague ones. If research synthesis is genuinely central to how you do this job, one clear example under your most relevant role is enough — repeating it across multiple jobs reads as padding.