How to Answer “Tell Me About a Time When You Had to Make a Decision with Incomplete Data”
Learn how to craft a clear, structured response to the interview question “Tell me about a time when you had to make a decision with incomplete data.” We cover why this question matters, a winning STA
This question isn’t about data. It’s about judgment: whether you can make a call when the information you want doesn’t exist yet.
Interviewers ask it because ambiguity is the default in tech. Products launch without complete metrics. Incidents happen with missing logs. Architectures get chosen before production load is known. They want to see if you freeze, or if you move.
Here’s how to answer it well.
Use STAR, but weight the Action heavily
Situation and Task set context. Result proves it worked. But the Action is where interviewers decide whether to believe you.
Don’t say “I gathered the team and assessed the risks.” Say what you actually did: the prototype you built to validate assumptions, the stakeholders you consulted, the risk matrix you created, the rollback plan you put in place before pulling the trigger.
Match your example to the role level
Mid-level (L5): One team, one technical decision, limited blast radius. You made the call and iterated fast.
Senior (L6/Staff): Cross-functional decision with real organizational risk. You structured the process and kept stakeholders informed.
Principal/Senior Manager (L7+): High-stakes, org-wide impact. You built the framework others used to decide, not just the decision itself.
Pick an example at or above the level you’re interviewing for.
Three example answers
Mid-level: ETL architecture without production data
Situation: We needed to choose an ETL pipeline architecture before we had production logs or workload metrics.
Action, as the senior engineer:
Organized a workshop with data engineers, DevOps, and product owners to surface our assumptions: peak load, data skew, retry rates.
Ranked risks by impact and likelihood.
Built a lightweight prototype on sample data.
Set up monitoring and rollback triggers before going live.
Result: The MVP launched in two weeks, processed 80% of expected volume without failures, and we cut end-to-end processing time 30% the following sprint.
Senior/Staff: Mobile release with incomplete test coverage
Situation: Before a major app release, our QA dashboard showed a 70% pass rate with 15% of critical user flows untested.
Action, as release manager:
Cross-referenced product analytics and support logs to identify the highest-risk journeys.
Ran manual smoke tests on those flows.
Proposed a phased rollout behind feature flags, starting at 10% of users.
Built a real-time monitoring dashboard for crash rates, documented rollback criteria, and briefed stakeholders on the contingency plan.
Result: No new crashes appeared in the first 24 hours. We rolled to 100% on schedule with a 20% bump in early-user adoption.
Principal/Senior Manager: Incident response with missing logs
Situation: During a production outage, our logging agent was misconfigured, leaving gaps in the data we needed to find root cause.
Action, as incident lead:
Assembled a war room across DevOps and security.
Reconstructed the missing picture by correlating metric spikes with service dependencies and pulling client-side logs to fill gaps.
Spun up a temporary high-verbosity logging pipeline.
Triaged errors by frequency and customer impact, and pushed status updates to stakeholders every 30 minutes.
Result: We resolved the top three error classes within 48 hours, cut error rates 85%, and improved incident response time 40% in follow-up drills after fixing the logging config.
What to do before your interview
Pick one scenario each from a product decision, a release, and an incident. That covers most follow-up angles.
Quantify the result: time saved, error rates reduced, adoption gained.
Name the specific steps in your Action section. Vague verbs (”coordinated,” “facilitated”) signal you didn’t actually lead it.
Practice the Action out loud. It should take 60-90 seconds and contain at least three concrete steps.
The candidates who stumble here either haven’t done this prep, or can’t explain what they actually did when it mattered. Fix both with 30 minutes of practice.