SeniorBehavioural

Tell me about a time you said no to a senior stakeholder. How did you make it stick without becoming the person who blocks everything?

What they are really testing: They want to see whether your no is anchored in a shared goal like cost, risk, or reliability, and whether you left the stakeholder with a path forward rather than just a refusal.

A real interview question

Tell me about a time you said no to a senior stakeholder. How did you make it stick without becoming the person who blocks everything?

What most people say

drag me

It was a bad idea and against best practice, so I refused and told them we do not do things that way here.

Best practice is not an argument to a business owner, and a refusal with no alternative just teaches people to route around you next time.

The follow-ups they ask next

  • What if he had escalated over your head and got it approved anyway?

    Say you would document the risk clearly and route it through whoever owns the risk acceptance, then implement the safest possible version of the decision.

  • How do you decide when something is worth a hard no?

    Draw the line at irreversible or regulated risk such as data exposure, and be honest that most other things are trade-offs you can negotiate.

What the interviewer is listening for

  • Agreed on the stakeholder's goal before disagreeing on the method
  • Quantified the risk instead of citing best practice
  • Delivered an alternative with a date and a cost
  • Distinguishes a hard no from a negotiable trade-off

What sinks the answer

  • Uses best practice or policy as the whole argument
  • Refuses with no alternative offered
  • Treats the stakeholder as the adversary
  • Cannot say what the risk was actually worth in money or exposure

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 had to hold a line with a director, but here is how I would think about it. I would first say the goal back to them so we are on the same side, then quantify the risk rather than quoting best practice, and then bring an alternative with a date so my no comes with a path to yes.

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