Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How One Company Cut Bad Hires by Dropping Degree Requirements
Transcript
- Lucas: So there's this mid-sized logistics firm in the Midwest, about 800 employees, and back in late 2024 they quietly deleted the degree requirement from every single job posting. No announcement, no press release. They just did it. Luna: And that's not exactly rare these days. A lot of companies say they're going skills-based. But you're implying this one actually tracked the outcome. Lucas: That's the thing. They tracked twelve months of data before and twelve months after. And the headline number: early turnover, meaning people who left within their first year, dropped 34 percent. Not hires without degrees necessarily, but overall first-year attrition. Luna: So removing the degree filter made retention better across the board. That seems counterintuitive unless they changed other stuff too. Lucas: Right, and they did. They didn't just open the floodgates. They replaced the degree filter with a two-stage assessment. First, a short online work sample, about twenty minutes, tied directly to the day-to-day tasks of each role. Then, for people who passed that, a structured interview where every candidate got the same core questions scored on a rubric. Luna: So the degree wasn't the only thing that changed. The entire screening process got more rigorous. That's a confounding variable. Lucas: Exactly. And I think that's the real lesson. The degree was a lazy proxy for competence. Once you remove it, you're forced to define what you actually need. And this company found that their old interview process was full of vague questions about 'leadership' and 'communication' that didn't predict much. Luna: I'd love to hear what one of those work samples actually looked like. Give me a concrete example. Lucas: For a warehouse supervisor role, the work sample was a simulated shift handoff. They gave candidates a report with delayed shipments, a staffing shortage, and a temperature issue on a cold-storage unit. The candidate had to write a brief email to the next shift explaining priorities. That's it. Luna: And that's a much better signal than a diploma. Because it's testing judgment under real constraints, not your ability to cite a textbook. Lucas: And they scored it against a rubric—did they catch the temperature issue, did they flag the staffing risk, did they communicate a clear plan. Two people could write very different emails and both score high, but it's a direct measure of the job. Luna: So what happened to the people who would have been filtered out by the degree requirement? Did they actually get hired in meaningful numbers? Lucas: About 28 percent of hires in the first year had no four-year degree. And their performance ratings, at the six-month mark, were statistically indistinguishable from the degree holders. But here's the kicker—their retention was actually better. The non-degree hires stayed longer. Luna: That's fascinating. Why do you think they stayed longer? Maybe they were more grateful for the opportunity, or maybe the job matched their expectations better because the assessment was so specific. Lucas: I think the latter is a big part of it. The work sample gave them a realistic preview. They knew exactly what they were signing up for. And the company found that realistic job previews reduce turnover because there's no 'this isn't what I expected' shock in the first month. Luna: And that's a classic finding from the research—realistic job previews cut attrition by around 10 percent on average. But this company saw 34 percent. That's a big jump. Lucas: True, and they also revised their onboarding to include a 90-day check-in where they explicitly asked about role clarity. So the assessment was one piece, but the whole system shifted toward transparency. Luna: Let's talk about the hiring manager side. Did they resist? I imagine some of them thought they were getting 'second-tier' candidates without degrees. Lucas: There was pushback in the first quarter. A couple of managers complained they had to spend more time screening because they couldn't just scan for 'bachelor's degree'. But once the data came in, the same managers were converts, because their teams were performing just as well with less turnover. Luna: So what's the cost saving here? Can we put a number on it? I know we've talked about hidden costs of bad hires before, but this is about retention. Lucas: They estimated that for a supervisor role, replacing someone costs about 40 percent of their annual salary in recruiting, training, and lost productivity. With 800 employees and a 34 percent drop in first-year turnover, they calculated roughly one point four million dollars saved over twelve months. Luna: That's the kind of number that gets a CFO's attention. And it came directly from removing a filter that wasn't doing its job. Lucas: And that's the broader point. Degree requirements are often a crutch. They let hiring managers avoid doing the hard work of defining what success looks like. When you remove the crutch, you're forced to get specific. And specificity is what drives better hiring decisions. Luna: But I want to be careful here. We're not saying degrees are worthless. There are plenty of jobs where a degree signals something real—medicine, law, engineering. This is about roles where the degree was just a lazy proxy. Lucas: Right. And the research backs that up. One study from Harvard Business School found that degree inflation—when jobs that historically didn't require a degree start requiring one—adds unnecessary barriers without improving performance. This company's experiment is a real-world example of that. Luna: So if a listener is sitting there thinking, 'Should we drop degree requirements?' What's your advice? Start with a pilot in one role family? Lucas: Exactly. Don't do it across the board overnight. Pick a role where you have enough hires in a year to get meaningful data. Define the work sample, train your interviewers on the rubric, and track everything. Then compare against the previous year's cohort. If the data doesn't show improvement, you can always go back. Luna: And what about the legal angle? Do you have to be careful about disparate impact? If you drop the degree, you might see a more diverse applicant pool, but you also need to make sure your assessment doesn't introduce a different kind of bias. Lucas: That's a smart point. The work sample has to be validated—you need to make sure it's measuring the job, not something like test-taking ability or cultural fit. This company ran a small internal validity study before scaling it up. They had 40 current employees take the assessment and compared their scores to their performance reviews. The correlation was solid, about.5, which is strong for a hiring tool. Luna: That's reassuring. So the takeaway isn't just 'drop degrees.' It's 'replace lazy filters with thoughtful ones.' Lucas: And that's the deeper theme of this episode. We often talk about hiring as if the problem is finding good people. But sometimes the problem is that our filters are doing the opposite of what we think they're doing. They're screening out people who would be great and letting in people who just have the credential. Luna: And that's why this conversation matters. I know a lot of our listeners are in HR or recruiting roles, and they're under pressure to hire faster. But this shows that slowing down to define the job properly pays off in the long run. Lucas: Yeah, and it's a reminder that the best hiring practice isn't a single trick—it's a system. The assessment, the structured interview, the onboarding check-in—they all work together. And the degree requirement was just the weakest link. Luna: Before we wrap up, I want to bring up something that's been on my mind. We're lucky enough to have a show like this that's completely ad-free. And that's because some listeners choose to support us. If these episodes have given you a new idea or saved you from a bad hire, you might consider helping keep that going. You can do that at buy me a coffee dot com slash fexingo. It's a small gesture, but it adds up. Lucas: Thanks for saying that, Luna. And honestly, it's the kind of support that lets us dig into stories like this one—where a simple change in a hiring process led to a million-dollar impact. We don't take that for granted. Luna: So back to the practical side. If someone wants to replicate this, what's the first step they should take tomorrow? Not a big project, just one small thing. Lucas: Pick one role you hire for regularly. Write down the top five tasks that person does each week. Then design a twenty-minute simulation that covers those tasks. That's it. That's the seed of a work sample. You can test it in a week. Luna: That's surprisingly doable. And if that simulation reduces your first-year turnover by even half as much as this company saw, you're looking at hundreds of thousands in savings. Lucas: And you'll have a much clearer sense of what you're actually hiring for. Which, honestly, is the best outcome of all. Luna: Well, this has been a great conversation. Thanks for joining us, and we'll catch you next time.