How to Answer: Tell Me About a Time You Disagreed With Your Manager

STAR method answers “Tell Me About a Time You Disagreed With Your Manager” by presenting evidence, respectful communication, the decision, follow-through and a lesson rather than personal criticism. Northeastern University recommends the five-component S-T-A-R-B method—Situation, Task, Action, Result and Bridge—in a 1–2 minute answer for Behavioural interviews.

How should you answer “Tell Me About a Time You Disagreed With Your Manager”?

Answer “Tell Me About a Time You Disagreed With Your Manager” with one real work-related disagreement: state the evidence, quote the key conversation, explain the decision, show what you did afterwards, and finish with the lesson in a 1–2 minute S-T-A-R-B answer, as recommended by Northeastern University’s behavioural interview guidance.

Use this opening:

“I chose a disagreement about a delivery timeline because it shows how I raise risk without losing ownership.”

Build the answer in five beats:

1. Situation and Task: Give the context and your responsibility in two or three sentences.
2. Action: Say what you actually said. For example: “I understood why the deadline mattered, but the current estimate excluded testing time. Could we compare the assumptions?”
3. Result: Explain the decision and its effect. The result might be a changed plan, a controlled risk, a useful lesson or committed delivery.
4. Bridge: Connect the experience to the vacancy: “That experience is relevant here because this role requires evidence-led challenge and committed execution.”

STAR means Situation, Task, Action and Result. S-T-A-R-B adds Bridge. Do not make the story a complaint about your former manager. Show judgement, listening and professional follow-through. CareerTestPrep presents judgement, communication, humility, professionalism and outcome as five dimensions to consider.

A constructive ending does not require your manager to change their mind. If the decision stayed the same, say how you confirmed the next steps, raised any remaining risk once and delivered the agreed plan. SeekArc’s answer guide discusses how to describe your conduct after a disagreement is resolved.

Practise the answer aloud. Keep prompts, not a script: situation, evidence, conversation, decision, lesson.

What is the interviewer really checking in your disagreement story?

Northeastern University assesses a disagreement story through relevant experience, conflict, pressure and ambiguity; this editorial model turns those areas into four tests, ordered by practical importance.

First, battle selection. Did you challenge a decision worth challenging, or defend a personal preference? This ranking is our interpretation of SeekArc’s guidance, which frames the question around courage calibration and conduct after losing. Choose a meaningful delivery risk, customer issue or resource decision. Avoid a theatrical confrontation.

Second, context. Did you understand what your manager knew that you did not? A strong answer allows your view to change after you hear about customer commitments, wider priorities or constraints outside your control. That shows judgement without weakening your ownership.

Third, evidence. Did you make a clear recommendation without turning the discussion into a verdict on your manager? Use a line such as:

“I understood why the deadline mattered, but I had evidence that the original estimate created a delivery risk, so I asked to compare the assumptions.”

Fourth, commitment. What did you do after the decision? 101Hired’s interview guide discusses two risks: not raising concerns and refusing to accept a decision.

This article emphasizes commitment after a decision: a constructive outcome may involve updating your view, executing responsibly and reporting the result honestly rather than trying to prove the manager wrong.

Being overruled can produce a stronger story. SeekArc treats behaviour after losing as a core test, while 101Hired presents commitment after an override as valuable evidence.

Interviewer: “What did you do when your manager disagreed?”

Candidate: “I clarified the decision, confirmed my responsibilities, and delivered the agreed plan without undermining it.”

That is emotional intelligence, not passive compliance. The Muse suggests presenting both sides fairly and explaining how the working relationship changed. Acknowledge the reasoning. Own your recommendation. Then own the decision.

What simple structure should you use before the interviewer interrupts?

The S-T-A-R-B method keeps a disagreement answer decision-focused: Situation, Task, Action, Result and Bridge, with Situation and Task limited to two or three sentences (Northeastern University; CareerTestPrep).

Use five beats:

1. Situation and Task: “The issue was…” State the decision and your responsibility.
2. Action: “My concern was based on…” Then: “I asked…” Include the exact conversation, not a summary.
3. Manager’s context: “My manager explained…” Show what changed or confirmed your view.
4. Result: “We decided…” Then state the business, relationship or risk outcome. The Muse also discusses resolution and changes in the working relationship.
5. Bridge: Link the lesson to the vacancy. “That experience is relevant here because…”

