Ten years ago I sat across from a candidate with no computer science degree, no bootcamp certificate, and a resume which looked like it belonged to three different people. Warehouse shift lead. Community college dropout. Two years teaching himself to code at night because a friend dared him to build a website for her dog-walking business.
I almost passed on him. The applicant tracking system had already flagged him as a mismatch. His resume didn't match the keywords in the job description, so it never should have reached me at all. It only did because a colleague pulled it out of the reject pile and said "read this cover letter first."
He turned out to be one of the best engineers I ever hired.
This story isn't rare. It's rarely told, because most of us never see the resumes filtered out before a human eye reaches them.
The Degree Was Never the Skill
Here's the uncomfortable part: a computer science degree tells you someone finished a program. It doesn't tell you whether they debug a production outage at 2am, explain a tradeoff to a non-technical stakeholder, or ship something a customer will pay for.
We've known this for years and kept hiring the same way anyway. Degree requirement in the posting. ATS filter tuned to reject anything without it. Recruiter screen asking "where did you study" before "what have you built."
The market is finally catching up to what good engineering managers have known for a while. According to TestGorilla's 2025 State of Skills-Based Hiring Report, 85% of employers now use some form of skills-based hiring, up from 81% the year before. Separately, 53% of employers surveyed in the same report say they've dropped degree requirements outright for roles they used to gate on a diploma.
Over half the market is admitting the degree filter screened out talent instead of screening it in.
Why Leaders Keep the Filter Anyway
If the data says skills-based hiring works, why do so many engineering orgs still lead with "bachelor's degree required" on the job posting?
Three reasons, and none of them are good ones.
It's easier to defend a bad hire when they had the "right" credentials. If a CS grad from a name-brand school doesn't work out, nobody questions your hiring process. If a self-taught engineer doesn't work out, suddenly the whole "we should hire outside the traditional pipeline" experiment gets shelved.
Screening resumes is faster than screening skill. A degree check is binary. A skills assessment takes design, time, and a willingness to sit with someone's actual work instead of their paper trail. Most hiring managers are understaffed and overloaded, so they reach for the fast filter even when they know it's the worse one.
Nobody wants to be the manager who broke the pattern. Hiring outside convention means explaining your decision upward. It's uncomfortable to defend a hire who doesn't look like the last twenty hires on the team, even when your gut (and increasingly the data) says the candidate is stronger.
I get it. I've felt all three pulls myself. None of them hold up when you look at what predicts engineering performance, in practice.
What Predicts a Good Engineer
Not the degree. Not the bootcamp certificate. Not even years of experience, past a certain point.
What predicts a good engineer is whether they take an ambiguous problem, break it into pieces, and ship something which works, then explain their reasoning to a teammate who wasn't in the room. Test for this with a real problem, not a resume line.
Here's what I look for now instead of a diploma:
- A project they built without being told to. Doesn't have to be impressive. Has to be theirs, start to finish. It shows whether they carry something across the goal line without a syllabus telling them what's due next.
- How they talk about a mistake. Ask anyone about a bug they shipped to production. The engineers worth hiring tell you exactly what went wrong and what they changed after. The ones who deflect or vague it out will do it again and hide it.
- Whether they ask good questions in the interview. A candidate who asks about your deployment process, your on-call rotation, or how the team handles disagreement is thinking about the job, not only the offer.
- A real work sample, not a whiteboard puzzle. Give them a small, real problem from your codebase or domain. Watch how they approach it, not only whether they land the "right" answer.
None of this shows up on a resume. All of it shows up in twenty minutes of real conversation or a few hours of real work.
The Business Case, Not Only the Fairness Case
I'll be direct: I'm not making this argument only because it's the fair thing to do, though it is. I'm making it because it's the smart thing to do.
Every qualified candidate filtered out by a degree requirement is a candidate your competitor gets to hire instead. In a market where engineering talent is expensive and hard to find, this is a self-inflicted wound. You're not protecting quality by requiring a degree. You're shrinking your own pool and paying more for what's left in it.
I lead with judgment over rigid filters in my own hiring, and I write about the broader version of this problem, why leaders default to process instead of judgment, at Step It Up HR. Bad hiring processes aren't usually the product of bad intentions. They're the product of managers who never had time to build a better one, so they kept the filter already there.
Where to Start
You don't need to rip up your hiring process overnight. Start smaller.
Pick one open engineering role. Remove the degree requirement from the posting. Replace it with a real work sample or a paid trial project. Track what happens to your candidate pool and your quality bar over the next quarter.
I'd bet you find what I found: the pool gets deeper, not shallower, and the hires get stronger, not weaker.
The warehouse shift lead I almost passed on stayed with the team for six years. He mentored four junior engineers, two of whom also came in through non-traditional paths, because he knew what it felt like to be filtered out before anyone read his cover letter.
Your next great engineer might be sitting in your reject pile right now, flagged by a system which never learned to read for what matters. Go look.