Tell Me About a Time You Disagreed With Your Manager: How to Answer
14 min read
·
How to answer 'tell me about a time you disagreed with your manager': the Stakes–Case–Ask–Commit structure, examples, mistakes, and a scored answer.
To answer "tell me about a time you disagreed with your manager," tell one real story in four beats: the decision at stake, your concern and the evidence behind it, how you raised it (privately, respectfully, with a specific alternative), and what was decided — including how you committed to the outcome, even if your manager overruled you. Keep it to about 90 seconds to two minutes spoken, use "I" for your actions, and end with the result and what you would repeat. The interviewer is testing whether you speak up with evidence and stay a good teammate afterward, so "I never disagree" and a story that makes your manager the villain both fail.
The rest of this guide names that structure and maps it to STAR, shows how to choose the story, gives four fictional worked examples (including one where you lose and one where you were wrong), lists the mistakes that sink these answers, explains how the coworker version differs, and shows a weak example answer we wrote and our rewrite run through the Interview Drills scorer.
What is the interviewer testing when they ask about a disagreement with your manager?
The interviewer is testing two things at once: whether you will raise a real concern with someone who has authority over you, and whether you can do it without damaging the working relationship. A good answer proves both — you spoke up with evidence, and you committed once the decision was made.
The question arrives in several forms. They test the same skill with a different counterpart:
- "Tell me about a time you disagreed with your manager." (or "your boss," "your supervisor")
- "Tell me about a time you disagreed with a decision."
- "Tell me about a time you pushed back."
- "Tell me about a conflict at work."
- "Tell me about a time you had a conflict with a coworker."
The manager, boss, and decision versions are about disagreeing upward. "Pushed back" can point at a manager, a client, or a senior stakeholder; pick the story where the pushback mattered most. "A conflict at work" leaves the counterpart open, and the coworker version removes the authority gap entirely — covered in its own section below.
One published version of the "disagree and commit" idea is in Amazon's leadership principles, which say leaders "are obligated to respectfully challenge decisions when they disagree" and that "Once a decision is determined, they commit wholly" (Amazon leadership principles). You do not need to be interviewing there for the pairing to apply: speaking up and committing afterward are the two halves of the answer.
What structure should you use?
Use what Interview Drills calls Stakes–Case–Ask–Commit: the Stakes (what was being decided, why it mattered, and your role), your Case (the concern and the evidence behind it), the Ask (how you raised it and what you proposed instead), and the Commit (what was decided, how you backed it, and the result). It is the STAR method adjusted for disagreement questions, where the Action has to show how you disagreed, not only what you did.
| Beat | Its one job | STAR equivalent | Rough share of a 90-second answer |
|---|---|---|---|
| Stakes | Name the decision, what rode on it, and your role in it | Situation + Task | ~15 seconds |
| Case | State your concern and the evidence — one specific fact, not a feeling | The reason behind your Action (no direct STAR step) | ~15 seconds |
| Ask | Show how you raised it: when, where, what you proposed, how you answered your manager's concern | Action | ~45 seconds |
| Commit | Say what was decided, how you backed it, the result, and the habit you kept | Result + learning | ~15 seconds |
The time shares are our coaching guideline, not research data. At two minutes, the extra time belongs in the Ask beat — what your manager said, and how you responded to it.
The reason the Case gets its own beat: a disagreement without evidence is a preference, and preferences are what interviewers worry about when they hear "I disagreed." One concrete fact — a past incident, a number, a customer complaint — turns "I thought it should be done differently" into a judgment call the interviewer can evaluate.
The reason the Ask is the longest beat: the interviewer is checking how you disagree. Strong Ask beats share four moves, which you can use as a checklist:
- Pick the setting. Raise it one-on-one or in writing before the decision meeting, not as an objection in front of the team.
- Lead with their goal. Show you understood what your manager was trying to achieve before saying where you differ.
- Bring an alternative, not just an objection. A smaller first step, a test, a phased rollout, or a different deadline.
- Take on the cost of your idea. If your alternative creates work or risk, offer to own it.
The reason Commit is not called "Result": in a disagreement story, what you did after the decision is part of the evidence. If you lost, the Commit beat is where you show you made your manager's plan work anyway.
How do you choose the right disagreement story?
Choose a disagreement that passes four checks: it was about work (a decision, plan, deadline, priority, or process — not a personality), you had a concrete reason beyond preference, you raised it directly with the person, and the story has a clear outcome you can state in a sentence. Who won does not matter.
| Too small | Right size | Too risky | |
|---|---|---|---|
| What it sounds like | Font choices, meeting times, a naming debate | A launch plan, a deadline, a hiring call, a process change, a customer commitment | A personal feud, harassment or legal issues, a manager you describe as incompetent, a disagreement you never resolved |
| Why it fails or works | Nothing at stake, so nothing to evaluate | Real stakes, your evidence, a visible way of raising it, a clear outcome | The interviewer remembers the conflict, not how you handled it |
| What to do | Look for a decision with consequences | Use it | Save serious workplace issues for a direct question, or pick another story |
Some published advice adds one more filter: choose a story that ended in compromise. A career coach quoted by The Muse (updated September 2022) recommends a conflict "where you both compromised and came to a mutually beneficial resolution." Compromise endings work, but they are not the only good ones. Three outcomes can each make a strong story:
- You persuaded your manager. Strongest when the Ask shows a smaller alternative and you took on its cost, so it does not sound like you simply won an argument.
- Your manager overruled you, and you committed. Shows you can disagree without dragging your feet. Say what you did to make the decision succeed.
- You were wrong. Shows you disagree in good faith and update your view. Say what you got wrong and what you now check first.
Scale the story to your level. Early-career candidates can use a disagreement with a shift lead, internship supervisor, or project lead. Senior candidates should pick one with team-level stakes — a roadmap call, a hire, a budget — because a small procedural disagreement reads as avoiding the question at that level.
If no story comes to mind, look through your story inventory before deciding you have none. The interview story bank method covers mining your history for stories, and a disagreement story can sometimes come from the same project as a failure or leadership story with different actions emphasized.
What does a good disagreement answer sound like?
A good disagreement answer names the decision, gives one piece of evidence, shows how you raised it in "I" language, and ends with what was decided and what you did next. The four examples below are fictional — written for this guide, with invented situations and figures — and each shows a different outcome. They are written shorter than a full 90-second spoken answer; when you say yours aloud, the extra time goes into the Ask beat.
You persuaded your manager (operations coordinator)
"My manager wanted to move our weekly inventory count from Friday to Monday to free up the weekend crew. (Stakes) I disagreed because Monday was our heaviest delivery day — I'd tracked the last six Mondays, and four had trucks arriving before 9 a.m. (Case) I asked her for ten minutes that afternoon, showed her the delivery log, and said I agreed with the goal of freeing up the weekend. Then I proposed Thursday evening instead, and offered to run the first two Thursday counts myself so she wasn't taking a risk on my idea. (Ask) She agreed to try it for a month. The counts finished on time all four weeks, the weekend crew got their Fridays back, and Thursday became the permanent count day. I learned to open with the goal we shared before I say what I'd change. (Commit)"
Your manager overruled you, and you committed (account manager)
"My manager decided to offer a client a two-week delivery date on a custom order to win a renewal. (Stakes) I thought it was too tight — our last two custom orders had each taken about three weeks. (Case) I raised it with him privately before the client call, with those two order timelines, and suggested promising three weeks with an option to beat it. He heard me out, but the client had said two weeks was a hard requirement, so he kept it. (Ask) Once he decided, I backed it fully: I booked production slots that day, set up a twice-weekly check-in with the production lead, and told my manager at the first sign of slip. We delivered in fifteen days, one day late, and the client renewed. I took two things from it: my concern was fair, and once the call is made, my job is to make it work, not to be right. (Commit)"
You were wrong (software developer)
"My team lead wanted to drop our manual release sign-off and rely on automated checks. (Stakes) I disagreed — I'd seen the manual step catch two bad configuration changes in the previous year. (Case) I wrote up both incidents and asked her to keep the manual step for one more quarter. She pointed out that both incidents would now be caught by a configuration test we'd added since, and asked me to check. (Ask) I checked, and she was right: the new test covered both cases. We dropped the manual step, release time went from about a day to a couple of hours, and nothing slipped through that quarter. What I changed is that before I push back now, I check whether my evidence is still current. (Commit)"
A conflict with a coworker (marketing specialist)
"A designer on my team and I disagreed about a campaign landing page — he wanted a full-screen video at the top, and I was responsible for the page's sign-up rate. (Stakes) Our previous video-heavy page had loaded slowly on phones, and phones were where the campaign's traffic came from. (Case) Instead of taking it to our manager, I asked him to look at the load-time report with me, and asked what the video needed to accomplish. It was brand feel, not information. We agreed to test a still image with a short video lower on the page against his version for a week. (Ask) The still-image version had the better sign-up rate, he kept the video in the lower section, and we've used the same one-week test to settle design debates since. (Commit)"
Notice what the four share: the Case is one specific piece of evidence, the Ask happens before or outside the decision meeting, and the Commit says what happened after the decision — not only who was right.
What mistakes sink a disagreement answer?
The mistakes that sink disagreement answers are claiming you never disagree, making your manager the villain, telling a story about winning, disagreeing about something trivial, raising it in the wrong setting, and ending on a vague lesson. Each can survive rehearsal because the answer still sounds smooth.
| Mistake | What it sounds like | Why it fails | The fix |
|---|---|---|---|
| "I never disagree" | "I'm pretty easygoing — I don't really disagree with my managers" | Gives the interviewer nothing to evaluate and can sound like conflict avoidance | Find a real disagreement about a decision, even a modest one |
| The manager as villain | "My boss was stubborn and didn't listen to anyone" | Shifts the story to someone else's character; the interviewer wonders how you'll describe them later | Describe your manager's goal fairly, then your concern |
| The victory lap | "I proved her wrong, and everyone saw it" | Makes the story about being right, not about how you disagreed | Put the weight on the Ask and the Commit |
| The trivial disagreement | A debate over a slide template or a meeting time | No stakes, so the disagreement shows nothing | Pick a decision with real consequences |
| The public objection | "I raised it in the all-hands" | Signals you go around the relationship instead of through it | Raise it one-on-one or in writing first |
| The vague "we" ending | "We talked about it and kind of met in the middle" | Hides what you did and what was decided | Say what you proposed, what was decided, and what you did next |
| The stock lesson | "I learned communication is key" | A platitude, not a change — nothing to verify | Name a specific habit, like bringing a past example and a smaller first step |
The Muse makes the same point about blame: "You're not trying to convince the interviewer that you were right in the situation. You're trying to show them how well you handled the conflict" (The Muse).
On "I never disagree," that same Muse article suggests that if you have truly never had a conflict with a boss, you give a hypothetical and walk through how you would handle it. That is a reasonable last resort, but a behavioral question asks for a past example, so look wider first: a disagreement with a team lead, a client, a senior colleague, or a professor on a project can carry the same structure. Use a hypothetical only after saying plainly that it is one.
How is the coworker-conflict version different?
The coworker version removes the authority gap: neither of you can simply make the call, so the interviewer is testing whether you can resolve a disagreement between equals without escalating too early or letting it fester. The structure stays the same; three things change.
| Disagreement with your manager | Conflict with a coworker | |
|---|---|---|
| Who decides | Your manager — your job is to make the case, then commit | Neither of you alone — your job is to find a way to decide together |
| What the Ask shows | Raising it with the right timing and an alternative | Understanding what the other person needs, and proposing a fair way to settle it (a test, shared criteria, a split of work) |
| When the manager comes in | They are the counterpart | Only after you've tried to resolve it directly, and ideally together: "let's take both options to our lead" |
| The biggest risk | Sounding insubordinate or like you go around your manager | Making the coworker the villain or sounding like you can't work with peers |
"Tell me about a conflict at work" lets you choose. Pick the version where your own actions were clearest and the outcome is easiest to state. "Tell me about a time you pushed back" works with either, and also with a client or senior stakeholder; whichever you pick, the Case beat — your evidence — has to show why the pushback was warranted, not just that you had an opinion.
If the question names your manager, do not swap in a coworker story. It dodges the part being tested.
What a scored answer actually looks like
We wrote the answer below as an example (it is not from a user) and typed it into the Interview Drills scorer — the same prompts, model, and scoring rubric the app uses for its "The Disagreement Story" behavioral drill — on October 8, 2026, three times. Typed answers carry no voice signal, so Delivery here judges how the text reads; spoken answers add pace, filler words, and pauses.
Answer (first take, typed):
"I don't really disagree with my managers much, I'm pretty easygoing. I guess there was one time my manager wanted to do a project a certain way and I thought it should be done differently, so we talked about it and kind of met in the middle. It worked out fine in the end. I think communication is key in those situations."
Overall score: 22 / 100 on all three runs. First run:
- Clarity 18 · Confidence 15 · Structure 12
- Conciseness 35 · Delivery 30 · Audience awareness 20
What the scorer flagged (first run, condensed):
- The opener "I don't really disagree with my managers much, I'm pretty easygoing" signals conflict avoidance or a dodge before the story starts — delete it and open with the situation
- The Action and Result are empty: replace "we talked about it and kind of met in the middle" with what you said, what evidence you brought, what was decided, and a concrete result
- "We" language hides what you contributed — say "I requested a meeting," "I prepared a comparison"
- "Communication is key" is a platitude closing; replace it with a specific thing you learned
Our rewrite (written by us, specific and owned, then scored the same way: 88 on all three runs):
"Last spring my manager wanted to launch our new onboarding emails to every customer at once. I disagreed, because our last all-at-once launch had a broken link that reached eight thousand people before anyone noticed. I asked for fifteen minutes, showed her that incident, and proposed sending to ten percent first for two days. She was worried about the delay, so I offered to own the monitoring myself and send her a one-line status each morning. She agreed. The test batch caught a formatting bug in Outlook that we fixed before the full send. I learned to bring a past example and a smaller first step instead of just an objection."
The rewrite follows Stakes–Case–Ask–Commit: the Stakes is the all-at-once launch, the Case is the earlier broken-link incident, the Ask is three moves in "I" language (asking for time, showing the incident, proposing a ten percent test) plus taking on the monitoring to answer her concern about the delay, and the Commit is what the test caught and the habit that came out of it. The first take shows three of the mistakes above — "I never disagree," the vague "we" ending, and the stock lesson — and has no specific story at all.
Two honest limits. First, even at 88, the scorer's first run listed four improvements, and two of them concern the setup and the ending: the result is a story beat rather than a measured outcome (how many customers did the full send reach, and what would the bug have cost?), and the Task — what the speaker was responsible for — is implied rather than stated. One sentence in the Stakes beat fixes the second: say what you owned. Add a number only if you have the real one; an invented figure is exactly what a follow-up question exposes. Second, the rewrite is 111 words, which is under a minute when spoken at a conversational 125 to 150 words per minute. That fits the 75-second target of the app drill it was scored on, but it is shorter than the 90-second-to-two-minute range above for a live interview, where the extra time belongs in the Ask beat — what your manager said and how you answered it.
What follow-up questions come after a disagreement answer?
Expect three follow-ups: "What would you have done if your manager had said no?", "How did the relationship hold up afterward?", and "Was it worth pushing on?" Each one tests whether you would commit to a decision you disagreed with.
- "What if your manager had said no?" Answer with the commit: what you would have done to make the original plan work and reduce the risk you flagged. "I'd have run it their way and set up the monitoring anyway" is the answer they are listening for.
- "How was the relationship afterward?" Be specific and brief: a later project you worked on together, or a process the two of you kept. Avoid "it was a bit awkward" without saying what you did about it.
- "Was it worth pushing on?" Explain why the stakes justified it — the customer, cost, or safety impact — and name a disagreement you chose not to raise because it did not clear that bar. That shows judgment about when to push.
The behavioral interview preparation guide covers building a full set of stories so a request for a second example does not leave you blank. If your disagreement story ended badly because of your own call, it may fit tell me about a time you failed better.
How do you practice a disagreement answer before the interview?
Practice it out loud, not on paper: write a four-line skeleton (Stakes, Case, Ask, Commit), say the answer two or three times in different words, and check each version for an apology at the start and a "we" ending. Listen for hedges like "I don't really disagree much" and "kind of met in the middle"; a recording can surface them when a written draft does not.
Record one take and listen for three things: whether your Case names one specific piece of evidence, whether your Ask says where and how you raised it, and whether your last sentences say what was decided and what you did next. Fix one problem per take.
Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up. It diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and, on the Interview Accelerator and Interview Pro plans, feeds the candidate's resume into scoring and feedback.
Tip
Full disclosure: Interview Drills is our product, and the scored example above came from its scorer. Each scored drill — answered aloud or typed — returns a 0–100 overall score and a score on six dimensions: Clarity, Conciseness, Confidence, Structure, Audience Awareness, and Delivery, plus an Interview-Ready Rewrite of your answer. A free account gets 3 scored drills per day; every paid plan includes a 14-day track, and story-based preparation has its own, The 14-Day Story Mastery Program. It is a training tool, not a live-interview copilot, and it does not cover coding or system design. The out-loud practice method above works without it.
If you are not sure which part of your interviewing needs work, the free 3-minute quiz (25 questions, no account needed) identifies your interview persona and blind spot.
Frequently asked questions
- Is it okay to say I've never disagreed with my manager?
- No. 'I don't really disagree with my managers' leaves the interviewer nothing to evaluate and can read as conflict avoidance, which is the opposite of what the question is looking for. Look wider before you give up: a disagreement about a deadline, a process, a priority, or a rollout plan counts, and so does one with a team lead, a client, or a senior colleague. If you truly have none, say so briefly and offer the closest real example you have; as a last resort, describe how you would handle it, and say plainly that it is hypothetical.
- What if my manager overruled me and I lost the disagreement?
- That can be a strong story. The question tests how you raised the disagreement and how you behaved after the decision, not whether you won. Explain your concern and evidence, how you raised it, what your manager decided, and how you then committed to the decision and made it work, including anything you did to reduce the risk you had flagged.
- Can I talk about a disagreement where I turned out to be wrong?
- Yes. A story where you raised a concern respectfully, your manager went ahead, and the result showed your manager was right demonstrates that you disagree in good faith and update your view. Say plainly what you got wrong and what you now check before pushing back. Avoid it only if being wrong involved the core skill of the job you want.
- How long should my answer to 'tell me about a time you disagreed with your manager' be?
- About 90 seconds to two minutes spoken, the same range this site's STAR method guide uses for behavioral answers (Interview Drills' own practice drill for this question targets a tighter 75 seconds). Spend a sentence or two on what was being decided and your role, one or two on your concern and evidence, the largest share on how you raised it and what you proposed, and the last 15 to 20 seconds on the decision, how you committed to it, and the result.
- Can I answer with a disagreement with a coworker instead of my manager?
- Only if the interviewer asked about a coworker or about 'a conflict at work' in general. If the question names your manager, a coworker story dodges the part being tested: disagreeing with someone who has authority over the decision. For a general conflict question, either works; pick the one where your actions were clearest.
- Should I mention going over my manager's head?
- Only if you told your manager first that you were going to escalate, and the stakes justified it, such as a safety, legal, or customer-harm risk. Escalating without telling your manager reads as a trust problem in an interview. If you do tell that story, make the conversation with your manager the center of it, not the escalation.
- What are interviewers looking for when they ask about disagreeing with a manager?
- Four things: that you speak up when something matters instead of staying quiet, that you base the disagreement on evidence rather than preference, that you raise it respectfully and in the right setting, and that you commit to the final decision even if it went against you. A specific story with your own actions and a clear outcome shows all four.