Interview questions for prioritization: 14 questions, probes and a 1–4 scale

Interview questions for prioritization should get the candidate to show you how they decided which work mattered most when there was more of it than anyone could do, what criteria they used, what they deliberately left undone, and how they told the people whose requests lost out. Below are fourteen questions, ten behavioral and four situational (including a ranking exercise you can run in ten minutes), each with follow-up probes, plus sample strong and weak answers, a 1–4 anchored scale and the mistakes that let busy-sounding candidates score well.

This is a different competency from the one covered in interview questions for time management, which looks at how a candidate runs their own day: estimating, focus time, their personal task list. Prioritization sits one level up. It is about choosing between projects, goals and stakeholders, often on behalf of a team. It is also related to, but separate from, decision making; prioritization is the specific, recurring decision about what gets resources first.

Prioritization, defined as something you can observe

Definition: prioritization is ranking competing work by its value to the goal, committing resources in that order, saying no or not yet to the rest, and re-ranking when circumstances change. Four behaviors make it visible:

• Explicit criteria. Ranking by something they can name, such as impact on a goal, deadline, risk or dependency, rather than by who asked loudest or most recently.
• Visible trade-offs. Naming what went to the bottom or off the list, not just what went to the top.
• Stakeholder handling. Telling people whose work was deprioritized, with the reason and a realiztic alternative.
• Re-prioritizing. Changing the order when new information arrives, without thrashing between priorities every week.

Ten behavioral questions, with follow-up probes

1. Tell me about a time you had more projects than your team could deliver in a quarter.
   Probes: How did you rank them? What happened to the ones at the bottom?
2. Describe a time you said no to a request from someone senior.
   Probes: What was your reason? What did you offer instead?
3. Tell me about a time two stakeholders each told you their work was the top priority.
   Probes: How did you decide? Did you involve anyone else in the decision?
4. Walk me through how you decided what to work on first when you started your current or last role.
   Probes: What did you deliberately leave alone for the first few months? How did that turn out?
5. Tell me about a time you re-prioritized in the middle of a project.
   Probes: What triggered it? What did it cost to change course?
6. Describe something you deprioritized that later turned out to matter more than you thought.
   Probes: What did you miss? What do you check now that you didn't then?
7. Tell me about a time you stopped a piece of work that was already under way.
   Probes: How did you tell the people doing it? What did you do with what had been built?
8. Describe how you've handled a backlog of requests, such as tickets, requisitions or client asks, that kept growing.
   Probes: What rule did you use to decide what to take next? Did anyone disagree with it?
9. Tell me about a time an urgent request pulled you away from something important but not urgent.
   Probes: How did you decide? What happened to the important work?
10. Describe a time you had to prioritize work for other people, not just yourself.
    Probes: How did you explain the order to the team? What did you do when someone disagreed?

Question 6 is the most revealing. A candidate who prioritizes deliberately will have a story about a call that went wrong and what they learned. A candidate who has never looked back at a prioritization decision tends to struggle with it.

Four situational questions, including a ranking exercise

11. The ranking exercise. Give the candidate a short list of six items written for the role, each with a one-line description of value, effort and deadline, and a single team goal for the quarter. Ask them to rank the list, say what they would drop, and explain how they would tell the owner of the lowest item.
    Probes: Halfway through, add a seventh item: "The CEO has just asked for this by Friday." What changes?
12. "You manage a small team. Sales wants a feature for a big prospect, support wants a fix for a recurring customer problem, and your manager wants progress on a long-term project. You can do one this month. Walk me through it."
    Probes: What would you want to know before deciding? What would you say to the two you didn't pick?
13. "Your top priority project gets blocked for two weeks waiting on another team. What do you do with that time?"
    Probes: How would you choose what to pull forward? Would you do anything to unblock the first project?
14. "In your first week, your new manager gives you a list of twelve things to 'look at'. What do you do?"
    Probes: What would you ask them? When would you come back with a plan?

For the ranking exercise, you are not looking for your own ranking. Several orders can be defensible. Score whether the criteria are clear, tied to the stated goal and applied consistently, whether the candidate is willing to drop items, and how they handle the seventh item. A good answer re-ranks with a reason; a weak one either ignores the CEO entirely or throws the rest of the plan out without thought.

What strong and weak answers sound like

Illustrative answers to question 3, written to show the contrast.

Weak: "I try to keep everyone happy, so I worked extra hours and managed to get both done. It was a stressful few weeks, but we delivered."

The weak answer avoided the choice entirely. Working harder is sometimes necessary, but it is not prioritization, and it does not scale. Ask what they would have done if extra hours weren't an option.

Strong: "Our sales director and our head of product both wanted the analytics team that month. I asked each of them what the work would change and by when. Sales needed a one-off report for a renewal worth a lot of revenue in three weeks; product wanted a dashboard with no firm deadline. I put the report first, gave product a specific start date, and sent both of them the same short note with the reasoning, so neither heard it second-hand. Product wasn't pleased, but the start date held."

The strong answer names criteria (value and deadline), gathers the information needed to apply them, makes an explicit choice, gives the deprioritized stakeholder a realiztic commitment, and communicates openly to both.

A 1–4 anchored rating scale for prioritization

If you hire recruiters, their prioritization skill has a very concrete form: which requisitions get their best hours. How to prioritize open requisitions describes the criteria a strong recruiter should be able to talk through.

Common interviewer mistakes with prioritization

• Rewarding "I got it all done." Delivering everything through overtime avoids the competency rather than demonstrating it. Always ask what they would have dropped.
• Scoring against your own ranking. In the exercise, a different order from yours can be well reasoned. Score the criteria and consistency.
• Scoring framework names. A candidate who names a prioritization matrix but cannot explain a real trade-off is weaker than one who uses plain criteria well.
• Ignoring the stakeholder side. Prioritization that nobody is told about causes as many problems as bad prioritization. Probe how the deprioritized people were told.
• Overlapping with time management. If another interviewer is covering time management, agree in advance who asks what. Otherwise both scores end up based on the same story. Interview panel roles and responsibilities covers giving each panelist a clear set of competencies to own.