OfferDrill.

Interview questions

The hard ones

How to answer "tell me about a time you disagreed with your manager."

This gives you a way to talk about disagreeing with your boss that shows spine without making you sound like a problem. You'll get the traps, a four-step build, and sample answers you can adapt to something that actually happened to you.

Why they ask it

They're checking two things at once, and they're checking them against each other. First: will you speak up when you think something's wrong? A person who nods at everything is expensive. They let bad decisions go through and nobody finds out until the money's spent.

Second: can you lose gracefully? Most disagreements at work end with someone else's call standing. They want to know what you do in that moment. Do you get on board and do the work, or do you sulk, slow-walk it, and tell people later that you warned everybody?

There's a quieter thing underneath, too. How you talk about your old manager right now tells them how you'll talk about this one. If the story's real but you tell it without contempt, that's the whole test, passed.

What not to say

"I can't really think of one. I've always gotten along with my managers."

It reads as either forgettable or not honest. Everyone has disagreed with a boss. Saying you haven't tells them you either don't pay enough attention to form an opinion or you won't say it out loud. Both are marks against you. You need a real example, even a small one.

A story where your manager was clearly an idiot and you were clearly right.

Nobody in the room knows your old boss. They only know you, and you're the person in front of them trashing someone who isn't there. Keep your manager's reasoning intact in the telling. "She was weighing X, I was weighing Y" beats "she didn't understand the system."

A disagreement you took over their head, to their boss or to a group, without going to them first.

This is the answer that gets people cut. It signals you'll create political messes. If you did escalate, say why you went to them first, what happened, and why escalating was the right call under the circumstances — not that you skipped a step.

Ending the story at "and they ignored me, and later it blew up just like I said."

You've made yourself the person who was right instead of the person who was useful. It also leaves the hiring manager wondering what you did for the six months in between. End on what you did after the decision, not on being vindicated.

Picking something trivial — the meeting time, the font on the deck.

It's a safe story, and that's the problem. It proves you'll push back on things that don't matter. Pick something with a real cost attached: a deadline, a budget, a hire, a decision that would have hurt a customer.

How to build a strong answer

  1. Pick a disagreement where the stakes were real and you handled it cleanly.
    Scan your last few years for a moment you thought a decision would cost something — money, quality, a customer, a person on the team. It doesn't have to be huge. A two-week timeline you thought was unsafe counts. What matters is that something was at stake and you raised it properly. If your best example is one where you went about it badly, pick a different one, or tell that one as a lesson learned and say what you'd do now.
  2. Set it up in two sentences, with your manager's reasoning included.
    Say your role, the decision on the table, and why your manager wanted what they wanted. Something like: "I was the [role]. My manager wanted to ship in [timeframe] because [their actual reason]. I thought that would mean [the specific risk]." Giving their side its due is what makes you sound senior. Skip the backstory about the reorg and the three people who quit. Two sentences.
  3. Say exactly how you raised it — privately, with something concrete in hand.
    This is the part that does the work, and most people rush past it. Name the setting: "I asked for fifteen minutes with him one-on-one." Name what you brought: data, a specific past example, a written list of risks, a cheaper alternative. And name what you asked for, which should be a decision, not a fight. "I laid out the three failure points and proposed we [alternative]. Then I asked what he was seeing that I wasn't." That last question is a real move. Use it if you used it.
  4. Land on what happened after the call was made — especially if you lost.
    Say who decided and what you did next. If your view won, say what the outcome was and give the actual number or result if you have one. If it didn't win, say so plainly and then say how you committed: "He made the call to go ahead. I built [the mitigation] so we'd catch it early if I was right, and I ran the launch." Losing well is a stronger answer than winning. It proves you can disagree without becoming a problem. Then stop. Don't add a moral.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, you disagreed on a timeline and your manager overruled you.

I was the lead on [the project]. My director wanted to launch by [date] because [the real business reason — a client commitment, a board date]. I thought the testing window was too short and we'd ship something that broke for [the specific group of users]. So I asked for time with her one-on-one before the plan went out. I brought the three places I thought it would fail and what each one would cost us if it did, plus an option that pushed the date by [amount of time]. Then I asked her what pressure she was under that I couldn't see, because I assumed there was some. There was. The date wasn't really movable. She heard me out and kept the date. So I asked for [the specific thing you asked for instead] — we ended up doing a staged rollout to [percentage] of users first so we'd find problems small instead of big. We did hit one of the issues I'd flagged, caught it in the first group, and fixed it before full release. I still think the longer timeline was the better bet. But she had information I didn't, and once she decided, my job was to make it work.

You disagreed on something with real money behind it, you did it privately with evidence, you asked a genuine question instead of just arguing, and when you lost you found a way to protect the downside anyway. The closing line is honest without being sour.

Early career, one internship or first job, small stakes but handled well.

During my internship at [company], I was cleaning up [the dataset or process] and my supervisor wanted me to do it [their way]. I'd found that [the other approach] was catching errors the first method missed — I'd run both on the same batch and the difference was [the actual number of records or whatever you measured]. I was pretty nervous about saying anything, honestly, because I'd been there about six weeks. So I sent him a short message asking if I could show him something for five minutes. I walked him through both outputs side by side. He asked me a couple of questions I couldn't answer — mostly about why the original method existed in the first place, which turned out to be [the reason]. We ended up using my approach for [the specific subset] and keeping his for the rest. The thing I took from it is that I should have asked why it was built that way before I assumed it was wrong. But I'd still speak up. He told me later he'd rather hear it.

Small stakes are fine when you're early. The example shows you brought evidence, you weren't reckless about it, and you learned something real. Admitting you should have asked "why" first is a strength, not a weakness — it's what experience actually teaches.

You disagreed, you pushed hard, and it turned out your manager was right.

My manager decided to [the decision] and I disagreed with it strongly. I thought [your reasoning]. I made the case twice — once in our one-on-one with [what you brought], and once more after I'd talked to [whoever gave you more information], because I thought the new information changed things. He listened both times and stuck with his call. I told him I wasn't convinced, but that I was in, and then I ran [your piece of it] the way he wanted it. He turned out to be right. [The outcome.] What I'd missed was [the thing you didn't see — a constraint, a longer time horizon, something about the customer]. I was looking at it from inside my own function. That one made me slower to assume I had the full picture, and it also made me more willing to say "here's what I'd need to see to change my mind" — which is a better question than just restating my position louder.

Being wrong out loud is uncomfortable and it reads as extremely credible. You still showed you'll push, twice, with new information. And the last line gives them a concrete habit you built, which is more convincing than "I learned to be open-minded."

What comes next

Answer this one well and the interviewer usually goes here:

  • What would you do differently if that came up again?
  • How do you know when to let something go versus keep pushing?
  • Have you ever gone over your manager's head? What happened?
  • Tell me about a time a decision went ahead that you still think was wrong. How did you handle it with your team?
  • How do you give your manager bad news?
  • What kind of manager do you work best with?
  • Has a direct report ever disagreed with you? How did you handle it?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

Pick the true story you're a little hesitant to tell, tell it in four clean parts, and trust that a person who can disagree and then commit is exactly who they're hoping walks in.