Data Analyst mock interview
Answer common data analyst interview questions out loud, from “Tell me about yourself” to how you’d find the cause of a drop in sales, then get feedback on what you said.
- Free, no account
- Answer by voice or by typing
- About 10 minutes
What they assess
What Data Analyst interviews look for
Technical skills
SQL, spreadsheets and a BI or scripting tool. Interviewers want to hear how you get from raw tables to an answer, not just which tools you’ve used.
Business sense
Whether you start from the question the business is asking, and can tell which numbers matter for a decision and which are noise.
Data quality and rigour
How you check data before you trust it: missing values, duplicates, joins that multiply rows, and results that look too good to be true.
Communication
Explaining findings to people who don’t work with data: a clear headline, the right chart, and honest caveats.
Stakeholder management
Handling vague requests, questioning the wrong metric, and prioritising when several teams want reports at once.
Questions
8 common Data Analyst interview questions, and how to answer them
- Opening
Tell me about yourself.
What they’re looking for: A short summary of the analyst you are: the tools you use, the kind of questions you answer, and one analysis that changed a decision.
How to answer: Start with your current role and the data you work with. Give one piece of analysis and what the business did because of it. Finish with why this role is the next step.
- Behavioural
Tell me about an analysis that changed a business decision.
What they’re looking for: That your work leads to action: you understood the question, found something real, and got people to act on it.
How to answer: Set out the question and who asked it. Explain your approach and the main finding in plain terms. End with the decision that was made and, if you know it, the result.
- Behavioural
Tell me about a time you found a problem with the data you were given.
What they’re looking for: Healthy scepticism and a method: how you spotted the issue, confirmed it, and fixed it before anyone relied on the numbers.
How to answer: Describe what looked wrong and how you noticed. Walk through how you traced the cause (a bad join, a tracking change, duplicate records). Finish with how you fixed it and who you told.
- Behavioural
Tell me about a time you explained a technical finding to a non-technical audience.
What they’re looking for: That you can turn analysis into a clear message, choosing what to leave out as carefully as what to include.
How to answer: Say who the audience was and what they needed to decide. Describe how you framed the headline and which chart or example you used. End with how they responded and what they did next.
- Role-specific
Sales dropped sharply last week. How would you find out why?
What they’re looking for: A structured approach: checking the data is right first, then breaking the drop down by segment, channel, region and time until the cause is clear.
How to answer: Start by confirming the drop is real and not a tracking or pipeline problem. Then split it by product, region, channel and customer type, and check for outside causes like a price change or a holiday. Finish with how you’d report what you found.
- Role-specific
How do you approach writing a complex SQL query?
What they’re looking for: A careful working habit: understanding the tables and what one row represents, building the query in steps, and checking the result against something you trust.
How to answer: Describe how you learn the tables before you write anything. Explain how you build up joins and aggregations in stages, checking row counts as you go. End with how you validate the final number.
- Role-specific
How do you decide which chart to use?
What they’re looking for: That you pick visuals for the message and the audience, not for decoration.
How to answer: Say that you start with the point you want the reader to take away. Give examples: a line for change over time, bars to compare categories, a table when people need exact values. Mention what you avoid, such as cluttered dashboards.
- Motivation
Why do you want to work here?
What they’re looking for: That you understand what the business does, what data it relies on, and how your skills would help.
How to answer: Name something specific about the company, its product or its customers. Connect it to the kind of questions you like answering with data. Finish with what you’d bring in your first few months.
More Data Analyst interview questions to practise
- Walk me through your resume and the tools you’ve used in each role.Opening
- Why are you interested in a data analyst role rather than data science or engineering?Motivation
- What kind of data problems do you enjoy most?Motivation
- Tell me about a time you worked with messy or incomplete data.Behavioural
- Tell me about a time a stakeholder disagreed with your findings.Behavioural
- Tell me about a time you automated a report or a manual process.Behavioural
- Tell me about a time you had several urgent requests at once. How did you prioritise?Behavioural
- Tell me about a time you made a mistake in an analysis. How did you handle it?Behavioural
- Tell me about a dashboard you built. Who used it, and what did they use it for?Behavioural
- What’s the difference between an inner join and a left join, and when would you use each?Role-specific
- How would you handle missing values in a dataset?Role-specific
- A manager asks you for “a dashboard of everything”. What do you do?Role-specific
- How would you measure whether a new marketing campaign worked?Role-specific
- How would you explain the difference between correlation and causation to a stakeholder?Role-specific
- What metrics would you track for a subscription business?Role-specific
- What questions do you have about how the data team works?Closing
All 24 questions on this page are in the practice above; each round picks five.
Mistakes to avoid
- Explaining the technique in detail but never saying what the analysis found or what changed because of it.
- Listing SQL, Excel, Tableau and Python without an example of what you did with each.
- Taking a vague request at face value instead of asking what decision the analysis is meant to support.
- Presenting numbers without saying how you checked them or what the caveats are.
Questions
About Data Analyst interviews
How the practice works and what happens to your answers: about this mock interview.
What is a data analyst interview usually like?
Most include a recruiter or hiring manager call, a technical round (often SQL questions, sometimes a take-home task or case study), and a behavioural round about past analysis and working with stakeholders. This practice covers the spoken parts: behavioural questions and talking through your approach.
Will I be asked to write SQL in the interview?
Often, yes, though the format varies: live in a shared editor, in a take-home task, or talking through how you’d write a query. Even when you aren’t writing code, expect to explain joins, aggregations and how you’d check a result.
How technical should my answers be?
Match the listener. With a hiring manager from the business side, lead with the question and what changed. With an analyst or data lead, go further into method. In both cases, finish with the result rather than the technique.