Interview questions
Data analyst interview questions for freshers
Fresher data analyst interviews are two tests wearing one coat: can you handle the tools (SQL above all, then Excel, then a BI tool), and can you think about a business problem with numbers. Many candidates prepare only the first and are surprised by the second.
The questions below cover both. Notice how many of them are really communication questions — "explain," "walk me through," "how would you tell." Analysis that can't be explained to a manager doesn't count, and interviews are built around that fact.
Question 1
Explain the difference between INNER JOIN and LEFT JOIN.
The most reliable SQL question in existence. Define both, then give the classic use case — LEFT JOIN to find customers with no orders — because the follow-up is almost always "when would you use LEFT?"
Question 2
What's the difference between WHERE and HAVING?
WHERE filters rows before grouping; HAVING filters groups after aggregation. Give a one-line example with GROUP BY and you've answered the follow-up before it's asked.
Question 3
How would you handle missing values in a dataset?
The trap is jumping straight to "fill with the mean." Start with why the data is missing — random or systematic — because that decides everything: drop, impute, or flag. The reasoning is the answer; the technique is a detail.
Question 4
Explain a dashboard or analysis project you've done.
Structure it as question → data → method → finding → what someone did with it. That last step is what separates an analyst from a chart-maker, even in a college project.
Question 5
What is the difference between correlation and causation?
Define both, give a memorable confound (ice cream sales and drownings both rise in summer), and say what you'd need to claim causation. This question predicts whether your future analyses can be trusted.
Question 6
Our app's daily active users dropped 15% last week. How do you investigate?
A structure test, not a knowledge test. Segment before speculating: which platform, region, user cohort? Check what changed — releases, marketing, tracking bugs, seasonality. Saying "first I'd check if the data is wrong" is a genuinely senior move.
Question 7
Which Excel functions do you use most?
Name real ones with real uses: VLOOKUP or INDEX-MATCH (know why the second is safer), pivot tables, COUNTIFS. One sentence on a thing you actually built in Excel beats a list of ten functions.
Question 8
What is a p-value?
The probability of seeing data this extreme if the null hypothesis were true — not "the probability the result is due to chance." Interviewers ask precisely because the common wrong version is so common.
Question 9
How would you explain your findings to a non-technical manager?
Lead with the answer, then the evidence, then the caveat — in words, not column names. They may ask you to actually do it for your own project on the spot, so rehearse that version out loud.
Question 10
Why data analytics, and why this company?
The HR round rides along here too. A specific moment — the first time a dataset told you something surprising — plus one concrete fact about the company's data problems makes this answer yours instead of everyone's.
Common questions
How much SQL do fresher data analysts need?
Comfortably: joins, GROUP BY with HAVING, subqueries, and ideally basic window functions like ROW_NUMBER. Most interviews include live SQL or a take-home — reading about SQL without writing it will not survive that.
Is Python required for data analyst roles?
For many fresher analyst roles SQL and Excel are the hard requirements, with Python (pandas) a strong plus that widens your options. Data scientist roles are a different story — there Python is core.
What projects should a fresher data analyst show?
One or two end-to-end analyses of a real, messy dataset — public data is fine — that end in a finding and a recommendation, not just charts. One project you can defend under follow-up questions beats five you can't.