Behavioral question

Your Engineering Manager wants to work on a new feature and you absolutely have no bandwidth. How will you handle it?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Prioritization and stakeholder communication under real resource constraints, judged through a specific handled situation.

Set the situation, name the specific feature request and why the team genuinely had no bandwidth at that time.
State the task, needing to say no or defer without damaging the relationship or blocking a potentially important idea.
Describe the action, how the request was evaluated against current roadmap priority using a shared framework, not just a gut no.
Describe how the decision was communicated, proposing a specific future sprint or a smaller scope that could fit now.
State the result, how the engineering manager responded and what happened to both the original roadmap and the deferred request.

Uses a specific comparison, showing the new feature's estimated impact against what is already committed for the quarter, not just saying we are busy.
Offers a concrete alternative, a smaller version of the feature that could fit in the current sprint, showing collaboration rather than a flat no.
Ends with a real result, the manager agreed to defer to the next quarter and the relationship stayed strong.

Simply saying no with no framework or reasoning shown.
No alternative offered, making it sound like a dead end rather than a negotiation.
No result described for how the manager reacted or what happened next.

What would you have done if the manager escalated this to your boss?
How do you decide when a mid sprint request is important enough to actually break the plan?