Half of "Degree-Required" Jobs Don't Actually Require a Degree

For every 77 million annual hires in 2023, the entire skills-based hiring movement produced about 97,000 extra workers without degrees. That's fewer than one in 700 hires. The press releases said the degree was dead. The hiring data says almost nothing changed. The posting got rewritten. The filter did not.

So when a job says "Bachelor's required," read it as a default, not a measurement. Most of the time, nobody checked whether the work actually needs a degree. They checked whether saying so was cheaper than thinking about it. This is the same move behind the so-called skills shortage that is mostly a wages problem: the requirement describes what's convenient to claim, not what the work demands.

Is the "degree required" line a real standard or just a default?

It's a liability shield. When you post "Bachelor's required," you aren't testing for ability. You're outsourcing the ability question to an institution that already charged the candidate to take it. The screen feels rigorous. It mostly isn't.

The cleanest proof is old. In 2015, 67% of production supervisor job postings demanded a college degree, while only 16% of the people actually doing the job had one. A 51-point gap between what the posting asked for and what the role demonstrably ran on. The degree wasn't predicting performance. The incumbents without one were already proving that.

Weak read: "The posting says degree required, so the job needs a degree." Strong read: "The posting says degree required. The person doing that exact job next to the new hire has a high school diploma and twelve years on the floor. The requirement is a habit, not a hurdle."

That same 2017 study counted 6.2 million middle-skills jobs at risk of degree inflation: roles where employers demanded a credential that workers without one were already filling successfully.

Why do companies keep using a filter they admit is broken?

Because the cost of a broken filter is invisible, and the cost of waiving it has a name attached.

Employers know. Two-thirds of them said that requiring a bachelor's degree for a middle-skills role makes the job harder to fill. And three in five admit they reject qualified candidates with relevant experience in favor of recent graduates. They can see the filter screening out people who'd do the job. They keep it anyway.

The incentive math explains it. If a degree-holding hire flames out, nobody gets blamed for the screen. It's standard. If a non-degree hire flames out, the manager who waived the requirement is exposed. So the safe move, every time, is to keep the line in. Privately, the belief holds too: 79% of employers still think a degree signals value for an entry-level worker, and 70% call it a strong indicator of career readiness. Even the ones issuing the press releases.

This is consistency working against you. The boring, repeatable default beats the heroic exception, and the default here is "leave the requirement in and hire the familiar profile."

What actually changed when employers dropped the requirement?

Mostly the wording. The audit that tracked it is brutal.

Of companies that announced skills-based hiring, 45% made no meaningful change to who they actually hired. Another 18% backslid after early gains. Only 37% did the real thing. And among firms that did drop degree requirements, they did it for just 3.6% of their roles. Within those roles, non-degree hiring rose 3.5 percentage points, for a net labor-market shift of 0.14 percentage points.

The posting side shows real motion. The share of US postings on Indeed requiring at least a degree fell from 20.4% to 17.8% from 2019 to 2024, and 52% of postings mentioned no formal education requirement at all. The front door changed. The screening behind it didn't. And by November 2025, roughly 1 in 5 postings (19.3% unadjusted) still required a bachelor's, while the occupation-adjusted share sat at 18.6%, just above its March 2024 low of 18.5% and still below pre-pandemic levels. The loosening that happened under talent scarcity has, at best, leveled off rather than continued.

What changed	What it looked like	What actually moved
Posting language	"Bachelor's required" became "degree preferred" or vanished	Real: degree mentions dropped across most occupations
Hiring outcomes	LinkedIn announcement, press coverage	~0.14 pp net shift across the labor market
The screening layer	"We're skills-first now"	45% changed nothing; 18% backslid

Why does the filter survive after the policy says it's gone?

Three reasons, and none of them are on the job posting.

First, the software. Only about a third of organizations using an applicant tracking system say it recognizes skilled credentials or certifications, even though 45% of employees hold them. So nearly half the workforce carries credentials that most screening tools simply can't read. The posting can say "not required" while the ATS still scores a bachelor's as a bonus and ranks you below it.

Real scenario: A candidate with six years of cloud infrastructure work, multiple AWS certifications, and a portfolio of production systems applies to a role marked "degree preferred, not required." The ATS, still coded to award points for a bachelor's, ranks them under a fresh CS graduate with zero production experience. The recruiter never sees the application. The policy changed. The code didn't.

Second, the human default under time pressure. A hiring manager with 200 applications and a Tuesday deadline reaches for the familiar signal. The degree is a shortcut, and shortcuts win when nobody has time.

Third, the asymmetry already named: the degree-holder who fails costs no one their reputation. The waiver that fails costs someone theirs.

Does dropping the requirement ever actually work?

Yes, when the company rebuilds the machinery, not just the sentence.

Maryland removed degree screens from half of all state roles within 90 days and saw a 34% increase in applicants from workers without four-year degrees within six months of the change. Colorado ran a version of the same play and two years later its non-degree hire rate sat at 25%, roughly flat year over year. Same headline policy, very different traction. Maryland paired removal with active sourcing changes. Colorado changed the rule and largely stopped there.

IBM is the clearest version of doing the work. By 2019, 15 to 20% of its US hires each year were coming in with a "new-collar" background, meaning no traditional four-year degree. The lesson the market took from IBM was "publish a press release." The lesson that actually mattered was that IBM also rebuilt assessments, an apprenticeship pipeline, and hiring-manager training. Competitors copied the announcement. They didn't copy the infrastructure.

This is compounding versus the one-time gesture. The 37% who rebuilt their intake get a sustained pipeline. The 45% who rewrote the posting get a LinkedIn post and the same hires.

The trade-off, said plainly

The degree isn't dead as a filter. It's just dishonest as one. If you have it, it still greases most ATS pipelines and most hiring managers' instincts. That's a real, present advantage, and pretending otherwise helps nobody, even as the degree quietly shifts from a ticket to a toll booth you keep paying for less return.

If you don't have it, the posting language is a trap. "Not required" frequently means "still scored." Betting your application on the stated policy, rather than on the actual screen behind it, is the costly mistake. And the filter genuinely binds in some places: degree requirements still run highest in STEM, finance, and professional-services roles, and licensed or regulated fields map the credential to a real prerequisite. The theater critique hits middle-skills and many white-collar service roles hardest, not all of them.

What to do now

If you have the degree, use it and stop second-guessing it. Put it where the ATS reads it and move on to the parts of your application that actually differentiate you.

If you don't, run a different play than the posting wants you to:

• Get to a human before the ATS decides. A referral, a recruiter DM, a hiring manager on LinkedIn. The credential screen lives inside the software, where most systems can't even read the certifications you do hold. A person can override that. The software won't, which is exactly why referrals are the whole game and the job board is the slow lane.
• Build evidence that makes the credential question irrelevant. A portfolio, shipped projects, role-specific certifications. The signals that predict success (trajectory, specific skills, quality of output) are exactly what a lazy credential screen buries. Surface them yourself.
• Target the 37%, not the 45%. Companies that rebuilt their intake (apprenticeship pipelines, structured skills assessments, named "skills-first" programs with actual hires behind them) are where "not required" is true. Spend your applications there.
• Read "preferred" as "scored." Assume the bachelor's still earns points in the ranking, and compensate with proof and a warm introduction, rather than trusting the disclaimer.

You don't control whether employers fix their filters. You control whether you walk up to the front door the posting describes or the side door the data describes. One of those gets you seen.

Want to know which roles still screen hard on the degree and which ones are theater, mapped against your actual experience? Ask Praxy on WhatsApp. I'll read your real career arc, not your credentials, and tell you where the filter is loose, where it's real, and how to get past it.