Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why You Should Ask About a Candidate's Worst Boss
Transcript
- Lucas: There's one interview question I've started asking every candidate I talk to, and it tells me more in five minutes than most of the other questions combined. Luna: Okay, I have to hear this. What is it? Lucas: I ask them to describe the worst boss they've ever had. Not the worst job, not the worst company — the worst individual manager. And then I just listen. Luna: That's interesting. Doesn't that risk them just trash-talking a former employer? Lucas: It can, and that's actually part of what I'm listening for. But the way someone answers tells you three specific things: their capacity for honest reflection, how they handle conflict, and whether they take any personal accountability. Luna: So you're not just looking for a horror story. You're looking for how they process it. Lucas: Exactly. A few months ago I was interviewing a product manager candidate. She described a boss who would change requirements every afternoon, then blame the team when projects slipped. She said — and I'm paraphrasing — 'I learned that I needed to document decisions in writing and confirm priorities by email every morning, because his memory was selective.' Luna: That's a great answer. She didn't just complain. She described what she did to adapt. Lucas: Right. Contrast that with another candidate who told me his worst boss was 'incompetent' and 'never listened.' When I asked what he did about it, he said, 'Nothing, it wasn't my job to fix him.' That told me a lot. Luna: Yeah, that's a red flag. It's not that he couldn't work with a difficult person — it's that he saw it as completely outside his control. Lucas: And that's the core insight. The question works because it's low-stakes for the candidate — most people have had at least one frustrating boss — but the answer reveals patterns they might not even realize they're showing. Luna: I've heard a variant of this where you ask about a time they disagreed with a manager. But this is more pointed. Lucas: The disagreement question is good, but it often prompts a rehearsed answer. People prepare for that. Nobody prepares for 'tell me about your worst boss' — it's personal, it's emotional, and it catches them off guard in a way that feels human, not like a gotcha. Luna: What do you do if they say, 'I've never had a bad boss'? That would feel like a dodge. Lucas: It happens. I usually follow up with, 'What about a boss who challenged you in a way that was uncomfortable?' And if they still can't think of anyone, that's a data point too. Either they've been incredibly lucky, or they're avoiding vulnerability. Luna: I read a study last year that said candidates who blame their worst boss entirely — with no self-reflection at all — are significantly more likely to leave their next job within twelve months. Lucas: That tracks with what I've seen. A friend who runs talent acquisition at a mid-size tech company added this exact question to their interview process about two years ago. He told me it helped them reduce early attrition by roughly thirty percent among new hires. Luna: Thirty percent? That's huge. What were they seeing before? Lucas: They were hiring people who interviewed well — polished answers, right buzzwords — but then struggled with real-world feedback and conflict. The worst-boss question surfaced that pattern before they made an offer. Luna: So how do you evaluate the answer? What's the ideal response? Lucas: I look for three elements. First, specificity — they describe actual behaviors, not vague personality attacks. Second, accountability — they acknowledge their own part, even if it's small. Third, learning — they explain what the experience taught them about work or about themselves. Luna: It's almost like a resilience test in disguise. Lucas: It really is. And it's especially useful for roles where the candidate will have to navigate internal politics or influence without authority. If they've only ever worked for great managers, they might not have developed those muscles. Luna: That's a good point. There's a difference between someone who's been well-managed their whole career and someone who's learned to thrive despite poor management. Lucas: Exactly. And the question also works for internal candidates. If you're promoting someone from within, you probably already know their work, but you might not know how they experienced their previous managers. I've seen promotions go sideways because the new manager turned out to behave exactly like the boss they used to complain about. Luna: So it's also a mirror. You might learn something about your own management culture. Lucas: Absolutely. If multiple candidates describe the same type of bad boss — say, a hands-off boss who gave no feedback — that might reflect a broader issue in your industry or even your own company. Luna: I want to try this in my next interview. But I'm a little nervous it might come off as too personal. Lucas: It can, if you don't frame it right. I always say something like, 'I'm curious about your management experiences — tell me about the worst boss you've worked for.' That sets a conversational tone. And I make sure to nod and stay neutral while they talk. If they seem uncomfortable, I'll add, 'No names needed, just the dynamic.' Luna: No names — that's smart. It gives them permission to be honest without worrying about burning bridges. Lucas: Right. And I've noticed that when candidates trust you with that story, the rest of the interview often becomes more open. They drop the script a little. Luna: What about the risk that they just trash everyone? I've met people who call every former boss terrible. That's a pattern in itself. Lucas: That's actually a clear signal. If every boss was the problem, the common denominator is the candidate. I once interviewed someone who described three consecutive managers as 'micromanagers.' When I asked for an example, each story involved them missing a deadline or skipping a meeting. The micromanagement was a response, not a cause. Luna: So you're listening for self-awareness even in the negative examples. Lucas: Exactly. The best answers are honest about the boss's flaws but also include something like, 'I could have communicated better' or 'I should have asked for clarity sooner.' That's the sweet spot. Luna: You know, this reminds me of something. 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, that's exactly right. We don't run ads, we don't sell data. It's just us and the audience. And if you've gotten something out of this conversation, that link is a simple way to keep it going. Luna: Alright, back to the question. Lucas, have you ever been asked this yourself in an interview? Lucas: I have, actually. A few years ago, I was interviewing for a senior editor role, and the hiring manager asked me. I told her about a boss who took credit for my work. And I said I learned to document contributions in team emails. She nodded and said, 'Good. You know how to protect yourself without being combative.' I got the job. Luna: That's a great validation of the method. It worked on you. Lucas: It did. And I still remember that interview because it felt real. Most interviews feel like two people performing. That question cut through the performance. Luna: So if someone's listening and wants to try this next week, what's your one piece of advice? Lucas: Listen more than you talk after you ask it. Let the silence sit. The candidate will often fill the gap with something revealing. And don't judge the first thing they say — the real insight is in the follow-up.