A behavioural interview asks what happened. A situational interview asks what you would do in a hypothetical case. Do not answer a past-event question with a policy speech.

The table below helps you choose evidence that matches your experience and keeps high-risk issues out of an ordinary disagreement story.

Choose a disagreement story that fits your evidence and risk

Candidate or situation	Use this type of disagreement	Evidence to name (guidance)	Safe ending to rehearse (guidance)
Early-career candidate	Process, priority or timeline	Observations, a small comparison or supervisor feedback	What you learned and how you followed through
Experienced individual contributor	Technical architecture, customer, delivery or resource decision	Data comparison, proof of concept or time-boxed experiment	Decision and execution outcome
Career changer	Volunteering, education, placement or previous industry	Concrete constraint, stakeholder need or result	Bridge the lesson to the target role
Manager or senior candidate	Priority, risk, people or cross-functional decision	Trade-offs, stakeholder impact and clear recommendation	Alignment and ownership
Ethics, legal, safety or compliance issue	Do not frame it as an ordinary disagreement	Escalation channel and documented risk	Reporting takes priority over disagree-and-commit

Source: Northeastern University, CareerTestPrep and The Muse.

For technical decisions, use a proof of concept when the claim is testable. Use a time-boxed experiment when the risk is reversible. Feature flags and kill switches add control when a live change could cause harm. A result need not be a metric. It can be a launch, changed process, prevented risk, improved trust or clear lesson. Never invent figures to make the story sound stronger.

What should three different candidates actually say?

Northeastern University’s S-T-A-R-B method turns a disagreement story into evidence of judgement, action, result and role fit through its behavioural interview guidance.

The scripts below are original illustrative examples. They are not reported cases from the linked sources. Adapt the facts to your own experience. Do not borrow numbers, outcomes or technical details that are not yours.

Early-career candidate

In a university project, my supervisor wanted to add scope before we had tested the core work. I understood that the extra features could improve the final result, but I was concerned about delivery risk. I showed where the first tests had failed and suggested checking the highest-risk parts before adding more. My supervisor agreed to reduce the initial scope. I completed the testing, recorded the remaining issues and supported the team’s presentation. That experience taught me to raise a concern around the decision, not around a person.

Bridge: “That experience is relevant here because this role needs careful prioritisation, clear evidence and reliable follow-through.”

Use a university, placement, volunteering or school example if it genuinely shows the same behaviour. Northeastern University recommends preparing stories across leadership, teamwork, conflict, problem-solving, resilience and time management. Describe the setting accurately. A supervisor is not automatically a line manager.

Experienced individual contributor

My manager preferred one technical approach for a new service, while I thought another option better matched the expected workload. I understood that the preferred approach could reduce short-term delivery effort, but I was concerned about maintenance later. I compared the access patterns and proposed a small, reversible proof of concept. The results supported keeping the existing design for that service, so we documented the decision. I then owned the architecture review and implementation work. The lesson was to make technical disagreement testable, reversible and useful to the team.

Bridge: “That experience is relevant here because this role needs someone who can challenge technical direction, update their view and own the agreed decision.”

Technical architecture is one valid disagreement type. It is not a requirement. Iteration Interview’s example uses a concrete technical event, while CoPilot Interview’s examples discuss timelines, CI history and staged rollouts. Those sources support the decision mechanisms, not this script. Candidates without engineering experience can use evidence about workload, customers, priorities or process risk.

Career changer

In a volunteer programme, the coordinator wanted one reporting process for everyone. I understood that consistency would make oversight easier, but I was concerned that the process would create unnecessary work for lower-risk cases. I compared the different needs and suggested trying the fuller process only where closer monitoring was needed. The coordinator chose a limited trial. I helped organise the tracking and followed the agreed process. The experience taught me to protect visibility while questioning work that does not serve the decision.

Bridge: “That experience is relevant here because this role needs someone who can improve a process while keeping stakeholder needs in view.”

