Behavioral ยท medium
Tell me about a time you influenced a decision using data.
Asked in Data Analyst interviews.
Short answer
Use STAR: Situation, Task, Action, Result with a quantified impact.
How to answer it
What they are really asking
Not whether you can run an analysis. Whether an analysis you ran changed what somebody did. The interviewer is listening for three things: that you picked a question that mattered, that you brought someone with you who did not start out agreeing, and that you can say what happened afterwards.
The most common failure is a story where the analysis was excellent and nothing changed. That is a story about analysis, not about influence.
The structure
STAR, with the weight in the last two letters:
Situation one or two sentences. Who, what was at stake, why it mattered.
Enough context to follow, and no more.
Task what you specifically owned. "We" hides whether you did anything.
Action what you actually did: the question you framed, the data you
used, how you handled the pushback. This is most of the answer.
Result what CHANGED. A decision, a number, a direction. With a figure
if you have one, and honestly if you do not.Two minutes total. Roughly fifteen seconds of situation, fifteen of task, sixty of action, thirty of result.
What a weak answer sounds like
- No conflict. Nobody disagreed, so no influence was needed and none was demonstrated.
- All method, no outcome. Five sentences on the SQL and none on what anyone did differently.
- "We" throughout, so it is impossible to tell what you did.
- The decision was already made and the analysis merely confirmed it.
- No number anywhere, when a number plainly existed.
How to build your own
- List three or four times you changed someone's mind, or failed to. Failures with a lesson interview well.
- For each, write the result first. If you cannot state what changed, it is not this story.
- Find the disagreement. Who resisted, and what moved them?
- Get one number: the effect, the cost avoided, or the size of the thing you were arguing about.
- Rehearse it out loud and time it. Written stories run long, and two minutes is shorter than it feels.
- Prepare two, so you are not stuck if the first fits an earlier question better.
FAQ
- What if I have no big win? A small, concrete, true story beats a large vague one. Changing one report that three people used is a real answer.
- Can I use a university project? Yes if it is all you have, and treat the stakeholder as real. Prefer work experience where it exists.
- What if the decision went against me? That is a good story, if you can say what you would do differently. It shows judgement rather than luck.
- How much detail on the method? Enough to show you were rigorous, then move on. They will ask if they want more.
In the interview
- What they are checking: that you changed a decision, quantified it, and can say why your argument landed.
- Common mistake: describing an analysis in detail and ending with "and I presented it to the team".