STAR method · behavioral interview · worked example
“Describe a time you had to deliver results with incomplete or unclear requirements.”
STAR method answer for ambiguity questions — pre-rendered example for product and engineering interviews.
Use this as a model — then adapt it with your own specific situation and measurable outcomes.
Situation
Mid-sprint, our PM went on emergency leave, leaving a half-written spec for a new user onboarding flow. The stakeholder review was in five days and no one else had full context on the business requirements.
Task
I needed to either unblock the frontend team with enough spec clarity to continue building, or escalate to engineering management to reprioritise the sprint — without knowing what "acceptable" looked like from the business side.
Action
I read all available context: the PM's draft spec, related Jira tickets, and a 10-minute Loom recording she had left. I identified three decision points where the spec was ambiguous and documented explicit assumptions for each. I shared these assumptions with the product director in a Slack message asking for a yes/no confirmation on each. Within two hours, I had confirmations on two of three points and a 15-minute call scheduled to resolve the third. I briefed the frontend team on the confirmed requirements and held the third screen in backlog.
Result
The team delivered four of five screens by the stakeholder review. The fifth was demoed as a wireframe with a confirmed timeline. The product director noted that my written assumptions document prevented a misalignment that had cost the team two full sprints the previous quarter.
The free STAR Builder tool helps you structure a complete answer for any behavioral question, then scores it on specificity, relevance, and impact. No sign-up required.