Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How One Failed Hire Saved Our Company Culture
Transcript
- Lucas: You hire a star. Great resume, great interview, great references. Six months later your best people are updating their LinkedIn profiles and you're wondering what went wrong. Luna: That specific story. I've seen it three times now — the hire who had all the hard skills but somehow made everyone around them worse. Lucas: Right. And I think we usually frame it as 'they didn't fit the culture.' But that's a lazy diagnosis. The real question is: what specific behaviors broke the team? And can you predict those before you make the offer? Luna: So give me the concrete example you found — the fintech case. Lucas: Yeah. So there's a Series B fintech company in New York — I'll call them ClearPay, not their real name. They hired a VP of Engineering from a FAANG company. Great pedigree. He had all the technical depth they needed. Lucas: Within two months, three senior engineers had quit. Not because of workload — because of how he ran meetings. He'd interrupt people publicly, dismiss ideas from junior team members, and take credit for work his reports did. Classic pattern. Luna: And none of that showed up in the interviews? Lucas: Not a hint. His references said he was 'demanding but fair.' The interview panel loved his strategic thinking. But they never asked the right questions about how he treated people when things went wrong. Luna: So what's the fix? How do you catch that? Lucas: The CEO of that company later told me they now use what they call the 'three-question culture screen.' It's not a personality test or a values card sort. It's three behavioral questions that get at whether someone actually lives the values they claim to hold. Luna: Okay, lay them out for me. Lucas: First question: 'Tell me about a time you disagreed with your boss about a decision you thought was wrong. What did you do?' They're looking for direct but respectful pushback, not silence or gossip. Second: 'Tell me about a time you made a mistake that cost the team time or money. How did you handle it?' Lucas: Third: 'Tell me about a time you worked with someone who was struggling. What did you do?' The pattern matters more than any single answer. If someone can't give a concrete example for all three, that's a red flag. Luna: I like that because it's not hypothetical. It's asking for actual past behavior. And the third one — helping a struggling teammate — that's a huge signal for collaboration. Lucas: Exactly. And here's the thing: the FAANG VP answered all three well in the interview. He said he'd challenge his boss, owned his mistakes, and mentored juniors. But the references were from people who had only seen him in a position of power, not from his peers or reports. Luna: So you need to talk to the people who worked for him, not just his boss. Lucas: Bingo. The CEO now insists on at least one reference from a former direct report, and one from a peer. And they ask a specific question: 'Would you choose to work with this person again if you had the choice?' Not 'are they competent' — 'would you choose them.' Luna: That's a fascinating reframe. Because competence is easy to verify. But willingness to work with someone again — that's a direct measure of how they make others feel. Lucas: Right. And the research backs it up. There's a paper from 2022 in the Journal of Applied Psychology — they looked at over 400 hires and found that the single best predictor of whether a new hire would cause voluntary turnover among their peers was the answer to exactly that question: 'Would your past colleagues choose to work with you again?' Luna: So you could almost skip the skills questions and just ask that. Lucas: You could. But I think the skill questions still matter. The issue is weighting. Most hiring processes weight technical competence at 70 or 80 percent and culture alignment at 20 or 30. The data suggests it should be closer to 50-50, especially for roles where collaboration is critical. Luna: And the cost of getting it wrong is huge. The ClearPay CEO estimated that one bad hire cost them about 1.2 million dollars in lost productivity, recruiting costs, and the hit to team morale. Lucas: That number includes the time other leaders spent firefighting, the ramp-up time for replacement hires, and the lost output from the people who quit. If you factor in the delayed product launch, it's probably higher. Luna: So what's the takeaway for a hiring manager listening right now? What's one thing they can do differently tomorrow? Lucas: Add that 'choose to work with again' question to your reference calls. And if you're the one interviewing, ask the candidate directly: 'If I called three former teammates right now, would they all say they'd want to work with you again?' Watch their reaction. The honest ones might pause and think. The ones who say 'of course' without hesitation — that's actually a yellow flag too. Luna: Because nobody's perfect. A little self-awareness about friction points is healthy. Lucas: Exactly. And if they can articulate a specific area where they know they're difficult — 'I can be impatient with slow decision-making' — that's actually reassuring. It means they've done the work to understand their impact on others. Luna: I want to zoom out for a second. You mentioned culture debt earlier. Can you define that? Lucas: Sure. Culture debt is the accumulation of small compromises on values that eventually erode a team's trust and cohesion. Every time you hire someone who's brilliant but cuts corners on collaboration, you add to the debt. Every time you look the other way when a top performer is rude to a junior, you add interest. Lucas: It's like technical debt. You can ignore it for a while, but eventually the interest compounds and the system breaks. The ClearPay case is a perfect example — one hire created so much culture debt that the company had to restructure the entire engineering org to pay it off. Luna: So the remedy is to build a hiring process that explicitly checks for culture alignment, not just culture fit. Fit is about whether they'll blend in. Alignment is about whether they'll uphold the values that make the team work. Lucas: That's a really important distinction. Fit can lead to groupthink. Alignment means everyone is committed to the same principles of how they work together, even if their styles differ. The VP of Engineering had great fit — he was ambitious, driven, smart. But his values around respect and humility were not aligned. Luna: And I think that's the deeper lesson. You can teach skills. You can't teach someone to care about how their behavior affects others. Lucas: Speaking of things that require care — and I mean this genuinely — we get to make these episodes because a small group of listeners chooses to chip in through buy me a coffee dot com slash fexingo. It keeps the show ad-free and independent. So if these conversations have moved your work forward in some small way, that's where you can help keep them going. Luna: Yeah, it's a simple way to support the kind of deep-dive conversations we try to have here. No pressure, just if it's valuable to you. Lucas: Exactly. So back to the practical — if you're building a hiring process from scratch or fixing a broken one, start with those three questions and the peer reference. It's not a silver bullet, but it's a much better filter than most companies use. Luna: And if you already have a process, audit the last three hires who didn't work out. Ask yourself: did we check for values alignment, or just for skills and polish? Lucas: That's the homework. And I'd add: ask the teammates who survived a bad hire what signals they wish you'd caught. They saw it coming. They always do. Luna: Alright, that's a good place to leave it. Next episode we'll talk about how to actually fire someone without destroying your team's trust. Lucas: That's a tough one. Looking forward to it.