Why pre-screen UX researchers before the portfolio interview
A research function fails quietly when it becomes a service desk. Teams request studies, the researcher runs them, findings are delivered, and nothing changes because the decisions were made before the request. The researchers who avoid this prioritise: they decline studies whose answer would not change anything and push toward the questions that would. That behaviour is describable in a short screen and almost invisible in a portfolio, which shows the studies that were run rather than the ones that were declined.
What actually matters when screening UX Researcher candidates
- 01
Method and rigour
Check how they choose between generative interviews, diary studies, unmoderated tests and surveys; ask about sample sizing, screener design, task construction, and avoiding leading questions.
- 02
Real casework
Probe actual studies run: participant counts, recruitment via UserTesting or Respondent, tools like Dovetail, Maze or Lookback, and which product decisions changed.
- 03
Interpretation and judgement
Assess synthesis: how they move from transcripts to themes, handle contradictory findings, weigh SUS or task success rates against qualitative signal, and flag low-confidence conclusions.
- 04
Reporting and testimony
Look for readout craft: highlight reels, prioritised recommendations, research repositories, and evidence they held ground with product managers or designers who disliked findings.
Pre-screening questions to ask UX Researcher candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Method and recruitment
3 questions01Can you describe your experience with user research methodologies?
Listen forMethods matched to question types, with a clear split between finding problems and measuring how common they are.
One method used for everything, or methods listed with no basis for choosing between them.
02What is your process for recruiting participants?
Listen forScreening against the actual user profile with awareness of who is easy to recruit and therefore over-represented.
Recruits from existing enthusiastic customers or internal contacts, with no acknowledgement of the bias.
03What steps do you take to avoid your own biases affecting the research?
Listen forConcrete safeguards such as a second coder, non-leading protocols and analysis planned before data collection.
Bias addressed as an intention to stay objective, with no procedural safeguard behind it.
Research that changed direction
3 questions04Can you give an example of research that changed the direction of a project?
Listen forA specific decision that changed, with what the evidence showed and how they got a team to accept an unwelcome finding.
Research that only ever confirmed the existing plan, or influence claimed with no decision named.
05How do you prioritise which user problems to study first?
Listen forCriteria including whether the answer would change a decision, plus a request they declined for that reason.
Runs whatever is requested, or prioritises by whichever team asked most recently.
06How do you measure the success of a research project?
Listen forSuccess defined as a decision made differently, rather than as studies completed or stakeholders satisfied.
Success measured by output volume, or by whether stakeholders liked the findings.
Reconciling conflict
3 questions07How do you handle conflicting feedback from different user groups?
Listen forSegmentation to see whether the groups genuinely differ, with a recommendation rather than both positions reported neutrally.
Reports the conflict without resolution, or averages across groups that want opposite things.
08How do you balance user needs against business objectives?
Listen forA real tension named with how it was resolved, rather than an assertion that good user experience is always good business.
Claims the two never conflict, or advocates for users with no reference to commercial constraints.
09What strategies do you use to ensure inclusivity in your research?
Listen forDeliberate recruitment of participants usually excluded, including disabled users, with a finding that only emerged because of it.
Inclusivity described as an intention, or samples that never include anyone using assistive technology.
Working to deadlines
3 questions10How do you handle tight deadlines when conducting research?
Listen forScope reduced while method stays sound, with the lost confidence stated plainly rather than quietly absorbed.
Refuses to compress under any circumstances, or compresses by dropping rigour without saying so.
11Can you describe your experience with remote user testing?
Listen forReal remote practice with the specific difficulties named, including recruitment quality and reading hesitation without seeing the room.
Treats remote as equivalent to in-person, or no awareness of how remote recruitment skews the sample.
12How do you communicate findings to stakeholders?
Listen forFindings framed around the decision with severity and confidence stated, and delivered early rather than in a final report.
Long reports delivered at the end, or method presented before the audience knows why it matters.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Method and rigour
35%5Matches method to decision stage, defends sample sizes, writes non-leading tasks, and names bias risks in their own past screeners.
Real casework
25%5Describes specific studies end to end with participant numbers, timelines, tooling, and the shipped design change each one triggered.
Interpretation and judgement
25%5Separates observation from inference, quantifies confidence, and cites a case where evidence contradicted their own or a stakeholder's hypothesis.
Reporting and testimony
15%5Delivers concise decision-focused readouts, maintains a searchable repository, and gives an example of persuading a resistant stakeholder with clips and data.
Research becomes a service desk when nobody says no, and portfolios only show the studies that ran. A one-way video screen asks what they declined.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a UX researcher take?
Fifteen minutes across eight to ten questions, answered async. Enough to hear how they prioritise, establish that their recruitment holds up, and find out whether any research of theirs changed a direction.
How does this differ from a research method interview?
Method interviews test whether someone can run a study. This screen tests whether they choose the right study and get it acted on, which is where research functions actually succeed or fail inside a product team.
Evaluating answers
What is the strongest signal when screening a UX researcher?
A study they declined to run. Researchers who prioritise can name a request they pushed back on because the answer would not have changed the decision. Those who run everything requested are operating a service desk.
How do I judge their handling of deadlines?
Ask what they cut when the timeline shortened. The answer you want reduces scope while keeping the method sound, and states plainly what confidence was lost. Researchers who either refuse to compress or quietly drop rigour are both a problem.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
