You Said You Dropped the Degree Requirement. Your Applicant Tracking System Didn't Get the Memo.
Marcus Webb on the gap between "we removed degree requirements" and what your ATS is still screening for — and who actually pays for it.
HR OPERATIONS
Marcus Webb
8/31/20263 min read


A hiring manager told me this week that her company "doesn't require degrees anymore" for the role she was filling. I asked how many non-degreed candidates had actually made it to an interview that quarter. She didn't know. She checked. The answer was zero. Nobody had lied to her. The job posting really did say "or equivalent experience." The applicant tracking system, set up two years before that language changed, was still filtering resumes without a degree field into a folder nobody looks at.
This is the part of skills-based hiring nobody wants to talk about at the conference panel, so let me name it plainly.
The Gap Between the Policy and the Practice
A Harvard Business School and Burning Glass Institute study looked at roughly 77 million U.S. hires and found that fewer than one in 700 came from companies that had genuinely opened roles to candidates without degrees. The same research sorted companies into three groups: about 37% showed real behavioral change in who they actually hired. Roughly 45% made what researchers called "in name only" changes — the degree language came out of the posting, but the hiring pattern stayed identical. The remaining 18% backslid, quietly reintroducing the old filter after an initial period of genuine change.
That middle group is where most of the companies I talk to actually sit, whether they know it or not. Indeed's Hiring Lab data from late 2025 shows 19.3% of U.S. job postings still explicitly require a bachelor's degree — down from where it used to be, but a real floor, not a rounding error. And here's the number that should make every HR leader uncomfortable: a TestGorilla survey found 41% of employers now say they value degrees more than they did five years ago, even as their public messaging moved the opposite direction.
Why This Isn't Just a Recruiting Problem
I want to be direct about who absorbs the cost of this gap, because it's not the company. It's the candidate who spent an evening tailoring a resume to a posting that promised "skills-based" consideration, got auto-filtered by a system nobody updated, and never knew why. It's the employee already on your team without a degree, watching open internal roles get filled by external candidates with degrees and less relevant experience, and drawing the correct conclusion about how much the stated policy actually protects people like them.
I've also watched the reverse mistake happen — HR teams so focused on removing degree language from postings that they never touch the actual screening logic underneath it. GPA screening has genuinely declined, from 73% of employers using it in 2019 down to 42% in 2026. That's real progress. But a policy change that stops at the job posting and never reaches the applicant tracking system's filters, the recruiter's informal shortlist habits, or the hiring manager's unstated preference isn't a policy change. It's a rebrand.
What Closing the Gap Actually Requires
Audit your ATS filters, not just your job postings. If "degree required" was ever a hard filter in the system, removing it from the posting doesn't remove it from the software. Someone has to go turn it off, and someone has to check that it's actually off.
Track who makes it to interview, not just who applies. The hiring manager in my story didn't know her zero-non-degree-interview number because nobody was measuring it. If you're not tracking this stage of the funnel by education background, you don't actually know whether your policy is working.
Give hiring managers a real alternative signal, not just permission. Telling a manager "you can consider candidates without degrees" without giving them a structured way to evaluate equivalent experience just pushes the decision back to gut instinct — and gut instinct defaults to the familiar credential.
Skills-based hiring was never going to fail because the idea was wrong. It's failing in the specific, boring, fixable places where the old system was never actually turned off. If your company made this announcement and you haven't checked whether the systems caught up to the sentence, that's the audit to run this quarter — before the next candidate spends an evening on an application that was never going to reach a human being.
Questions? Reach out anytime.
support@workplayengage.store
WorkPlayEngage is a product of Dieza Publishing. © 2026 WorkPlayEngage. All rights reserved.
Privacy & Security Note: WorkPlayEngage templates are native Google Sheets. We do not host your data, and we never have access to your employee names or internal metrics. Your engagement remains 100% private within your organization’s Google Drive.
Play:
Baby Pool
Big Guess
NFL Survivor Pool
Super Bowl Squares (Coming Soon)
Office Bingo (Coming Soon)
Help
WorkPlayEngage:
Our Story
Contact Us
Blog
Privacy Policy
