Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How a Peer Interview Saved a Company from a Toxic Hire
Transcript
- Lucas: You know how in most hiring processes, the final round is with a senior manager or the department head? There's a reason a lot of companies are adding a peer interview step before that. Luna: Is that the one where the candidate meets potential teammates? I've heard it can be awkward. Lucas: It can be, but when it's structured right, it catches things the managers miss. I want to tell you about a case at a mid-sized SaaS company that almost hired a candidate who would have been a disaster — and a peer interview saved them. Luna: Now I'm curious. What happened? Lucas: Before I dive in, I want to mention something. If these conversations have moved your work forward in some small way, supporting the show is easy — a couple of dollars a month at buy me a coffee dot com slash fexingo keeps it ad-free and independent. Luna: Yeah, that small support really adds up. Thanks to everyone who already chips in. Lucas: Alright, back to the story. So this SaaS company was hiring for a senior product manager. The candidate had a resume full of brand-name companies, strong recommendations, and he nailed the interviews with the VP and the director. Luna: Sounds like a slam dunk. What went wrong? Lucas: The company had recently started a pilot where candidates spent thirty minutes with three potential teammates — not to evaluate technical skills, but to talk through a real problem and see how they collaborated. This candidate, let's call him Mark, started strong, but within ten minutes he was talking over people, dismissing ideas, and explaining basic concepts in a condescending tone. Luna: Ouch. And the managers didn't see any of that? Lucas: Not at all. In the manager interviews, Mark was polished, deferential, and asked smart questions. He knew how to perform for authority. But with peers, his mask slipped. The three teammates all independently noted the same behavior in their feedback forms. Luna: So what did the company do? Lucas: The hiring manager was initially reluctant because the candidate was so strong on paper. But the peer feedback was consistent and specific — phrases like 'dismissive,' 'talks down to people,' 'doesn't listen.' They decided to pass on Mark. Later, a reference from a former colleague hinted at 'leadership style friction' that had caused team turnover at his previous job. Luna: So the peer interview essentially saved them from a toxic hire. Do you have a sense of what that would have cost? Lucas: Honestly, it's hard to put an exact number, but studies show that a bad hire can cost anywhere from thirty to fifty percent of their annual salary in lost productivity, morale damage, and rehiring costs. For a senior PM making, say, one hundred and fifty thousand, that's at least forty-five thousand — and that's conservative. The culture hit is often bigger. Luna: So how do you structure a peer interview so it's not just a friendly chat? I imagine you need more than 'do you like this person?' Lucas: Exactly. The best peer interviews have a clear purpose. One approach is to give the candidate a real but anonymized problem the team has faced and ask them to walk through how they'd approach it. Peers are trained to observe not just the solution, but the process — do they ask clarifying questions? Do they invite input? Do they get defensive when challenged? Luna: That makes sense. It's about patterns, not a single answer. Lucas: Right. The feedback form should be simple — three to five questions on things like collaboration, receptiveness to feedback, and communication style. Avoid vague questions like 'Would you enjoy working with them?' Instead ask: 'Did the candidate seem open to your ideas?' or 'How did they react when you disagreed?' Luna: And you need to make sure the peers feel safe giving honest feedback, especially if it's negative. Otherwise they might just say everything was fine. Lucas: Biggest challenge right there. The company in our story used anonymous aggregated feedback — each peer submitted their form separately, and the hiring manager only saw a summary. That reduced social pressure. Also, they made it clear that negative feedback was valued, not punished. Luna: I've also heard that peer interviews can backfire if the team is already cliquey or if they see a new hire as a threat. How do you guard against that? Lucas: Great point. You need to train peers on what to look for and what not to look for. They're not judging technical competence — that's for the technical screen. They're judging interpersonal dynamics. And you should rotate who participates to avoid one person dominating the feedback. Some companies even use a standardized scoring rubric. Luna: So what's the bare minimum for a peer interview to be useful? Is thirty minutes enough? Lucas: Thirty to forty-five minutes is plenty. Any shorter and you only get surface-level chat. The key is to include a task — a mini case study or a debate — that forces interaction. You can't just have them talk about their hobbies. Luna: I can see why this is valuable, especially for roles where teamwork is critical. But what about roles that are more individual contributor, like a data analyst who works mostly alone? Lucas: Even then, they need to collaborate with stakeholders or present findings. A peer interview can reveal how they handle questions or pushback. It's less about 'are they fun to grab coffee with' and more about 'will they communicate effectively with the people they depend on.' Luna: Is there any research on peer interviews predicting performance? Or is it mostly anecdotal? Lucas: There's some data. A Google study on their own hiring process found that peer interviews had a moderate correlation with later performance ratings — not as strong as structured behavioral interviews, but better than resumes or unstructured chats. Combined with other signals, it improves prediction. Luna: So it's not a silver bullet, but it's another data point. And in Mark's case, it was the deciding factor. Lucas: Exactly. The company later hired a different candidate who performed very well in the peer interview — engaged, collaborative, humble. That person became a top performer. The peer interview didn't just avoid a bad hire; it helped confirm a good one. Luna: I like that framing. It's not just a veto tool, it's a validation tool. Lucas: Right. If you're already using structured interviews and skills tests, adding a peer component is a low-cost way to catch what managers might miss. It's especially helpful for checking culture add — or in this case, culture subtraction. Luna: Culture subtraction — I'm going to steal that. So if a listener wants to try this, what's the first step? Lucas: Start small. Pick one role — ideally one where teamwork is key — and design a thirty-minute peer session with a simple problem. Train three peers on what to observe. Create a feedback form with three specific questions. Run it for a few candidates and see what you learn. Luna: And if the peers consistently flag something the managers didn't see, you know it's working. Lucas: Exactly. The goal isn't to add bureaucracy, it's to add insight. And sometimes that insight is the difference between a great team and a toxic one.