A month after you shipped a dashboard, you discover it has been overstating a key metric that leadership uses for planning. What would you do?
Scenario questions test judgment under uncertainty. Below is a sample answer for this one, the traps candidates fall into, and the probes interviewers follow up with.
A strong example answer
I would treat it as a live incident, not a quiet fix, because I shipped the dashboard.
First, verify before alarming anyone. In one real case, a join was double-counting returning users and had inflated weekly active users by roughly 18 percent. Before telling a soul, I would pin down when the error started, which reports consumed it, and produce corrected figures — I bring answers, not just alarm.
Same day, I would inform my manager and the analytics lead with a short note: what is wrong, the corrected numbers, who planned on the bad data, and a correction plan. Then I would alert those stakeholders myself. In that case the finance team had sized a hiring plan on the inflated growth figure, and catching it within a week let them adjust before offers went out — a far smaller mess than it could have been.
Third, fix the query, add an automated daily validation comparing the metric against an independent source, and write a brief postmortem so the team learns from it.
What I would skip is waiting for a perfect root-cause story before speaking up. Silence is what turns an honest mistake into a trust problem. Owning it fast actually raised my standing with leadership, and the automated check has caught smaller issues since.
A framework for your own answer
- Situation: Explain how you discovered the discrepancy and which metric was affected.
- Task: Clarify who relied on the inflated number and what decisions were at stake.
- Action: Walk through verifying the error, notifying stakeholders with corrected figures, and fixing the root cause.
- Result: Give the impact of fast disclosure and the guardrail you added to prevent recurrence.
Common mistakes to avoid
- The fix means nothing if the people who already planned on the wrong numbers never hear about it.
- Don't wait for a perfect root-cause story before alerting your manager.
- Candidates sometimes blame the pipeline or a teammate; owning the correction is the whole answer.
- What stops the same error next month? A fix shipped without a validation guardrail leaves the door wide open.
Follow-up questions to prepare for
A strong answer invites follow-ups — interviewers probe to check the reasoning holds up. Prepare for questions like:
- How do you decide which stakeholders need to be notified, and in what order?
- What validation checks do you run before any new dashboard goes live?
- What if the corrected number reversed a decision leadership had already announced?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator