Tell Me About a Time You Disagreed with Your Manager

What Interviewers Are Actually Testing

This is NOT a question about conflict. It's a question about professional judgment, influence skills, and intellectual courage. They want to see that you can disagree constructively while maintaining the relationship.

Hidden intent: How do you handle situations where you're right but don't have authority? Do you escalate destructively, comply silently, or find a way to make your case with evidence?

Mid-level: Show you can express disagreement professionally and either persuade or commit after losing the argument. Senior: Demonstrate that you disagree based on data/evidence (not ego), that you've influenced decisions at the organizational level, and that you know when to commit and move forward even when you still disagree (disagree-and-commit).

Strong Answer (Senior-Level)

My engineering manager wanted to rewrite our payment processing service from Python to Go to improve latency. The service was handling 50K transactions/day with p99 latency around 800ms.

I believed the latency issue wasn't language-bound. Our profiling data showed 85% of latency came from synchronous database calls and a third-party fraud detection API, not CPU-bound processing. A rewrite would take 3-4 months, introduce regression risk in a critical payment path, and not address the actual bottleneck.

I put together a one-page analysis showing the profiling data, estimated the rewrite timeline with regression testing, and proposed an alternative: async database calls using connection pooling plus a caching layer for the fraud API responses. I scheduled a 30-minute meeting — not a Slack message, because the nuance needed a real conversation.

My manager's concern about Go was valid for our future scale — Go would handle 10x traffic growth more efficiently. I acknowledged this and proposed we revisit the rewrite after implementing the quick wins, using the latency improvement data as a baseline.

We implemented the async changes in 2 weeks. P99 latency dropped from 800ms to 180ms. The rewrite was deprioritized because the immediate problem was solved. Six months later, we did eventually migrate to Go, but by then we had clear data on which components actually needed it.

The key: I disagreed with data, not opinion. I acknowledged the validity of my manager's longer-term concern. And when the decision was made, I committed fully to the implementation.

What Weak Answers Miss

• Describes a trivial disagreement — choosing a meeting tool or code formatting style doesn't demonstrate professional judgment
• Frames it as "I was right, my manager was wrong" — this is a collaboration question, not a vindication story
• No data or evidence in the argument — just "I felt we should do X" without backing it up
• Doesn't mention what happened after the disagreement — the resolution and relationship impact matter as much as the conflict
• Skips the commit phase — not explaining how you moved forward after the decision was made suggests you hold grudges

Follow-Up Questions Interviewers Ask

1. "What would you have done if your manager had still decided to proceed with the rewrite?" — Strong answers demonstrate disagree-and-commit: "I would have committed fully to the rewrite, raised my concerns for the record, and made sure the implementation succeeded."
2. "Have you ever been wrong in a disagreement with your manager?" — Strong answers show self-awareness and growth. The ability to admit being wrong is as important as the ability to disagree.
3. "How do you decide when to push back vs when to accept a decision?" — Strong answers describe a framework: push back when you have data and the stakes are high, accept when the decision is reversible or when you've made your case and the authority has decided.

Related Resources

• Behavioral Interview Questions
• Describe a Project Failure
• STAR Method Practice