Skills-Based Hiring Is Growing. But Removing Degree Requirements Is the Easy Part

REMOTE HIRING INTELLIGENCE

An employer can delete “bachelor’s degree required” from a vacancy and still run the same credential-driven hiring process. If recognizable employers, impressive titles and résumé polish continue deciding the shortlist, the wording has changed. The evaluation has barely moved.

Recent employer research shows growing interest in skills-based hiring. The practical question is whether hiring teams can recognize capability once familiar filters are removed.

Skills-based hiring is moving into the mainstream

In NACE’s Job Outlook 2026 findings, 70% of participating employers reported using skills-based hiring, compared with 65% a year earlier. This college-recruiting survey had 183 employer respondents, predominantly NACE members, with responses collected in August–September 2025.

Separate research captures a different measure. In iHire’s September 2026 report, 39.3% of surveyed employers reported giving skills-based hiring greater emphasis over traditional degree requirements. Its survey included 318 employers across 57 U.S. industries.

Meanwhile, WGU’s January 2026 Workforce Decoded release reported that 46% planned to increase their focus on skills over degrees. That national survey involved 3,147 U.S.-based respondents and was conducted in autumn 2025.

These are different populations and questions: reported use, increased emphasis and future intention. Together, they suggest momentum toward capability-focused recruitment. They do not establish that every employer using the label evaluates candidates effectively.

The degree was often doing several jobs at once

A degree can signal subject knowledge, sustained effort and professional preparation. Recognizable credentials also help recruiters process applications quickly. Those are understandable reasons to consider them.

The problem begins when a convenient shortcut becomes the deciding evidence for a capability it does not directly measure. A university name cannot show how someone explains a billing error to a frustrated customer. An unfamiliar qualification does not establish that they cannot.

Employers should identify what a credential is supposed to demonstrate, then decide whether more direct evidence is available. That makes standards more precise while allowing relevant education to retain its value.

Removing a degree requirement changes who can apply. Skills-based hiring changes how you decide.

Start with the work, before applications arrive

Define the outcomes the role will own before rewriting its requirements. A remote support hire might need to resolve customer issues accurately, document decisions and hand work over across shifts.

Then separate requirements deliberately:

• Must have: capabilities needed immediately, plus credentials genuinely necessary for the role.
• Teachable: skills the team has the time and resources to develop after hiring.
• Preference: useful background that should not automatically exclude an otherwise capable person.

These categories depend on the job. One employer can teach its ticketing software; another may need an experienced specialist immediately. The distinction should reflect the work and onboarding capacity, rather than an inherited job description.

Apply the Skill → Evidence → Decision test

For every important requirement, connect a defined capability to evidence and a shared way of judging it.

Written communication: review a relevant, appropriately redacted writing sample and discuss its intended audience. Judge clarity, accuracy and whether the reader can act on it.

Spreadsheet analysis: examine previous work or use a short, realistic exercise. Judge calculation accuracy, assumptions and interpretation, rather than the phrase “advanced Excel” on a résumé.

Remote collaboration: ask for examples of documented decisions and cross-time-zone handovers. Judge how the candidate made ownership, dependencies and next steps clear.

Write the criteria before reviewing candidates. Give assessors a shared description of strong, adequate and insufficient evidence, and ask them to record reasons before discussing the shortlist.

Global job titles and years of experience need context

Across companies, countries and industries, similar work can carry different titles. A startup’s operations lead might own responsibilities divided among several specialists elsewhere. Conversely, identical titles can conceal very different levels of responsibility.

For remote candidate evaluation, ask what someone delivered, what they personally owned and under which constraints. Familiarity with an employer or education system should not substitute for examining that evidence.

Experience remains valuable. Five years in a field offers context, but does not automatically reveal complexity, performance or current capability. A candidate with fewer years should not automatically outrank an experienced colleague because of one strong test result, either.

Duration describes time spent. Evidence helps reveal the depth of that experience. Evaluate both together.

Skills-based hiring should not become endless testing

Replacing a degree filter with five assessments can create another barrier. An exercise adds value only when it addresses an unresolved question about relevant work.

A work-sample test is not mandatory. Existing portfolios, a structured discussion of previous work or relevant qualifications may already provide useful evidence. Where an exercise is needed, explain its purpose, expected time and scoring criteria. Keep it proportionate to the role and hiring stage.

Avoid duplicating tasks across interview rounds or requesting substantial unpaid work. Use fictional or sanitized material, allow candidates to protect confidential information, and communicate any rules about AI assistance before the exercise.

Interview for evidence, then score it consistently

Broad questions invite broad claims. Replace “Are you good at prioritizing?” with: “Describe two important deadlines that collided. What did you prioritize, what did you communicate, and what happened?”

For distributed work, ask: “How did your team coordinate a handover when colleagues were not online together?” Follow up on the candidate’s own actions and the outcome.

Use the same core questions and criteria across candidates, with follow-ups to clarify individual examples. Score the substance of the answer against the role’s requirements. Confidence and presentation can inform relevant communication judgments, but should not stand in for evidence of the work.

Keep legitimate requirements and clearer hiring signals

Professional licenses, regulated qualifications, security requirements, specialized training and genuine senior experience can remain essential. Skills-based hiring calls for understanding why each requirement belongs, rather than removing qualifications indiscriminately.

Remote hiring also needs clear eligibility, location and schedule information. A strong skills match cannot resolve incompatible working hours or a role’s geographic restrictions.

WorkinVirtual’s remote jobs experience surfaces eligible locations, work arrangements and application routes. The broader principle is to organize useful job and professional information so employers can evaluate fit with less repeated decoding, and candidates can explain their capabilities without rebuilding their professional story each time.

That is a direction for better hiring infrastructure: clearer signals, with human responsibility for the decision. AI may assist. Humans decide.