Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Time You Disagreed With a Decision Interview Question
Transcript
- Lucas: You're in an interview and the hiring manager leans forward and says: 'Tell me about a time you disagreed with a decision made by your manager or a senior leader.' Luna: That question makes a lot of people squirm. It feels like you're being asked to prove you're a team player — but also that you have a spine. Lucas: Exactly. And the worst thing you can do is pick a disagreement about something trivial — like what font to use in a slide deck. That signals you can't prioritize. Luna: So you need a genuine conflict, but not one where you were insubordinate or just plain wrong. It's a narrow band. Lucas: Right. I think the best answers land on a disagreement about process or strategy — something where you had a valid alternative view, you voiced it professionally, and the outcome was either a compromise or a better result. Let's build a framework. Luna: I'm ready. Where do we start? Lucas: Step one: set the stakes. You need to explain the context in one or two sentences so the interviewer understands the importance. Don't spend thirty seconds on background. For example: 'At my last company, we were launching a new feature and the product lead wanted to ship it in two weeks with minimal testing. I was concerned that would break our core checkout flow.' Luna: That's good — immediately I know the tension: speed versus quality. And it's not personal. Lucas: Step two: explain your reasoning. This is where you show your analytical side. Why did you think your approach was better? Use data if you have it. 'I pulled the error logs from the last three rapid releases and found that each one caused a two-percent drop in conversion for the first week.' Luna: So you're not just saying 'I had a bad feeling.' You have evidence. That makes the disagreement about facts, not ego. Lucas: Exactly. Step three: describe how you voiced the disagreement. This is the make or break moment. You don't say 'I told my manager he was wrong.' You say something like: 'I scheduled a fifteen-minute chat and walked through the data. I framed it as a risk I wanted to flag, not a challenge to his authority.' Luna: That's smart. And it's honest — most managers appreciate when someone brings a concern early rather than after the fact. Lucas: Step four: the resolution. What happened? Ideally you reached a compromise — maybe you did a phased rollout, testing on ten percent of users first. Or your manager overruled you, but you explain why that was fine. 'He decided to go ahead, but I respected the decision and made sure the launch went smoothly.' That shows maturity. Luna: And if your idea was adopted? That's even better — but don't overplay it. You want to sound like a team player who happens to be right, not a hero. Lucas: Right. Now, there's one trap I see candidates fall into all the time: they choose a disagreement where they were clearly wrong and try to spin it as a learning experience. That almost never works because the interviewer walks away thinking you have poor judgment. Luna: Yeah, you want the interviewer to think 'I'd want that person on my team, even when we disagree.' Not 'I'd have to watch my back.' Lucas: Let's do a full example. I'll play candidate, you be the interviewer. Luna: Okay. Tell me about a time you disagreed with a decision. Lucas: Sure. In my previous role as a product analyst, my team was deciding which metrics to track for a new subscription feature. The lead engineer wanted to build a custom dashboard from scratch. I disagreed — I had data showing that our existing analytics tool could handle eighty percent of the requirements in half the time. I pulled a one-page comparison of cost and timeline, and proposed a hybrid: use the existing tool for now, build custom reports for the remaining twenty percent later. The lead agreed, and we shipped two weeks ahead of the original estimate. Luna: That works. You had a specific reason, you brought data, you proposed a compromise, and you named a concrete result. The whole thing takes about forty-five seconds. Lucas: And notice I didn't say the engineer was wrong — I said 'I disagreed.' Language matters. You want to depersonalize the conflict. Luna: One more thing — what if the disagreement was with a peer, not a manager? That's also a common variation. Lucas: Great point. The same framework applies, but the stakes might be lower. You can lean more into collaboration: 'My peer wanted to use method A, I preferred method B. We ran a small experiment to test both, and B won.' That shows you're results-oriented and willing to test assumptions. Luna: I think this is one of those questions where preparation really pays off. You can have two or three examples ready — one with a manager, one with a peer, maybe one with a client. Lucas: Absolutely. And if we've helped you think through a career move or decision like this, I want to mention something quickly. This show has always been ad-free — and that's only possible because of listeners who chip in a couple of bucks a month. A few dollars genuinely keep the lights on here. Luna: Yeah, it really does make a difference. If you've gotten value from episodes like this one, you can support the show at buy me a coffee dot com slash fexingo. Lucas: It's that simple. No tiers, no perks, just helping us keep the content free for everyone. Okay — back to the disagreement question. There's one more nuance I want to explore. Luna: What's that? Lucas: The follow-up. Sometimes after you give your example, the interviewer will ask: 'What would you do differently if you could go back?' This is a chance to show self-awareness. Maybe you'd escalate sooner, or you'd gather more data before speaking up. But don't undermine your original action. Luna: Right, you want to show growth without admitting you messed up. Something like: 'In retrospect, I would have involved a third stakeholder earlier to get buy-in.' That's a refinement, not a retraction. Lucas: Exactly. And one last thing: avoid negative language about the other person. Even if your manager was being unreasonable, don't say 'my boss was stubborn.' Frame it as 'we had different priorities' or 'we were operating under different constraints.' Luna: That's the golden rule of behavioral interviews: you are the common denominator in every story. If you blame others, the interviewer will wonder if you're the problem. Lucas: So to recap: pick a substantive disagreement, use a four-part structure — stakes, reasoning, voicing, resolution — and keep it under a minute. Practice it out loud until it sounds natural, not rehearsed. Luna: And if you're looking for more interview prep, we've covered everything from brainteasers to salary expectations in earlier episodes. This one fits right in. Lucas: Next time we'll talk about how to answer the question 'Why do you want to leave your current job?' — which is another landmine if you're not careful. Luna: I'm already thinking of examples. See you next time. Lucas: Take care.