● Interview question

“Tell me about a time you disagreed with your boss” — answers that work

By The Don't Wing the Interview Team · Published 5 July 2026

This question is a judgment test disguised as a conflict question. The interviewer wants to know three things: whether you speak up when you think a decision is wrong, whether you do it with evidence and respect rather than ego, and what you do after the decision goes against you. A candidate who has never disagreed with a manager looks passive; one who frames the manager as a fool looks unmanageable.

The strongest answers follow a simple arc: you noticed a specific risk in a decision, you brought data and a proposed alternative to your manager privately, a real conversation happened, and you committed fully to whatever was decided — even when it was not your preference. That last beat, often called disagree and commit, is what separates a professional from a complainer.

The biggest trap is choosing a story where you were simply right and your boss was simply wrong. It feels satisfying to tell, but the interviewer hears someone rehearsing a grudge. Pick a disagreement where both sides had a point, and let the process — not your vindication — carry the story.

What the interviewer is listening for

A disagreement about substance — a risk, a customer, a deadline — not about your workload, your title, or personal friction.
Evidence and a proposed alternative, raised privately and once, rather than repeated complaints or public challenges.
Genuine steel-manning of the manager's position: you can explain why their view was reasonable given what they were accountable for.
A clean disagree-and-commit beat: once the call was made, you executed it fully, without back-channel grumbling or quiet sabotage.
Respect in the telling — no eye-rolling subtext, no story engineered to prove the boss incompetent.
Some sign the relationship got stronger, or that you learned something about how and when to escalate.

How to structure your answer: Position, Case, Decision, Commit

01
Set up the decision and the stakes
One or two sentences on what your manager decided or planned, and the specific risk you saw. Make the stakes concrete — a delivery, a customer, a safety or quality issue.
02
Make your case the right way
Describe how you raised it: privately, with data or a worked example, and with an alternative attached. Show you acknowledged the pressures your manager was balancing.
03
Report the decision honestly
Say what was decided — adopted, adapted, or overruled — and give your manager credit for the parts they got right. Resist any temptation to score points.
04
Commit and close the loop
Explain how you executed the final decision at full effort, what the outcome was, and what the exchange taught you about disagreeing productively.

A weak answer — and what the interviewer hears

“My boss wanted to launch a campaign that I knew was going to flop, and I told him so, but he went ahead anyway. Sure enough, it flopped, exactly like I predicted. After that he started listening to me a lot more, so in the end it worked out. I think it shows I have good instincts and I'm not afraid to speak my mind.”

The story exists to prove the boss wrong and the candidate right — a rehearsed grudge, not a judgment sample.
“I knew” and “I predicted” with no evidence, no alternative proposal, and no sign of how the disagreement was actually raised.
The candidate appears to have watched the campaign fail rather than helping it succeed once the decision was made.
A hiring manager hears a preview of their own future: every overruled opinion becomes an I-told-you-so.

Example answers that work

Illustrative examples — build yours from your real experience, never from a script.

Manufacturing — disagreeing over a schedule decision

At the packaging plant where I was a line supervisor, my plant manager decided to postpone the quarterly preventive maintenance window on our oldest filler line to protect a big shipment commitment. I understood the pressure — the customer was our largest account — but that line had been drifting on torque readings for weeks, and I believed we were trading a planned eight-hour stop for an unplanned multi-day one. I pulled the downtime log and the recent quality checks, and asked for fifteen minutes with him privately. I proposed a middle path: a compressed maintenance window on the weekend, with my team split across two shifts so the shipment date held. He challenged my numbers, we went through them together, and he approved the weekend plan but cut the scope to the two highest-risk components — his call, and a reasonable one given overtime costs. The technicians found a worn drive coupling that would likely have failed mid-run. The shipment left on time, and afterward he started asking supervisors for risk flags before schedule changes, which I took as the real win.

Why this works

The disagreement is about a concrete operational risk with real stakes, not personality or preference.
The candidate brings logs and readings, proposes an alternative, and raises it privately — the full evidence-based playbook.
The manager's constraint (the customer commitment) is treated as legitimate, and he keeps authority over the final scope.
The outcome is shared credit and a better process, not a told-you-so moment.

Common mistake: Telling this story with the worn coupling as the punchline — “and I was right” — instead of the collaborative decision. The discovery matters less than how the disagreement was handled.

Marketing — overruled, then committing anyway

In my second year as a marketing coordinator at a B2B software firm, our head of marketing shifted most of the next quarter's budget into two industry trade shows. I thought our webinar funnel deserved that money — our last three webinars had produced steadier pipeline than the previous year's booth. I put a one-page comparison together, cost per qualified conversation for each channel based on our own numbers, and walked her through it one-on-one with a proposal to split the budget. She heard me out, then explained something I had not weighted: two strategic accounts had specifically asked to meet us at those shows, and face time with them mattered more than channel efficiency that quarter. She kept the original plan. I told her I disagreed but was fully in, and then I acted like it — I built the pre-show outreach sequences, booked twenty-eight meetings for the booth team, and never relitigated the decision. One of those strategic accounts advanced to a contract discussion that quarter. I still think webinars were undervalued, but she was optimizing for something I could not see from my seat, and that reshaped how I argue budget cases now.

Why this works

The candidate loses the argument and commits anyway — the exact disagree-and-commit behavior managers want evidence of.
Effort after the decision is specific and verifiable: outreach sequences built, twenty-eight meetings booked.
It shows intellectual honesty: the boss had context the candidate lacked, and the candidate says so without self-flagellation.
The closing lesson — arguing with awareness of what leadership is optimizing for — signals growth, not resentment.

Common mistake: Ending with “but I still think I was right” as the final note. Keep the emphasis on full-effort execution and what the manager saw that you did not — otherwise the commitment sounds grudging.

Frequently asked questions

What if I genuinely have never disagreed with a boss?

Look harder — the question is really about pushing back on any decision from someone with more authority. A priority call you questioned, a deadline you thought was unsafe, a process you asked to change all qualify. Saying you have never disagreed reads as either low engagement or fear of authority, and both score worse than a modest, well-handled disagreement told honestly.

Should I pick a story where I turned out to be right?

Be careful with it. If you were right, keep the tone factual and give your manager credit for hearing you out; never gloat. A story where the decision went against you and you still executed it wholeheartedly is often more impressive, because it proves you can lose a debate without losing commitment — a quality managers actively hire for.

How do I avoid sounding difficult or insubordinate?

Show that you disagreed through the right channel: privately, once, with evidence and a concrete alternative — not repeatedly, publicly, or behind your manager's back. Make clear you understood their constraints and that you accepted the final call as theirs to make. Interviewers are listening for respect for the decision-making process, not for whether you won.

What if my boss reacted badly when I pushed back?

You can mention a cool reception without making the manager the villain. Focus on what you controlled: how you raised it, how you adjusted your approach, and what you learned about timing or framing. If the relationship recovered, say so briefly. Spending your answer on the manager's flaws shifts the story from your judgment to your grievances, and that always costs you.