The short answer
Describe a calm triage process, not "I do everything immediately."
Prioritization framework
- 1Impact: revenue, compliance, customer-facing, blocked team
- 2Urgency: true deadline vs "ASAP"
- 3Effort: hours vs days
- 4Risk: wrong data worse than delayed data?
- 5Dependencies: unblock others first when possible
Then communicate ETA and what slips.
Example outline
> 2 requests: (A) CEO dashboard missing today's sales, (B) analyst wants a new nice-to-have column. I validate A is a broken load (high impact), fix freshness first, then schedule B. I message both: "Fixing production freshness now; new column tomorrow afternoon."
Fresher tip
In projects, prioritize broken builds / wrong numbers over polish features.
Interview tip: Say how you push back politely when everything is labeled P0.