There are two ways to fail this question and they are opposites, which is what makes it hard. Answer that you never disagree with managers, that you trust their judgement and get on with it, and you sound like someone with no spine who will let a bad decision happen rather than speak up. Answer with a story about how you fought your manager and won, and you sound like a problem, someone who cannot take direction.
The competency being tested lives in the narrow space between those two. It is: can you challenge a decision the right way, at the right time, and then commit to the outcome whether or not it went your way. That last part, the committing, is the bit almost everyone drops.
The shape of a strong answer
A good disagreement story has a distinctive arc:
- You raised it privately and early, not in front of others and not after the decision was locked.
- You led with the concern, not the ego. The disagreement was about the work or the risk, never about who was right.
- You made your case and then accepted the call. Either your manager changed their mind, or they did not and you got behind the decision anyway.
The version where you accept the call and it turns out you were right is actually the strongest of all, because it shows you can disagree, defer, and not gloat. Interviewers notice restraint.
A worked example
"In a summer job at a small events company, my manager wanted to cut the budget for the check-in staff at a conference to save money, moving from four people to two. I thought it was a mistake, because the previous year the queue at registration had been the number one complaint on the feedback forms, and two people would make it worse.
I did not want to just object, so I went to her one to one before it was final, and rather than saying 'I disagree', I brought the previous year's feedback and the arrival pattern, which showed everyone turned up in the same forty-minute window. My point was that the saving was real but the risk was to the thing clients complained about most.
She listened, but she still decided to go with three people rather than four, not the two she had planned and not the four I wanted. Which was fair. It was her budget and her call. I did not sulk about not getting all four, I just made sure the three of us on the day were properly briefed so the queue moved fast, and registration did not come up in the feedback that year.
What I learned was that disagreeing works far better when you bring the evidence and then genuinely let them decide. If I had dug in for four, I think she would have stopped listening to me on the next thing."
Why it works
The candidate disagrees, which clears the first bar: they are not a pushover. But look at how carefully it is done. Private, before the decision is final, evidence-led, and framed around the client risk rather than "I think you are wrong". Then the manager makes a partial call, three not four, and the candidate does not treat that as a defeat. They commit and make it work.
The closing insight is the sharpest part: disagreeing well protects your ability to disagree next time. That is a mature understanding of workplace capital that most candidates do not have, and stating it plainly signals you will be an easy person to manage precisely because you know how to push back without becoming exhausting.
What to avoid
Claiming you never disagree. It reads as either dishonest or spineless. Managers want people who will tell them when something is off, tactfully. Pretending you always agree is not the safe answer it feels like.
The heroic override. "I knew better, I pushed, I was proved right, they thanked me." Even if true, it makes you sound like someone who treats managers as obstacles. Strip the triumph out.
Disagreeing in public. If your story involves contradicting your manager in a meeting in front of the team, the interviewer hears someone who will undermine them. The private-first instinct matters.
Never committing. If the decision went against you and your answer stops there, it looks like you carried a grudge. The interviewer specifically wants to hear what you did once the call was made against you. That is where they find out whether you are safe to hand a decision to.
Choose the disagreement carefully
The best examples are disagreements about substance with a real stake, a budget, a deadline, a quality decision, an approach with a downside you could see. Avoid trivial ones (where to go for the team lunch) and avoid ones where your manager was behaving badly, which is a different and riskier story. If you are early in your career, a tutor, a supervisor on a project, or a team captain all count as the "manager" figure. The competency skeleton does not care about their job title.
The single most common failure here is tone drifting from "I raised a concern" into "I was right and they were wrong" without the candidate noticing. Say your answer aloud and listen for whether you sound like someone a manager would want to hear from. If you practise it with feedback, that drift gets caught before the day, not during it.