Tell Me About a Time You Dealt with Ambiguity: Answer Framework and Examples

"Tell me about a time you dealt with ambiguity" is a behavioural interview question. It appears in graduate and experienced-hire interviews because most real jobs involve incomplete information. A manager says "have a look at why sales dipped", a client asks for "something more modern", or a project changes direction halfway through. The employer wants to know whether you freeze, guess wildly, or move forward in a sensible, checked way.

Interviewers usually listen for four things. The first is comfort with uncertainty: did you stay calm and constructive rather than waiting to be told exactly what to do? The second is clarifying judgement: did you ask the right questions, of the right people, at the right moment, without pestering anyone for answers you could have found yourself? The third is reasonable assumptions: where you could not get an answer, did you make a sensible assumption and say so openly? The fourth is progress: did you still deliver something useful?

Keep this four-part lens in mind as you read on. Every choice you make, from the story to the closing line, should help the interviewer tick those boxes.

The strongest ambiguity stories have three ingredients: a genuinely unclear starting point (a vague brief, missing data or conflicting signals), a decision you had to make without full information, and a result you can point to. If the instructions were actually clear and you simply found the task hard, you are telling a difficulty story, not an ambiguity story, and the interviewer will notice.

Test each candidate with five questions. Was it truly unclear what success looked like or what to do first? Did you have to decide something without being able to confirm it? Can you explain exactly how you reduced the uncertainty? Can you show the outcome? And can you tell it in about two minutes? A story that passes at least four is worth rehearsing.

Prepare two or three candidate stories. Analytical roles suit a messy-data story, while consulting, operations and project roles suit a vague-brief story. If you are early in your career, our first job interview questions guide explains how to draw on university and part-time experience credibly.

The STAR method (Situation, Task, Action, Result) is still the backbone of a good answer, and our STAR method guide covers it in depth. For ambiguity questions, it helps to give the Action stage a specific internal shape. Use Clarify, Assume, Act.

Clarify. Explain what was unclear and what you did to narrow it down. Strong clarifying steps include re-reading the brief, looking at past examples, asking the person who set the task one or two specific questions, and speaking to anyone who had done something similar. The key is doing some groundwork first so your questions are sharp, such as "I understand the goal as X; is that right, and does it include Y?"

Assume. Some uncertainty will remain. Say what you assumed and how you kept the risk low. You might have written the assumption down and shared it, built the first version so it was easy to change, or tested the assumption on a small sample before committing. This is the part most candidates skip, and it is the part that sounds most like a good colleague.

Act. Describe the first concrete step you took and how you adjusted as clarity improved. Then give the result, with numbers or a clear before-and-after where possible, and close with one sentence on what you learned or now do routinely.

Use "I" for your own actions and "we" only for genuinely shared ones. Interviewers are scoring your contribution, so be precise about what you personally did.

Interviewers are impressed less by the amount of uncertainty you faced and more by the technique you used to deal with it. If you can name a specific method, your answer stops sounding like luck. The table below lists approaches that are credible at graduate level, with how to phrase each one.

Notice that most of these involve communication, not private guesswork. Ambiguity is rarely solved by thinking harder alone; it is usually solved by turning an unclear request into a visible, checkable one. That is the core insight to show.

Finally, remember proportion. Not every unclear point needs a meeting. Part of good judgement is deciding which uncertainties are worth a question and which you can resolve with a sensible default. If you can explain that distinction in your answer, you will stand out.

The examples below are illustrative models, not scripts. Replace the details with your own, keep the shape, and aim for around two minutes when spoken.

Example 1: Internship (vague brief)

Situation: "On a summer placement in a marketing team, my supervisor asked me to 'look into why newsletter sign-ups had dropped'. There was no deadline beyond 'this month' and no data source named." Clarify: "I asked two questions: what decision the answer would feed into, and whether sign-up data was available by source. She said it was for a budget discussion in two weeks, and pointed me to the web analytics. I also checked last quarter's report to see how the team usually presented findings." Assume and act: "I could not confirm whether a website redesign had changed tracking, so I assumed the data was comparable and stated that clearly. I broke sign-ups down by page and device, and shared a one-page draft after three days instead of waiting." Result: "The draft showed the drop was concentrated on mobile after a form change. My supervisor confirmed the redesign had moved the form, the team restored it, and she used my summary in the budget meeting. I now always share an early draft when a brief is open-ended."

Example 2: University (group project)

Situation: "For a final-year group project, our brief was a single paragraph and the marking criteria were broad. Four of us had different ideas of what was expected, and two weeks passed with little progress." Clarify: "I emailed the module leader with three specific questions about scope and format, and also read two high-scoring past projects they had made available." Assume and act: "Answers were partial, so I suggested we write our assumptions on one page, such as report length and which data to use, and I circulated it for approval. I then proposed splitting the work into four sections with a review meeting every Friday." Result: "We submitted on time, the group received a strong mark, and the module leader's feedback praised the clarity of our structure. It taught me that writing the assumptions down quickly aligns a group."

Example 3: Volunteering (no handover)

Situation: "I became treasurer of a university society mid-year after the previous treasurer left, with no handover notes and an unclear picture of what we had committed to spend." Clarify: "I contacted the previous treasurer, who answered a short list of questions, and reviewed bank statements and the students' union's guidance on society finances." Assume and act: "Where records conflicted, I made a cautious assumption, treating uncertain payments as already committed, and flagged them to the committee. I built a simple spreadsheet of income, spending and open items, and updated it weekly." Result: "Within a month we had a reliable budget, avoided an overspend on a planned event and passed the union's year-end check. I wrote a handover document so the next treasurer would not face the same problem."

The wording of the question stays the same, but what counts as an impressive answer shifts with the role. Employers rarely publish the exact competencies they score against, so use the job description as your guide: words such as "fast-paced", "dynamic", "client-facing" or "start-up" are hints that ambiguity is a daily reality in the role.

If the employer uses a published competency framework, read it before you prepare. Some frameworks have headings such as "making effective decisions" or "seeing the big picture", and an ambiguity story can often be framed to fit them. Our competency-based interview guide explains how to map your stories to a framework.

Whatever the role, keep the tone grounded. Interviewers have heard plenty of dramatic stories where everything was chaos and the candidate saved the day. A calm, methodical account of turning something unclear into something workable is usually more convincing.

Most weak answers to this question fall into a handful of patterns. Check your draft against the list below.

Expect follow-up questions. Prepare short answers to these six:

• What would you have done if your supervisor had not been available?
• How did you decide which assumption to make?
• What was the biggest risk in the approach you took?
• Did anything turn out differently from what you assumed?
• How did you keep other people informed?
• What would you do differently next time?

The fourth question is the most revealing. A good answer admits that one assumption was slightly off, explains how you spotted it and shows the damage was limited because you had kept the work flexible. That is precisely the behaviour employers hope to see. For more general advice on avoiding slip-ups, read our how to prepare for a job interview guide.