Tell me about a time you disagreed with your manager.

The complete answer guide: what this question really tests, two example strong answers in different angles, the common weak answer rewritten, and the trap most candidates fall into. This is a conflict archetype question — see the broader pattern guide for the structural shape.

What this question is really testing

The interviewer isn't evaluating whether you're a "yes person" or checking if you have a backbone. They're making a binary read on whether you understand organizational hierarchy and political capital. Specifically, they want to know if you're someone who escalates disagreements appropriately, picks battles worth fighting, and can maintain a productive working relationship even when you don't get your way. The fear lurking behind this question is hiring someone who either becomes a passive doormat who never speaks up when they see problems, or worse, someone who turns every tactical difference into a hill to die on and poisons team dynamics.

What separates strong candidates from weak ones is demonstrating that you disagreed about something substantive (not petty), approached it with data and deference (not emotion), and most critically, that you could execute fully on the decision even after losing the argument. The interviewer is watching for any hint of bitterness, score-keeping, or inability to commit once a decision is made. They're also assessing your judgment: did you pick an appropriate battle, or are you the person who argues about everything? The best answers show you understand that disagreeing is part of your job, but that your manager's decision-making authority is also part of the structure that makes organizations function.

Two strong answers, two angles

Angle A: Data-driven reversal

"In my last role as a product manager, my manager wanted to delay our mobile app launch by two months to add a social sharing feature he felt was critical. I disagreed because our user research showed that 80% of our target users prioritized offline functionality, which we already had built. I put together a one-pager with the research data, competitive analysis showing our competitors weren't winning on social features, and a proposal to launch on time with social sharing as a fast-follow in six weeks. After presenting it in our 1:1, he agreed to move forward with the original timeline. We launched on schedule, hit 10K downloads in the first month, and added social sharing in the next release where it got minimal adoption—validating that we'd prioritized correctly."

Angle B: Losing the argument, winning the relationship

"I was a senior engineer when my manager decided to rebuild our authentication service using a new framework I thought was too bleeding-edge for our production environment. I scheduled time with him, walked through my concerns about documentation gaps and the small community size, and suggested we pilot it on a lower-stakes internal tool first. He appreciated the input but decided the performance gains were worth the risk, and he had more context on our roadmap than I did. I committed fully—I became the team expert on the new framework, built out internal documentation, and actually ended up advocating for it on another project six months later. The rebuild went smoothly, and I learned that sometimes the best outcome of a disagreement is discovering your manager was right."

The common weak answer

"My manager wanted to implement a new process for handling customer requests, but I thought it was inefficient. I told him my concerns and we talked about it. Eventually we found a compromise that worked for both of us, and the team was happy with the result."

This answer fails because it's completely bloodless—there's no actual disagreement, no stakes, no specifics about what made the process inefficient or what the compromise entailed. The interviewer learns nothing about your judgment (was this worth disagreeing about?), your approach (how did you make your case?), or your professionalism (what happened to the relationship?). It sounds like you're describing a mild preference difference about where to order lunch, not a meaningful professional disagreement. Reframe it: "My manager wanted to add three approval layers to customer refunds over $50, which would have added 2-3 days to resolution time. I showed him data that 60% of our refunds were under $100 and our CSAT dropped 15 points for every day of delay, then proposed a $200 threshold instead. He agreed, and our resolution time stayed under 24 hours."

The one trap most candidates fall into

The trap is making yourself the hero of the story. When you frame the disagreement as "I was right and I convinced my short-sighted manager to see the light," you're accidentally telling the interviewer that you lack humility and don't respect authority. Even if you genuinely were right and your manager was wrong, positioning yourself as the lone voice of reason signals that you'll be exhausting to manage. The interviewer starts wondering: will this person second-guess every decision? Will they undermine me in front of the team if they disagree?

The counterintuitive move is to give your manager credit even in stories where you changed their mind, and to have at least one story ready where you disagreed, lost the argument, and it turned out fine or even better than your original position. That second type of story is actually more powerful because it proves you can subordinate your ego to team decisions. Interviewers know that in healthy organizations, managers should be right more often than not—they have more context, more experience, and broader visibility. If every disagreement story you tell ends with you being vindicated, you're inadvertently suggesting either that you had terrible managers or that you have an inflated sense of your own judgment. Neither read helps you get the job.

Common questions