101Hired’s examples discuss reporting workload and account priorities as examples of non-technical disagreement. Your result does not need to prove that you were right. It needs to show what you understood, what the manager decided and how you worked afterwards.

Which answers should you avoid, and how can you repair them?

CareerTestPrep recommends a direct attempt before escalation, except for ethics, legal, safety or serious-harm concerns requiring immediate escalation.

Say the weak line aloud. Then replace it.

• Passive: “I never disagree with my manager.”
  Repair: “I usually ask questions early so concerns do not become surprises.”

• Blaming: “My manager had no idea what they were doing.”
  Repair: “We had different views of the delivery risk, so I compared the assumptions.”

• Passive compliance: “I was overruled, so I did it.”
  Repair: “I confirmed the decision, raised the remaining risk once, and then executed the agreed plan.”

• Overconfidence: “My solution was obviously right.”
  Repair: “The available evidence supported my recommendation, but I listened for context I did not have.”

Personal criticism weakens credibility. The Muse suggests explaining how the working relationship changed without attacking the manager. If the relationship remained strained, stay factual:

“The decision remained unchanged, but I kept the work professional, documented the risk, and learned to raise concerns earlier.”

Have Backbone; Disagree and Commit, part of the Amazon Leadership Principles and linked there to Jeff Bezos’s 2016 shareholder letter, does not mean silent obedience.

Disagree-and-commit never overrides ethics, legal duties, safety reporting or compliance processes. Use the proper escalation channels. Do not polish a serious reporting failure into an interview story about loyalty. For a real workplace or legal matter, use the organisation’s formal process and qualified advice.

How should you adapt the story to the role you want?

PostgreSQL and NoSQL answers should name the constraint, compare access patterns and use a reversible test, because technical disagreement becomes credible when maintenance trade-offs are testable (Iteration Interview). Say: “I compared the PostgreSQL and NoSQL access patterns, ran a proof of concept and recorded the maintenance trade-off.”

Product, sales and procurement answers should connect the disagreement to customer impact, procurement substantiation and compliance. Name the commercial risk without inventing a financial result. Customer-support, legacy-process and dashboard examples offer useful shapes (CareerTestPrep). For a launch concern, explain how feature flags, kill switches or a staged rollout limited exposure (CoPilot Interview).

People-manager answers should show emotional intelligence and conflict resolution. Explain how you invited stakeholder input, protected the other person’s dignity and made it safe to raise a concern. A client-account story works when it shows both the relationship and the decision (The Muse).

Executive and senior answers should name decision rights, escalation channels and the cost of delay. Then show how you aligned teams after the decision. If the issue involved ethics, legal risk, safety or compliance, describe the correct reporting route rather than ordinary disagree-and-commit.

Non-technical candidates can replace architecture evidence with workload records, customer feedback, policy requirements, a documented comparison or a time-boxed experiment. Prepare a parallel version for a peer, department decision or company policy. Keep the same action and follow-through, but change the authority relationship.

How do you practise saying it aloud in two minutes?

Northeastern University recommends practising each behavioural interview story aloud until it sounds conversational, and keeping the answer to 1–2 minutes; its guidance also names Big Interview for recording and review (Northeastern University).

Record one attempt. Listen once. Check whether you explained the disagreement, the evidence, the decision and what you did next. Repeat without reading full sentences. Keep five prompts visible:

• Situation
• Concern
• Action
• Result
• Bridge

Recommended timing split

This is an editorial recommendation, not a source finding:

• 20 seconds: Situation and Task.
• 60 seconds: Your concern, evidence and exact conversation.
• 25 seconds: Result and decision.
• 15 seconds: Bridge and learning.

Stop at the end. Cut background before cutting the decision or your follow-through.

Prepare recovery lines before the interview:

• “Let me clarify the decision point.”
• “The evidence I had then was…”
• “I do not remember the exact wording, but my message was…”

Recorded-answer review is one form of interview practice described by Northeastern University in connection with Big Interview. AI interview practice and answer graders provide another format.

What did your manager say when you raised it?
Give the substance if you cannot recall the exact wording. Try: “My manager explained that the deadline protected a customer commitment. I acknowledged that constraint, then asked whether we could reduce scope or test the highest-risk part first.”

