Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How a Blind Résumé Review Changed Hiring Outcomes
Transcript
- Lucas: So Luna, there was a story this week about a mid-sized SaaS company that decided to strip names and photos off every résumé that came through their applicant tracking system. They even removed the university names. Six months later, they had a twenty-two percent increase in diversity among final-round candidates, and their time to hire dropped by nine days. That's a pretty dramatic outcome. Luna: Nine days is huge. But I'm a bit skeptical. How do you actually anonymize a résumé in the age of LinkedIn and GitHub? Anyone can just Google the candidate and find out who they are. Lucas: That's exactly the tension. The company I'm talking about, they didn't try to hide the candidate's identity forever. They just delayed it. The first screen was done blind — no name, no contact info, no school names. But the hiring manager inevitably does their online research before the interview. So the blind part only really affects the initial shortlisting decision. Luna: So it's more like a 'blind first look' than a fully blind process. But even that can be powerful if it changes who makes it to the first conversation. Lucas: Right. And what's interesting is that they combined the blind review with a structured scoring rubric. Each résumé was scored on specific criteria: relevant experience, specific skills, career progression. No free-form notes. That's what really cut the bias, not just the anonymization itself. Luna: That makes sense. I remember reading about orchestra auditions in the seventies. They started putting musicians behind screens, and the proportion of women in top orchestras jumped dramatically. But it wasn't just the screen — they also made the auditions more structured, with the same pieces for everyone. Lucas: Exactly, and that's the key parallel. Blind screening alone isn't magic. It works when you pair it with a clear definition of what good looks like. Otherwise you're just removing names and still making gut calls. Luna: And the nine days saved — where did that come from? Is that just because they had fewer résumés to review, or something else? Lucas: Probably a mix. They were spending less time on each résumé because they weren't trying to read between the lines about pedigree or personal brands. And they had fewer interview rounds because the first screen was now more effective at picking the right candidates. They went from four rounds to two for most roles. Luna: Fewer rounds and faster hires. That's the kind of outcome any recruiter would love. But I'm curious — did anyone push back internally? Hiring managers can be territorial about their process. Lucas: Oh, definitely. The biggest pushback came from managers who were used to scanning for 'target schools' or specific companies. They felt like they were losing a shortcut. One manager actually said, 'I can tell a lot from where someone went to school.' And the CHRO's response was, 'You can tell a lot, but you can't tell if they can do the job.' Luna: That's a great line. And it touches on something — if you're removing school names, you're also removing a signal that might actually be useful for some roles. Not everything can be learned on the job. Lucas: True. And that's why they didn't do it for every role. They piloted it for software engineering and customer success positions — roles where they were hiring in volume and where the skills could be assessed through work samples and structured interviews. For more senior roles, they kept a more traditional process because the network and track record mattered more. Luna: So it's not a one-size-fits-all. That's a nuance I appreciate. And I'd love to know — did they measure anything else besides diversity and time to hire? Like, did the quality of hires actually improve? Lucas: They looked at performance ratings after six months on the job. There wasn't a statistically significant difference compared to before, but there was a slight uptick in the average rating. More importantly, the retention rate for new hires went up by about eight percent. So the candidates who came through the blind screen were staying longer. Luna: That's a strong signal. Long-term retention often says more about fit than any interview performance. And I imagine the hiring managers eventually came around once they saw that the new hires were performing well. Lucas: They did, but it took time. The first few months were rough. There was a learning curve for everyone involved. But once they saw the data, the skepticism faded. Now, the company is expanding the blind review to more departments. Luna: And this is what I love about this show — we get into the messy reality. It's not just 'blind hiring works' and everyone high-fives. There are real challenges and trade-offs. Lucas: Absolutely. And speaking of practical realities — we should mention that this show is ad-free and listener-supported. If these conversations have moved your work forward in some small way, and you feel like buying a coffee, the link is buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. No pressure, just a low-key way to keep us going. Luna: Yeah, I mean, we put a lot of research into each episode, and it's nice to know it's useful. But back to blind reviews — one thing that fascinates me is the research in Europe. There were some field experiments in France and Germany where they sent out thousands of fake résumés, some with foreign-sounding names, some with local names. The differences in callback rates were stark. Lucas: Right, those studies showed that applicants with North African or Turkish names got significantly fewer callbacks. But when they repeated the experiments with anonymized résumés, the gap almost disappeared. That's pretty compelling evidence that the name itself was triggering bias. Luna: And yet, in practice, very few companies actually do this. Why? If the evidence is that strong, why isn't everyone jumping on board? Lucas: A few reasons. First, it's a logistical pain. Your ATS has to be configured to hide certain fields, and if you're getting a lot of referrals, the referrer's name is right there in the email thread. Second, there's a fear of losing 'culture fit' — which is often code for 'hiring people like us.' And third, there's genuine concern that you might miss out on top talent from less obvious backgrounds if you don't have the full picture. Luna: That last point is interesting. Some people argue that blind hiring can actually hurt diversity if you're not also looking at candidates from non-traditional paths. Because if you remove the school name, you might miss someone who went to a top school but also had a non-traditional background that made them exceptional. Lucas: But the data from this company suggests the opposite. They saw an increase in candidates from underrepresented groups making it to the final round. And they also saw an increase in hires from non-elite schools. So the blind screen was actually broadening their pool, not narrowing it. Luna: So what's the takeaway for a listener who wants to try this? What's the first step you'd recommend? Lucas: Start small. Pick one role family, like junior software engineer or customer support, and run a pilot for ninety days. Set up a structured scoring rubric first — that's crucial. Then anonymize the résumés in your ATS or just have someone external strip the identifying info before the hiring manager sees them. Measure not just diversity, but also time to hire, quality of hire, and retention. And be prepared for pushback. Luna: And what about the pushback from candidates? Did anyone complain about not being able to showcase their brand? Lucas: That's a good question. In this case, candidates were informed that the initial screen was blind, and the feedback was mostly positive. They felt it was a fairer process. Some even said they appreciated that it focused on their actual experience rather than their network. Luna: That's a nice side effect. It also sends a signal that the company cares about fairness, which can be a recruiting tool in itself. Lucas: Exactly. And that's one of the reasons they decided to make the pilot permanent. It wasn't just the numbers — it was also the brand boost. They're now marketing themselves as a 'blind-first' employer, which is a differentiator in a crowded market. Luna: I love that. It's a smart move. But before we wrap up, I want to circle back to something you said earlier about the structured rubric. Can you give an example of what that looked like for a customer success role? Lucas: Sure. They had five criteria. One was 'experience with onboarding customers,' which they defined as having managed at least ten onboarding projects. Another was 'written communication skills,' which they scored based on the candidate's résumé format and clarity. There was also 'product knowledge' — they gave extra points for familiarity with similar SaaS tools. And 'growth trajectory' — they looked for promotions or increased responsibility within the same company. Each criterion was scored from one to five, and they only advanced candidates with a total of eighteen or higher. Luna: So it's a quantitative threshold, not a gut feeling. That must have made the hiring managers more comfortable once they saw the system in action. Lucas: It did. And it also made the interviews more focused because they already knew the candidate had passed a standardized bar. The interview became about digging deeper into the specific criteria, rather than starting from scratch. Luna: That makes a lot of sense. I think the biggest lesson here is that blind hiring isn't about removing all information — it's about removing the irrelevant information that triggers bias, while keeping the relevant stuff that predicts performance. Lucas: Exactly. And that's the nuance we wanted to get to. It's not a magic bullet, but when done thoughtfully, it can be a powerful tool in the hiring toolkit. Luna: Well, I'm curious to see how this evolves. Maybe in a year we'll have data on whether the diversity gains actually stick, and whether the retention improvements continue. Lucas: I'd love to do a follow-up. For now, I think the takeaway is this: if you're considering blind hiring, don't just strip names and call it a day. Build a structured process around it, run a pilot, and measure everything. It might just transform your hiring, but you have to do it right. Luna: And if you've tried something like this, we'd love to hear about it. But for now, thanks for joining us. We'll catch you next time.