Engineering Manager
Imagine your team's project is going to miss its deadline. How would you tell the stakeholders, and what would you include?
What the interviewer is looking for
- This question tests stakeholder management. Aligns with product and leadership, communicates risks early, negotiates scope and builds trust across teams.
- Strong answers: Telling them early, being honest about the cause, the new estimate with confidence level, options such as reducing scope, and next steps.
- Likely follow-up: How would you handle a stakeholder who reacts badly?
Another way it may be asked: You've just realised a launch will be three weeks late. Who do you tell, when, and what do you say?
A structure to follow: Answer, explain, example, limits
- Step 1
Answer
Give your direct answer in the first sentence so the interviewer knows where you are going.
- Step 2
Explain
Say how it works or why you would do it that way, in plain words before jargon.
- Step 3
Example
Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.
- Step 4
Limits
Say when your approach would not be the right one. It shows judgement.
This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.
Common slips
- Reciting a definition without showing you have applied it.
- Using terms you cannot explain if asked a level deeper.
- Claiming experience beyond what you can discuss in detail.
How to practise it
Say the answer in 90 seconds, then answer the follow-up as if it were a new question.
Related questions
- Tell me about a time leadership asked for something your team couldn't deliver in time. How did you negotiate the outcome?
- If you were a new manager taking over a team, what would you do in your first month to get to know your people?
- Two engineers on your team strongly disagree about how to build something, and it's slowing things down. What would you do?
- How do you design an interview process that's fair and actually predicts who will do well on your team?
- How do you balance new feature work, technical debt and on-call load across a quarter?