What happened when your manager said no?
State the decision plainly. Then show execution: “The decision stayed unchanged. I confirmed my responsibilities, recorded the remaining risk and delivered the agreed plan.”

What would you do differently?
Name one change. “I would raise the concern earlier, with the comparison already prepared. That would leave more time to test the alternatives.”

Was escalation appropriate?
For ordinary disagreements, explain the direct conversation first. Ethics, legal, safety or serious-harm concerns require the relevant reporting route rather than silent disagreement and commitment (CareerTestPrep).

How did the relationship change?
Use evidence from the working relationship. “We disagreed on the decision, but we kept the review factual and agreed how to raise delivery risks earlier.” Do not claim improved trust unless your example supports it.

Razen Rehearsal Sandbox: When the panel asks what happened after your manager said no

You are interviewing for a senior delivery role at Northstar Payments. The panel wants a real disagreement, and you have one: in March, your manager chose a six-week launch date for a fraud-monitoring release, while your testing showed the date left two high-risk payment flows uncovered. You have one chance to show that you raised the risk without making the story about winning.

Setting. A 45-minute video interview for Senior Delivery Manager. Emma, the hiring manager, leads the interview. Daniel, the operations director, joins as the second interviewer.

Cast

• Maya, Candidate answering the interview question. At stake: She must show judgement without sounding combative or passive.
• Emma, Hiring manager testing conflict judgement. At stake: She needs evidence that Maya raises risks, accepts decisions and protects delivery.
• Daniel, Operations director testing follow-through. At stake: He wants to know whether Maya supports a decision after losing the argument.

The Wrong Way

Emma: Tell me about a time you disagreed with your manager.

(Emma leans towards the camera and leaves the question open.)

Maya: Last March, my manager wanted to launch our fraud-monitoring release in six weeks. I showed that two payment flows had failed testing, so I recommended an eight-week timeline with a staged rollout.

(Maya speaks quickly, listing evidence as if presenting a case.)

Emma: What did your manager say?

(Emma raises one hand slightly, stopping Maya before the result.)

Maya: He said the six-week date was already promised to the client, but I still felt the risk was too high. I explained that we couldn't responsibly launch with those failures.

(Maya tightens her jaw and stresses “responsibly.”)

Daniel: So did he change the date?

(Daniel glances at his notes, waiting for the decision.)

Maya: No. He went ahead anyway. I followed the plan, but the launch had an issue in one of those flows, which proved my concern was right.

(Maya gives a short shrug and looks down.)

Emma: How did you handle that with the team?

