Explain a Past Analysis Project
Part of the Data Analyst Roadmap
In short
"Tell me about an analysis you're proud of" comes up in almost every interview. A clear, structured two-minute story beats a rambling ten-minute tour of everything you did.
Walking an interviewer through a real project (from your portfolio or work) — the problem, your approach, what you found, and its impact — one of the most predictable interview questions.
Think of it like this
Telling the story of a trek
When friends ask about your trek, you don't list every step. You say where you went, the tough part, what you did about it and the view from the top. A project story should feel the same: short, clear, with a high point.
Watch it happen
The STAR structure for a project story
1/4Situation, in one or two lines: "Our college canteen was throwing away a lot of food every week."
The big ideas
What you need to know
Keep it to two minutes
Practise until the core story fits in two minutes. The interviewer will ask for more if they want it.
Say "I", not just "we"
In team projects, be clear about what you personally did. That's what they're hiring.
Use real numbers honestly
Give results with numbers you can defend. If you don't have exact figures, describe the change without inventing them.
End with a lesson
One line on what you'd do differently shows you reflect and improve.
Save yourself the pain
Common mistakes
Oops
Spending three minutes on the background and rushing the result.
Do this instead
Keep situation and task short. Spend most time on your actions and the result.
Oops
Describing tools in detail: "I used pandas, then seaborn, then...".
Do this instead
Focus on decisions and impact. Mention tools briefly where they matter.
Your mission
Script and record your story
Quick check
In a STAR answer, which part should usually take the most time?
Go deeper
- 1Prepare a tight 2-3 minute walkthrough of your strongest Phase 14 portfolio project.
- 2Structure it as: problem, approach, finding, impact — in that order.
- 3Practice fielding a technical follow-up question about your methodology.
More behavioral at this stop
Handling Ambiguous Requests
Disagreement With Stakeholders
Communicating a Failed Analysis
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
