Data analyst interview questions usually come in three types: technical questions on SQL and tools, case questions where you work through a business problem, and behavioral questions about how you communicate. Interviewers care as much about your reasoning as your syntax, so talk through your thinking.
For behavioral questions, the STAR method keeps your stories focused on what you did and what changed.
What SQL questions are asked in a data analyst interview?
Expect joins, aggregation, filtering with WHERE and HAVING, and often window functions. A common trap is how a LEFT JOIN interacts with filters and COUNT, so explain your logic before you write the query. If a case question stumps you, our tips for hard interview questions help you think out loud.
To find customers with no orders this year, I'd LEFT JOIN customers to orders and put the date condition in the ON clause, not the WHERE clause. If I filter on the orders table in WHERE, the NULL rows for unmatched customers get dropped, and it behaves like an inner join. Then I'd keep only the rows where the order ID is NULL and count the customer IDs.
How do you handle missing or messy data?
Show that you investigate before you fix, and that you document your choices.
On a churn project at Contoso, about a tenth of accounts had no signup channel. Before filling anything in, I checked whether those accounts were different, and most turned out to come from an old partner system. I labeled them as their own group instead of guessing, noted it in the report, and asked the data engineering team to fix the feed.
How do you explain technical results to a non-technical audience?
Lead with the answer and what it means, then support it with one chart.
When our regional managers asked why repeat purchases dropped, I opened with one sentence: customers who waited more than five days for delivery were much less likely to buy again. I showed a single bar chart by delivery time and suggested two options to test. I kept the regression details in an appendix, and only one person asked to see them.
Tell me about a dashboard you built
Describe who used it, what decisions it supported and what changed.
I built a Tableau dashboard for the support team leads at Fabrikam. I started by asking which decisions they made each morning, and the answer was mostly staffing. So the top row showed ticket volume against forecast and backlog by queue, with drill-downs below. The leads stopped requesting a daily spreadsheet, which saved me about four hours a week.
How would you analyze an A/B test?
Cover the setup, the result and the business decision. Mention practical significance, not just the p-value.
First I'd confirm the test ran its planned length and that traffic split evenly between groups. Then I'd compare conversion rates, check the confidence interval and p-value against the threshold we set in advance, and ask whether the lift is big enough to matter for revenue. If key segments behaved differently, I'd flag that as a follow-up test rather than a conclusion.
How do you check your work before sharing it?
Interviewers want a repeatable habit, not a promise that you're careful.
I reconcile key totals against a trusted source, like the finance close numbers, and check row counts before and after every join. I scan for duplicates, nulls and values outside the expected range. For anything high stakes, I ask a teammate to review the query. That habit once caught a join that was double counting refunds before the report went to leadership.
When do you use Excel, SQL or Python?
Match the tool to the size of the data and how often the work repeats.
I use SQL to pull and aggregate data where it lives, especially for large tables. I switch to Python with pandas when the cleaning is complex or the analysis runs every month, because a script is easy to rerun and review. Excel is still my choice for quick checks on small extracts and for sharing results with people who want to explore the numbers themselves.
Practice more scenario questions in our behavioral interview quiz, and make sure your data analyst resume names the same tools and projects you plan to discuss.