Data Analyst Fresher Interview Questions and How to Answer Them

A data analyst interview for a fresher is rarely about clever tricks. Interviewers want to know three things: can you work with data using basic tools, can you think clearly about a business question, and can you explain your answer in simple words. This guide walks through the questions that come up most often and shows how to answer each one so that you sound prepared but natural.

How the interview is usually structured

Most companies run two or three rounds. The first is often an online test or screening call covering SQL, Excel and aptitude. The second is a technical discussion where someone reviews your projects and asks follow-up questions. The last round is a manager or HR conversation about communication, teamwork and your plans. Knowing this helps you split your preparation time instead of studying everything at once.

SQL questions you should expect

SQL is the most common skill tested for freshers, so practise it daily. Typical questions include:

• What is the difference between WHERE and HAVING?
• Explain INNER JOIN, LEFT JOIN and FULL JOIN with a small example.
• How do you find duplicate records in a table?
• What is a window function and when would you use RANK or ROW_NUMBER?
• How do you find the second highest salary?

A good answer to the WHERE and HAVING question is short and exact: WHERE filters individual rows before grouping, while HAVING filters groups after aggregation, so it can use functions such as SUM or COUNT. For duplicates, show that you understand grouping:

SELECT email, COUNT(*) AS times
FROM users
GROUP BY email
HAVING COUNT(*) > 1;

When you write a query in an interview, say your plan first: which table you start from, what you filter, and what you group by. Interviewers score your thinking as much as the final syntax.

Excel and spreadsheet questions

Excel questions are practical. You may be asked to explain XLOOKUP or VLOOKUP, build a pivot table from a sample sheet, or clean messy text data. Be ready to explain when a pivot table is better than a formula, how SUMIFS differs from SUMIF, and how you would remove duplicates or handle blank cells. If you have used Excel in a college project or internship, describe exactly what you cleaned and what decision the result supported.

Statistics questions

You do not need advanced mathematics, but you must know the basics well. Be able to explain mean, median and mode, and say when the median is the better measure, for example with salaries that contain a few very high values. Know what standard deviation tells you, what a correlation is, and why correlation does not prove causation. If asked about a p-value, a safe answer is that it shows how likely your result would be if there were really no effect, and a small value suggests the result is unlikely to be pure chance.

Python and pandas questions

If your resume lists Python, expect questions on lists and dictionaries, loops, and pandas. Common ones are how to read a CSV file, how to find missing values, how groupby works, and how merge compares with an SQL join. A strong answer mentions the actual methods, such as read_csv, isna, fillna, groupby and merge, and explains why you chose one approach, for instance filling missing ages with the median instead of the mean.

Power BI or Tableau questions

For visualisation tools, interviewers look for good design judgement. Be ready to explain what a measure is, why a star schema keeps reports fast, and how you would choose a chart. Use a line chart for trends over time, a bar chart to compare categories, and avoid pie charts with many slices. A dashboard should answer one clear question and use few colours.

Business and case questions

Case questions test thinking, not memory. A common example is: sales dropped by twenty percent last month, how would you investigate? A good approach is to confirm the data is correct, then break the drop down by product, region, channel and customer type, compare with the same period last year, check for events such as price changes or stock shortages, and finally suggest next steps. Speak in steps and invite the interviewer to correct your assumptions.

Questions about your projects

Every fresher is asked about projects, so know yours deeply. Be ready to explain where the data came from, what problems you found while cleaning it, which method you used and why, and what insight you found. If you cannot explain a project in two minutes, simplify it before the interview.

Common mistakes to avoid

• Memorising answers word for word instead of understanding the idea.
• Writing SQL silently without explaining your approach.
• Listing tools on your resume that you cannot discuss.
• Giving a long answer when the interviewer wanted a short definition.
• Saying you do not know without trying. It is fine to say, I am not sure, but I would start by checking the table structure.

A simple one-week plan

On days one and two, revise SQL joins, grouping and window functions with ten practice queries each. On day three, practise Excel pivot tables and lookup formulas. On day four, review statistics basics and write one-line explanations in your own words. On day five, revisit your two best projects and prepare a two-minute summary for each. On day six, practise two case questions out loud. On day seven, do a full mock interview with a friend and note which answers felt weak.

Final advice

Confidence in a fresher interview comes from clarity, not from knowing everything. Answer in plain language, give small examples, and be honest about what you are still learning. Keep practising on real datasets, and use the interview questions section on Hire Daily to test yourself regularly.