What does "ambiguity" mean in an interview question?

It means a situation without clear instructions: an unclear goal, missing information, no obvious owner, or priorities that kept changing. You're being asked how you worked in it.

Can I use a story where things changed halfway through?

Yes, but focus on how you got clarity on the new direction, not just on adapting. If the change itself is the story, see tell me about a time you adapted to change.

Is it bad to say I asked my manager for help?

No. Asking is good, especially with a clear question and a suggested answer. What looks weak is asking "What should I do?" with nothing prepared.

How do I answer if I prefer clear instructions?

Be honest but show you can cope: "I work best with a clear goal, so when there isn't one, I propose one and get it agreed." That turns a preference into a method.

What if my assumption turned out wrong?

That can be a good story. Explain how your small first step meant the mistake cost little, and how quickly you changed course.

Tell me about a time you dealt with ambiguity: how to answer it

What the interviewer wants to hear

Ambiguity questions are common in fast-moving companies, startups, product and consulting roles, and anywhere a manager won't always be there to tell you what to do. Versions you might hear: "Tell me about a time you had to work without clear instructions," or "Describe a project where the goal kept changing."

They are testing whether you can do two things at once:

Keep moving instead of waiting for someone to make it clear.
Reduce the uncertainty by asking the right people the right questions, instead of guessing and hoping.

Answers fail at both ends. "I waited until my manager clarified" shows no initiative. "I just decided what to do and did it" can sound reckless. The strong answer sits in the middle.

Name what was unclear

Start by saying exactly what kind of ambiguity it was. It makes the story sharper and shows you think clearly:

What was unclear	Example	What good handling looks like
The goal	"Improve onboarding," with no target	Proposing a measurable goal and getting it agreed
The owner	Two teams each thought the other was doing it	Naming the gap and getting one owner confirmed
The information	Data was missing or contradictory	Making a stated assumption and checking it early
The priorities	Everything was "urgent"	Ranking it yourself and asking someone to confirm
The process	A brand-new task nobody had done before	Drafting a plan and getting a quick review

A structure for your answer

The situation and what was unclear. One or two sentences. "I was asked to 'sort out' our supplier list, with no brief and a manager on leave for two weeks."
What you did to get clarity. Who you asked, what you read, which questions you put to them. "I asked finance which suppliers cost us most and the warehouse which ones caused late deliveries."
The assumption you made, out loud. "I assumed the goal was to cut late deliveries, not cost, and wrote that at the top of my plan so anyone could correct it."
The small first step. Something you could change cheaply if you were wrong. "I started with the three worst suppliers instead of all forty."
The result. What got done, and whether your assumption held. "When my manager came back she agreed with the focus, and we replaced two suppliers that month."
What you'd do the same next time. One line.

Step 3 is the heart of the answer. Saying an assumption out loud, so it can be corrected, is the skill.

Example answers

These are made-up examples to show the structure. Build yours from your own work.

Example answer for a project or operations role

"Our director asked me to 'make the monthly report more useful' and then went into a week of meetings. Nobody could tell me what 'useful' meant. I sent a two-question message to the six people who received the report: what do you use it for, and what do you skip? Four replied, and three said they only looked at the overdue items. So I assumed the goal was to make overdue work easier to spot. I wrote that assumption at the top of a one-page draft, moved the overdue items to the top and cut two sections nobody used, and sent it to the director with a note: 'Here's my reading of the brief; tell me if I've got it wrong.' She approved it with one change, and the report went from twelve pages to five."

Example answer for a new graduate

"In my internship, my supervisor asked me to research competitors for a new product, but didn't say which competitors or what to compare. Rather than guess, I spent an hour making a short list of eight companies and five things to compare, and asked her in our next check-in whether that was the right scope. She cut it to four companies and added pricing. Because I'd checked early, I didn't waste a week on the wrong comparison, and the final summary was used in the team's planning meeting."

Example answer for a customer-facing role

"A new client signed up without a clear list of what they wanted in their first month, and their contact was hard to reach. I set up a 15-minute call, came with three options for what we could deliver first, and asked them to pick one. They chose the second. We delivered it in two weeks, and that call became our standard way to start with new clients."

Mistakes to avoid

Mistake	Why it hurts	Try instead
"I waited for clarification"	Sounds passive	Show what you did while waiting
Guessing silently and getting lucky	Shows risk, not judgment	Say how you checked your guess
Blaming the unclear manager	Makes you sound difficult	Describe the situation neutrally
A story where nothing was really unclear	Doesn't answer the question	Name exactly what was missing
No result	The story stops halfway	Say what got done and if your assumption held

Practice it out loud

This question invites follow-ups like "What if you'd been wrong?" or "How did you decide who to ask?" Prepare one-line answers to both. Say the whole story out loud and time it: aim for 90 seconds. If you want a partner who asks those follow-ups, Speaking Coach has an "Ask for clarity" scene and mock interviews where the AI interviewer responds to what you actually said.