Tell me about a time leadership asked for something your team couldn't deliver in time. How did you negotiate the outcome?

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.
• What to bring out: Understanding the real business need, evidence-based estimates, offering options with trade-offs, protecting the team from burnout, and a credible commitment.
• Expect a follow-up like: How did the relationship with leadership look afterwards?

Another way it may be asked: Your boss says a big feature must ship next month, and you know it's not realistic. What did you do?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the stakeholder management you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• Imagine your team's project is going to miss its deadline. How would you tell the stakeholders, and what would you include?
• 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?

Browse all questions