A bachelor’s degree used to be the filter. No degree, no interview, whatever you could actually do.<\/p>\n\n\n\n
That filter is coming down. Maryland scrapped degree requirements across thousands of state jobs in 2022 and became the first state to do it. IBM had already stripped them out of roughly half its US postings. Google, Delta, Bank of America, Walmart, all moved the same way.<\/p>\n\n\n\n
One thing worth knowing before you get excited: the job ads changed a lot faster than the hiring did. More on that below, because it’s the part most articles on this leave out.<\/p>\n\n\n\n
Strip out the credential. Ask what the person can do. That’s the whole idea.<\/p>\n\n\n\n
A skills-first posting names the work instead of the diploma. “Can build and ship a REST API” rather than “BS in Computer Science required.” The candidate proves it with a portfolio, a take-home task, a certification, or six years of doing the job somewhere else.<\/p>\n\n\n\n
Degree-based hiring uses education as a proxy. It assumes four years at a university produced someone who can think and finish things. Sometimes true. The problem is what the proxy screens out, which is everyone competent who took a different route.<\/p>\n\n\n\n
Competency-based hiring, if you see that phrase, is the same thing with an HR accent.<\/p>\n\n\n\n
Four kinds of skills get assessed:<\/p>\n\n\n\n
Cybersecurity is the clearest case. More open security roles in the US than credentialed people to fill them, and it’s been that way for years. When you can’t fill the seat, “degree required” stops being a standard and starts being a self-inflicted wound.<\/p>\n\n\n\n
Same in skilled trades, nursing, and data engineering.<\/p>\n\n\n\n
A 2019 computer science graduate learned frameworks half the industry has since replaced. Someone with two years of production experience and an AWS certification is useful in week one.<\/p>\n\n\n\n
The gap is worst where technology moves fastest. Nobody’s degree covered prompt engineering, because that job didn’t exist when the syllabus was written.<\/p>\n\n\n\n
Drop the degree line and the pool widens immediately. For a role costing money every day it stays open, time-to-fill is the number the hiring manager actually feels.<\/p>\n\n\n\n
Degree requirements screen out veterans, career changers, self-taught developers, bootcamp graduates, and a disproportionate share of Black and Hispanic workers less likely to have finished a four-year degree. Removing the requirement doesn’t fix hiring bias. It removes one barrier that had nothing to do with capability.<\/p>\n\n\n\n
Adoption is uneven. It runs fastest where the work is demonstrable and the shortage is real.<\/p>\n\n\n\n
Information technology.<\/strong> Furthest along by a distance. Ship code, show the repo, get the interview. Most software developer roles<\/a> now weigh a GitHub history over a transcript.<\/p>\n\n\n\n Artificial intelligence.<\/strong> The field outran the universities. Published models, Kaggle placings, and fine-tuning work carry real weight in AI hiring<\/a>.<\/p>\n\n\n\n Cybersecurity.<\/strong> Certifications function almost as licenses. Security+, CISSP, OSCP. Employers filling security roles<\/a> often care more about which certs you hold than where you studied.<\/p>\n\n\n\n Digital marketing.<\/strong> Results are public. Campaign numbers, traffic graphs, a site you grew. Hard to fake, easy to check, which is why marketing teams<\/a> went skills-first early.<\/p>\n\n\n\n Healthcare, manufacturing, sales, and customer support<\/strong> license or measure rather than credential. A sales rep’s quota attainment is the entire argument.<\/p>\n\n\n\n Roles where this is most visible: software developer, AI engineer, data analyst<\/a>, digital marketing specialist, and UX designer<\/a>. Each has a portfolio format an employer can inspect in ten minutes.<\/p>\n\n\n\n Quality of hire improves<\/strong> because you tested the thing you needed. Someone who passed a realistic take-home contributes in week two, not month three.<\/p>\n\n\n\n Recruitment costs drop.<\/strong> Shorter cycles, less agency spend, fewer rounds spent discovering someone can’t do the work.<\/p>\n\n\n\n Retention gets better.<\/strong> People hired against a clear picture of the job arrive less often to find it wasn’t what they thought.<\/p>\n\n\n\n Productivity rises<\/strong> for the obvious reason. You hired job-ready.<\/p>\n\n\n\n Innovation benefits from range.<\/strong> A team who all took the same path reaches for the same answer. The bootcamp graduate changes what gets proposed in the room.<\/p>\n\n\n\n Now the caveat this trend needs. Researchers at the Burning Glass Institute and Harvard Business School tracked what happened after companies removed degree requirements from postings. The ads changed. The hiring barely did. Their follow-up work put the real shift at roughly one in every 700 hires.<\/p>\n\n\n\n Read that as a warning, not a debunking. Cutting a line from a job description is easy. Changing what a hiring panel rewards at 4pm on a Thursday is the hard part, and most companies have only done the first one.<\/p>\n\n\n\n More doors, if you can prove the work.<\/p>\n\n\n\n The burden shifted, though. A degree was one credential you earned once. Skills-first hiring asks you to keep proving it, every application. Some find that fairer. Nearly everyone finds it more work.<\/p>\n\n\n\n Define the skills first.<\/strong> Before touching the ad, write down what someone must do in the first 90 days. If the team can’t agree on that list, the posting was never the problem.<\/p>\n\n\n\n Rewrite the job descriptions.<\/strong> Cut the degree line unless the role is licensed. Cut the “5+ years” reflex too. Same proxy, different clothes.<\/p>\n\n\n\n Use assessments that resemble the job.<\/strong> A short coding task against a realistic problem. A case study with a messy data set. Not a four-hour unpaid project, which mostly filters for who has free weekends.<\/p>\n\n\n\n Run structured interviews.<\/strong> Same questions, same order, same rubric for everyone. This is the biggest single change on the list and the one most often skipped, because unstructured interviews feel productive while measuring almost nothing.<\/p>\n\n\n\n Keep evaluating after the hire.<\/strong> Otherwise you’ve hired skills-first into a company that still promotes credential-first, and your best non-traditional hires leave within two years.<\/p>\n\n\n\n AI-powered screening now ranks candidates on demonstrated competencies rather than education fields. Useful, with a real risk attached: a model trained on your last decade of hiring will reproduce your last decade of bias at speed.<\/p>\n\n\n\n Platforms like HackerRank and Codility handle technical screening at volume. Applicant tracking systems parse for skills keywords, which is why your resume needs the words from the posting in it. Digital portfolios do the proving. Certifications from AWS, Google, Microsoft, and CompTIA supply verifiable credentials, most now issuing a badge an employer checks in one click.<\/p>\n\n\n\n Verification is the piece still catching up. Anyone can claim a certification on LinkedIn.<\/p>\n\n\n\n Identifying genuine skills.<\/strong> Claims are cheap. Ask for work samples and verify certifications through the issuer’s badge system, not the resume.<\/p>\n\n\n\n Standardizing assessments.<\/strong> Different interviewers testing different things produces noise you’ll mistake for signal. One rubric, scored independently before anyone talks.<\/p>\n\n\n\n Hiring manager bias.<\/strong> Panels drift back to pedigree under time pressure. Blind the education field on first-pass review and watch what happens to your shortlist.<\/p>\n\n\n\n Internal resistance.<\/strong> Usually from leaders who got their own job through a degree and hear the change as a judgment. Pilot it on two roles and argue from your own retention numbers a year later.<\/p>\n\n\n\n Measuring potential.<\/strong> The genuinely hard one. Past performance predicts well for similar work and poorly for a step up. Nothing solves it completely, and anyone selling a tool that does is selling you something.<\/p>\n\n\n\n Build the portfolio.<\/strong> Three finished things beat twelve abandoned ones.<\/p>\n\n\n\n Get one certification the postings actually name.<\/strong> Read twenty job ads in your target role, count which certs repeat, earn that one. Don’t collect them.<\/p>\n\n\n\n Learn the technical skills narrowly.<\/strong> Depth in what employers are hiring for beats a shallow pass across five tools.<\/p>\n\n\n\n Put numbers on your achievements.<\/strong> “Cut page load from 4.2s to 1.1s” is evidence. “Improved site performance” is a claim.<\/p>\n\n\n\n Fix your LinkedIn headline and skills section.<\/strong> Recruiters search by skill. If the words aren’t there, you’re not in the results.<\/p>\n\n\n\n Contribute to open source<\/strong> if you’re technical. A public, timestamped record of your work and how you take feedback.<\/p>\n\n\n\n Keep the communication side sharp.<\/strong> Technical ability gets you assessed. Explaining a tradeoff to a non-technical stakeholder gets you hired. The blog goes deeper on professional communication skills<\/a> and on building a professional development<\/a> habit that survives month two.<\/p>\n\n\n\nBenefits of Skills-Based Hiring for Employers<\/strong><\/h2>\n\n\n\n
Benefits for Job Seekers<\/strong><\/h2>\n\n\n\n
\n
How Employers Can Successfully Implement Skills-Based Hiring<\/strong><\/h2>\n\n\n\n
The Role of Technology in Skills-Based Hiring<\/strong><\/h2>\n\n\n\n
Common Challenges and How to Overcome Them<\/strong><\/h2>\n\n\n\n
Future Trends in Skills-Based Hiring<\/strong><\/h2>\n\n\n\n
\n
How Job Seekers Can Prepare for Skills-Based Hiring<\/strong><\/h2>\n\n\n\n