Data Analyst mock interview questions
20 questions a Data Analyst panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. SQL screen plus a business case round for data analyst interviews.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Weekly active users dropped eleven percent week over week. The head of product is asking you in Slack what happened. Talk me through what you do first, and what you say back.
[Your answer. Claire adapts follow-ups to what you say]
Scored on a rubric tailored to Data Analyst interviews
Answer one real Data Analyst question now
A question a Data Analyst panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“Weekly active users dropped eleven percent week over week. The head of product is asking you in Slack what happened. Talk me through what you do first, and what you say back.”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
20 data analyst mock interview questions
The questions a Data Analyst panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
Weekly active users dropped eleven percent week over week. The head of product is asking you in Slack what happened. Talk me through what you do first, and what you say back.
Why they ask it: The signature data analyst case. The interviewer is testing whether you check the data before you explain it, and whether you segment rather than guess. Candidates who start listing causes without ruling out an instrumentation break fail here.
A strong answer: Rule out the boring explanations first: a tracking or pipeline change, a definition change, a partial week, a bot filter. Then cut the drop by platform, region, new versus returning and acquisition channel to find out whether it is broad or concentrated. Say what you will send in the next hour versus the next day, and tell the stakeholder what you do not yet know rather than committing to a cause early.
- 2.
Write me a query that returns, for each customer, their second-highest order value. Then tell me what happens if a customer has two orders of the same value.
Why they ask it: The classic SQL screen. It tests window function fluency and, more importantly, whether you notice that ties change the answer depending on which ranking function you reach for.
A strong answer: A window function partitioned by customer and ordered by value descending, filtered to rank two. Then the tie distinction stated explicitly: ROW_NUMBER breaks ties arbitrarily and always returns a row, RANK leaves gaps so rank two may return two customers or none, DENSE_RANK gives the second distinct value. A strong answer asks which definition the business wants.
- 3.
A stakeholder asks you for a dashboard showing revenue by region. What do you ask them before you build it?
Why they ask it: The requirements question. The whole point is whether you treat the request as a solution someone has already picked, and go looking for the decision underneath it.
A strong answer: What decision this changes, who looks at it and how often, what they would do differently if the number went up or down, which definition of revenue (booked, recognised, net of refunds) and which region field (billing, shipping, sales territory). Then the offer to answer the underlying question directly if a one-off analysis would settle it faster than a dashboard nobody maintains.
- 4.
Explain the difference between a LEFT JOIN and an INNER JOIN, and tell me about a time a join silently corrupted your numbers.
Why they ask it: Fan-out from a join against a table that is not unique on the join key is the most common way an analyst ships a wrong number. Interviewers want to hear that you have been burned and now check.
A strong answer: The mechanical difference stated plainly, then a real fan-out story: joining orders to a line-item or address table that had multiple rows per key, and revenue inflating as a result. The habit that came out of it: check row counts before and after a join, confirm grain on both sides, and aggregate to the right grain before joining rather than after.
- 5.
How would you tell whether a change in a metric is real or just noise?
Why they ask it: Analysts are asked to interpret movement every week. The interviewer is checking for basic statistical hygiene without expecting a data scientist's depth.
A strong answer: Compare against normal week-to-week variation rather than the single previous week, look at the same period in prior weeks for seasonality and day-of-week effects, check whether the change is larger than the historical range, and note sample size on small segments. Being willing to say the movement is within normal variation is a strong signal, not a weak one.
- 6.
Tell me about an analysis where you found the answer the requester did not want.
Why they ask it: Tests independence. Analysts sit close to people with strong priors, and the interviewer wants to know whether your conclusion moves with the audience.
A strong answer: The specific finding, how you pressure-tested it before presenting so you were not simply contrarian, how you framed it to the stakeholder (leading with the decision implication rather than the disagreement), and what actually happened. Including the part where you were partly wrong makes it more credible, not less.
- 7.
You have thirty minutes with the executive team and forty slides of analysis. What do you present?
Why they ask it: Communication weighs more than modelling in this role. This question sorts people who report findings from people who drive decisions.
A strong answer: The recommendation first, then the two or three pieces of evidence that carry it, then the caveats that would change the answer. Detail goes in an appendix. A strong candidate names what they would cut and says explicitly that the executive needs a decision, not a methodology walkthrough.
- 8.
How do you handle a metric that two teams define differently?
Why they ask it: Metric drift is a daily reality and a governance question. The interviewer wants to know whether you unilaterally pick one or actually resolve it.
A strong answer: Surface the difference concretely (show both numbers side by side with the definitions), find out why each team defined it that way because usually both are correct for their purpose, get an owner to agree a canonical definition, then document it where people look and make the canonical version the one that is easy to query. Naming the certified-source or metric-layer approach lands well.
Common questions in every interview
These come up in almost every Data Analyst interview regardless of the company or the round.
- 9.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 10.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 11.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 12.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 13.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 14.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 15.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 16.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 17.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 18.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 19.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 20.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Related roles
All Data & analytics →No spam. Unsubscribe anytime.
Ready to practice as a Data Analyst?
Sign up free, no card. 3 full scored interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 887+ roles to choose from
Questions & answers
- Is the Data Analyst mock interview free?
- Yes. 3 full scored Data Analyst interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic Data Analyst job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a Data Analyst job description first, then practice the interview with the same JD for a tighter loop.