Prompt
“How do you prioritize when everything is urgent?” or “Tell me about a time you had to say no.”
What interviewers are testing
- Business judgment — connecting work to revenue, risk, compliance, or user trust.
- Clarity under pressure — explicit trade-offs, not fake multitasking.
- Stakeholder management — communicating delays or cuts without surprise.
Senior/Staff DE angle
Show how you classify work: reversible vs irreversible, data quality risk, downstream contract (who consumes this dataset and for what decision). Staff candidates often get portfolio questions — multiple teams, fixed capacity — so practice naming one thing you stopped or de-scoped.
Structure
- Clarify impact — what breaks if this slips vs that (quantify where possible).
- Segment — must-ship, time-boxed spike, backlog; align with partners in writing when it matters.
- Sequence — critical path, parallelizable work, dependency order.
- Communicate — owners, dates, and what “good enough” means for each tier.
Example moves (adapt to your story)
- Time-box a thin slice to production with clear limitations documented.
- Freeze schema changes while stabilizing ingestion.
- Trade latency for correctness when the decision is irreversible.
Follow-ups to expect
- “What if leadership insisted on everything?”
- “How do you handle tech debt vs features?”
- “Give an example where you were wrong about priority.”
Mistakes to avoid
- Implying you never deprioritize anyone — credibility drops.
- Purely technical ordering with no business language.
Drill
Prepare one example where you intentionally delayed scope to protect data quality, correctness, or safety — and what you shipped instead in the same quarter.