Tell Me About a Conflict With Your Manager

This one carries a hidden risk that the coworker-conflict version does not. When the conflict is with your manager, the interviewer is quietly asking: are you going to be hard to manage? You have to show backbone and the ability to disagree, while making it clear you are not someone who undermines the people you report to.

What they're really testing

It sits across collaboration and ownership on the four-signal model, plus a manageability screen. Can you push back up the chain with judgment, and then get behind the decision your manager makes? They are watching for two failure modes: a pushover who never disagrees, and a rebel who cannot let a call go.

The mental model for this question

The principle: disagree privately, commit publicly, and frame it around their goals, not yours.

PRIVATELY    raise it one-on-one, not in front of the team
       +
  THEIR GOALS  argue in terms of what your manager is trying
               to achieve, not what you'd prefer
       +
  COMMIT       once they decide, back it fully and visibly

The "their goals" reframe is the senior move. "I think we should do X because it is cleaner" is an opinion. "I am worried this timeline puts the launch you committed to at risk, here is why" speaks to what your manager actually owns. You are helping them succeed, not winning a point.

One more thing that quietly does a lot of work: show that you actually understood their position before you pushed on it. A line like "I could see why he wanted to hit that date" tells the interviewer you were arguing with the decision, not the person, and that you were not just waiting for your turn to talk. Steelman their side out loud, then raise your concern. It is the difference between a disagreement and a standoff.

How to structure your answer

STAR. Keep the Situation neutral, never paint your manager as a villain. Action: how you raised it (in private, with reasoning tied to their goals). Result: what was decided, and crucially that you committed to it. Learning: what you took away about managing up.

A strong sample answer

My manager wanted to ship a feature without an analytics integration to hit a board demo date. I thought we would regret launching blind, with no way to see if anyone used it. But I also knew the demo date was something he had personally committed to leadership.

I did not raise it in standup. I asked for ten minutes one-on-one and framed it around his goal: "I know the demo date matters, and I want it to go well. My worry is that if we launch with no analytics, the first question leadership asks, 'is it working,' is one we will not be able to answer." I proposed a middle path, a lightweight event or two we could add in half a day rather than the full integration.

He heard it, and we agreed to ship the two key events and defer the rest. It added almost no time and we had usage numbers within a week, which actually helped him in the follow-up review. The takeaway for me was that disagreeing with a manager goes much better when you anchor it to what they are on the hook for, not to your own preference. Even on the times the call went his way, framing it that way kept the relationship solid.

Pitfalls

• Trashing the manager or making them the bad guy. It makes you look like the problem.
• Raising the disagreement publicly, which reads as undermining them.
• A story where you never commit, or stayed resentful. That is the manageability red flag.
• Picking a values-level blowup. A reasoned professional disagreement lands far better.

Now write yours

Choose a disagreement you raised well and committed to. Frame the Action around your manager's goals.