A degree requirement is a proxy that bundles several unrelated signals: baseline literacy and numeracy, the ability to finish a long structured commitment, some domain knowledge, and access to higher education. Removing it only improves hiring if you replace the parts you actually needed with something you measure directly.
- A degree bundles four signals. Decide which ones you needed, then measure those specifically.
- Removing the requirement while keeping "degree preferred" in the ad changes nothing except your press release.
- The risk of dropping it badly is that the decision moves to the least structured stage of your process.
- Where a degree is a genuine legal or professional prerequisite, keep it — that is a licence, not a proxy.
- Check whether your replacement measure has better outcomes across groups. Assume nothing.
The degree is doing four jobs at once
This is why the debate goes in circles. "Do we need a degree?" is unanswerable, because a degree requirement bundles four separate signals that happen to travel together:
- Baseline reasoning, literacy and numeracy. Someone got through several years of assessed work.
- Persistence through a long structured commitment. They finished something that took years.
- Domain knowledge. For some fields, specific and genuinely relevant.
- Access. They could get in, get funded, and stay.
The first three are things you might legitimately need. The fourth is not a quality signal at all — it is a record of circumstance, and it is the reason degree screens correlate with family income far more tightly than with job performance.
So the useful question is not "should we require a degree?" It is: which of those four were we relying on, and how would we measure it directly?
What replaces each part
| What the degree was standing in for | What to measure instead |
|---|---|
| Baseline reasoning and numeracy | A short, job-relevant work sample or validated aptitude measure — the same one for everyone |
| Persistence on long work | Evidence of a sustained project: a maintained open-source library, a business run for two years, a long tenure with growing scope |
| Specific domain knowledge | A knowledge assessment on that domain, scoped to what the role uses |
| "Someone else vetted them" | Nothing. This part was never yours, and it was never a measurement |
The fourth row is the important one. A meaningful share of the comfort a degree provides is outsourced judgement — the sense that an institution already filtered. That comfort is not predictive, and giving it up is the actual cost of the change. Teams that do not name this out loud tend to reintroduce it as "we only look at candidates from good companies", which is the same proxy wearing a different hat.
The failure mode: the decision moves, it does not disappear
Here is what usually happens when a degree requirement is removed without a replacement:
- The ad now says "degree or equivalent experience", so reviewers still see education and still weigh it, only now inconsistently.
- Volume goes up, screening time per application goes down, and reviewers lean harder on the fastest available heuristics — employer brand, keyword density, name familiarity.
- The final decision lands in the least structured stage, usually an unscripted conversation.
Net effect: the same or worse outcomes, plus a press release. The decision did not become fairer. It became less legible, which also makes it harder to defend.
This is the general pattern with proxies: remove one without adding a measurement and the weight redistributes onto the remaining proxies, silently. It is worth reading alongside the biases that actually change hiring outcomes.
Where a degree requirement should stay
Keep it where it is a licence, not a signal:
- Statutory or regulated professions where the qualification is a legal precondition to practise.
- Roles where a specific accredited programme is the only realistic route to the required knowledge, and you can say concretely what that knowledge is.
- Client or funding contracts that mandate credentialed staff.
In those cases the degree is not a stand-in for ability — it is part of the job's definition. Say so explicitly in the ad, with the reason. Candidates respect a requirement that comes with a rationale.
Doing it properly, in order
1. Audit your postings. For each degree requirement, write down which of the four signals you were relying on. Several will have no answer. Those are the ones to remove first.
2. Add the measurement before you remove the filter. Not after. The assessment layer is what keeps a wider funnel from turning into a subjectivity festival.
3. Remove education from the evaluation surface. Not just from the requirements list — from what reviewers see while scoring. Instructions to ignore a visible field do not work reliably; withholding the field does. This is the same logic behind blind evaluation.
4. Rewrite the ad around the skill. See how to write a skills-based job description for the phrasing.
5. Measure the outcome of the change. Compare selection rates by group before and after, and compare the performance of the cohort you hired under the new process. If your replacement measure has worse outcomes across groups than the degree screen did, you have swapped one problem for another and need to know that.
How CalHire handles it
The platform has no education field in the evaluation path at all. Candidates declare skills and prove them through one cheat-resistant assessment — a skills test plus a text interview — and the resulting composite score is built from test, interview, and role-fit. There is no résumé-match component and no degree input, because neither ever reaches the scoring surface: identity and background are stripped at an architectural boundary before any model sees a candidate.
A candidate with no degree and a strong verified score outranks a credentialed candidate with a weak one, and the employer sees why. That is not a policy setting someone can quietly relax — it is how the pipeline is built. The mechanics are on the features page, and the candidate's view is on for candidates.
Frequently asked questions
- Is it legal to require a degree?
- In most jurisdictions, yes — but a requirement that screens out protected groups at different rates can attract scrutiny if it is not job-related and consistent with business necessity. That is a well-established principle for selection procedures generally, and it is why "we have always asked for one" is a weak position. Where a degree is a statutory or professional licensing prerequisite, it is a legitimate requirement rather than a proxy. This is general information, not legal advice.
- What actually replaces a degree?
- Whichever component you relied on. For baseline reasoning, a validated work-sample or aptitude measure. For persistence, evidence of a long self-directed project or sustained employment. For domain knowledge, a knowledge assessment. For "someone else vetted them", nothing — that part was never yours and never reliable.
- Will dropping degree requirements increase application volume unmanageably?
- Volume usually rises, which is exactly why the measurement has to come first. A wider funnel with no assessment layer means more resumes read by tired humans, which is the worst of both worlds. A wider funnel with a consistent assessment layer is the point of the exercise.
- Do we have to remove degrees from the application entirely?
- You do not have to, but it helps. If the field is visible to reviewers it will influence them, whatever the policy says. Withholding education from the evaluation surface is more reliable than asking people to ignore it.