Made Decision with Incomplete Information
Last Updated: June 4, 2026
Medium Priority
6 min read
AI Mock Interview
Practice this question in a realistic, spoken behavioral interview.
Question
Give an example of a time when you had to make a decision with incomplete information.
This question tests engineering judgment under uncertainty: how you handle a decision where waiting for full information is itself a costly choice. Pick a moment where the data was genuinely incomplete and walk through what you knew, what you did not know, the assumption you made, how reversible the decision was, and what you watched for after the call was made.
What Makes the Ambiguity Credible
The answer should make the uncertainty visible:
- Waiting had a cost: Make it clear why delaying for perfect information would have hurt the project, customer, or team.
- You reduced uncertainty before deciding: Mention the data you could gather, the people you consulted, and the questions you answered quickly.
- You named the assumptions: A good ambiguity story says what you believed to be true and how confident you were.
- You managed reversibility: Explain whether the decision was a one-way door or two-way door, and what you did to limit downside.
- You owned the result: Close the loop with what happened, what signal you watched, and what you changed when reality arrived.
Where This Answer Usually Goes Wrong
- Waiting until you had full information: That is not deciding under uncertainty, that is delaying.
- Pretending you had more data than you did: Be honest about what you guessed.
- No mention of how you would reverse: Mature decisions under uncertainty include the cost and path of being wrong.
- Skipping the cost of inaction: Sometimes not deciding is itself a decision. Name it.
- Picking a trivially low-stakes example: "I had to decide between two restaurants for the offsite" is not the level the question is asking about.
How to Talk Through the Ambiguous Decision
Slow down at the moment where you made the call. The answer should make clear what you knew, what you still had to assume, how reversible the decision was, and what you watched for afterward.
- Gather what you can: Show how you reduced uncertainty before deciding. Spell out the information you found, the source you trusted, and the gap that still remained.
- State your assumptions: Clearly articulate the assumptions you had to make to fill in the gaps.
- Act and make it reversible: Explain how you kept room to pivot if your assumptions were wrong: feature flag, pilot, fallback path, staged rollout, or explicit rollback owner.
- Learn and iterate: Explain how you set up a feedback loop to validate your assumptions and learn from the outcome.