Tell me about a time you were given a task or project with unclear or incomplete requirements. How did you move forward?

behavioral · Junior level · general

What the interviewer is really asking

Assesses how the candidate makes progress when the goal is fuzzy — whether they reduce ambiguity through questions and assumptions rather than stalling or guessing silently.

What to say

• Describe what specifically was unclear and why you couldn't just start coding blindly.
• Explain how you reduced the ambiguity — questions you asked, assumptions you wrote down and validated, a small spike to learn.
• Show how you made forward progress without waiting indefinitely for perfect clarity.

What to avoid

• Don't say you waited until someone handed you a complete spec — that signals you can't operate without one.
• Avoid guessing silently and building the wrong thing because you didn't want to ask questions.
• Don't describe peppering your manager with every tiny question instead of batching and proposing answers.

Example answers

Strong: I was asked to 'add reporting' to a dashboard with no detail on which metrics. Rather than stall, I drafted a short proposal: the three metrics I thought mattered most, a rough mockup, and two open questions. I shared it with the product owner and got answers in one round instead of a dozen back-and-forths. That document became the spec, and I built the right thing the first time.

Weak: The requirements were vague, so I waited for the product owner to come back with a proper spec before I started anything.