(Emma's tone becomes more probing.)

Maya: I told them we should have waited. I still delivered my part, but I made sure everyone understood that I had raised the risk beforehand.

(Maya points once towards herself, then folds her arms.)

Why it fails. Maya raises a valid risk, but the lines “I still felt the risk was too high” and “which proved my concern was right” turn the answer into a case against her manager. She reports the failure as vindication and never shows how she updated her view, clarified the decision or helped the team recover. Daniel's question exposes the missing behaviour after she lost the argument.

The Right Way

Emma: Tell me about a time you disagreed with your manager.

(Emma asks the question, then stays silent so Maya can choose the story.)

Maya: In March, my manager set a six-week launch for a fraud-monitoring release. My testing showed two high-risk payment flows were still failing, so I asked to compare the deadline with the risk of a staged launch.

(Maya slows on “asked to compare” and keeps both hands still.)

Emma: What did you say to him directly?

(Emma tilts her head, inviting the exact conversation.)

Maya: I said, “I understand the client commitment. My concern is that these two failures affect payment approval, so I recommend two more weeks or a smaller first release.” He explained that the date had already been promised and that a delay would put the account at risk.

(Maya looks into the camera for the quoted words, then relaxes her shoulders while naming his reason.)

Daniel: What happened when he kept the six-week date?

(Daniel looks up from his notes and holds the question for a beat.)

Maya: I confirmed the decision, raised the remaining risk once in the launch record, and owned the test plan for the smaller first release. One flow still needed follow-up after launch, so I helped the team close it without blaming the decision.

(Maya pauses before “confirmed,” then speaks in short, level phrases.)

Emma: What did you learn from that disagreement?

(Emma softens her voice but keeps the question direct.)

Maya: The evidence supported my recommendation, but my manager had customer context I didn't have. I learned to separate the quality of my challenge from whether I win it, then execute the agreed decision. That matters here because this role also needs evidence-led challenge and committed delivery.

(Maya opens one hand on “but,” then finishes with steady eye contact.)

Why it lands. The right version keeps the risk specific but gives the manager a credible reason for the decision. Maya pays a price: the launch still carries risk, and one flow needs follow-up. The answer lands because she records the concern, accepts the decision, owns the smaller release and states what changed in her judgement rather than claiming victory.

<aside class="razen-coach-card" data-razen-scenario="when-the-panel-asks-what-happened-after-your-manager-said-no"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=when-the-panel-asks-what-happened-after-your-manager-said-no&amp;article=how-to-answer-tell-me-about-a-time-you-disagreed-with-your-manager&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=how-to-answer-tell-me-about-a-time-you-disagreed-with-your-manager">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start factual and compact when naming the six-week deadline; shift to a firmer tone on “two high-risk payment flows were still failing.”
• Soften slightly when stating the manager’s customer constraint, then return to a firm, practical tone for “I confirmed the decision.”
• Finish with warmer authority on the Bridge sentence, showing respect without sounding grateful for approval.

Pause placement

• Pause for 2 seconds after Emma asks the opening question, before naming the March release.
• Pause for 1 second after “I recommend two more weeks or a smaller first release,” so the recommendation sounds deliberate.
• Pause for 2 seconds after Daniel asks what happened when the date stayed fixed; do not rush past the overruled moment.
• Pause for 1 second before “but my manager had customer context I didn't have,” marking the update in your view.

Physiological cues

• Keep both feet on the floor while saying the quoted recommendation; press your fingertips lightly together instead of clasping your hands.
• Look at the camera for the risk and recommendation, then briefly lower your gaze when recalling the manager’s customer constraint.
• Drop your shoulders before answering what happened after the decision; suppress the shrug that signals resentment.
• Breathe out before the final Bridge sentence and keep your jaw loose so “committed delivery” does not sound defensive.

Recovery moves

• If you start arguing that you were right, say: “Let me separate the risk I raised from the decision we made.”
• If you lose the exact wording, say: “I don’t remember the exact sentence, but my message was that the two failed flows made the launch risk specific.”
• If Emma interrupts before the result, say: “The decision stayed at six weeks. The part I owned after that was the smaller release and the recorded follow-up risk.”
• If you sound resentful, say: “I’m describing the constraint my manager had, not excusing the risk. I raised it, documented it, and then delivered the agreed plan.”

Watch it explained

Frequently asked questions

What is the best structure for answering this interview question?

Use S-T-A-R-B: describe the Situation and Task briefly, explain the Action with the exact words you used, give the Result, then Bridge the lesson to the role. Keep the story focused on one disagreement and practise it aloud so it sounds conversational rather than memorised.

Should I choose a story where my manager changed their mind?

No. A manager changing the decision can show evidence-based influence, but being overruled can show judgement and commitment. Choose the story with the clearest decision, responsible behaviour and useful result. Explain what you learned, including any context your manager knew that you did not.

What if I have never disagreed with a manager?

Use a real example of questioning a plan, suggesting an alternative or raising a risk with a supervisor, tutor, volunteer lead or project owner. Say why the situation is comparable, then focus on how you raised the concern, responded to the decision and followed through.

How long should my answer be?

Aim for about 1–2 minutes. Northeastern University recommends that range, while other interview guides suggest about one minute or two minutes. Use the time to cover the evidence, conversation, decision and follow-through. A concise answer with a clear result beats a longer account of workplace history.

What should I say if the disagreement involved safety, legal risk or compliance?

Do not frame serious risk as an ordinary personality disagreement. Explain that you raised the issue through the correct ethics, legal, safety or compliance channel, followed the required process and protected people or the organisation. Seek qualified professional advice for a real legal, safety or employment matter.