BEHAVIORAL · AMBIGUITY AND JUDGMENT
Tell me about a time the requirements were unclear: sample answer
Whether you can make progress when the goal is vague: turning a fuzzy request into a measurable target, deciding what you need to know versus what you can assume, and lowering the risk of being wrong with small, reversible steps.
Also asked as
- Tell me about a time you had to balance a customer need against a technical constraint.
- Describe a project where the requirements were unclear. How did you move forward?
- Tell me about a decision you made without all the data you wanted.
- Tell me about a time your judgment turned out to be right when others disagreed.
- Describe a time you had to cut scope to ship. How did you choose?
- Describe a time you used data to change a decision.
The short version: Show how you made a sound decision with incomplete information, and how you reduced the risk.
Sample STAR answer
An invented example from typical software engineering work, about 260 words, around two minutes spoken. Use the structure, not the story: yours should be real.
Situation Our product lead told my team that "search feels slow" in our marketplace app and asked us to make it faster. There was no target, no deadline, and nobody could say which searches were slow.
Task I was asked to lead the work. My job was to turn "faster" into something we could measure and ship, without spending a month just studying the problem.
Action I started by defining what "slow" meant. I added timing to the search path and found the median was fine, around 300 milliseconds, but the slowest five percent took over three seconds, mostly searches with several filters. I then spent a day with our support and product colleagues to check whether those were the searches people complained about, and they were. I proposed one goal: bring the 95th percentile under one second within six weeks. I also wrote down my assumptions, such as "users care more about the first page of results than the total count", so we could test them. We shipped in three small steps, each behind a flag: caching popular filter combinations, skipping the exact total count for large result sets, and adding a missing database index. After each step I checked the numbers before moving on.
Result The slowest five percent of searches dropped from over three seconds to about 800 milliseconds in five weeks, and searches that ended with a click on a result rose by six percent. The one assumption that turned out wrong, that nobody looked at total counts, we fixed by showing an estimate instead.
Weak answer vs strong answer
Weak
"The requirements were unclear, so I set up meetings with all the stakeholders to get clarity. Once everyone agreed on the requirements, we built it and it went well."
Why it scores low: Waiting for clarity from others is the opposite of what is being tested. There is no target you defined, no assumption you made, no risk you reduced and no result.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show how you made a sound decision with incomplete information, and how you reduced the risk.
How the story changes with level
At SDE 1, ambiguity is usually inside a task: unclear edge cases or a vague ticket. Show that you asked focused questions, wrote down assumptions and checked in early.
At senior or staff level, the ambiguity should be about what to build at all, across teams. Show that you framed the problem for others, set the goal and success measure, and made the call that let several people move.
Follow-up questions interviewers ask
- How did you choose the 95th percentile instead of the average?Explain that averages hide the slow requests real users notice.
- What would you have done if you could not get any data?Make a reversible decision, state the assumption, and set a date to check it.
- How did you keep the product lead informed?Describe a short weekly update with the metric and the next step.
- When do you stop gathering information and decide?When the next piece of data would not change the decision, or when the step is easy to undo.
Amazon Leadership Principles that test this
Are Right, A Lot · Tell me about a time you made a decision with incomplete information that turned out to be right.
Have strong judgment and good instincts, seek out views that differ from yours, and work to prove your own beliefs wrong.
Situation My team needed a queue for a new background job system. Most of the team wanted to run our own open-source message broker because we had used it before.
Task I was asked to make the recommendation. I leaned towards a managed queue service, but I knew I could be biased, so I wanted a decision that would hold up.
Action I wrote down the three things that mattered most: operating effort, cost at our expected volume, and delivery guarantees. Then I asked the two strongest supporters of running our own broker to write the best case for it, and I took their points seriously. They were right that self-hosting was cheaper at very high volume. I checked our real numbers: we were about twenty times below the point where that mattered, and running our own broker meant on-call work for a team of four. I also listed what would make me change my mind, such as volume growing tenfold, and set a review date six months out.
Result We chose the managed queue. At the six-month review our volume was still far below the break-even point, and we had spent no on-call time on the queue. The written criteria made the review take one meeting.
Tip: Show how you looked for disagreement and data that could prove you wrong, not just that you guessed correctly.
Companies that test this
- GoogleGeneral Cognitive Ability · Role-Related Knowledge and Experience · Googleyness
- AmazonAre Right, A Lot · Dive Deep
- NetflixJudgment · Courage · Resilience
- UberAdaptability · Grit
- SpotifyHuman Judgment
- PalantirExecution, judgment and learning from failure
- IntuitCourage
- VisaLead courageously
- SwiggyNever Settle
Prepare your own
Write your story in the story bank and tag it "Ambiguity and judgment"; it will show up against every company value that tests this theme.
Related: Customer focus · Speed and delivery · Resilience and courage · Diving deep