Hire for skills. For most roles, what a candidate can actually do predicts performance far better than where they went to school, and a blanket degree requirement quietly deletes qualified people from your shortlist before you ever meet them. Degrees still matter where the law or the licensing body says they do. Everywhere else, treat the diploma as one data point, not a gate.
Updated August 2026.
What is skills-based hiring?
Skills-based hiring is a method of evaluating candidates on demonstrated ability — what they can do, what they have already done, and what they can prove in an assessment — rather than on the credentials they happen to hold. The degree does not disappear from the file. It stops being the thing that decides whether anyone reads the rest of the file.
In practice that means a job posting that lists capabilities instead of qualifications, a screening step that tests those capabilities, and an interview built around work the person has actually produced. It is a change to your filter, not a change to your standards.
What is the real difference between skills-based hiring and degree-based hiring?
The difference is where the evidence comes from. Degree-based hiring accepts a credential as a proxy for competence and screens people out early on that basis. Skills-based hiring asks the candidate to demonstrate competence directly and screens people out on the demonstration. Same goal, opposite order of operations.
| Degree-based hiring | Skills-based hiring | |
|---|---|---|
| What gets screened first | Education field on the resume | Demonstrated ability and relevant work |
| Size of the talent pool | Narrow, and narrows further every year | Wider, including career changers and self-taught candidates |
| Main evidence used | A credential earned years ago | A work sample, test or portfolio produced now |
| Typical failure mode | Hiring someone qualified on paper who cannot do the job | Hiring someone capable now who lacks long-term theory or depth |
| Effort required from you | Low up front, high after a bad hire | Higher up front, lower after |
| Best suited to | Licensed and regulated professions | Sales, trades, operations, marketing, support, most technical work |
Why are more employers dropping degree requirements?
Employers are dropping degree requirements because they cannot fill roles and the degree filter is removing people who could do the work. That is the whole reason. It is not a social project and it is not a hiring fad. When a business has an open seat costing it revenue every week, and its own posting is rejecting candidates who have done the exact job elsewhere, the requirement stops looking like a standard and starts looking like a self-inflicted wound.
Running CPG Recruitment since March 2020 across 25-plus industries in Canada and the US, the pattern is consistent. The roles that stay open longest are almost always the ones with a requirement nobody can justify when you ask them to. I ask clients one question about every line in the requirements section: what happens if a candidate does not have this? If the answer is “nothing, really,” it is not a requirement. It is a habit.
Removing those habits is also the cheapest speed you will ever buy in hiring. Tightening what a role actually needs is a large part of how we cut average time-to-fill from 68 days to 37.
Which roles still require a degree?
Roles still requiring a degree are the ones where a licensing body, a regulator, an insurer or a client contract demands it. Those requirements are not yours to remove. Everything else is negotiable.
- Keep the requirement for licensed professions: medicine, nursing, law, professional engineering, accounting designations, pharmacy, and any role where the credential is the legal permission to practise.
- Keep it where a customer contract, government tender or insurance policy names the credential in writing.
- Replace it with a skill test for most technical, operational, administrative and creative roles.
- Drop it entirely in sales, customer success, skilled trades, warehouse and logistics leadership, and most first-line management. Track record beats coursework in every one of these.
- Convert it to “degree or equivalent experience” when you genuinely want the theory but do not need the paper. Then define what equivalent means before you post the job, not after a candidate argues for it.
How do you assess skills without a degree to lean on?
You assess skills by making the candidate do a small, real version of the job and judging the output against a standard you wrote down before you saw it. A degree is a shortcut that lets you skip this. Take the shortcut away and you have to build the assessment, which is exactly the work most hiring processes have been avoiding.
- Write the scorecard first. Three to five capabilities the role genuinely requires, each with a description of what good looks like. If you cannot write it, you do not know what you are hiring for yet.
- Give a work sample, not a homework assignment. Thirty to sixty minutes, paid if it goes longer, drawn from something the role does weekly. A sales candidate handles an objection live. An operations candidate fixes a broken schedule.
- Ask structured behavioural questions. Same questions, same order, every candidate. “Walk me through the last time you did this” surfaces more than any hypothetical.
- Check references on the specific skill. Not “was she good” — “how did she handle the quarter when the numbers were down?”
- Score independently, then compare. Every interviewer commits to a number before the debrief. It kills the loudest-voice-wins problem.
Most of this fails at step one, which is why writing a job description that attracts the right candidates is worth more attention than the interview stage that follows it.
What are the risks of skills-based hiring?
The main risk of skills-based hiring is that you remove the degree filter and put nothing in its place, which leaves you with a bigger pile of applicants and no better way to sort it. That is not skills-based hiring. That is just an open door.
The second risk is testing for the job as it exists today and ignoring where it goes in two years. Somebody can be perfectly capable in the role now and have no foundation to grow into the next one. Ask about the trajectory, not just the current capability.
The third is volume. Wider pools mean more applications and more screening hours, and unprepared teams respond by slowing down. A slow process loses the good candidates first, which is a problem worth understanding before you widen anything — see why a slow hiring process costs you the best people.
How do you rewrite a job posting for skills-based hiring?
Rewrite the posting so every line describes something the person will do or must be able to do, and delete every line that describes a category of person. “Bachelor’s degree required” is a category. “Can build a weekly production schedule for a 40-person floor” is a skill. Swap one for the other and the quality of your applicant pool changes within a week.
Two more edits worth making at the same time. State the salary range, because candidates who are strong enough to be picky will not apply blind. And name the first ninety days explicitly: what this person delivers by day 30, day 60, day 90. Serious people read that section and self-select. The rest never make it to your inbox, which is the point.
If your postings keep pulling the wrong people, the requirements section is usually the culprit. It is one of the most common hiring mistakes employers make, and one of the few that costs nothing to fix.
Frequently Asked Questions
Does skills-based hiring lower the quality of your hires?
No, as long as you replace the degree filter with a real assessment. Quality drops when you remove a screen and add nothing back. It rises when you swap a proxy for direct evidence, because you are now judging the candidate on the work instead of on a credential earned years before the job existed.
Do I have to remove degree requirements from every job posting?
No. Keep the requirement anywhere a licensing body, regulator, insurer or signed client contract demands the credential. Review every other posting one line at a time and ask what actually happens if a candidate does not have the degree. If the honest answer is nothing, remove it.
How does skills-based hiring affect salary expectations?
Pay for the role, not for the resume. If you set the range by what the work is worth to your business and hold it for everyone, skills-based hiring does not change your compensation structure at all. If you have been quietly paying degree holders more for the same output, it will expose that, and you should fix it before a candidate does.
Will my applicant tracking system still filter out candidates without degrees?
Yes, if you leave the old knockout rules switched on. Most teams edit the job posting and forget the system underneath it, so the ATS keeps rejecting the exact people the new posting was written to attract. Audit your knockout questions and required fields the same day you change the posting.
Getting this right takes an honest look at what your roles genuinely require, and most teams are too close to their own job descriptions to see it. That is the conversation we have with clients every week. Contact CPG Incorporated and we will go through your open roles line by line and tell you which requirements are real and which ones are costing you candidates.