Data analyst interview questions: 23 questions and a scorecard for interviewers
The short answer
Good data analyst interview questions test SQL and data skills, how the analyst cleans and checks data, how they define metrics, and how clearly they explain findings to people who are not analysts. Ask for real examples, such as a time the numbers didn’t match or an analysis that changed a decision, and listen for how they checked their work and who acted on it. A recruiter screen before the client’s technical round should confirm the tools the client uses, such as SQL, spreadsheets, a BI tool and Python or R, plus work arrangement, right to work, start date and pay expectations. Score every candidate against the same five criteria so the decision rests on evidence.
All 23 questions with why you ask each one, what a strong answer shows and follow-ups, plus the data analyst scorecard and rating guide. Free to download and adapt; no sign-up needed.
When to use these questions
Data analysts turn raw data into answers people can act on, so an interview needs to show how someone gets from a vague business question to a trustworthy number and a clear recommendation, not only which tools they list. The strongest evidence comes from specific analyses: the question, the data, the checks they ran and what the stakeholder did next.
For agency recruiters, the screen before the client’s technical round or take-home task is where to confirm the essentials: hands-on SQL, the spreadsheet, BI and Python or R skills the client needs, experience with similar data and business questions, and the practical facts of work arrangement, start date and pay expectations. Communication can be judged directly in the screen, even by a recruiter who doesn’t write SQL.
23 data analyst interview questions
Grouped by what they test. Pick the questions that match the role, ask every candidate the same ones in the same order, and score each answer against the scorecard below.
SQL and working with data
Ask about real queries and real datasets. How an analyst checks their own results matters as much as the syntax.
Question 1: Walk me through the most complex query you wrote recently. What did it need to answer, and how was it structured?
- Why ask it:
- Tests real SQL depth rather than a listed skill.
- A strong answer shows:
- Joins, aggregations, CTEs or window functions explained in terms of the business question they answered.
- Follow-up:
- How did you check the result was right?
Question 2: The total from your query doesn’t match the number in the finance team’s report. How do you find out why?
- Why ask it:
- Tests a systematic approach to reconciling data.
- A strong answer shows:
- Checking definitions, filters, date ranges, time zones and duplicate rows from joins, step by step, before assuming either source is wrong.
Question 3: How would you find each customer’s first purchase and the time until their second, using SQL?
- Why ask it:
- A quick check of practical SQL reasoning that the client may test in more depth.
- A strong answer shows:
- A sensible approach such as window functions or a self-join, with attention to ties, nulls and customers who only bought once.
Question 4: A query or dashboard you own has become slow. What do you look at first?
- Why ask it:
- Shows awareness of performance and data volume.
- A strong answer shows:
- Checking filters, joins and how much data is scanned, using pre-aggregated tables or the query plan, and involving data engineering where needed.
Question 5: When do you reach for a spreadsheet, a BI tool or Python or R, and why?
- Why ask it:
- Tests judgment about tools rather than loyalty to one.
- A strong answer shows:
- Choices based on data size, repeatability and audience, with a real example of each.
Data cleaning and quality
Real data is messy. Look for habits that catch problems before a number reaches a stakeholder.
Question 6: Tell me about a dataset you had to clean before you could use it. What was wrong, and what did you do?
- Why ask it:
- Tests practical data cleaning experience.
- A strong answer shows:
- Specific issues such as duplicates, missing values, inconsistent formats or outliers, and the decisions they documented.
Question 7: How do you check an analysis before you share it?
- Why ask it:
- Shows the habits that keep wrong numbers away from decisions.
- A strong answer shows:
- Sanity checks against known totals, row counts at each step, spot checks of individual records and a second reviewer for high-stakes work.
Question 8: Tell me about a time you found an error in a report after it had been shared. What did you do?
- Why ask it:
- Tests honesty and ownership.
- A strong answer shows:
- Telling the people affected promptly, correcting the report, and changing the process so it doesn’t happen again.
Question 9: How do you handle missing or unreliable data when a stakeholder still needs an answer?
- Why ask it:
- Shows judgment when conditions are imperfect.
- A strong answer shows:
- Being open about the limits, giving a range or a caveated answer, and proposing how to fix the data at its source.
Metrics and analysis
Analysts are often handed vague questions. Look for clear definitions and careful reasoning about cause and effect.
Question 10: A manager asks you to find out whether a new feature is “working.” How do you turn that into a metric?
- Why ask it:
- Tests how they translate a vague goal into something measurable.
- A strong answer shows:
- Clarifying the goal first, choosing a primary metric and guardrail metrics, and agreeing the definition before pulling data.
- Follow-up:
- What could make that metric misleading?
Question 11: Tell me about a metric you defined or redefined. What did you have to agree with the business?
- Why ask it:
- Shows experience with definitions that other people rely on.
- A strong answer shows:
- Specific decisions on what counts, time windows and edge cases, written down and agreed with stakeholders.
Question 12: Sales rose the month after a marketing campaign. How would you work out whether the campaign caused it?
- Why ask it:
- Tests understanding of correlation versus causation.
- A strong answer shows:
- Considering seasonality, other changes and comparison groups, and recommending a test where possible rather than claiming credit.
Question 13: Describe an analysis you ran that led to a decision. What was the question, and what changed because of it?
- Why ask it:
- Links their work to business impact, which a non-technical recruiter can assess.
- A strong answer shows:
- A clear question, their own part in the analysis, and a concrete decision or result.
Question 14: Have you analyzed an A/B test or other experiment? How did you decide whether the result was real?
- Why ask it:
- Checks experimentation basics where the client runs tests.
- A strong answer shows:
- Awareness of sample size, statistical significance, test duration and checking the groups were split fairly, at a depth that matches their experience.
Communicating findings and working with stakeholders
An analysis only matters if people understand and use it. Any interviewer can judge these answers.
Question 15: Explain one of your recent findings to me as if I were the department head who asked for it.
- Why ask it:
- Tests communication directly, and a non-technical recruiter can judge it.
- A strong answer shows:
- The answer first, a few supporting points in plain language, and a clear recommendation.
Question 16: How do you handle a stakeholder who disagrees with what the data shows?
- Why ask it:
- Shows confidence and diplomacy together.
- A strong answer shows:
- Listening to the concern, rechecking the data, and holding to the evidence while staying open to a fair challenge.
Question 17: How do you prioritize when several teams send you data requests at once?
- Why ask it:
- Tests how they manage competing demands.
- A strong answer shows:
- Asking what decision each request supports and when it is needed, agreeing priorities openly, and building self-serve reports for repeat questions.
Question 18: Tell me about a dashboard or report you built. Who used it, and what did you change once they started using it?
- Why ask it:
- Shows they design for the people using the data.
- A strong answer shows:
- A named audience, a clear purpose, and changes made in response to how people actually used it.
Must-haves and logistics
Ask these of every candidate before the client’s technical round or take-home task, and check the answers against the resume.
Question 19: Which SQL databases, BI tools and programming languages have you used in your work in the last two years, and for what?
- Why ask it:
- Confirms hands-on experience with the client’s tools.
- A strong answer shows:
- Specific tools, ideally the client’s warehouse and BI platform, tied to real projects and recent dates.
Question 20: What kinds of data and business questions have you worked on, such as sales, product, marketing, finance or operations?
- Why ask it:
- Clients often value experience with similar data.
- A strong answer shows:
- Specific domains and datasets that overlap with the client’s.
Question 21: The role is [remote, hybrid or on-site, and location]. Does that work, and when could you start?
- Why ask it:
- Rules out arrangement and timing mismatches early.
- A strong answer shows:
- A clear yes, or the specific constraint, and a firm start date or notice period.
Question 22: Are you legally authorized to work in [country] for this employer, and will you need visa sponsorship now or in the future?
- Why ask it:
- Confirms eligibility; ask every candidate the same question in the same way.
- A strong answer shows:
- A direct answer, recorded the same way for every candidate.
Question 23: What pay range are you looking for in this role?
- Why ask it:
- Checks fit with the client’s budget without asking about pay history.
- A strong answer shows:
- A realistic range you can compare with the client’s budget.
Data analyst interview scorecard
Five criteria for this role, with what a score of 1, 3 and 5 looks like. Scores of 2 and 4 sit between them.
| Criterion | What it means | Score 1 looks like | Score 3 looks like | Score 5 looks like |
|---|---|---|---|---|
| SQL and technical skill | Writes correct queries and picks the right tool for the job. | Lists SQL but cannot describe a real query or how it was structured. | Explains a recent multi-step query clearly and reasons through the SQL prompt. | Handles edge cases unprompted, discusses performance and chooses tools to suit the task. |
| Data quality and rigor | Cleans data carefully and checks results before sharing them. | No checking habits; assumes the data is right. | Describes cleaning a messy dataset and a consistent checking routine. | Reconciles sources methodically, documents decisions and fixes problems at the source. |
| Analytical thinking | Turns vague questions into clear metrics and sound conclusions. | Jumps to conclusions or treats correlation as cause. | Defines a sensible metric and names likely confounding factors. | Clarifies the decision first, defines metrics with guardrails and proposes tests to establish cause. |
| Communication | Explains findings plainly and leads with the answer. | Walks through methods without reaching a conclusion, or relies on jargon. | Gives a clear answer with supporting points in plain language. | Adapts to each audience, uses visuals well and ends with a clear recommendation. |
| Stakeholder impact | Works with stakeholders so analysis leads to decisions. | Cannot name a decision their work influenced. | One clear example of an analysis that changed a decision. | Several examples of shaping questions with stakeholders, managing priorities and handling disagreement. |
The 1–5 rating scale
The same scale for every criterion and every candidate.
| Score | Level | What it means |
|---|---|---|
| 1 | Well below requirement | No relevant evidence, or an answer that contradicts the requirement. |
| 2 | Below requirement | Partial evidence with important gaps. |
| 3 | Meets requirement | Clear, relevant evidence at the level the role needs. |
| 4 | Above requirement | Strong, specific evidence beyond the expected level. |
| 5 | Exceptional | Repeated high-quality evidence with clear impact. |
How to run the interview with these data analyst interview questions
- 01
Step 01
Agree the must-haves first
Confirm the essential credentials, experience and availability with the hiring manager or client before any interviews. - 02
Step 02
Pick 8 to 12 questions
Take the must-have questions, then the questions that test what this role needs most. Use the same set, in the same order, for every candidate. - 03
Step 03
Ask for real examples
When you hear “we” or “I would”, ask what the candidate personally did, and what happened in the end. - 04
Step 04
Score before you discuss
Rate each criterion on the scorecard with the evidence behind it, then compare with other interviewers. - 05
Step 05
Verify before you submit
Check licenses, certifications and right to work against the original source before you put the candidate forward.
Red flags, and questions not to ask
- Cannot explain how they checked that a number was right before sharing it.
- Lists SQL, Python or a BI tool but cannot describe a real query, script or dashboard they built.
- Presents a correlation as proof that one thing caused another.
- Cannot say which part of a team analysis was their own work.
- Describes stakeholders as people who “don’t understand data” instead of explaining it to them.
- Age, marital or family status, pregnancy or plans for children, religion, ethnicity or national origin, sexual orientation or gender identity. These are protected characteristics under the UK Equality Act 2010 and US federal law, and they say nothing about whether someone can do the job.
- Health, sickness absence or disability before an offer. You can ask whether the candidate needs any adjustments for the interview, and whether they can do the essential tasks of the job.
Screen data analyst applicants before the first call
Add these questions to a Beatview AI interview and every applicant answers them on video or audio, with the same time limit. Beatview scores each answer against your criteria and shows the reasoning, and you can share the shortlist with your client through a password-protected link. AI interviews are on the Pro plan; the Free plan screens resumes for one active job.
Data analyst interview questions: frequently asked questions
Still deciding?
Bring a live vacancy and we’ll walk through where automation ends and recruiter review begins.
Ask for real examples that test SQL, data cleaning, defining metrics, reasoning about cause and effect, and communicating findings, such as a time the numbers didn’t match or an analysis that changed a decision. Add must-have questions on the client’s tools, work arrangement, right to work, start date and pay expectations, and ask every candidate the same questions in the same order.
Ask the candidate to explain a recent finding as if you were the person who requested it, and to describe a decision their work changed. You can judge clarity, structure and ownership without knowing SQL. Confirm which tools they have used recently and on what, and leave detailed SQL questions or take-home tasks to the client’s technical round.
A short practical exercise is useful, but agree with the client who runs it and when. Some clients prefer to set their own in the technical round, so the recruiter screen can focus on experience, communication and logistics. If you do test, use realistic data and score every candidate the same way.
It depends on the client. SQL and spreadsheets are everyday tools in many analyst roles, often alongside a BI tool for dashboards and sometimes Python or R for deeper analysis. Ask which tools the client actually uses and screen for those, rather than a generic list.
Get the data analyst interview questions template
All 23 questions with why you ask each one, what a strong answer shows and follow-ups, plus the data analyst scorecard and rating guide.
Opens in Excel, Google Sheets or Numbers. Version 1 October 2026.