4 views
# Answering "Tell Me About a Time You Worked With Unclear Requirements" Ambiguity questions are common for product, analytics, operations and engineering roles. The interviewer wants to see whether you stall, guess, or create clarity. ## What a strong answer shows 1. You noticed the ambiguity early instead of discovering it at the deadline. 2. You asked targeted questions or made explicit, documented assumptions. 3. You shipped something small to test those assumptions. 4. You adjusted once you learned more. ## Example > "A sales director asked for 'a dashboard showing churn risk'. Nobody had defined churn risk. I drafted a one-page proposal with three possible definitions and the data each needed, and asked her to pick one in a 15-minute call. We launched a simple version in a week, then refined the scoring after two sprints of feedback. Churn-risk accounts flagged by the dashboard saw 20% more check-ins." ## Phrases that help - "My first step was to write down what I assumed and confirm it." - "I chose a reversible first version so we could learn quickly." ## Avoid Blaming the stakeholder for being vague, or describing weeks of waiting for perfect specs. ## Practise out loud Ambiguity stories get long quickly; time yourself to two minutes. Disclosure: I work on Linkjob AI — you can try [Linkjob.ai](https://www.linkjob.ai/) to rehearse answers like this with real-time feedback.