Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why Skills-Based Hiring Beats Degree Requirements
Transcript
- Lucas: So we talk a lot on this show about what makes a good hire. But there's one filter that's been in place for decades that might actually be screening out your best candidates: the four-year college degree requirement. Luna: You're talking about the shift to skills-based hiring. I've been seeing more companies drop degree requirements from job postings, but I wonder how much of it is real versus just optics. Lucas: That's exactly the question. And the data is starting to give us a pretty clear answer. A 2024 study from Harvard Business School looked at companies that removed degree requirements and replaced them with skills assessments. They found that hires made through skills-based methods were 40 percent more likely to stay past two years, and they performed at the same level or better than degreed hires in 85 percent of roles. Luna: Forty percent better retention is huge. But why aren't more companies doing this if the data is so clear? Lucas: There are a couple of reasons. First, habit. Recruiters have been trained to use the degree filter because it's easy—it's a quick yes or no. Second, there's a fear of lowering standards. But the research shows that a degree is actually a pretty poor predictor of job performance. It predicts socioeconomic background and persistence more than it predicts actual skills. Luna: So what does a good skills assessment look like? Because I've seen some companies use really generic tests that don't tell you much. Lucas: Right, the assessment has to be job-specific. The best example I've seen is IBM. They launched a skills-first hiring initiative a few years ago and they use what they call 'micro-credentials'—short, project-based assessments that mimic actual work tasks. So for a cybersecurity role, you'd get a simulated network breach and you have to show how you'd respond. That's way more predictive than asking where someone went to school. Luna: That makes sense. And IBM isn't alone. Google has their Career Certificates program, which is designed for people without degrees. I think they've hired thousands from that pipeline. Lucas: Exactly. And what's interesting is that these companies aren't just doing it for altruistic reasons. They're doing it because they found that the talent pool was too shallow when they restricted themselves to degree holders. In technical fields especially, there are plenty of self-taught programmers or people who went through boot camps who are just as good as computer science grads. Luna: But there is a risk, right? If you don't design the assessment well, you could end up with biased results or test for the wrong things. Lucas: Absolutely. A poorly designed assessment can be worse than a degree filter. For example, if the test is timed and requires fast typing, you might be screening for processing speed and not the actual skill. The key is to use a structured, validated assessment that's been tested for predictive validity. Companies like Pymetrics and Codility offer platforms that help with that. Luna: So what's the first step for a small business that wants to try skills-based hiring but doesn't have the budget for those platforms? Lucas: Start small. Pick one role—maybe a role you've had trouble filling—and redesign the hiring process around a work sample test. For a customer service role, you could give candidates a simulated difficult call and see how they handle it. Then track performance and retention for that cohort compared to your traditional hires. That gives you your own data to build from. Luna: I like that. And if someone is listening and thinking, 'My company would never go for this,' what would you say? Lucas: I'd say the data is on your side. Show them the Harvard study. Show them that IBM and Google and even the UK government are moving this direction. And point out that every day you require a degree, you're turning away candidates who could be your best performers. The cost of a bad hire is much higher than the cost of redesigning your process. Luna: You know, this conversation reminds me of why we keep this show ad-free. If these discussions have moved your thinking forward, listener support is what keeps it going. Lucas: Yeah, it's a small gesture that makes a big difference for us. If you've gotten value from an episode like this one, you can support the show at buy me a coffee dot com slash fexingo. Luna: Now, back to the topic. One thing I want to dig into is the impact on diversity. Studies show that degree requirements disproportionately exclude people of color. How does skills-based hiring change that? Lucas: That's a great point. The data is pretty striking. A 2023 report from the National Bureau of Economic Research found that when companies removed degree requirements for mid-level roles, the share of Black and Hispanic hires increased by 15 to 20 percent. The reason is structural: Black and Hispanic applicants are less likely to have a four-year degree due to systemic barriers, but they have equivalent skills. So skills-based hiring is one of the most effective diversity tools you can use. Luna: But there's a counterargument: some say skills assessments can also be biased if they're not designed carefully. For example, if the assessment uses language that's more familiar to native speakers. Lucas: That's true, and it's a valid concern. The solution is to validate your assessment on diverse candidate populations. If you see score gaps by demographic group, you need to revise the assessment. It's not about lowering standards—it's about measuring the right things fairly. And the advantage is that a degree is actually a proxy for privilege, while a well-designed assessment measures ability directly. Luna: So what about the candidates themselves? How should someone without a degree position themselves to get hired through a skills-based process? Lucas: First, build a portfolio of work that demonstrates your skills. For a developer, that means a GitHub repo with clean code and projects. For a marketer, it means case studies of campaigns you've run. Second, get certified in specific skills—Google, Microsoft, and Salesforce all offer industry-recognized certifications. And third, practice for work sample tests. Many companies will give you a take-home assignment, so treat it like a real job task. Luna: And for employers listening, what's one thing they can do this week to start shifting toward skills-based hiring? Lucas: Audit your current job descriptions. Look for any role that has a degree requirement and ask yourself: is this degree really necessary to do the job? If the answer is no—and in most cases it will be—remove it. Then replace it with specific skills and experience you're looking for. That's the easiest win. You'll immediately widen your applicant pool without sacrificing quality. Luna: It sounds simple, but I imagine many companies won't do it because of inertia. Lucas: That's exactly right. And that's the opportunity for the ones that do. The labor market is tight in many sectors—companies that can tap into non-degree talent have a real competitive advantage. They get to choose from a larger pool, and they get better retention. It's one of those rare cases where doing the right thing for equity also improves your bottom line. Luna: So we're seeing a convergence of data, business case, and social impact. That's a powerful combination. Lucas: Yeah, and I think we're still early in this shift. A 2025 survey from LinkedIn found that only 35 percent of US job postings have removed degree requirements, even though 70 percent of companies say they value skills over degrees. There's a gap between talk and action. But the trend is clear, and it's accelerating. Luna: That gap suggests there's still a lot of education needed inside organizations. Lucas: Exactly. Hiring managers are often the biggest hurdle. They're used to seeing 'Bachelor's degree required' and they're worried that removing it will flood them with unqualified applicants. But the fix is to have a structured screening process that assesses skills upfront. You can still filter out unqualified candidates—you just do it based on ability, not on a credential. Luna: And the data shows that when you do that, you get better hires. So why are we still having this conversation? Lucas: Because change is slow. But episodes like this are part of how it happens. If one listener goes back to their office tomorrow and removes a degree requirement from a job description, that's progress. Luna: I think that's a good place to leave it. Next week, we're looking at the rise of fractional executives and what that means for hiring at startups. Lucas: Yeah, that's a fascinating topic. More companies are hiring part-time C-level talent to save costs. We'll dig into the trade-offs. Luna: Until then, thanks for listening. Lucas: And if you want to support the show, you know where to find us: buy me a coffee dot com slash fexingo.