How to Answer 'Tell Me About a Time You Disagreed With Your Manager'
Why This Question Exists
The disagreed with manager interview question is a test of two things simultaneously: your ability to think independently and your ability to handle authority professionally. Interviewers want to see that you're not a passive yes-person who accepts every bad decision — and also that you're not someone who fights every call that doesn't go your way.
The failure modes are predictable:
Too cautious: "I always try to align with my manager's vision. I might raise a concern but ultimately I support whatever decision they make." This sounds like someone who would never push back on anything, which is a problem in any knowledge work role.
Too aggressive: "I thought my manager was wrong and I wasn't afraid to say so. I pushed hard for my approach." Without nuance about how you pushed and what you did when you didn't get your way, this signals poor judgment.
What works is a story that shows you raised a real concern, through the right channels, with good reasoning — and either influenced the outcome or accepted the decision gracefully and moved on.
Picking the Right Story
A good disagreement story has these qualities:
The disagreement was substantive. It should be about something that mattered — a product decision, a technical approach, a hiring call, a strategy — not a preference about how meetings are run.
You had a legitimate, well-reasoned position. You weren't just resistant. You had data, experience, or a clear rationale.
You raised it directly with your manager. Not to other team members, not passive-aggressively in a Slack channel — directly.
The resolution was professional. Either you influenced the decision, or you disagreed and committed. Both are acceptable outcomes. What's not acceptable is "I kept pushing until it became a problem" or "I just did it my way anyway."
The Structure: Context → Your Position → How You Raised It → Resolution
- Context — What was the decision or situation your manager was taking a direction on?
- Your position — What did you think should happen instead, and why?
- How you raised it — What did you actually say, in what setting, with what framing?
- Resolution — What did you and your manager land on? What happened with the work?
Bad Answer
"I once disagreed with my manager about a technical decision. I explained my perspective but they went with their approach. I respected their decision and we moved forward. It ended up being fine."
No detail, no learning, no real story. "It ended up being fine" sounds like the candidate is either minimizing the conflict or has nothing to say about it.
Good Answer
"My manager wanted to ship a new analytics dashboard to all enterprise customers at once — a hard cutover. I thought we should do a phased rollout to a subset first, given that the new UI was a significant departure from what customers were used to.
I asked for 20 minutes to walk through my concerns. I pulled up our support ticket volume from the last major UI change — it had spiked 3x in week one — and estimated that a hard cutover to all 80 enterprise accounts simultaneously would create a support load we weren't staffed to handle. I also proposed a specific alternative: 10 accounts in week one, review support volume, then roll out to the rest.
My manager pushed back — the sales team had made commitments around the launch date. We went back and forth and landed on a middle path: staged rollout, but on a compressed two-week timeline instead of my original four-week proposal. I thought two weeks was too fast but it was better than all-at-once, and I committed to it fully.
Support volume did spike — about 2x — but it was manageable. I was wrong about the severity; my manager was right that the urgency was real. The post-mortem actually strengthened our relationship because I'd raised a legitimate concern and we'd found a workable solution together."
This answer shows a real disagreement with real stakes, a structured way of raising it (data, proposal, meeting), a professional outcome (compromise, full commitment), and honest reflection on who was right. That last part — acknowledging the manager's decision was reasonable even if you weren't fully convinced — is unusually credible.
What to Do If You've Never Pushed Back on a Manager
If you genuinely can't think of a time you disagreed with a manager, that's a problem to address before the interview — not something to admit in it. Push harder:
- Was there ever a project direction you thought was suboptimal?
- A hiring decision you would have made differently?
- A technical approach you had concerns about but didn't voice?
The last one is actually a useful story if you frame it as: "There was a time I should have raised a concern and didn't — here's what I learned from that." That level of self-awareness can make a stronger impression than a conflict story delivered without insight.
Practice This Now
This answer lives or dies on tone. The exact same story sounds confident and professional in one delivery, and combative or weak in another.