Skills-based hiring: what it actually means and how to build a process around it

The degree requirement has functioned for decades as a rough proxy for a set of attributes employers care about: the ability to complete a long-term commitment, some baseline of analytical and written communication skill, and a signal that the candidate could navigate institutional expectations. The problem is that the proxy has degraded significantly as a predictor of job performance while the cost of obtaining it has increased dramatically for candidates.

A Harvard Business Review analysis of degree inflation in the US labor market found that employers were requiring degrees for roles that had been filled successfully by non-degree holders for years, with no evidence that degree holders performed better in those roles. The requirement had become a filtering mechanism by default, not by design. Companies including IBM, Google, and Accenture have publicly moved to drop degree requirements for large portions of their roles specifically because their own hiring data showed credentials were not predicting performance.

What skills-based hiring actually requires

The phrase skills-based hiring is used loosely enough that it has come to mean almost anything. In its most useful form it means: defining the specific competencies a role requires to produce good outcomes, building an evaluation process that generates actual evidence of those competencies in candidates, and making hiring decisions based on that evidence rather than on resume signals that correlate with but do not directly measure the relevant skills.

That is considerably more demanding than removing a checkbox. A degree requirement is easy to screen for. A skills-based process requires hiring managers to articulate precisely what skills the role requires, at what level, and how those skills will be assessed fairly and consistently across all candidates. Most hiring processes have never gone through that exercise, and starting it reveals how often roles are defined by credential and title history rather than by actual function.

The job description is where this becomes visible first. A well-structured job description for a skills-based process names observable competencies rather than credential proxies. Instead of "Bachelor's degree in a related field," it says what the person will actually need to be able to do in the role: analyze data, write clearly for a non-technical audience, manage a project with multiple stakeholders. Those are things you can assess. A degree requirement is a thing you can verify. They are not the same.

Why the shift is happening now

Several forces have converged to make skills-based hiring more viable and more necessary than it was a decade ago.

The skills gap in many industries is real and worsening. Employers cannot find enough candidates with the credentials they historically required for roles that did not actually need those credentials, while simultaneously overlooking large pools of capable candidates who have developed the relevant skills through non-traditional paths. The labor market pressure alone is pushing companies to reconsider what they are actually trying to select for.

LinkedIn's Talent Solutions data shows that skills-first hiring has expanded significantly in recent years, with LinkedIn itself adding skills assessments and skills-based job filters because employer demand for them has grown. The tooling to support skills assessment has also improved: structured assessments, work sample tasks, and job-relevant simulations have become more accessible and easier to integrate into hiring workflows than they were five years ago.

The equity dimension has also become harder to ignore. Degree requirements disproportionately screen out candidates from lower-income backgrounds, candidates who entered the workforce early to support families, and candidates from communities where four-year college attendance has historically been lower. A hiring process that uses skills as the primary filter rather than credentials produces more diverse candidate pools without the legal and reputational risk of diversity programs that modify decisions after evaluation.

How to assess skills instead of credentials

The most predictive skills assessments share a common characteristic: they require candidates to do something that resembles the actual work of the role, rather than talk about it or answer questions about their past experience with it.

Work sample tests, where candidates complete a realistic abbreviated version of a core task of the role, are among the most validated predictors of job performance in the research literature. A writing assessment for a content role, a data analysis task for an operations role, a brief scenario-based problem for a customer-facing role: these generate direct evidence of the relevant skill rather than an inference chain from credential to assumed capability.

Structured behavioral interview questions, when they are designed specifically around the competencies the role requires, also produce useful evidence. The structured interview process is the vehicle for this: consistent questions, consistent evaluation rubrics, and trained interviewers who are scoring responses against defined criteria rather than forming impressions. The combination of a work sample and a structured interview is more predictive than either alone, and more predictive than credential screening plus an unstructured interview by a meaningful margin.

Workstyle assessment is the third component that skills-based hiring processes often add, particularly for roles where the technical skills are assessable but where performance in the specific working environment also depends on fit with how the team operates. A candidate who has the skills but whose working style is misaligned with the role will produce the same outcome as one who lacks the skills: a hire that does not work out and a cost that compounds.

The practical challenges

Skills-based hiring is not simply better. It is more demanding to implement and has real failure modes that companies do not always anticipate.

The first challenge is calibration. When you remove credential signals, the people doing the screening need clearer guidance on what they are looking for. An ATS can filter for degrees automatically. Evaluating whether a work sample demonstrates the required level of analytical skill requires trained judgment. Hiring managers who have not been through that calibration will apply idiosyncratic standards, which reintroduces inconsistency through a different mechanism than credentials did.

The second challenge is candidate experience. Adding a skills assessment step adds time and friction to the process for every candidate, including many who will not get the role. Assessments that are too long, poorly designed, or feel unrelated to the job will be abandoned before completion or will drive candidates to ghost the process entirely. The assessment needs to be directly relevant, proportionate in length to the stage of the funnel, and clearly framed as a demonstration opportunity rather than a test.

The third is that skills-based evaluation requires more hiring manager time upfront, in the process design phase, than credential-based screening does. The investment is worth making because it produces better hires and reduces the cost of a bad hire, but it does not happen automatically. Teams that announce skills-based hiring without building the supporting process tend to revert to credential-based decisions under time pressure.

Where to start

The most useful entry point is not a company-wide policy change but a single role where the hiring manager is willing to do the work of defining skills explicitly and building an assessment for them.

Start by listing the three to five most important things someone in the role needs to be able to do in their first six months, described as observable behaviors rather than credentials or titles. For each one, identify what evidence would convince you that a candidate has this capability. Then build the evaluation process backward from that evidence: what questions, tasks, or observations would produce it?

Run the role with that process, hire someone through it, and measure how the hire performs at ninety days against the competencies that drove the evaluation. That feedback loop is what converts skills-based hiring from a policy statement into an actual organizational capability. The companies that have made it work at scale did not start with a framework. They started with one role, one hiring manager, and honest data about whether the people they hired through the new process performed better than the people they hired through the old one.