Prompt and when it applies
An interviewer may ask, “Tell me about a time you disagreed with your manager. What did you do, and what happened?” The signal is whether you can use evidence to voice dissent under unequal authority, accept a decision, and keep delivering. It is not an invitation to judge your manager.
This is a behavioral-description question, so use a real event. A project, launch plan, technical choice, customer commitment, or performance feedback can work. Remove private details, confidential numbers, and unsupported motives. If the person was a project lead rather than your direct manager, state the reporting relationship clearly.
What the interviewer is assessing
A strong answer forms a complete evidence chain: the goal, your basis for judgment, how you made the disagreement discussable, how you acted after the decision, the result, and what changed afterward. The U.S. Office of Personnel Management explains that structured interviews should target job-related competencies and use consistent questions and proficiency benchmarks for comparison.
A weak answer says, “I communicated respectfully and we solved it.” It hides the quality of your judgment and says nothing about ownership when the manager kept the original plan. Ending with “I won” can make collaboration sound like a contest.
Questions to clarify before answering
- Which goal was at stake? Quality, risk, user experience, cost, or schedule changes the evidence and trade-off.
- What did you know then? Separate information available at the time from the later outcome; do not narrate hindsight as foresight.
- Did you own the decision? If not, show recommendation, escalation, and execution rather than claiming unilateral control.
- Was your proposal accepted? Either result works. Explain validation when accepted, or risk controls and delivery when rejected.
- What must stay confidential? Replace customer, system, and sensitive numeric details while keeping direction and relative impact.
A 30-second answer framework
You can start: “I’ll share an example about a goal trade-off. The team had to balance schedule and risk, and I raised a different recommendation based on a specific piece of evidence. I first confirmed what my manager was optimizing, then used a small validation and a fallback to make the risk concrete. My manager chose a direction, and I owned implementation with checkpoints. The result was …, and I turned the lesson into ….”
This gives you Situation, Task, Action, Result, and reflection without reciting labels. Keep the focus on your judgment and actions; do not hide individual work behind “we.”
Step-by-step deep answer
1. Pick a verifiable, proportionate story
Choose an event where you can explain the goal, constraints, and result. A rollout strategy, test scope, or schedule allocation is easier to verify than “we had different philosophies.” Avoid disciplinary matters, undisclosed finance, or outcomes you cannot explain.
2. Tie dissent to a goal and evidence
Restate the goal your manager was protecting, then explain your risk judgment. For example: “The goal was a Friday launch. I worried that a full cutover would amplify payment failures, so the previous two weeks of error distribution led me to propose a 5% canary.” This acknowledges the goal while making the disagreement testable. Evidence can be logs, user feedback, experiment results, or a capacity estimate; use numbers you can defend.
3. Offer a reversible validation path
Do not stop at “that will not work.” Offer a bounded next step: a small-traffic test, shadow run, extra monitoring, one-rule change, or explicit stop condition. State when a signal will arrive, what result would change the decision, and who will observe it. If validation is expensive, explain why a direct decision is still rational.
4. Let the manager decide and state your commitment
Confirm that you share the same understanding after raising the concern. If the manager accepts your proposal, explain how you drove it. If the original plan remains, explain the guardrails, risk record, and delivery actions you added. Accepting a decision is not abandoning judgment; the failure is passive execution or a private alternative after alignment.
5. Close with results and reflection
Cover both business and collaboration outcomes: on-time launch, defect or rework change, and a new team check. If the result was poor, name the wrong assumption and the evidence you would gather earlier next time. Indeed’s example guidance likewise emphasizes voicing a difference, accepting a supervisor’s choice, continuing to perform, and reflecting on the lesson.
6. Draw a boundary for safety, compliance, or integrity
If the disagreement involves a security flaw, legal duty, discrimination, or data exposure, “accept the decision” is not the whole answer. Say that you would preserve evidence, use the organization’s escalation path, and protect users or the company within your authority. Do not invent a whistleblowing outcome; describe only actions you actually took.
7. Keep one reusable decision rule
Remember: align on the goal, then show evidence; propose a reversible test, then accept the decision; finally prove ownership with results and reflection. The rule applies to disagreements with a manager, product owner, or cross-functional decision maker.
High-quality sample answer
The following is a fictional example. Its numbers demonstrate structure and must be replaced with your own experience:
“During a settlement-service redesign, my manager wanted to apply a new validation rule to every merchant on Friday to meet a quarterly target. I owned the migration script and found that one class of older merchant records lacked the new field; a full cutover could reject valid orders. I did not simply reject the plan. I confirmed that Friday was a fixed launch constraint, reviewed 30 days of error samples, and proposed a 5% merchant canary with a rejection-rate threshold and a manual rollback trigger. I added a pre-migration check and live alerting, with a review every two hours. My manager accepted the canary. It exposed two rules that needed legacy-field compatibility; we fixed them and expanded on schedule without a batch of false declines. In the review, I added field-coverage checks to the release checklist. I learned to protect the goal, make dissent reversible, and stay accountable after the decision.”
The answer does not claim, “I convinced my manager.” It demonstrates goal alignment, evidence, guardrails, execution, and a lasting process improvement.
Common mistakes
- Mistake → Describe the manager as incompetent or stubborn → Why it fails → The story becomes a character judgment → Fix → Use the constraints and evidence available at the time.
- Mistake → Talk only about standing your ground → Why it fails → It omits ownership after the decision → Fix → State how you executed, monitored, and escalated.
- Mistake → Invent a perfect percentage → Why it fails → The result cannot survive follow-ups → Fix → Use explainable relative change, or label a number as fictional and replace it with real data.
- Mistake → Use “we” for the whole story → Why it fails → The interviewer cannot see your judgment → Fix → Mark your observation, recommendation, action, and owned result.
- Mistake → Treat a safety or compliance issue as an ordinary opinion gap → Why it fails → It hides a duty to escalate → Fix → Explain evidence preservation, escalation, and protection steps.
Follow-ups and how to respond
What if your manager insists on the original decision?
Confirm the decision and success criteria, then propose the smallest guardrails: monitoring, rollback, owner, and review time. If the risk crosses a safety, compliance, or integrity boundary, say you would escalate under policy instead of silently proceeding. Show commitment to execution alongside independent judgment.
What if your recommendation later proved wrong?
Own the assumptions and evidence limits, identify the signal that disproved the view, explain how you helped limit harm, and name the check you would add next time. Do not rewrite the mistake as something you “knew all along.”
How do you know when to escalate?
Use impact and irreversibility: user safety, legal duties, data exposure, or material financial risk should be documented and routed through a formal channel even without decision authority. A reversible, small-scope trade-off can first be tested within the project. Disagreement alone is not an escalation criterion.
Did the disagreement change your relationship with your manager?
Describe a concrete behavior change: sharing a risk list earlier, confirming decision context in one-on-ones, or adding release checkpoints. Do not stop at “we became closer”; explain which working practice changed.