First: What kind of research capability do you need?
Before evaluating candidates or choosing an engagement model, get clear on what you're actually trying to accomplish. "We need a UX researcher" is a category, not a requirement.
The questions that matter: What decisions should research be informing? Are you in discovery (understanding users and opportunities) or validation (testing designs and assumptions)? Do you need qualitative depth, quantitative measurement, or both? How much of the team's time goes to research questions today? How integrated do you need the researcher to be?
The answers shape which engagement model makes sense, which type of researcher to look for, and how you'll know the hire is working.
Choose the engagement model before you write the JD
The engagement model — embedded full-time, fractional, contract, or permanent — should be decided before you start recruiting. Each looks for somewhat different things and attracts a different segment of the researcher market.
Embedded / contract
A researcher joins your team for a defined period. Good default when you need research moving quickly, you want someone integrated into the team, or you're not ready to commit to a permanent hire. Faster to execute than a permanent search. The researcher typically works on an hourly basis.
Fractional
Defined hours per week or month. Good when research needs are consistent but don't fill a full-time role. Requires a researcher with the discipline and communication skills to stay effective with limited availability. Not all researchers fit this well — screen for it explicitly.
Permanent hire
Right when you're committed to building a research function, research is a permanent part of your product process, and you need someone building institutional knowledge over time. Higher investment, higher return.
Managed / agency
The team you're engaging does the research. You get deliverables. Good for defined projects, external perspective, or when you don't have the infrastructure to support an embedded researcher. See our agency page for more.
What to look for: the profile that actually matters
Research hiring is often done like design hiring — looking for a portfolio, checking educational background, evaluating surface presentation. This doesn't work well for research because:
- Research work is often confidential. Strong researchers have thin public portfolios not because the work was bad but because it lived inside companies.
- A beautiful research deck doesn't tell you about interview quality, synthesis depth, or whether the research actually changed anything.
- The skills that make a great researcher — methodological range, facilitation quality, synthesis depth, organizational navigation — are harder to see than design skills.
What to look for instead:
Professional environments
Where someone has worked tells you a lot about the organizational sophistication, research rigor, and stakeholder complexity they've navigated. A researcher who spent five years at a respected product company has operated in a research environment with standards. That matters.
Research ownership
Did they run studies independently, or did someone else set the agenda and hand them a discussion guide? Can they describe taking a vague product question and turning it into research that actually answered it? Research ownership is a strong signal of senior capability.
Methodological range and reasoning
Ask them to walk through a past study: why that method, what it could and couldn't tell them, what they'd do differently. A strong researcher can have a principled conversation about methodology. An average one defaults to whatever method they're most comfortable with.
Synthesis quality
Ask them to describe how they synthesized a specific study. Not what tools they used — how they moved from raw data to insight. Strong synthesis is analytic, not just organizational. It surfaces tensions, mental models, and implications — not just themes.
Communication and organizational impact
Research that doesn't change decisions is waste. Ask them to describe a time their research changed what the team built. If they struggle to name one, that's worth probing. Ask how they adapt findings for different audiences.
Interview questions that reveal quality
Generic behavioral questions produce generic answers. These work better:
- "Walk me through a research project from brief to delivery — what decisions did you make and why?" (Tests ownership, reasoning, synthesis)
- "Tell me about a time you pushed back on the research question you were given. What happened?" (Tests research judgment, organizational navigation)
- "Describe a study that didn't go the way you planned. What went wrong and what did you do?" (Tests adaptability, honesty, problem-solving)
- "How do you decide when enough research is enough?" (Tests research judgment, pragmatism)
- "What's a research finding you had that stakeholders didn't want to hear? How did you handle it?" (Tests communication, conviction, organizational dynamics)
- "What would you want to know about our users in your first 30 days? How would you find out?" (Tests curiosity, methodological instinct for your context)
The portfolio problem — and how to work around it
Require that candidates come prepared to discuss specific studies in detail, not just walk through a portfolio deck. Ask them to bring one study they're proud of and walk through it — not the polished version, but the actual process, decisions, and outcomes.
Consider a lightweight work sample: give them a real research brief (scrubbed of confidential details) and ask them to come back with a research plan. Evaluate the reasoning, not just the artifact. How did they frame the question? What trade-offs did they name? What did they not include and why?
The Miro UX research guide is a useful benchmark for understanding what rigorous research thinking looks like in practice.
Scoping a role for your specific context
A UX researcher at a 20-person startup is a different job than the same title at a 2,000-person enterprise. Be honest about which environment you are and what you're actually asking for.
At an early-stage company, you want someone who can operate without infrastructure — no research ops, no established recruiting panel, no template library. Someone who builds what they need and gets research done anyway.
At a mature research organization, you want someone who can work within existing systems, collaborate with other researchers, and maybe specialize in a particular method or product area.
Being honest about this in your job description will attract the right candidates and save everyone time.
Setting the engagement up for success
Hiring is the beginning, not the end. Research works best when:
- The researcher has a direct line to the decisions research is supposed to inform. If findings go through two layers of PM before anyone acts on them, that's a structural problem.
- There's a clear understanding of how research gets prioritized. Someone should own the research agenda — either the researcher or a PM/design lead in close collaboration with them.
- The researcher is involved early enough to shape decisions, not just validate them after the direction is locked.
- Findings are shared broadly, not just with the people who commissioned the study. Research insights that sit in one team's hands have limited leverage.
When to use an agency vs. hire someone
If you have a specific project — a product launch, a research gap, a question that needs answering — and you don't need ongoing research capability, a managed approach (agency or consultant) may be faster and more efficient than hiring someone embedded.
If research is part of your ongoing product process — if decisions should be continuously informed by user evidence — you need embedded capacity. That might start as a contract or fractional engagement before becoming permanent.
The wrong call in either direction is expensive: overhiring for a project that ends, or under-investing in capability you need continuously.