How to Answer “Tell Me About a Time You Disagreed With Your Manager”

The interviewer isn't asking whether you were right. They're picturing you as a first-year at 1 a.m., looking at a number your associate got wrong, and wondering what you'll do next.

This one shows up in almost every behavioral round, and it's easy to underestimate. What sits underneath it is judgment inside a hierarchy, which is the exact situation you'll be in for your first two years in banking or PE.

As an analyst you will regularly see things your associate or VP missed. A growth rate that doesn't tie to the CIM. A comp that shouldn't be in the set. A page that contradicts another page. The person across the table wants to know whether you'll say something, whether you'll say it well, and whether you can let it go when the call doesn't go your way.

What the question is actually testing

Strip away the wording and the interviewer is listening for a handful of things. None of them is “did you win.”

• Your disagreement had a real basis. You noticed something specific, and you had a reason beyond preference or a gut feeling.
• You raised it in the right place and at the right time. Privately, early enough to matter, and not in front of a client or a room full of senior people.
• You came with evidence and a suggestion, not just a complaint.
• You were open to being wrong, and you actually listened to the other side.
• Once a decision was made, you committed to it and did the work properly, even if it wasn't your call.

That last one gets skipped more than any other. Plenty of candidates tell a story that ends with them being proven right, and the interviewer walks away unsure whether this person can take an instruction they don't love.

Picking the right story

Most of the answer is decided before you open your mouth, by which story you choose. A good one has three features. The disagreement was about the work itself (a number, a method, a deadline, a priority call), the stakes were real but not dramatic, and the other person comes across as reasonable.

That last point matters. If your manager in the story sounds careless or foolish, the interviewer starts wondering how you'll describe them in a year. You want the disagreement to read as two sensible people looking at the same problem differently.

Where good stories usually come from

• An internship where you questioned an assumption, a data source, or how something was presented.
• A part-time job where you thought a process could be done better and had to convince someone senior.
• A student investment fund or club where the lead wanted to pitch something you had doubts about.
• A group project with a clear lead, where you pushed back on the approach or the split of work.

Stories to leave out

• Anything about personality, tone, or how someone treated you. That's a different question, and it rarely lands well here.
• A disagreement about an ethical or legal issue. It changes the question entirely and puts the interviewer in an awkward spot. If they want that story, they'll ask for it directly.
• A story where you went over your manager's head on the first attempt.
• Anything you'd be uncomfortable having the interviewer repeat to a colleague.

A structure that holds up

STAR (situation, task, action, result) is fine as a skeleton, but this question needs one extra beat at the end. Roughly:

1. The setup, in two sentences. Where you were, what you were working on, who the other person was by role.
2. The disagreement, stated plainly. What they wanted to do, what you thought instead, and the specific reason.
3. How you raised it. When, where, what you brought with you, and how you framed it.
4. What happened. Whether they changed course, you changed your mind, or you met somewhere in the middle.
5. What you'd keep doing. One sentence on what the experience taught you about raising concerns, ideally something you could picture doing again as an analyst.

Aim for about ninety seconds to two minutes. Most of the time should go to steps two and three. The setup is where people ramble, and the interviewer doesn't need the full org chart to follow along.

What a solid answer sounds like

Here's the shape of one, written as a hypothetical so you can see the beats. Use your own story. A borrowed one falls apart the moment the interviewer asks a follow-up.

Notice what it does. The disagreement is about a number, with a concrete reason. It was raised privately, with work attached and a soft opening. The outcome was a compromise, not a clean win, and the candidate executed the version they didn't fully prefer. That's close to exactly what an interviewer hopes to hear.

If you turned out to be wrong

Don't avoid these stories. A disagreement where you pushed back, heard the other side, and realized your manager had context you didn't is often a stronger answer than one where you were vindicated. It shows the thing interviewers worry about most in a confident candidate, which is whether you can actually be talked out of a position.

The key is that your original concern still has to be reasonable. “I thought we should do X, they explained Y, and I hadn't known about Y” works. “I thought we should do X for no real reason and I was wrong” doesn't tell them anything good.

Why this question lands differently in finance

In a lot of industries this is a generic culture question. In banking and PE it maps onto something you'll do every week. Models and decks pass through several layers of review, and the analyst is usually the person closest to the numbers. Interviewers want someone who will flag a problem, because a wrong number in a client book is expensive. They also want someone who won't relitigate every comment on a page turn.

If you can, pick a story that sounds like that world. A disagreement over a number, a source, or a deadline tradeoff is easier for a banker to picture than a dispute about a club's event schedule. It doesn't need to be a finance job. It just needs to involve the kind of judgment the job does.

The follow-ups to expect

A good interviewer will push on the story once you finish. Have honest answers ready for these.

• "How did your manager react when you brought it up?"
• "What would you have done if they'd just said no and moved on?"
• "Looking back, would you handle it any differently?"
• "Have you ever disagreed and decided not to say anything?"
• "What if you'd found the problem the night before it went to the client?"

For the “what if they said no” version, the answer they want is simple. You would do it their way, do it well, and maybe keep a note of your concern in case it came up again. Escalating past them is something you'd only consider if the issue were serious, and even then you'd tell them first.

Answers that quietly cost you

• "I don't really disagree with people." It reads as either untrue or a sign you won't speak up when it counts.
• A story where the manager is the villain and you're the hero.
• Raising the issue in front of a client, a senior person, or the whole team.
• Going around your manager before talking to them directly.
• An ending where you were right and nothing else happened. No sign you'd have committed if you'd lost.
• Spending a minute on background and fifteen seconds on what you actually did.
• Vague language like "we had different visions" with no concrete detail about what the disagreement was.

Common questions

This answer usually comes right after your resume walk-through, and the two work best when they sound like the same person. See what “walk me through your resume” is actually testing for how to set that one up.