Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How Skills-Based Hiring Beat the Degree Filter
Transcript
- Lucas: So, Luna, I've been digging into a logistics company outside Columbus — about 400 employees — and they did something pretty radical in early 2025: they removed the degree requirement from every single job posting, including management roles. Luna: Every role? That's bold. Did they replace it with anything, or just open the floodgates? Lucas: They replaced it with a structured skills-assessment platform. Every candidate, regardless of background, has to complete a work-sample test that mirrors the actual job. For warehouse supervisors, it's a simulated shift-planning exercise. For accounting clerks, it's a data-entry and reconciliation task. Luna: So they're testing the actual work, not the resume. What happened after 18 months? Lucas: Hires from non-degree backgrounds jumped 42 percent, and first-year turnover dropped 28 percent. That's the headline. But the story is really in how they designed and rolled it out — and what almost derailed it. Luna: Almost derailed it? I'm guessing the CEO's nephew was involved. Lucas: Exactly. The CEO's nephew applied for a logistics coordinator role. He had a business degree from a decent school, but he scored in the bottom quartile on the assessment. The hiring manager was ready to pass, but the CEO's office called to 'check in' on the process. Luna: Oh, that's a classic. What did they do? Lucas: The VP of HR held the line. She presented the data — the assessment had been validated against high performers, and the nephew's score predicted poor on-the-job performance. The CEO backed down, but it created a lot of internal tension. They had to have a company-wide conversation about what the new process meant. Luna: That's the part people don't talk about — the change management. It's not just flipping a switch on the ATS. Lucas: Right. They spent three months training every hiring manager on how to interpret the assessment scores, how to combine them with structured interviews, and how to avoid over-relying on gut feel. They also had to recalibrate their expectations — some managers initially thought the assessment was too hard, but the data showed it was actually a better predictor than the degree filter. Luna: Did they run into any legal issues? Removing degree requirements can have disparate impact questions if it's done inconsistently. Lucas: Good point. They worked with an employment attorney to validate the assessments against job performance, which is the key defense under the Uniform Guidelines on Employee Selection Procedures. They also made sure the assessments were applied uniformly to all candidates, not just those without degrees. That was critical. Luna: So it's not just about removing a filter, it's about replacing it with something better and defensible. Lucas: Exactly. And the results went beyond turnover. Their candidate pool became more diverse — hires from underrepresented groups increased by 30 percent, because the degree requirement was disproportionately screening out qualified people from lower-income backgrounds. Luna: That's a tangible outcome. But what about the people who already had degrees? Did they feel threatened by the change? Lucas: There was some resentment initially. One senior manager said, 'I had to work my way through college, and now you're telling me it doesn't matter?' But the HR team framed it as 'the degree still matters, but it's not the only signal.' They emphasized that the assessment is a more direct measure of the skills needed to succeed. Luna: I can imagine that being a tough sell. How did they ultimately get buy-in? Lucas: They ran a pilot in one department first — the warehouse operations team — and showed the results side-by-side with the old hiring data. When the pilot team's error rates dropped and their productivity metrics improved, the skeptics started to come around. Data beats opinion. Luna: That's a great way to build momentum. What kind of assessments are they using exactly? I'm curious if it's off-the-shelf or custom. Lucas: They started with an off-the-shelf platform for general cognitive ability and situational judgment, but quickly realized they needed to customize the work-sample tests for their specific roles. They spent about three months working with the platform vendor to build simulations that matched their actual workflows. Luna: That's a significant upfront investment. Did it pay off in the long run? I'm thinking about cost per hire and time to fill. Lucas: Actually, their cost per hire went down by about 20 percent because they were spending less on external recruiters and fewer bad hires that would have cost them in rehiring and training. time to fill stayed about the same, but the quality of hires improved dramatically. The CEO told me the assessment was the best ROI they've seen in HR in a decade. Luna: That's a strong endorsement. But I want to push back a little. Isn't there a risk that the assessment becomes a new filter that's just as biased as the degree requirement? I mean, if the assessment is designed by people who all have degrees, they might unconsciously favor certain ways of thinking. Lucas: That's the sharpest question you can ask, and they were aware of it. They did a differential validity study to check whether the assessment predicted performance equally across different demographic groups. They found no significant differences, but they also committed to reviewing the assessments annually to ensure they don't become stale or biased. Luna: So it's not set-and-forget. That's refreshing — too many companies adopt a tool and then never revisit it. Lucas: Absolutely. And they also made sure that the assessment isn't the only factor. They use a weighted scoring system that includes the assessment, a structured interview, and a reference check that's now focused on past behaviors rather than just 'were they a good employee.' Luna: That aligns with what we've talked about in past episodes — structured reference checks can uncover things that resumes can't. Lucas: Right. And that's why this case is so compelling. It's not just about dropping degrees — it's about building a more holistic, evidence-based hiring process. They're actually measuring the things that matter for performance, not just proxies like where you went to school. Luna: I think that's something our listeners can really take to heart. You mentioned the cost per hire went down, but what about the learning curve for hiring managers? Did they need a lot of training to interpret the assessments? Lucas: They invested about 20 hours of training per manager, which is a lot, but it paid off. The managers learned how to use the scores to inform their interviews, not to replace them. For example, if a candidate scores low on a particular subscale, the manager knows to ask more targeted follow-up questions about that skill. Luna: That's a great integration. It's not just a numeric gate, it's a conversation starter. Lucas: Exactly. And the feedback from candidates has been surprisingly positive. They actually appreciate that the process is transparent and job-related. One candidate told them, 'I felt like I was being judged on what I could do, not what was on my paper.' That's the kind of candidate experience that builds a talent pipeline. Luna: That's a powerful quote. It makes me think about how we talk about hiring in general — we often focus on the employer's side, but candidates are also evaluating us. Lucas: And that's a good segue to something I want to mention. You know, we've been having these conversations for over 160 episodes now, and I've heard from a lot of listeners that they've applied some of these ideas in their own hiring. If you're one of those listeners, and if these conversations have moved your work forward in some small way, we'd be grateful if you'd consider supporting the show. Luna: Yeah, it's what keeps this podcast ad-free and independent. You can do that at buy me a coffee dot com slash fexingo — it's a simple way to say thanks and help us keep going. Lucas: And now, back to the logistics company. So they've seen these great results, but they're not resting on their laurels. They're now looking at whether they can apply the same skills-based approach to their internal promotions. Luna: That's a natural next step. You've mentioned internal mobility in a past episode, and this seems like a perfect fit. Lucas: It does. They're starting to use the same assessment battery for employees who want to move into supervisory roles, instead of relying on tenure or a degree. The early indications are that they're finding hidden talent within their own ranks — people who might have been overlooked before. Luna: That's exciting. It's basically applying the same philosophy — measure skills, not pedigree — to your existing workforce. Lucas: Exactly. And the biggest lesson from this case, I think, is that the degree requirement is a lazy filter. It's easy to use, but it's not a good predictor of job performance. When you invest in building a better filter, you get better outcomes — not just in who you hire, but in who you keep and who you promote. Luna: And it forces you to really think about what success looks like in each role. That's a valuable exercise in itself. Lucas: It is. So if you're a hiring manager or an HR leader, the question to ask yourself is: what are you really using degrees as a proxy for? And could you measure that more directly? The answer might open up your talent pool in ways you didn't expect.