Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Resolved a Conflict Question
Transcript
- Lucas: 'Tell me about a time you resolved a conflict.' It shows up in almost every behavioral interview, yet I think it's one of the most mishandled questions out there. Luna: Totally. Either people pick a story that's too small — 'I disagreed with a coworker about which font to use' — or they go the other way and it sounds like a HR nightmare. Lucas: Exactly. And if we've helped you think through a career move or how to handle a tricky interview moment, honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It keeps this show ad-free and totally listener-supported. Luna: Yeah, it really does. And we never want to put that behind a paywall. So if you find yourself using one of these frameworks in an actual interview, that's the best thank-you. Lucas: Alright, so let's dig in. The mistake most people make is treating this as a 'who was right and who was wrong' story. Hiring managers don't care about the winner. They care about whether you can keep a team functional when tension spikes. Luna: Right. And whether you addressed the underlying issue or just smoothed it over. That's the real signal. Lucas: Let me give you a concrete example. A few years ago I was advising a medical-device company that was about to launch a new monitoring system. Two engineering leads — one hardware, one software — had a genuine disagreement about the release timeline. The hardware lead wanted to delay because a sensor calibration wasn't stable. The software lead argued that if they delayed, they'd miss the regulatory window and the whole project would lose nine months. Luna: That's a high-stakes conflict. Not a font debate. Lucas: Right. Now, if you interviewed one of those engineers and asked them to tell you about a time they resolved a conflict, the wrong answer would be: 'I convinced the other person I was right.' Because that's not resolution — that's domination. The better answer would be: 'I recognized we had a legitimate trade-off, so I proposed a structured experiment.' Luna: So you want to hear that they stepped back from the personal debate and looked at the problem objectively. Lucas: Exactly. So here's the framework I recommend. I call it the three-step: situation, intervention, and structural fix. Situation is just the context — keep it to two sentences. Intervention is what you actually did in the moment. Structural fix is what you changed so the same conflict doesn't recur. Luna: The structural fix is the part most people skip. They just say 'we talked it out' and leave it there. Lucas: And that's why their story feels flat. Let me show you how this plays out with the medical-device example. The situation: hardware lead wants a two-month delay, software lead says that kills the regulatory window. Intervention: you convene a one-hour meeting where each lead presents their data — calibration test results versus regulatory filing deadlines — and you facilitate a decision to run a two-week accelerated test on the sensor. If it passes, you launch on time. If it doesn't, you delay. Luna: So you're not choosing sides. You're creating a path that respects both concerns. Lucas: Precisely. And the structural fix — this is key — after the test passed and the product launched, you implement a monthly cross-team check-in where hardware and software share their risk registers. Now the next conflict gets flagged early, not two weeks before launch. Luna: That's the part that tells the interviewer you're not just a firefighter — you're a systems thinker. Lucas: Exactly. And you can apply this framework to almost any conflict story. Say you're in marketing and you had a budget dispute with the sales director. Situation: you wanted to spend on brand awareness, they wanted to spend on direct sales incentives. Intervention: you proposed a three-month A-B test across two regions. Structural fix: you created a quarterly joint budget review where both teams see the same ROI data. Luna: I love that because it shows you can depersonalize the conflict and focus on evidence. One thing I'd add: in your intervention step, it helps to explicitly name the shared goal. Like, 'We both want to hit the quarterly revenue number, we just disagree on the path.' Lucas: That's a great point. It signals emotional intelligence — you're acknowledging the other person's intent. And that's a subtle signal hiring managers latch onto. Luna: What about a story where you were actually the cause of the conflict? Do you ever want to tell that version? Lucas: Absolutely, if you handled it well. That can be even more powerful because it shows self-awareness. But you have to be careful. The story needs to show you recognized your mistake early and took corrective action. For example, 'I realized I'd been dismissive of a colleague's input in a meeting. I apologized privately, then made sure to publicly credit their idea in the next meeting.' The structural fix might be that you now start every project with a roundtable where everyone shares their perspective before you give yours. Luna: That's a good one. And it avoids the trap of sounding like you're bragging about being right. Lucas: Right. Now, one more thing I want to caution against: don't pick a story where the conflict was about something trivial. Even if you have a great structural fix, if the situation sounds like a petty squabble, the interviewer will wonder why you couldn't just let it go. Luna: What's the threshold? Like, if it's about a font or a color scheme — too small? Lucas: I'd say if the stakes aren't clear to someone outside your team, it's too small. The conflict should have a tangible consequence: delayed timeline, lost revenue, customer impact, team morale. Otherwise, it sounds like you're wasting energy on things that don't matter. Luna: And if you don't have a high-stakes conflict story? Not everyone works in product launches or sales disputes. Lucas: You can still find something. Think about a time you disagreed on a process or a priority. Even a disagreement about which software tool to use can work if you frame the stakes — maybe one tool would have cost the team ten hours a week in manual work. The key is to demonstrate that you approached it systematically and left the team better off. Luna: So to wrap this up — the three steps: situation, intervention, structural fix. And the meta-lesson is that the interviewer is looking for evidence that you can turn tension into a better process, not just win an argument. Lucas: Exactly. Next time you're prepping for an interview, write down three potential conflict stories, run them through this framework, and pick the one that has the clearest structural fix. That's the one that will stick in the interviewer's mind. Luna: And if you try it, let us know how it goes. We'd love to hear — but for now, that's our time. Lucas? Lucas: Yeah, I think that's a solid place to leave it. Thanks for listening, and we'll see you next time.