
Skills-based hiring is having a moment. Job postings are dropping degree requirements. LinkedIn has rebuilt entire search filters around it. Roughly three-quarters of recruiters now call it a top hiring priority for 2026. Read enough coverage and you would think this is a brand-new idea, something HR just invented. It isn’t. Independent professionals have been hired this way for years. Nobody brings on a freelance video editor or a fractional CFO based on where they went to school. The freelance world has been running a skills-based hiring model the whole time. Full-time hiring is just now catching up, and the data shows the catch-up is slower than the headlines suggest.
The Skills-Based Hiring Headlines Look Great
On paper, the shift is real. The National Association of Colleges and Employers found that seventy percent of employers now report using skills-based hiring practices. That’s up from sixty-five percent the year before. Most of that growth is showing up at the interview and screening stage. LinkedIn’s own research suggests something similar. Evaluating candidates by skill instead of job title or degree can expand a talent pool by up to ten times. Employers who lead with skills are also meaningfully more likely to land a successful hire. Even at the leadership level, the pressure is mounting. SHRM reports that a strong majority of CEOs expect to lean more heavily on independent contractors and project-based talent this year. That’s a quiet admission: the traditional full-time hiring funnel isn’t flexible enough to keep pace on its own.
It’s not hard to see why the idea is appealing. A resume tells you where someone has been. It doesn’t tell you whether they can do the job. Every HR leader who has sat through a mediocre first ninety days already knows that. Skills-based hiring promises a shortcut around that guesswork: evaluate the work itself, not the story around it. It’s a good instinct. The problem shows up in the execution, not the idea.
The Part the Headlines Leave Out
Here’s where it gets more honest. A 2026 Lumina Foundation and Gallup survey polled two thousand U.S. employers. Even among companies that formally removed degree requirements, most still say they prefer degree holders. That preference shows up when it comes down to an actual decision. Roughly three-quarters expect a college degree to matter as much or more five years from now. Nearly half say most jobs at their organization genuinely require one. That is not a company that has adopted skills-based hiring. That is a company that has adopted skills-based hiring language, while quietly keeping the old filter running in the background. It’s an easy trap to fall into. Removing a line from a job posting is a policy change. Actually evaluating someone on what they can do, independent of the letters after their name, is a behavior change. And behavior change is slower, harder, and a lot less quotable in a press release.
Where Skills-Based Hiring Already Works, Without the Debate
This is exactly the gap freelance and project-based work never had to close. It never had the filter to begin with. When a business brings on independent talent for a defined deliverable, the resume is almost beside the point. What matters is whether the person can do the specific thing the project needs, on the timeline it needs it. That’s skills-based hiring in its purest form. It’s the model FlexTal was built around from day one. A dedicated Customer Success Manager works with a company to define the actual skill gap. That’s often different from the job title that used to fill it. From there, the manager matches against FlexTal’s vetted Flexible Talent Network. There’s no assumption that a four-year degree or a specific industry background is the only credible route to competence. Neither is a traditional career path. There’s just the work, and whether someone is demonstrably good at it.
What This Actually Means for How You Hire
None of this means degrees or traditional experience stop mattering. It means the companies getting real value out of skills-based hiring treat it as an operating shift. It’s not just a talking point for them. Start with the outcome a role or project actually needs to produce, not the resume shape that has historically filled it. That distinction matters even more when a team is weighing a gap. Is it a genuine skill shortage or simply a capacity problem dressed up as one?
Get the Sequencing Right Before You Post the Role
It also means being honest about where flexible, project-based talent can help. That kind of talent can close a gap faster and more precisely than a six-month full-time search. That’s especially true when the work is scoped clearly from the start. Vague job descriptions are still the fastest way to sabotage a skills-based approach before it even starts. That’s true no matter how progressive the hiring policy sounds on paper. A skills-first job posting with a vague scope underneath it is still a coin flip. It’s just a coin flip with better marketing.
There’s also a sequencing question most companies skip past. Before deciding whether a role needs to be filled at all, it’s worth asking a simpler question. Is the gap even a hiring problem in the first place? Sometimes what looks like a missing skill set is actually a capacity problem. The team already has the skill. What’s missing is the time. No amount of skills-based rigor in the interview process fixes a capacity shortfall. Getting that distinction right, before a req even gets posted, is half the battle.
The freelance and independent talent market didn’t adopt skills-based hiring because it was trending. It adopted it because there was never another option that made sense. You can’t hire someone for a six-week project based on a degree they earned a decade ago. Full-time hiring is welcome to catch up. It just won’t get there by dropping a line from a job post and calling it done. That takes an actual willingness to hire the work, not the resume. It also takes honesty about the difference between the two.


