How to answer: “Tell me about a time you disagreed with your manager”

What the interviewer is evaluating

Interviewers ask this question to assess whether you can handle professional disagreement constructively. They want to see that you have opinions and the confidence to express them through appropriate channels, whilst also knowing when to defer and how to do so graciously even when you do not agree with the outcome.

They are also listening for red flags: candidates who blame managers, who refused to implement decisions they disagreed with or who describe every conflict as a case of them being right and their manager being wrong. Those patterns suggest someone who is difficult to manage and will likely cause disruption in a new team.

A strong example answer

About two years ago, my manager wanted to accelerate a major system migration from twelve months to seven, following pressure from the board to show progress ahead of a strategic review. My view was that seven months was not achievable safely. We had three legacy integrations that had never been fully documented and an external vendor whose delivery timelines were already slipping.

I raised my concerns in a one-to-one meeting rather than in the team forum, because I wanted to give him the opportunity to engage with my reasoning privately before any decision was made publicly. I put together a two-page summary of the specific risks with each legacy integration, along with a proposed compromise: a twelve-month timeline with clear milestone reviews at months three and six that would give the board visibility of progress without compromising delivery quality.

He listened carefully and pushed back on some of my assumptions, which was fair. I had been conservative on one of the integration estimates. We ended up agreeing on a nine-month timeline with an explicit risk register that was shared with the board. That felt like the right outcome.

The migration did encounter problems at month seven, exactly where I had flagged the risk. We completed it at month ten, a month ahead of the adjusted plan. My manager was generous enough to acknowledge in the retrospective that the early risk conversation had been valuable.

The lesson for me was about the importance of raising concerns early, with evidence, through the right channel, and then committing fully to whatever is decided.

Use the STAR framework

situation: Manager wanted to compress a system migration from twelve months to seven, following board pressure. Three poorly documented legacy integrations and a slipping external vendor made the shorter timeline high-risk.

task: Raise the concern professionally without causing unnecessary conflict, and present an alternative that addressed the board's visibility needs whilst protecting delivery quality.

action: Raised concerns privately in a one-to-one meeting with supporting documentation, proposed a nine-month compromise with milestone reviews, and engaged in good faith with the manager's pushback on estimates.

result: Agreed on a nine-month plan with a shared risk register. The migration encountered problems at month seven as predicted but completed at month ten, one month ahead of the adjusted plan.

Common mistakes to avoid

Weak answers usually fail the same three ways: too vague, a little defensive, or about something this job never asks you to do.

• Saying you have never disagreed with a manager, which reads as either no initiative or a habit of telling people what they want to hear
• Describing a disagreement that makes your former manager look incompetent or malicious
• Choosing an example where you won the disagreement unambiguously and your manager was simply wrong
• Refusing to go into any detail to "protect confidentiality", which is usually just evasion

How to make your answer stronger

Read these once, then say the whole answer out loud. Waffle is invisible on paper and obvious the second you hear it.

• Choose a disagreement about a professional decision, such as a strategy, a process or a timeline, rather than a personal clash. The former shows professional judgement; the latter risks sounding like a complaint.
• Show that you raised the disagreement through the appropriate channel, at the appropriate time and with supporting evidence. This is what "professional courage" looks like.
• Be balanced about the outcome. If your manager was ultimately right, say so. If you were right, say that too, then give the opposing view its due.
• Demonstrate that you committed fully to the agreed course of action even if it was not your preferred approach. Interviewers need to know you can implement decisions you did not choose.
• End with a reflection on what the experience taught you. This turns a potentially sensitive topic into a learning story.

Frequently asked questions

What if I have never had a significant disagreement with a manager?

Look more broadly. The question works just as well for a disagreement with a senior colleague, a project lead or a stakeholder above you. If you genuinely have no suitable example, choose the smallest genuine disagreement you can recall and prepare it thoroughly.

Is it acceptable to say that I was right and my manager was wrong?

Yes, if that is what happened and you can describe it without bitterness or superiority. The most credible version of that story includes a clear account of how you raised your view, how you engaged with the alternative perspective and how you behaved after the decision was made.

Should I avoid naming my former manager or company?

You do not need to name individuals, but you can name the company if you choose. What matters is that the story is specific and believable, not that it is anonymised to protect anyone.

What if the disagreement involved a genuine ethical concern?

If you are referring to something you believed to be ethically wrong, say so clearly. Describe how you raised it, what the response was and what you did as a result. These are the most important disagreements to have handled well, and interviewers take them seriously.