What Skills-Based Hiring Forgot to Replace

When a company drops the degree requirement from a job posting, it thinks of itself as removing a barrier. That's true. But a requirement is also a filter, and a filter does work. Once it's gone, someone else has to do that work.

The case for dropping degrees was a good one. Credential requirements were screening out people who could plainly do the job. Someone who spent four years doing hands-on technical work shouldn't be rejected before a recruiter ever sees their name, just because those four years weren't spent in a classroom. IBM, Google and Apple all dropped the requirement, and by one count roughly 45% of Fortune 500 job postings no longer asked for a four-year degree by 2025.

So the pool got wider, which was the point. What didn't reliably follow was better hires. I think the reason is simple enough that it's easy to miss: when you let more people in, you have to get better at telling them apart, and most teams didn't.

Think about what a recruiter sees. Suppose a role used to draw around 120 applications and now, without the degree line, draws three or four times that. The recruiter has the same hours in the day and the same tools she had before. The one thing that changed is that the blunt instrument she used to cut the pile down is gone. And the pile is getting harder to read, because AI-generated applications are now flooding ATS platforms, so a growing share of what she reads was polished by software. She has more applicants, less trustworthy paper, and no extra help.

Resumes can't show skills

This is where it gets odd. Skills-based hiring means judging people by what they can do. But the screening tools most companies use were built to judge what people have written down. An ATS keyword filter can tell you whether a resume contains the word "Python." It can't tell you whether the person who typed it writes code you'd want to maintain. A resume can say someone has sales experience. It can't tell you whether they can build rapport with a cold lead who is trying to get off the phone.

Resume review, written questionnaires and keyword matching were tools for checking credentials, and companies are now using them to check the thing credentials used to stand in for. They measure what candidates put on paper. Skills mostly don't live on paper. You find out about them by talking to someone.

So what a lot of companies ended up with is a new philosophy running on an old process. They took away the degree filter and put nothing in its place that can evaluate what they now say they care about.

What would work

We've known for a long time what predicts job performance reasonably well. Research going back decades puts structured interviews near the top of the list, behind only work samples and cognitive ability tests. A structured interview does something a resume can't. You ask everyone the same core questions, and you follow up when an answer is vague. You see how someone reasons through a problem and whether their claims about themselves hold up after two or three direct questions.

In a sense, the skills-based movement pointed right at this. If what you care about is ability, conversation is the obvious way to find it. But the conversation is the expensive part, and it's the part most teams skipped.

The arithmetic is worth doing, because it shows how little of this is about recruiters trying harder. A recruiter who does a dozen screening calls a day would need around six weeks of nothing but calls to speak with 400 applicants for a single role. And she has more than one role. Talking to every plausible candidate and probing the vague answers, which is what doing skills-based hiring properly would mean, is simply beyond what one person can do.

That gap is the problem we built Asendia around. The limit in that arithmetic is one person's day, and software doesn't have it. Asendia can hold the first structured conversation with every applicant soon after they apply, however many of them there are, so nobody sits in a queue waiting for a recruiter to get free. If someone applies for a sales development role, it doesn't scan their resume for "SDR." It calls them and asks how they've handled a cold outreach situation, then follows up on what they say and asks for specifics. Answering out loud in real time is a different test from writing a polished response with ninety seconds to think.

What the recruiter gets back is evidence instead of a stack of keyword matches: a summary of each conversation, the candidate's answers in their own words, and a ranking by how well they qualify, all written into the ATS. The size of the applicant pool stops mattering much, whether it's 80 people or 800, and the recruiter's time goes to the conversations where her judgment actually counts.

None of this means the degree requirement should come back. Dropping it corrected a real mistake. But removing a filter without replacing it just moves the work downstream, to a place where it's harder to see and more expensive to fix. If you're going to judge people by what they can do, you need some way of finding out what they can do, and for most jobs that means talking to them.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!