MidBehavioural

Describe a time a stakeholder gave you a deadline you knew was not achievable. What did you do?

What they are really testing: They are testing whether you push back with evidence and a plan, or whether you either quietly agree and then miss, or refuse and become the blocker.

A real interview question

Describe a time a stakeholder gave you a deadline you knew was not achievable. What did you do?

What most people say

drag me

I told them it was not possible in that time, but they said it was fixed, so we worked weekends and just about made it.

It rewards heroics over planning, shows no evidence based negotiation, and quietly signals that the person will always fold under pressure.

The follow-ups they ask next

  • What if there was no way to cut scope?

    Say you would make the risk explicit in writing, name what would be cut under pressure, such as testing, and ask the business to accept that trade-off openly.

  • How accurate was your six week estimate in the end?

    Be honest about the variance and what you would pad differently, an estimate you defend blindly is a red flag.

What the interviewer is listening for

  • Estimated before pushing back
  • Negotiated scope rather than asking for more time
  • Kept the client's actual outcome in view
  • Put the trade-off in writing so a real decision could happen

What sinks the answer

  • Agreed to the date and hoped
  • Made it a fight about respect rather than about scope
  • Solved it by working weekends and calls that heroism
  • No numbers behind the claim that it was impossible

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

I have not been in exactly that spot, but my instinct is to not argue in the room. I would break the work down first, come back with a written estimate, and then try to find a smaller version of the thing that still lands on their date.

Keep going with behavioural

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free