Interview guide
Data Analyst interview questions
Data analyst interviews test SQL, spreadsheet and BI skills, business understanding and how clearly you communicate findings. Expect a take-home or live case with real-looking data.
Role-specific questions
1.Revenue dropped 10% last week. How would you investigate?
Why they ask: Structured problem solving.
How to answer: Check data quality first, then segment: product, region, channel, new vs returning. Compare to seasonality. Form hypotheses and test the biggest first.
2.What’s the difference between a LEFT JOIN and an INNER JOIN?
Why they ask: SQL fundamentals.
How to answer: Explain with a concrete example, including what happens to unmatched rows and how that can silently inflate or drop counts.
3.How do you choose the right chart?
Why they ask: Communication through visuals.
How to answer: Trends over time → line; comparison → bar; part of whole (few parts) → stacked bar. Avoid 3D and pie charts with many slices.
4.Tell me about an analysis that changed what the team did.
Why they ask: Impact.
How to answer: The question, the data, the finding, and the decision — with a number if you can.
5.How do you make sure your numbers are right?
Why they ask: Trust is an analyst’s currency.
How to answer: Reconcile against a known source, sanity-check totals, peer review queries, and document definitions.
6.How would you define an ‘active user’?
Why they ask: Metric design and business sense.
How to answer: It depends on the product’s core value action and frequency. Propose a definition, its blind spots, and how you’d validate it.
Reading answers isn’t practising them
Get questions built from your résumé and a real job post, answer out loud, and get STAR scoring, follow-up questions and pace feedback. Free to start.
Behavioral questions
Every data analyst interview includes these. Answer with STAR: the Situation, your Task, the Actions you took, and the Result — with a number where you can.
7.Tell me about yourself.
Why they ask: It sets the frame for the whole interview and tests whether you can summarise your career around what they need.
How to answer: 90 seconds: present (current role and one proud result), past (the path that got you here), future (why this role is the logical next step). Skip your life story.
8.Tell me about a time you disagreed with a teammate or manager.
Why they ask: They want to see that you can push back with evidence and still commit once a decision is made.
How to answer: Use STAR. Show how you understood their view, what data you brought, how it was resolved — and what you did if you lost the argument.
9.Describe a project that failed or didn’t go to plan.
Why they ask: Ownership and learning matter more than a perfect track record.
How to answer: Pick a real failure you contributed to. Spend most of the answer on what you changed afterwards — ideally with a later result that proves it.
10.Tell me about a time you had to deliver under a tight deadline.
Why they ask: They’re testing prioritisation and communication, not heroics.
How to answer: Explain what you cut or re-scoped, who you told and when, and the outcome. Mention the trade-off you consciously accepted.
11.What’s an accomplishment you’re most proud of?
Why they ask: It shows what you value and the scale you operate at.
How to answer: Choose one relevant to this role. Make your personal contribution clear (“I”, not “we”) and end with a number.
12.Why do you want to work here?
Why they ask: They want evidence you chose them — not just any job.
How to answer: Connect something specific (their product, a recent launch, how the team works) to your experience and what you want to do next.