Ambiguity questions ask what you do when the goal is unclear, the requirements keep changing, or there is more work than time. They test judgment: how you turned uncertainty into a plan, which trade-offs you made explicit, and how you kept people informed as things moved.
Theme 6 of 6 in behavioral themes
What the question is testing
Real projects rarely arrive fully specified. The interviewer wants to know whether you stall, guess silently, or reduce the uncertainty on purpose: asking the right people, making assumptions explicit, delivering something small to learn from, and saying no or not yet when you have to.
How to structure the answer
- Situation: what was unclear or changing, and what was at stake.
- Task: what you were expected to deliver despite it.
- Action: how you narrowed it down (questions, written assumptions, a first slice), the trade-offs you put in front of others, and how you kept them updated.
- Result: what shipped, and how the plan changed as you learned.
- Learning: how you now start work that is vague.
An example answer
Question: "Tell me about a project with unclear requirements." The details are invented to show the shape.
Situation Sales asked for "better reporting" for enterprise customers,
with a renewal deadline in six weeks.
Task I was asked to lead the engineering side with no spec.
Action I interviewed three customer-facing colleagues, found the two
reports blocking renewals, and wrote one page of assumptions
and what we would not build yet. I shipped a rough version of
the first report in a week for feedback, and sent a short
update every Friday with what had changed.
Result Both reports shipped in five weeks, the renewal went through,
and the third request we had parked turned out unnecessary.
Learning Writing down assumptions early turns vague requests into
decisions someone can agree with or correct.Common mistakes
- Describing the chaos at length and the method briefly.
- Waiting for full requirements before doing anything.
- Making big assumptions silently and being surprised later.
- Never saying no, so everything was late.
- No mention of keeping stakeholders informed as things changed.
How to say it out loud
Name the uncertainty, then your first move: "Nobody could tell me what better meant, so I started by asking the three people closest to the customers." Concrete first steps are what the interviewer is listening for.
Keep the story's structure visible even though the project was messy; structure is a scored delivery metric in Devana's behavioral rubric, and a calm, ordered telling of a chaotic project is itself evidence that you handle ambiguity well.
Practice questions
These come from Devana's question bank, in the order to try them. Each one starts a voice mock interview with Josh, Devana's AI interviewer, on that question, so you practice explaining the story out loud as well as getting it right.