Prompt

“Tell me about a time you owned something when requirements were unclear or shifting.”

What interviewers are testing

  • Problem framing before execution — did you narrow “what good looks like”?
  • Decision quality with incomplete information — options, bets, reversibility.
  • Accountability through delivery — not heroics, clear ownership when things wobble.

Senior/Staff DE angle

Staff loops often probe 0→1 data work: new domain, messy sources, unclear SLAs. Show how you staged work (spikes, contracts, canary pipelines) and how you aligned metrics with the business question — not only how you coded the fix.

STAR outline

  • Situation: Ambiguous objective, conflicting stakeholder expectations, or missing definitions of “done.”
  • Task: What you explicitly took ownership of — scoping, success criteria, risk callouts.
  • Action: How you reduced ambiguity: interviews, data profiling, prototypes, RFCs, incremental releases.
  • Result: Quantified impact and what became repeatable (playbook, guardrails, monitoring).

Follow-ups to expect

  • “What would you do differently?”
  • “Who disagreed with you and how did you handle it?”
  • “How did you know you were done?”

Prepare one sentence each so you don’t stall.

Mistakes to avoid

  • Sounding like the PM should have written better specs — show your moves to clarify.
  • Confusing activity with ownership (meetings held vs decisions and outcomes).

Drill

Write two drafts of the same story: one where you had direct authority, one where you influenced without authority. Same outcome; different levers. Pick the stronger version for interviews.