Every company runs its hiring a little differently, but fresher data analyst interviews tend to follow a familiar shape. Knowing the shape lets you prepare for each stage on purpose instead of hoping for the best.
Stage 1: Resume screen
Before any test, someone reads your resume. What gets you through: a clear one-page resume, the right keywords for the role (SQL, Excel, Python, Power BI, as relevant), and projects with real business context. Our guide on putting projects on your resume covers this in detail.
Stage 2: Online assessment
Often a timed test with some mix of:
- SQL queries on given tables (very common).
- Aptitude: percentages, ratios, averages, data interpretation from tables and charts.
- Excel questions on formulas or pivot tables.
- Sometimes Python basics or multiple-choice statistics.
How to prepare: timed SQL practice on unfamiliar tables, and data interpretation questions. Speed matters, so practise until filtering, grouping and joining are automatic.
Stage 3: Technical interview
A live conversation where you write SQL (on a shared screen or paper) and explain concepts. Expect:
- Two to four SQL problems, often building in difficulty, using the common patterns.
- Questions about your projects: "Why did you choose this chart?", "How did you handle missing values?", "What would you do differently?"
- Concept questions: joins, window functions, mean vs median, what a p-value means.
- Sometimes a pandas task: group, merge, clean.
How to prepare: explain your projects out loud. If you cannot explain a choice you made, the interviewer will notice. Practise thinking aloud while you write queries.
Stage 4: Case study or business round
This round tests whether you can think like an analyst, not just code. You might get a question such as:
- "Orders on our app dropped last week. How would you investigate?"
- "Which metrics would you track for a new subscription feature?"
- "Here is a small dataset. What insights would you present to the manager?"
A structure that works:
- Clarify the question and the goal. Dropped compared to what? Which platform? Which cities?
- Break it down: orders = visitors × conversion. Which part fell?
- Form hypotheses: tech issue, competitor offer, seasonality, price change, a data pipeline problem.
- Say what data you would check for each, and in what order.
- Conclude with a recommendation, even if it is tentative.
Interviewers care more about a clear, structured approach than about guessing the "right" cause.
How to prepare: practise on business problems with context. Our guided projects and live projects are built around exactly this kind of question.
Stage 5: HR or managerial round
Common questions: tell me about yourself, why data analytics, why this company, a time you solved a problem, strengths and weaknesses, willingness to relocate. Prepare short, honest answers with one concrete example each, ideally from your projects.
A preparation plan
- Daily: solve a few SQL questions under time pressure.
- Weekly: finish or improve one project section, and explain it out loud as if to an interviewer.
- Before each interview: read about the company's business and think of two or three metrics it probably cares about.
- After each interview: write down every question you were asked and practise the ones you struggled with.
Rehearse
Reading about interviews is not the same as answering under pressure. Use our mock interview to rehearse, and keep the SQL interview set as your daily warm-up.
Practise what you just read
Reading helps; writing the code yourself is what sticks. Start here: