Should I pick a disagreement I won or one I lost

Pick one you lost and executed anyway. Interviewers hear the winning version constantly and it tells them nothing about how you behave when a decision goes against you. A story where you were overruled, delivered the work properly, and later found out your manager had information you did not is the strongest version of this answer.

Is it risky to say my manager was right

It is the opposite of risky. Saying your manager was right, and naming the specific thing you had not considered, demonstrates that you update your view when the evidence changes. The answer that worries a hiring manager is the one where the candidate has never once been wrong in a disagreement with someone senior.

What if I have never disagreed with a boss

You have, you are probably filtering for dramatic conflicts. Use a small one: a priority you thought was wrong, a process you wanted changed, a deadline you thought was unrealistic. The scale does not matter. What matters is that you said it out loud to them and that you can describe what happened next.

Disagreed With Your Manager: Answer Examples

Why interviewers ask this

When an interviewer says tell me about a time you disagreed with your manager, they already know how the story ends, because it ends the same way in almost every interview. The candidate raised a concern, brought data, the manager reconsidered, and the outcome was better for it. That version answers a question nobody asked. What the interviewer is trying to establish is whether you can lose an argument to someone senior and then go and execute their decision properly. That is the actual job, several times a quarter. A candidate who only has stories about being vindicated is telling you, without intending to, what happens on the occasions when they are not.

An answer that sounds fine

My manager wanted to push our new onboarding flow live before we had run it past the support team, because she was under pressure to hit a quarterly commitment. I disagreed, and I thought the volume of tickets would swamp us. So I pulled the numbers from the last two launches, showed her we had seen a forty percent spike in contacts each time, and suggested we soft launch to ten percent of new signups instead. She agreed it was worth a week. We caught two confusing steps in the flow during that week, fixed them, and the full launch went out with contacts up only about eight percent. It was a good example of disagreeing constructively and letting the evidence lead the conversation rather than making it personal, which is something I try to do whenever I push back on a decision.

Where it breaks

The answer is well built and it describes a disagreement the candidate won. That is the problem, because winning is not the skill in question here. The interviewer has a team where decisions go against people regularly, and what they need to know is what this candidate does on the Monday after being overruled, which this story cannot tell them. There is a quieter tell as well. The manager in this account has no reasoning of her own beyond quarterly pressure, which makes her an obstacle who yields rather than a person holding a defensible position, and real managers are almost never the first thing and almost always the second. Anyone who has looked up how to answer interview question disagreement with boss has read the advice to show data and stay respectful, and that advice produces exactly this answer, which is why it no longer distinguishes anybody.

The follow-up

Did you end up doing it their way or yours, and were they right?

Mine, in that case, so I suppose I won that one. Although, I mean, she was right that the delay cost us the quarterly number, which I did not really weight at the time. There was another one where she wanted to keep a legacy report running and I thought it was dead weight. We kept it, and I let it go at the time. Turned out finance was using it for the audit and I had not checked.

The second story is the one worth the interview, and it took a direct question to get it out. He was overruled, he was wrong, and he found out he had been wrong because he had not checked who depended on the thing he wanted to kill. That is a candidate learning the limits of his own information, which is worth considerably more to a hiring manager than a candidate who once produced a convincing chart. The chart is a skill. Knowing what the chart does not contain is judgment. Notice also that he had this story available and did not choose it, because he had been taught that the good answer is the one where he wins.

An answer that holds up

I wanted to retire a legacy revenue report that took me half a day each month to maintain, and my manager said no. I pushed back twice. Once in our one to one, and once over email with a breakdown of the hours it was costing me across the year. She held the line without explaining much beyond saying it was needed for now, which frustrated me at the time because it read as a decision made on instinct rather than on anything I could examine. I kept maintaining it and I stopped arguing, because the decision was hers and I had said my piece. Two months later the audit came round and finance pulled three years of that report. If I had won that argument we would have been reconstructing it from raw exports under deadline. What I took from it is that when someone senior holds a position they cannot fully explain, the reason is usually a dependency I cannot see, and I now ask who else touches something before I propose removing it.

The interviewer asks whether he did it her way, and whether she was right.

Her way, and yes. I maintained the report for another two months while I disagreed with it. She was right and I was working off a picture of the cost that had nothing about the audit in it.

Practice this question

Say your answer to this question out loud, then get asked whether you did it their way and whether they were right. Answer it now, free, no account.

Tell Me About a Time You Disagreed With Your Manager