Data analyst interview questions: what gets tested and how to answer

The analyst questions that decide the round — how you handle a metric drop, a stakeholder who wants a different answer, dirty data — plus what each is testing.

Data analyst6 questionsUpdated 2026-11-15

Analyst interviews are less about SQL syntax and more about judgement with incomplete data. The strongest signal is whether you can describe a method, a limitation and a decision in the same answer.

Recruiter screenSQL / technical screenCase or take-homeStakeholder / behaviouralHiring manager
Question 1

A key metric dropped 15% overnight. What do you do?

What it is testing
Whether you check data quality before drawing conclusions.
How to answer
Start with instrumentation: tracking change, pipeline delay, definition change. Then segment by dimension to localise it. State the order, because the order is the skill.
Question 2

Tell me about a time your analysis changed a decision.

What it is testing
Whether analysis had an effect, or was a report nobody read.
How to answer
The decision at stake, what you found, who changed their mind, and the outcome. If nobody changed anything, say what you would do differently.
Question 3

A stakeholder wants a different answer from your data. What happens?

What it is testing
Integrity under social pressure.
How to answer
Separate the question from the answer: restate what they want to know, show the sensitivity, and offer the version of the analysis that supports their hypothesis if the data allows it.
Question 4

How do you handle missing or dirty data?

What it is testing
Whether you document assumptions or silently impute.
How to answer
Name the mechanism of missingness, the threshold you set, and how you flagged it in the output. The flag is what protects the decision downstream.
Question 5

How do you decide which metric to put in front of an executive?

What it is testing
Whether you optimise for clarity or for completeness.
How to answer
One primary metric, one guardrail, and a stated risk. Completeness is what makes dashboards unread.
Question 6

Tell me about a time you were wrong about a number.

What it is testing
Whether you check your own work and admit it fast.
How to answer
What you published, how it was caught, how quickly you corrected it, and the check you added. Speed of correction matters more than the error.

Questions people also ask

How much SQL is tested in an analyst interview?

Typically one technical screen with joins, window functions and a data-quality question. Beyond that, interviews test interpretation — the coding part is a gate, not the whole assessment.

Should I bring a portfolio?

Only if it demonstrates a decision, not a chart. One project described as problem, method, limitation and outcome is worth more than five dashboards.

Practise this role

Run a data analyst mock interview.

Questions one at a time, a five-category score, and a rewrite of every answer. Free during the beta.

Start practising
Other roles