Tell Me About a Time You Disagreed With Your Manager

To answer "tell me about a time you disagreed with your manager," describe their decision and what was at stake, explain how you pushed back with a question, evidence or an alternative, and say what shipped and what you do differently now. Aim for ninety seconds to two minutes. Interviewers want to see you disagree and still deliver.

HIDEA AI is an ethics-forward desktop interview copilot for live sessions and for mock practice. This loop uses the Verbal surface. You still speak or type every answer.

What the answer has to do

The minute has room for four beats: their call, what you did, what shipped, and a stop. A fifth beat is another disagreement, and it invites more questions about it. Use the beats the way a STAR answer does: a short setup, most of the minute on what you did, then the outcome and the habit you still use. Leave the labels unsaid.

• Their call. One or two sentences. The decision they wanted, said fairly, and the work at stake. A date, a customer, or a risk. Not a tour of their management style.
• What you did. The longest part. The question you asked, the evidence you brought, or the option you proposed. One thread of action, in "I." Pushing back counts. Waiting for them to notice does not.
• What shipped. The decision that stood, and the habit you still use. You committed once the call was made, even when it stayed theirs. "I was right" is not an outcome.
• A stop. About ninety seconds to two minutes, then wait. The next question is the interview.

One example

This is a shape. It is not your story, and it is not a script. Swap in a disagreement you actually had with a manager.

"My manager wanted the launch on Thursday, because the sales date was already public. I wanted a week, because the rollback was untested. I asked for twenty minutes and restated their date before I made a case. I proposed a smaller launch: the path customers already used, the new path behind a flag, and one person named for the rollback. They kept Thursday and took the flag. It shipped. After that I wrote the rollback owner down before I asked for time, so the next pushback started with the date they were protecting."

Their call is two sentences. The rest is the pushback and the habit that followed. If your version is still describing their style at the halfway mark, you have not started.

Answers that sound fine and still fail

Four versions of this answer sound reasonable on paper and fall apart out loud.

• "I don't really disagree with my manager." That is a dodge. They asked for a time you pushed back, and for what shipped.
• The whole minute on how wrong they were. The decision never arrives. If you are still angry, pick another story.
• A win where you overruled them and they thanked you. No date, no risk, and no moment where you committed to a call that was not yours.
• "We figured it out." The sentence never lands on what you asked, what you proposed, or what shipped.

A longer sample answer does not close those gaps. Saying their call, what you did, and what shipped, once, against a timer you do not pause, does.

A conflict with a coworker interview answer is a disagreement with a peer. This question has a manager in the room: they can close the decision, and you still have to ship. A time you failed interview answer is a miss you owned. Tell me about yourself interview practice is the opener, before any story.

What does "disagree and commit" mean in an interview?

It is a common phrase for stating your case, then supporting the decision once it is made, even if it was not the one you wanted. In an interview story it shows up as two moments: the pushback, and the point where you committed to their call and shipped. A story that has only the first moment sounds stubborn. A story that has only the second sounds like you never spoke up.

A ten-minute practice loop

One disagreement. About ten minutes, including the notes. A second story in the same sitting only teaches the second story. The live round will not offer you a warm-up.

1. Set the timer. Two minutes of setup. Write the role in the corner if you need it. Write their call in the margin, in a few words, not a paragraph. Set a timer for ninety seconds to two minutes. Close the sample answers.
2. State their call. One or two sentences. The decision they wanted, said fairly, and why the work cared. If you are still listing their faults, you have not started.
3. Name what you did. The pushback, in "I." What you asked, what you brought, and what you proposed. If the sentence is still about them, you have not reached the action.
4. Name what shipped. The decision that stood, and the habit you still use. If you cannot say what shipped, you do not have the answer yet. Stop the loop and pick a disagreement you can actually describe.
5. Stop. Even if the timer has seconds left. A second disagreement spends the minute.
6. Write three lines. The first sentence you actually said. The place you blamed them. One line you will say differently next time. Then close it.

Stop when the timer ends, even if the outcome is one clause short. Going long teaches you that the minute is optional.

Follow-ups they ask

The story is the opening. These questions sit next to it. Have one sentence ready for each, from the same story.

• What would you do differently? The habit you already use, or the one thing you would raise earlier. Do not invent a new flaw while they are waiting.
• What if they had said no? The next step you actually had: a smaller trial, a written risk, or shipping their call. Say that you tried the conversation first.
• How did the work look after? The release you still owned, or the check you still share. A claim that you are totally fine is thin if you cannot name the work.
• What changed in the work? The process, not a moral. A written risk, a smaller first ship, or one thing you raise before the date is public. If nothing in the work changed, the story is not finished.

Say it on the Verbal surface

A phone timer and an empty room will run the loop. When you want the same Verbal surface you will open on the day, say the answer there. A Verbal mock uses that surface: the app asks, and you say this answer out loud.

• Verbal, Live coding, System design, and Project are separate surfaces. This practice uses Verbal.
• A mock and a live session are the same desktop app, on macOS and Windows. A mock is the app asking the questions. A live session is the interview in front of you.
• STAR is a shape for a story. Leave the labels unsaid. Say it in your own words.
• The answer is still yours. The surface does not sit the round for you.

The longer spoken loop, one story and one follow-up, is verbal interview practice. Using a structure without announcing the labels is the STAR method.

Fifteen session minutes a day are free on all four surfaces, with no credit card. That is enough to say this answer more than once. A scored verbal mock, where the app asks the questions, listens, and scores a 20- or 30-minute round, is on Pro and Pro+. What the plans include is on the FAQ page.

Where answers fail

• A story with no stakes. The disagreement was a mood, and the date, the customer, or the risk never entered the minute.
• Their call missing. You argued your side and never said what they were protecting.
• No pushback. You described the tension and never said what you asked, brought, or proposed.
• Nothing shipped. The meeting ended, and the work that still went out never arrives. So does the habit.

Say one disagreement before the call

Run one disagreement with a manager before the round: about two minutes, their call, what you did, and what shipped, said out loud. The Verbal surface is the one you open for a mock and for a live session. Download HIDEA AI.

Where to go next

• Say the answer on the Verbal surface of the interview copilot.
• Get set up for a mock in the setup guide.
• See plans on pricing.
• If the other person was a peer, read the conflict with a coworker answer.