Tell me about a stretch when everything on your plate was urgent at once. What ended up last, and how did you choose?
Why this works
Prioritization only exists when something loses — a candidate who finished all ten things wasn't prioritizing, they were sprinting. Asking what went last forces the real skill into view: the ranking judgment, and whether the people waiting on the losers ever heard about it.
Follow-up probes
- What actually happened to the things at the bottom?
- Who did you warn that their work would wait?
- Which call would you make differently now?
What good looks like
A ranking principle they can state — impact, dependencies, blast radius — rather than loudest-first, the owners of deprioritized work told before the deadline rather than after it, and at least one call they'll admit was wrong.
Red flags
Everything got done through sheer hours — endurance dressed up as prioritization; the order was set by whoever asked last or loudest; owners of the dropped work found out at the deadline; or a system pitch arrives with no incident attached.
More Planning & delivering results questions
All 11 planning & delivering results questions
Related across competencies
Build the interview around it
One vetted question is an ingredient, not the meal. Plan the interview and three short steps will work out which competencies your role needs, no account required. Or subscribe and get new vetted questions and interview guides as we publish them.