The short answer
Ambiguity is normal in DE (unclear grain, missing owners, vague "real-time").
Ambiguity toolkit
- 1Write assumptions explicitly
- 2Ask the minimum clarifying questions
- 3Propose 2 options with trade-offs
- 4Ship a thin vertical slice
- 5Validate with the stakeholder early
- 6Iterate
STAR outline
Situation: "Build a customer activity table" with no grain defined.
Action: I proposed two grains (daily per user vs event-level) with example rows. Stakeholder chose daily. I documented grain + in the README and built staging first for review.
Result: Avoided a rewrite; analysts trusted the table definition.
Fresher tip
Capstone briefs are often vague. Show how you created clarity.
Interview tip: Ambiguity handling = questions + written assumptions + early feedback.