Pre-Screening Interview Questions to Ask a User Experience (UX) Researcher

Last updated on

Product teams hire UX researchers to stop shipping on opinion. These questions separate researchers who choose a method to fit the question from those who run the same usability test regardless of what is being asked.

TL;DR, what to screen for

The best pre-screening questions for a UX researcher test four things: whether they choose methods to fit the question rather than habit, whether they have run studies on real products with real users, whether they separate what they observed from what they concluded, and whether their findings survive a stakeholder who disagrees. Ask about a study whose findings were ignored. Every researcher has one.

  • Method fits the question
  • Studies on real products
  • Observation versus inference
  • Findings that survive

Why pre-screen UX researchers before the portfolio review

UX research portfolios reward presentation, and presentation is not the skill you are hiring. A well-designed slide showing personas and a journey map tells you nothing about whether the recruitment was sound, whether five participants supported the conclusion drawn, or whether the researcher noticed that the moderator had led every session. A short screen gets at method and reasoning before the portfolio review, where the artefacts tend to dominate the conversation.

What actually matters when screening User Experience (UX) Researcher candidates

  1. 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.

  2. 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.

  3. 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.

  4. 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 User Experience (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 fits the question

3 questions
  1. 01What UX research methodologies are you familiar with, and how do you choose between them?

    Listen for

    Methods matched to question type, with a clear split between finding problems and measuring how common they are, plus one they deliberately avoid.

    Runs usability tests regardless of the question, or lists methods with no basis for choosing between them.

  2. 02Describe a time you had to adjust your research method partway through a project.

    Listen for

    A specific change with the trigger named: recruitment failing, the question shifting, or early sessions showing the protocol was not working.

    Runs the planned study regardless of what early sessions reveal, or changes method with no stated reason.

  3. 03What does a typical user interview process look like for you?

    Listen for

    A protocol with open questions, awareness of leading, and a habit of asking about past behaviour rather than future intentions.

    Asks participants what they would like or would use, or has no guard against leading them toward an expected answer.

Studies on real products

3 questions
  1. 04Can you give an example of a research project you led, and what came of it?

    Listen for

    A study on a shipped product with the decision it changed, plus their own role separated from the rest of the team's contribution.

    Coursework or speculative projects only, or a study that produced a report and changed nothing.

  2. 05Have you conducted remote user testing? Can you describe how you ran it?

    Listen for

    Real remote practice with the specific difficulties named: recruitment quality, connection failures, and reading hesitation without seeing the room.

    Treats remote as identical to in-person, or has no view on how remote recruitment introduces bias.

  3. 06Have you ever conducted a UX audit? Can you discuss that experience?

    Listen for

    A heuristic review with findings prioritised by severity, and honesty that an audit is expert opinion rather than evidence from users.

    Presents audit findings as user research, or produces a long undifferentiated list with no prioritisation.

Observation versus inference

3 questions
  1. 07Can you discuss your experience with qualitative and quantitative data analysis?

    Listen for

    A coding process for qualitative data with some check on their own bias, plus a clear sense of what their sample size can and cannot support.

    Reports percentages from five participants, or codes interviews alone with no second reader and no audit trail.

  2. 08How do you go about defining user personas?

    Listen for

    Personas grounded in collected data with behaviour as the axis rather than demographics, plus a view on when personas are not worth building.

    Builds personas from stakeholder assumptions, or produces demographic profiles with no behavioural evidence behind them.

  3. 09How do you ensure participant privacy and ethical practice in your research?

    Listen for

    Consent that covers recording and retention, data minimisation in practice, and a case where they stopped or altered a session for a participant's sake.

    Consent treated as a form to sign, or recordings retained indefinitely with no stated policy.

Findings that survive

3 questions
  1. 10Have you been in a situation where stakeholders disagreed with your findings? How did you handle it?

    Listen for

    A real disagreement with how they responded: showing raw sessions, inviting the stakeholder to observe, or conceding where the objection was fair.

    Repeats the findings more firmly, or abandons the conclusion entirely as soon as someone senior objects.

  2. 11Are you comfortable presenting and articulating research findings to stakeholders?

    Listen for

    Findings framed around the decision at hand, with severity and confidence stated, rather than a chronological walkthrough of the study.

    Presents method before findings, or reports everything observed with no prioritisation for the audience.

  3. 12How do you collaborate with designers, product managers and engineers during a project?

    Listen for

    Team members brought into sessions as observers, plus a way of getting findings in front of people early rather than in a final report.

    Works in isolation and delivers a report at the end, or has never had a designer watch a session.

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.

  1. 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.

  2. Real casework

    25%

    5Describes specific studies end to end with participant numbers, timelines, tooling, and the shipped design change each one triggered.

  3. Interpretation and judgement

    25%

    5Separates observation from inference, quantifies confidence, and cites a case where evidence contradicted their own or a stakeholder's hypothesis.

  4. 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 portfolios reward presentation, which is not the skill being hired. A one-way video screen lets you hear how a candidate chooses methods and defends findings before the portfolio review.

Try it on Hirevire

Screening 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 choose methods, how they recruit, and how they handled a stakeholder who rejected their findings, before a portfolio review anchors on artefacts.

Should the screen replace the portfolio review?

No, it should come first and change what you ask in it. Once you know how a researcher reasons about method and evidence, the portfolio review can focus on the decisions behind the artefacts rather than the artefacts themselves.

Evaluating answers

What is the strongest signal when screening a UX researcher?

Clean separation of observation from inference. Strong candidates say what participants did, then what they concluded, and mark the gap between the two. Researchers who report conclusions as if they were observations will overstate findings the same way in your team.

How do I judge answers about small sample sizes?

Look for a defensible rationale rather than a rule. Five participants is fine for finding usability problems and useless for estimating how common something is. A researcher who knows which claims their sample supports is the one you want.

Go deeper on this role

Sanat Hegde
Sanat Hegde
Founder, Hirevire

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

Trusted by 500+ Companies

Screen User Experience (UX) Researcher candidates on Hirevire

Turn this question list into an async video screen in minutes. Every applicant answers the same method, recruitment and stakeholder questions on camera, so you can compare reasoning rather than slide craft.