Do not say no; make the tradeoff explicit and let them choose. Ask what problem the request solves and how urgent it truly is, then show which committed work would have to move to make room. Keep the negotiation off your engineers. If it is genuinely urgent, take it and drop something visible, so the cost stays on the record instead of being absorbed silently by the team.
Why interviewers ask this
This tests whether you can hold a boundary without becoming the department of no. Interviewers listen for curiosity about the underlying need, transparent tradeoffs rather than heroics, protection of the team's focus, and a sensible escalation path when the stakeholder outranks you. Silently absorbing extra scope is the failure mode they are screening for, because it hides cost and burns teams out quietly.
How to structure your answer
- Ask what problem the request solves before answering.
- Present the tradeoff as a choice with named consequences.
- Keep the negotiation off your engineers.
- Say how you escalate when the pressure outranks you.
Example answer
I never open with no, because that starts a fight I do not need. I open with what is driving this and when do you actually need it, and a decent share of the time the honest answer is next month, at which point it goes into planning like everything else. When it is real, I make the trade visible. The sprint has these five things, this is the one I would drop, and dropping it means the reporting work slips a week and the finance team will notice. Then they choose. That does two things: it keeps the decision with the person who owns priorities, and it stops the pattern where engineering absorbs scope quietly and then gets asked why everything is late. I also keep that conversation away from my engineers. If a director drops into standup with a request, my team's answer is to point at me, because a mid level engineer should not be negotiating with a director. If somebody insists on both, I escalate the same day with numbers and let two directors have the conversation.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What if the stakeholder goes directly to an engineer anyway?
- How do you handle a genuine emergency that cannot wait?
- How do you keep a record of these interruptions over a quarter?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions