Prioritizing competing requests when team capacity is constrained

Quick Overview

A behavioral product manager interview question about deciding what a team should work on when there is more valuable work than capacity. It tests a repeatable prioritization method, a concrete example with explicit cuts, how the decision was communicated to stakeholders, and how the outcome was measured and revisited.

Prioritizing competing requests when team capacity is constrained

Company: Infinitus Systems

Role: Product Manager

Category: Behavioral & Leadership

Difficulty: medium

Interview Round: Other

The interviewer wants to know how you decide what your team works on when there is more worthwhile work than people and time. Describe the approach you use to prioritize under constrained capacity, and ground it in a real situation where you had to make that call: what was competing, what you chose, what you deferred or declined, and how it turned out. ```hint Show the cuts, not only the picks Anyone can list what they chose to build. Make clear what you decided not to do, what evidence drove that call, and how you told the people whose requests lost out. ``` ### Clarifying Questions - Does "limited bandwidth" refer to my own time as the PM, my engineering team's capacity, or both? - Are you looking for my general method, one specific past example, or the method illustrated through an example? - Which planning horizon matters most here: day-to-day interruptions within a sprint, or quarter-level roadmap trade-offs? - Should the example involve pushing back on a senior stakeholder or an important customer, or is any competing-priorities situation fine? ### What a Strong Answer Covers - A repeatable method that starts from the goal the team is accountable for and compares options on value, effort, confidence and urgency, rather than on gut feel or on who asks loudest. - A concrete example with the actual competing items, the capacity limit, and an explicit decision about what was deferred or dropped. - How the decision was communicated to the stakeholders whose requests were cut, and how disagreement was handled. - The outcome measured against the goal, what was learned, and how priorities are revisited when new information arrives. - Awareness of work that cannot be ranked on value alone, such as security, compliance or reliability obligations. ### Follow-up Questions - Two senior leaders each insist their request is the top priority, and you can staff only one this quarter. What do you do? - Tell me about a time your prioritization turned out to be wrong. How did you notice, and what did you change afterward? - An urgent customer escalation arrives mid-sprint while the team is fully committed. How do you decide whether it displaces planned work?

Overview: A behavioral product manager interview question about deciding what a team should work on when there is more valuable work than capacity. It tests a repeatable prioritization method, a concrete example with explicit cuts, how the decision was communicated to stakeholders, and how the outcome was measured and revisited.

Infinitus Systems logo
Infinitus Systems
Jan 17, 2026
mediumProduct ManagerOtherBehavioral & Leadership
0
0

The interviewer wants to know how you decide what your team works on when there is more worthwhile work than people and time. Describe the approach you use to prioritize under constrained capacity, and ground it in a real situation where you had to make that call: what was competing, what you chose, what you deferred or declined, and how it turned out.

Clarifying Questions Guidance

  • Does "limited bandwidth" refer to my own time as the PM, my engineering team's capacity, or both?
  • Are you looking for my general method, one specific past example, or the method illustrated through an example?
  • Which planning horizon matters most here: day-to-day interruptions within a sprint, or quarter-level roadmap trade-offs?
  • Should the example involve pushing back on a senior stakeholder or an important customer, or is any competing-priorities situation fine?

What a Strong Answer Covers Guidance

  • A repeatable method that starts from the goal the team is accountable for and compares options on value, effort, confidence and urgency, rather than on gut feel or on who asks loudest.
  • A concrete example with the actual competing items, the capacity limit, and an explicit decision about what was deferred or dropped.
  • How the decision was communicated to the stakeholders whose requests were cut, and how disagreement was handled.
  • The outcome measured against the goal, what was learned, and how priorities are revisited when new information arrives.
  • Awareness of work that cannot be ranked on value alone, such as security, compliance or reliability obligations.

Follow-up Questions Guidance

  • Two senior leaders each insist their request is the top priority, and you can staff only one this quarter. What do you do?
  • Tell me about a time your prioritization turned out to be wrong. How did you notice, and what did you change afterward?
  • An urgent customer escalation arrives mid-sprint while the team is fully committed. How do you decide whether it displaces planned work?