Method choice is the centre of it: why this study, this sample, this analysis. Expect to be asked about a finding stakeholders did not want, and what you did about it.
Design loops centre on the portfolio review, and the work is not what is being assessed — the reasoning behind it is. Expect to justify decisions you made years ago to someone who will ask what you rejected.
Practising this out loud matters more here than almost anywhere, because a portfolio you know intimately is very easy to narrate badly under time pressure.
MockLive AI runs a spoken UX Researcher mock interview — behavioral and product sense rounds — with an AI interviewer who asks questions like “Why this method for this question?”, follows up on what you actually say and scores you on a fixed rubric; the first 7-minute interview is free. How it compares with other AI interview tools →
Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.
A balanced round across experience and role-specific topics.
Scored on: User-first framing · Prioritization & execution · Product judgment & influence
Past experience, STAR stories, collaboration, and conflict.
Scored on: User-first framing · Prioritization & execution · Product judgment & influence
You drive: users, pain points, solutions, and metrics.
Scored on: User-first framing · Prioritization & execution · Product judgment & influence
Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.
The gap between these two is most of your score, and it is easier to see than to be told.
“Tell me about a finding stakeholders did not want.”
Reporting that you presented it and they disagreed. It describes an event rather than a skill.
How you made it hard to dismiss — the evidence you chose, who you brought in early, the framing that moved it from criticism to a shared problem — and honestly whether the decision changed. Research that never changes anything is the failure mode of the role.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For UX Researcher roles, a general round runs with Leila — customer insight, prioritization, product judgment, and execution trade-offs. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a UX Researcher interview →Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioural questions and STAR, and system design.
Questions like these: “Why this method for this question?” “How do you size and recruit a sample you can defend?” “Tell me about a finding stakeholders did not want.” “How do you tell a real signal from a loud participant?” “When is qualitative research the wrong tool?” “How do you make research change a decision rather than sit in a deck?”
Expect General / Mixed (A balanced round across experience and role-specific topics), Behavioral (Past experience, STAR stories, collaboration, and conflict) and Product Sense (You drive: users, pain points, solutions, and metrics). Method choice is the centre of it: why this study, this sample, this analysis. Expect to be asked about a finding stakeholders did not want, and what you did about it.
Method chosen by habit, with no defence of why it suits this question. Overclaiming from a small qualitative sample. No answer on influence, so the research has no path to a decision.
Out loud, with someone who follows up. MockLive AI's interviewer for this role asks these questions, pushes back on thin answers and scores you on a fixed rubric, with the transcript and every answer replayable. The first 7-minute interview is free and needs no card.