Leaders are feeling it from both sides. There are more open roles to fill, and at the same time, it is getting harder to identify the right candidates quickly. Volume is not the problem. Signal is.
That is why skills-based hiring has become such a common talking point.
More companies are moving away from rigid credential requirements and toward evaluating what candidates can actually do. Organizations like IBM have shifted toward skills-first hiring, including removing degree requirements for a significant portion of roles, in an effort to expand access to talent.
On the surface, it sounds like a meaningful shift.
But when you look at how hiring actually happens inside most organizations, a different picture emerges.
The language has changed. The process has not.
What Skills-Based Hiring Was Supposed to Fix
For years, hiring relied heavily on proxies.
Degrees, job titles, and years of experience were used as shortcuts to predict performance. These signals were easy to scan, easy to filter, and easy to standardize across large applicant pools.
The problem is that they were never particularly accurate.
A candidate can have the right title and still struggle to perform. Another candidate can have no formal credentials and still operate at a high level from day one.
Skills-based hiring was meant to correct that imbalance.
Instead of asking where someone worked or what degree they hold, the focus shifts to how they think, how they approach problems, and how they execute in real situations.
Organizations like IBM have highlighted a growing shift toward skills-first job design, with many roles no longer requiring a traditional four-year degree.
That shift matters.
But it only works if the evaluation process actually reflects it.
The Screening Layer Is Where the Model Breaks
Most hiring teams did not redesign their process when they adopted skills-based language.
They kept the same structure.
A typical flow still looks like this:
- Resume comes in
- System filters based on keywords, experience, or education
- Recruiter reviews a narrowed pool
- A small percentage of candidates move to a phone screen
The issue is not what happens at the interview stage.
It is what happens before that.
If candidates are filtered out before anyone evaluates their ability, then the system is still operating on credentials, even if the job description says otherwise.
This is the gap most companies underestimate.
They believe they are hiring for skills, but their process never gives those skills a chance to surface.
Why Companies Default Back to Credentials
This is not usually a strategy problem. It is an operational one.
Evaluating skills takes more effort than verifying credentials.
A degree is simple. It is either there or it is not. Systems can check it automatically.
Skills require context.
You have to understand how a candidate approaches a problem, how they make decisions under pressure, and how they communicate their thinking. That requires interaction.
For hiring teams managing high applicant volume, that interaction has always been the bottleneck.
So the system falls back to what it can handle efficiently.
