Prioritization Questions

Show how you decide what matters most, make the trade-off visible to the people it affects, and say "not now" without losing their trust.

How It Works

Prioritization questions ask what you do when there's more work than time. "Tell me about a time you had competing deadlines" isn't asking whether you worked hard enough to do everything. It's asking how you decided what came first, what you chose not to do, and how the people affected found out.

Interviewers care because every team has more requests than capacity. The expensive mistakes come from quietly dropping something, or from saying yes to everything and missing all of it. They want to see that you can make a call, explain it and hold it when someone pushes.

Impact. How many users it touches, how much revenue or risk is involved, and which goal it moves.
Urgency and cost of delay. What gets worse each week you wait, and what would be just as good next month.
Reversibility. A choice that's easy to undo can be made quickly. One that isn't deserves more care.
Effort. A small fix with real impact often goes first, because it clears attention for the rest.

The decision is half the answer. The other half is how you made the trade-off visible. Strong answers say who was affected, how they found out and what they got instead: a later date, a smaller version or a workaround. "Not now, and here's when" lands far better than a silent no, and it keeps the person's trust for their next request.

At mid-level, the story is often about your own work: two deadlines in one week and a call about which one slips. Senior engineers are expected to prioritize for a team and push back on scope with product partners. At staff level, it's usually across teams or quarters, such as which project the group should stop so the important one gets done.

Pressure questions ("tell me about a time you worked under a tight deadline") are usually prioritization questions in disguise. Answer them with what you chose to cut, not how many hours you worked. Tell it with STAR, and keep the action on the decision rather than the grind.

What Interviewers Listen For

The criteria you used to decide, said plainly: impact, urgency, cost and risk.
What you chose not to do, or to do later.
How the people affected found out, and what they were offered instead.
Whether the important work stayed protected once the pressure arrived.
Calm under pressure: a clear decision, not a story about heroic hours.

How It's Asked

The same question comes in many wordings. Any of these wants the same kind of story.

Tell me about a time you had too many priorities at once.
Describe a time you had competing deadlines. How did you decide what to do first?
Tell me about a time you had to say no to a stakeholder.
Tell me about a time you worked under a lot of pressure.
Describe a time you had to cut scope to hit a deadline.
How do you decide what to work on when everything is urgent?
Tell me about a time you pushed back on a request from product or leadership.

Sample Answers

The Question

Tell me about a time you had competing priorities and couldn't do everything.

Try drafting your own answer first, then compare. Both answers are invented.

Show Sample Answers

A Common Answer

That's pretty much every sprint, to be honest. At my last job I was pulled in a lot of directions: feature work, bugs, requests from sales, on-call. I'm really organized, so I keep a list and rank everything by urgency each morning.

One quarter it got really intense and I worked a lot of late nights, but I got everything done on time. I think the key is staying on top of things and communicating.

A Strong Answer

I was tech lead for a team of three on the billing team at an HR software company. We had a usage-based invoicing feature due in four weeks, and it was promised to customers in writing. In the same week, two more things landed. Our nightly invoice job started crashing about twice a week, and each crash cost someone half a day to rerun and check. And a sales director asked for a custom export for a prospect he expected to sign that month. We couldn't do all three at full size, and it was my call how to split the team.

I asked two questions about each: what gets worse every week we wait, and what's hard to undo. The crash got worse every week, and a bad rerun could send customers wrong invoices, which you can't quietly take back. So it went first, and I took it myself so the other two engineers could stay on the launch. It took me four days to find a database connection leak and fix it.

The launch had a written commitment and a fixed date, so I protected it. The export was the hard one. A lost deal matters, but nothing got worse for existing customers if it waited. Instead of replying no in a message, I met the sales director and asked what the prospect actually needed. It turned out to be one monthly CSV with five fields, and our existing usage report already had four of them. I offered to add the fifth that week, about a day of work, and to scope the full custom export after launch. Then I posted the trade-off in our team channel, tagging my manager and our product manager, so nobody learned about it from a missed date.

The job didn't crash again in the three months I tracked it, and the launch shipped two days early. The prospect signed using the stopgap report. When we scoped the custom export after launch, they no longer needed it, so we never built it. What I'd change is how long I took to talk to the sales director. I spent two days treating his request as yes or no before asking what was behind it, and the real need was much smaller than the request.

Why It Works

The strong answer names its criteria (what gets worse with waiting, what's hard to undo) and applies them to each item. The weak answer says "rank by urgency" and never shows a single decision.
Something didn't get done. The custom export waited, and the candidate says how the sales director heard about it and what he got instead.
The important work stayed protected: the candidate took the interruption personally so the launch team wasn't pulled off it.
The weak answer's result is late nights. Working more hours sidesteps the question, which is about choosing.

Common Pitfalls

Describing your system instead of a decision. To-do lists and morning rankings are habits. The question wants one time you had to choose.
Doing everything by working late. It sounds dedicated, but it skips the trade-off, and some interviewers will hear that you can't say no.
Saying no without saying what happened next. A good answer includes what the other person was offered and how they took it.
Letting the loudest request win by default. If the urgent thing always goes first, the story shows reaction, not prioritization.
Making the trade-off silently. Even a correct call costs trust when the people affected find out from a missed date.