Prioritization Under Pressure

How to choose what to do first when everything is labeled urgent: a simple framework, explicit trade-offs, a clear no, and a plan for technical debt.

Overview

Every engineer has more requests than time. The question is how you choose. When three teams each call their request top priority, do you pick by who is loudest, by who is most senior, or by a principle you can explain?

Interviewers ask this to see three things. First, that you weigh value against cost instead of reacting. Second, that you make trade-offs visible, so stakeholders choose with open eyes instead of being surprised later. Third, that you can say no to a good request to protect a better one. In interviews for senior and lead roles, expect the questions to be about setting priorities for a whole team, not only for yourself.

Method — A framework you can explain in one sentence — Gut feel, or 'my manager decided'
Trade-offs — Said out loud: doing A means B slips by N days — Silent slips discovered later
Saying no — Offers options: later, smaller, someone else — Says yes to everything, or a flat no
Data — Value and cost estimated, even roughly — Loudest request wins
Follow-through — Checked the result and adjusted — Never looked back

What you will be able to do

Sort competing work with the urgent-important matrix and a value-per-effort score.
Say no in a way that keeps the relationship and offers real options.
Make the case for technical debt in terms stakeholders act on: time, risk and incidents.
Hold a priority call under pressure, or commit fully when you are overruled.

Interview questions

How do you prioritize when several urgent things compete for your time?
Tell me about a time you had to say no to an important request.
How do you manage technical debt alongside feature work?
How do you handle stakeholders who disagree with your priorities?

Prioritization Under Pressure

Overview

What you will be able to do

Interview questions

More Behavioral topics