Expect experiment design and causal reasoning over model trivia. The recurring trap is a question where the data cannot support a confident answer — saying so, and stating what you would need, is the mark.
Data loops test two things that pull against each other: rigour with methods, and the judgement to know when a rough answer is the right one. Candidates who are strong on one are often visibly weak on the other.
Expect questions where the data is deliberately insufficient. Stating the assumption you are making, and what would change your answer, is most of the mark.
MockLive AI runs a spoken Data Scientist mock interview — behavioral, live coding, system design and technical deep-dive rounds — with an AI interviewer who asks questions like “Design an experiment to test whether this feature increases retention”, 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: Analytical communication · Data & inference rigor · Decision quality
Past experience, STAR stories, collaboration, and conflict.
Scored on: Analytical communication · Data & inference rigor · Decision quality
Solve a coding problem in the editor, out loud.
Scored on: Problem-solving communication · Engineering correctness · Adaptability & craft
How the live coding round works →Architecture, scale, data models, and trade-offs.
Scored on: Technical communication · Engineering depth · Ownership & collaboration
Drill into your resume projects and domain fundamentals.
Scored on: Analytical communication · Data & inference rigor · Decision quality
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.
“The metric moved but the experiment was underpowered. What do you tell the team?”
Reporting the lift. It is the answer stakeholders want and it is the reason this question is asked at all.
Say plainly that the result does not support a confident conclusion, give the range it is consistent with, and state what would settle it — more time, a bigger sample, a different unit of randomisation. The willingness to say 'we cannot know yet' is the mark.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For Data Scientist roles, a general round runs with Marcus — metrics, experiments, causal reasoning, and decisions under uncertainty. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a Data Scientist 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: “Design an experiment to test whether this feature increases retention.” “The metric moved but the experiment was underpowered. What do you tell the team?” “How do you tell correlation from causation with only observational data?” “Walk me through a model you built that did not get used.” “How would you detect that a metric moved for a boring reason?” “What would you need to answer this question properly, that you do not have?”
Expect General / Mixed (A balanced round across experience and role-specific topics), Behavioral (Past experience, STAR stories, collaboration, and conflict), Live Coding (Solve a coding problem in the editor, out loud), System Design (Architecture, scale, data models, and trade-offs) and Technical Deep-Dive (Drill into your resume projects and domain fundamentals). Expect experiment design and causal reasoning over model trivia. The recurring trap is a question where the data cannot support a confident answer — saying so, and stating what you would need, is the mark.
Model trivia in place of experimental judgement. Most of this loop is causal reasoning, not algorithms. Producing a confident number from data that cannot support one. No sense of what the business would do differently depending on the answer.
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.