Describe a time you had to push back on a deadline or a stakeholder request.
What they are really testing: Whether you can say no upward with evidence rather than either capitulating or being obstructive. They also want to see you offer options instead of just refusing.
A real interview question
Describe a time you had to push back on a deadline or a stakeholder request.
What most people say
drag me
“I told them it was not possible and that they needed to give us more time.”
It is a refusal with no alternative, which reads as inflexibility and gets overruled. Stakeholders can accept risk if they understand it, but they cannot act on "no" with no options attached.
The follow-ups they ask next
They pick the risky option against your advice. How do you behave?
Commit fully and make it as safe as possible, with extra monitoring and a rehearsed rollback. Sulking or saying I told you so destroys your ability to be heard next time.
How do you quantify risk when you genuinely do not know?
Say so, and give the failure mode and blast radius instead of a fake probability. "I cannot tell you the odds, but if it fails, payments fail" is honest and still decision-useful.
What the interviewer is listening for
- Finds the real driver behind the date
- Quantifies risk in business terms
- Offers options and accepts the decision
What sinks the answer
- Flat refusal
- Vague risk language
- Resentful compliance afterwards
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 first [asked what the date was tied to]. Then [made the risk concrete: this specific failure mode at this traffic level]. I brought [3 options with trade-offs] rather than a no, [let them make the business call], and [wrote down the decision and reasoning].”
Keep going with behavioural
Mid
Tell me about a time you broke production. What happened and what did you do?
Mid
Tell me about a time you disagreed with a developer about how something should be deployed.
Mid
Tell me about a time you were on call and it went badly.
Mid
Tell me about a mistake that cost the company money.
Mid
Walk me through a time you inherited a system nobody understood. Where did you start?
Mid
Tell me about something repetitive you automated. How did you decide it was worth it?
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