Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Worked With a Difficult Colleague
Transcript
- Lucas: You know that question that makes every candidate pause? 'Tell me about a time you worked with a difficult colleague.' Luna: Oh, it's a classic. And it's loaded, because you can't just say 'my coworker was a jerk' — even if it's true. Lucas: Exactly. Hiring managers ask it to assess two things: your emotional intelligence and your conflict-resolution skills. But most people treat it like a therapy session or a gossip session, and both are fatal. Luna: So what's the right way to answer? Give me a framework I can actually use. Lucas: I like the SBI model — Situation, Behavior, Impact. It's borrowed from organizational psychology, and it keeps your answer neutral and evidence-based. Let me walk through a real case from a product manager I coached. Luna: I'm listening. Lucas: This PM was at a mid-sized SaaS company. She had to collaborate with a data scientist who consistently deprioritized her requests. Every time she asked for a quick analysis, he'd say 'not in the sprint' and go silent. Luna: So the classic 'my coworker doesn't care about my deadlines' story. Lucas: Right. But instead of saying 'he was unhelpful,' she framed it as a structural mismatch. The Situation: they had competing priorities — she needed speed, he needed rigor. The Behavior: he always deferred without explaining why. The Impact: product decisions got delayed, and she felt shut out. Luna: And then what? How did she resolve it? Lucas: She scheduled a 15-minute check-in before each sprint planning. She asked him: 'What data would you need to prioritize my request?' That flipped the dynamic — now they were solving a problem together, not negotiating a favor. Luna: So she turned a personality conflict into a process issue. That's smart. Lucas: That's exactly the trick. The interviewer doesn't care about who was 'right.' They care about whether you can depersonalize conflict and find a workable path forward. Luna: What about the emotional piece? Don't you have to acknowledge that it was hard? Lucas: You do, but in one sentence. Say 'it was frustrating at first' — then immediately move to what you did. If you linger on the feeling, you sound like you're still resentful. Luna: So the wrong answer would be something like 'he never responded to my emails and I had to escalate to his manager.' Lucas: Exactly. That makes you look like someone who goes straight to authority instead of trying to work it out. The better approach: 'I realized we had a communication breakdown, so I proposed a weekly sync to align priorities.' Luna: What if the situation genuinely didn't get resolved? Like, the colleague was just impossible? Lucas: Then you choose a different story. Seriously. Never pick a story that ends badly — unless you learned something huge from the failure. And even then, you have to show you'd handle it differently now. Luna: So every story needs a positive outcome or a lesson. What about the STAR method — Situation, Task, Action, Result — does that work here? Lucas: It does, but SBI is tighter for this specific question because it forces you to separate the person from the behavior. STAR can make you narrate a whole timeline; SBI keeps the focus on what happened and what you did about it. Luna: I want to practice one. Imagine a candidate says: 'I had a coworker who always missed deadlines, so I started following up with him every day.' Is that a good answer? Lucas: It's okay, but too vague. The interviewer wants specifics. What deadlines? What was the impact? Did you talk to him about it, or just micromanage? A better version: 'Situation: we were working on a joint presentation for the C-suite. Behavior: my colleague consistently submitted his slides late, which put our rehearsal at risk. Impact: I realized we lacked a shared timeline. So I proposed a shared tracker with milestones and a two-day buffer before final review. The result: he delivered on time for the next two presentations.' Luna: That's concrete. I can picture it. And you never said he was lazy or irresponsible. Lucas: Exactly. You describe the behavior, not the character. That's the whole game. Luna: What about the phrase 'difficult colleague'? Some people interpret that as 'my boss.' Should you talk about a manager? Lucas: You can, but it's riskier. If you criticize your boss in an interview, the hiring manager might wonder if you'd do the same to them. Stick to a peer or a cross-functional partner if you can. Luna: Good point. So what's the one takeaway you want listeners to remember? Lucas: The goal isn't to prove you won. It's to prove you can collaborate under friction. Use SBI — Situation, Behavior, Impact — to tell a story that's about solving problems, not complaining about people. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, it really helps us keep making episodes like this. And now, back to one more nuance: what if the colleague was more senior than you? That's a common twist. Luna: I'd love to hear that. Because if they're senior, you can't just 'schedule a sync' — it's more delicate. Lucas: Right. In that case, you lean on influence rather than authority. Say you're a junior analyst and a senior engineer keeps ignoring your data requests. You might say: 'I asked if I could shadow their sprint planning to understand their capacity. That built empathy on both sides.' The key is humility — you're trying to understand their world, not change it overnight. Luna: That's a good example. So the answer is adaptable based on power dynamics. Lucas: Exactly. And that adaptability itself signals emotional intelligence. If you can read the room in your story, the interviewer trusts you'll read the room at their company. Luna: So next time someone asks 'tell me about a time you worked with a difficult colleague,' you're ready. Lucas: You've got a framework, a real example, and a clear pitfall to avoid. Use SBI, depersonalize, and always end with what you learned or improved.