To answer “tell me about a time you disagreed with your manager”, pick a real, work-focused disagreement — an estimate, a technical direction, a priority call — where you raised your concern privately and early, backed it with evidence rather than opinion, and then committed fully to whatever was decided. Spend most of your two minutes on how you raised it and what you did after the decision, not on proving you were right. The interviewer is checking two things at once: that you will speak up to someone who has power over your work, and that you will not undermine them when the call goes the other way.
If your story is with a teammate instead, see our guide to answering “tell me about a conflict with a coworker”. This page covers the version where the other person outranks you.
Why the manager version is a different question
With a peer, you are equals working out a problem. With a manager there is an authority gap: they can overrule you, they write your review, and they are often carrying context or pressure from above that you cannot see. That changes what the interviewer listens for:
- Courage. Did you actually say something, or go along and complain later?
- Judgment about how and where. A concern raised in a 1:1 with a written breakdown lands differently from one raised in front of the whole team.
- Curiosity about their reasons. Managers often know things you don’t — a customer commitment, a budget limit, a reorg. Strong answers show you asked.
- Commitment after the call. If you lost the argument, did you make the decision succeed, or did you slow-walk it?
- Loyalty in the retelling. How you describe a former manager previews how you will describe this one.
Amazon writes this tension into its Leadership Principles. Have Backbone; Disagree and Commit says leaders should “respectfully challenge decisions when they disagree,” and adds: “Once a decision is determined, they commit wholly” (Amazon Leadership Principles, checked October 2026). Jeff Bezos’s 2016 letter to shareholders recommends saying “disagree and commit” out loud to keep decisions moving when a team can’t reach consensus. Other companies look for the same behavior without the label. For Amazon loops, map your story with our Amazon Leadership Principles examples.
Which disagreements make good stories
The safest material is a disagreement about the work, where reasonable people could land on either side. Some topics are fine but need care, and a few should stay out of the interview entirely.
| Disagreement | Engineering example | Use it? | The ending that works best |
|---|---|---|---|
| Estimate or timeline | Your manager promised six weeks; your task breakdown says ten | Yes — common and easy to follow | A scope trade-off you proposed, or a date you helped reset |
| Technical direction | Full rewrite vs. incremental refactor; adopting a new framework | Yes | A time-boxed prototype or experiment that settled it |
| Priorities | A feature freeze while reliability problems pile up | Yes | Data that changed the plan, or a smaller slot you won |
| Process | A new review rule, on-call rotation or ticket workflow | Yes, if the stakes were real | A trial period with a check-in date |
| Launch risk | Releasing to everyone at once vs. a staged rollout | Yes — strong for senior roles | You lost, committed and built the safeguards |
| Your rating, pay or promotion | Disputing a performance review | Avoid | Reads as self-interest rather than judgment |
| Ethics, safety or legal issues | Being asked to ship something you believed broke a law or policy | Rarely, and only if you used proper channels | Not a “disagree and commit” case — say so plainly |
Also skip stories where you went over your manager’s head without telling them, the disagreement never resolved, or you still sound annoyed. New grads can use an internship manager, research supervisor or student team lead — the shape matters more than the title.
A five-beat structure for disagreeing up
This is STAR with the middle split in two, because what happened after the decision matters as much as what came before. Our behavioral STAR examples cover the base format.
- The decision (one or two sentences). What your manager decided or proposed, and why it mattered to the team or the customer.
- Their reasoning, then yours. State their view the way they would: “She needed a date she could give the partner; I didn’t think that date was realistic with the dependency we had.”
- How you raised it. Where (a 1:1, a short doc, a design review), when (ideally before the commitment went public) and with what (an estimate breakdown, a benchmark, incident history, a proposed alternative). Framing the concern in terms of your manager’s goals is the biggest upgrade most answers can make.
- What was decided and how you committed. You persuaded them, they persuaded you, or you met in the middle. If you lost, name the specific things you did to make their plan work.
- Result and what changed. What happened, how the working relationship looked afterward, and what you now do differently when you disagree with a manager.
Aim for about two minutes out loud, with beats 3 and 4 taking more than half of it.
Example answers to “tell me about a time you disagreed with your manager”
These are example answers we wrote to show the shape at three levels; they are not real candidates’ stories. Replace every detail with your own project, and only use numbers you can defend if asked.
New grad or intern: persuaded by context you didn’t have
Decision and positions: “In my internship, my manager asked me to build a dashboard for build times from scratch. I found an existing internal tool that already collected most of the data and thought extending it would save me half the internship. She preferred the new build.”
How I raised it: “I asked for 15 minutes in our 1:1 and brought a short comparison: what the existing tool had, what was missing and a rough estimate for each path. I asked what I was missing rather than telling her she was wrong.”
Decision and commitment: “It turned out the tool’s owners planned to retire it the next quarter, which she knew from a planning meeting I wasn’t in. That changed my mind. I built the new dashboard, reused the old tool’s data-collection approach, and wrote a short note on why we didn’t extend it.”
Result and reflection: “I shipped it before my final presentation. What I took away: when a manager’s decision looks odd, my first question is what they know that I don’t.”
Mid-level: changing the plan with data and a small ask
Decision and positions: “My manager announced a quarter-long freeze on refactoring so the team could focus on a feature push. I agreed with the goal but thought our flaky integration tests would slow the push itself — most pull requests needed several CI reruns before they went green.”
How I raised it: “Instead of arguing in the planning meeting, I pulled two weeks of CI history and estimated the engineer-hours the reruns cost. I sent it before our 1:1 with one specific ask: one engineer for one sprint to fix the five worst tests, with a check-in at the end.”
Decision and commitment: “He agreed to the time box but nothing beyond it, and asked me to own it. I fixed the worst tests, stopped there as agreed and went back to the feature work.”
Result and reflection: “Review turnaround improved noticeably, and he started asking for data like that before planning. I learned that ‘give me a small, time-boxed bet’ is much easier for a manager to say yes to than ‘you’re wrong about the freeze.’”
Senior: losing the argument and committing anyway
Decision and positions: “My director wanted to launch a redesigned checkout to all customers on the day of a marketing campaign. I wanted a staged rollout over a week because the change touched payment code. Her constraint was real: the campaign date was fixed and partners were already promoting it.”
How I raised it: “I wrote a one-page risk note with two options — a full launch with safeguards, or a staged launch starting three days earlier — and we went through it together. She chose the full launch.”
Decision and commitment: “Once she decided, I treated the full launch as my plan. I added a feature-flag kill switch for each payment method, built a launch dashboard and set alert thresholds with the on-call engineer.”
Result and reflection: “One payment method showed elevated errors in one region; we switched it off with the flag within minutes and fixed it the next morning. In the retro, she proposed staged rollouts for future payment changes. The lesson for me wasn’t ‘I was right’: my first note read as ‘don’t launch,’ when she needed a plan that still hit the date.”
Weak vs. strong: the same story told two ways
Most weak answers lose points in the telling, not the situation:
| Beat | Weak version | Strong version |
|---|---|---|
| Describing the manager | “He didn’t really understand the technical side.” | “He was balancing a partner commitment I didn’t know about yet.” |
| Where you raised it | “I pushed back hard in the team meeting.” | “I raised it in our 1:1 first, so he wasn’t put on the spot.” |
| Evidence | “I just had a bad feeling about the timeline.” | “I broke the work into tasks and the estimate came out at ten weeks, not six.” |
| The ask | “I told her the plan wouldn’t work.” | “I asked for one sprint to test my approach, with a check-in at the end.” |
| Losing | “So I did it her way, and it went wrong like I said.” | “Once she decided, I built the safeguards that made her plan work.” |
| Escalation | “I went to my skip-level to get it overturned.” | “We agreed to bring both options to the director together.” |
| Ending | “Eventually they admitted I was right.” | “Here’s what we both do differently now.” |
Follow-up questions to expect
The follow-ups show whether the story is real and how you behave around authority. Prepare a short answer to each:
- “What did your manager say when you first raised it?” Have their actual reaction ready, including any pushback.
- “What would you have done if they still said no?” In the version where you won, explain that you would have committed, and what that would have looked like.
- “Did you consider going to your skip-level?” A good answer: only for something important, only after telling your manager, and ideally together.
- “How did this affect your relationship with your manager?” Give a concrete sign: they started looping you into planning, or asked for your estimate first next time.
- “Tell me about a time you disagreed with your manager and you were wrong.” Your second story covers this.
- “What if your manager asked you to do something you thought was unethical?” Make clear that disagree-and-commit covers judgment calls, not ethics or safety. There you would raise it clearly and use the company’s reporting channels if needed.
How to practice this answer
- Pick two stories with different endings. Go through 1:1s, estimates you questioned and launches you worried about; choose one where you changed the plan and one where you committed to a plan you disagreed with.
- Draft each in the five beats. The free STAR story builder shows a word count and spoken-time estimate.
- Say it out loud to an interviewer. A free AI mock interview in CoPilot Interview builds behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with what to fix and a model answer.
- Drill the follow-ups with a friend, especially “what if they still said no?”
A strong disagreement story often doubles as a leadership story; our behavioral interview help page collects the other common prompts, and the Amazon behavioral interview guide shows how deep Bar Raiser follow-ups go.
Rehearse your disagreement story out loud
In the desktop app’s Mock Interview mode, paste your résumé and the job description, choose a behavioral-heavy mix and answer each question out loud. Every answer gets a score out of 10, what to fix and a model answer — free for 15 minutes a day, no credit card.
Try a free AI mock interviewFAQ
Is it risky to talk about disagreeing with your manager in an interview?
Not if you tell it well. Interviewers want people who raise concerns; the risk is only in the telling. Show you raised it respectfully, understood your manager’s reasons and committed to the final decision.
What if my manager was clearly wrong?
You can say the outcome showed your concern was valid, but keep the focus on what you did and what changed afterward. Describe your manager’s reasoning fairly and avoid any “I told you so” tone.
Should I pick a story where I won the argument or lost it?
Have both ready. A story where you lost and committed fully is often the stronger one, because it shows you can support a decision you disagreed with.
How long should my answer be?
About two minutes. Keep the setup brief and spend most of the time on how you raised the concern and what you did after the decision.
Is going to my manager’s manager ever a good answer?
Sometimes, for high-stakes issues, but tell your manager first and ideally go together with both views written up. Going around your manager without telling them is one of the clearest red flags in this question.
What if I have never disagreed with a manager?
Look smaller: an estimate you questioned, or a disagreement with an internship manager, professor or student team lead. Saying you have never disagreed reads as avoidance.