The traditional hiring process has relied on familiar signals: degrees, job titles, years of experience, certifications, and recognizable employers.
Those signals can still provide useful context.
But they do not necessarily tell you whether someone can actually do the job.
That distinction is becoming increasingly important as organizations deal with changing technology, persistent skills gaps, AI-driven job transformation, and increasingly specialized IT roles.
The shift toward skills-based hiring is no longer just an HR trend. It is becoming a practical response to a labor market where the skills required for a role can change faster than traditional credentials.
The question for employers is no longer whether skills-based hiring is coming.
It is whether your hiring process is actually designed to identify skills.
What Is Skills-Based Hiring?
The short answer is: skills-based hiring evaluates candidates primarily on the capabilities required to perform a job rather than relying on degrees, job titles, or other traditional credentials as automatic filters. It focuses on what candidates can demonstrate, apply, and deliver.
A skills-based approach does not mean ignoring education or experience.
It means putting those credentials in the right place.
For example, instead of asking:
Does this candidate have a four-year degree and five years of experience?
a skills-first process asks:
Does this candidate have the technical, problem-solving, communication, and business skills required to succeed in this role?
That is a fundamentally different question.
And it can produce a fundamentally different candidate pool.
Research from SHRM’s 2025 skills-first research found that relevant work experience and demonstrated skills and competencies ranked as the top factors in hiring decisions, ahead of educational background and interview performance.
Yet there is an important catch.
Many organizations say they are skills-first without actually changing how they hire.
Saying Skills-Based Hiring and Doing It Are Two Different Things
In summary: removing a degree requirement from a job description does not automatically create a skills-based hiring process. The assessment, screening, interviewing, and selection stages must also evaluate candidates based on demonstrated capabilities.
This is where many organizations get stuck.
Changing the wording of a job posting is relatively easy.
Changing the behavior of hiring managers is harder.
A genuinely skills-based process requires organizations to rethink the entire hiring journey:
- How the role is defined
- How the job description is written
- How candidates are sourced
- How resumes are screened
- How interviews are structured
- How technical skills are assessed
- How candidates are compared
- How hiring decisions are documented
The OECD similarly describes skills-first approaches as extending across hiring and broader talent management, including how organizations identify, assess, and develop talent.
In other words, this is not simply a recruiting tactic.
It is a workforce strategy.
Why Skills-Based Hiring Is Gaining Momentum
The short answer is: organizations are turning toward skills-based hiring because traditional credentials can limit access to capable talent while job requirements are changing rapidly.
SHRM’s 2025 research found that 34% of organizations reported often or almost always using skills-first strategies in hiring, while more than half of organizations that rarely or never use them expressed interest in adopting them.
The movement is also being accelerated by technology.
AI is changing the skills organizations need, while simultaneously making some traditional tasks easier to automate.
More than 80% of HR professionals, HR executives, supervisors, and workers surveyed by SHRM agreed that AI will change which skills are valued, and 80% of HR professionals said they expect companies to prioritize AI-related competencies over the next three years.
That creates a problem for traditional hiring.
If the job is changing, a static checklist of credentials may not tell you much about whether someone can succeed in it.
Skills Have a Shorter Shelf Life
A degree can remain on a resume for decades.
A technical skill may become outdated much sooner.
That does not make education less valuable. It means employers need additional ways to determine whether a candidate’s current capabilities match the organization’s current needs.
This is particularly important in IT.
Cloud platforms evolve. Security threats change. AI tools emerge. Development practices shift. Infrastructure becomes increasingly automated.
The ability to learn and adapt can therefore be just as important as what someone already knows.
Why Traditional Hiring Filters Can Miss Good Candidates
In summary: degree requirements, rigid job titles, and narrow experience filters can eliminate candidates before employers ever evaluate the skills that actually matter for the role.
Consider an IT infrastructure position.
A conventional screening process might prioritize:
- A specific degree
- A specific job title
- A specific number of years of experience
- A particular certification
- Experience with a predetermined list of technologies
A skills-first process might instead prioritize:
- Infrastructure troubleshooting
- Cloud administration
- Automation
- Security awareness
- Incident response
- Communication
- Problem-solving
- Ability to learn unfamiliar technologies
The second approach can reveal candidates who would otherwise be screened out.
This matters because skills are acquired in many different ways.
Professionals develop capabilities through:
- Formal education
- Certifications
- Previous employment
- Internal projects
- Self-directed learning
- Military experience
- Contract work
- Volunteer work
- Apprenticeships
- Personal projects
A candidate’s job title does not always tell the full story.
The IT Industry Is Especially Suited to Skills-Based Hiring
The short answer is: IT roles are particularly well suited to skills-based hiring because technical capability can often be demonstrated through practical work, projects, assessments, and problem-solving.
An IT professional can show competence in ways that extend far beyond a resume.
For example:
Software Development
Instead of relying solely on years of experience or a list of programming languages, employers can evaluate:
- Code quality
- Architecture decisions
- Debugging ability
- Testing practices
- Security awareness
- Problem-solving
Cybersecurity
Candidates can demonstrate:
- Incident response
- Threat analysis
- Risk assessment
- Security controls
- Vulnerability management
Cloud and Infrastructure
Hiring teams can assess:
- Infrastructure design
- Automation
- Monitoring
- Troubleshooting
- Cloud architecture
- Disaster recovery
IT Project Management
Employers can evaluate:
- Stakeholder communication
- Planning
- Risk management
- Budget awareness
- Team coordination
- Delivery performance
The point is not to eliminate interviews.
It is to make interviews more useful.
Your Job Description May Be the First Problem
The short answer is: a skills-based hiring process starts with a job description that clearly distinguishes essential capabilities from traditional requirements that may not predict performance.
Many job descriptions become wish lists.
They include every tool the team has ever touched, every certification someone has mentioned, and an experience requirement copied from an older version of the role.
The result can be a position that appears far more restrictive than the actual job.
A better approach is to separate requirements into three categories.
Must-Have Skills
These are capabilities the person genuinely needs on day one.
For an IT role, this could include:
- Specific technical competencies
- Troubleshooting
- Security fundamentals
- Communication
- Project execution
Developable Skills
These are useful capabilities that a strong candidate can reasonably learn after joining.
Not every candidate needs to arrive fully formed.
Nice-to-Have Credentials
Degrees, certifications, and specific platform experience can still matter.
But employers should ask:
Is this credential genuinely necessary to perform the job, or is it simply familiar?
That distinction can dramatically expand the talent pool.
Build the Hiring Process Around Evidence
In summary: the strongest skills-based hiring processes ask candidates to provide evidence that they can perform the work rather than simply claim that they possess the required skills.
This is where the hiring process becomes more rigorous, not less.
Instead of simply asking:
Are you experienced with cloud infrastructure?
ask:
Tell us about a cloud infrastructure problem you diagnosed. What caused it, what did you do, and what was the outcome?
Instead of:
Do you have leadership experience?
ask:
Describe a situation where you had to influence a technical team without having direct authority.
Instead of:
Do you know cybersecurity best practices?
ask:
Walk us through how you would respond to a suspected security incident.
These questions generate evidence.
And evidence is much more useful than a checkbox.
Use Structured Interviews
The short answer is: structured interviews make skills-based hiring more consistent by asking candidates comparable questions and evaluating responses against defined criteria.
Unstructured interviews often reward confidence, familiarity, and personal chemistry.
Those things can matter.
But they are not necessarily indicators of job performance.
A structured interview might evaluate candidates against predetermined competencies such as:
| Competency | What to Look For |
| Technical expertise | Accurate application of relevant knowledge |
| Problem-solving | Logical diagnosis and decision-making |
| Communication | Clear explanation of complex issues |
| Adaptability | Ability to learn and respond to change |
| Collaboration | Ability to work across teams |
| Business judgment | Understanding of organizational impact |
The goal is not to turn hiring into a spreadsheet.
The goal is to create a consistent standard for evaluating people.
Assess Skills Without Creating an Obstacle Course
In summary: skills assessments should replicate meaningful aspects of the job without creating unnecessary tests that burden candidates or measure skills the role does not actually require.
A good assessment answers a simple question:
Can this person do the work?
For an IT position, that might mean:
- Reviewing a piece of code
- Troubleshooting a simulated incident
- Designing a basic infrastructure solution
- Analyzing a security scenario
- Prioritizing competing technical issues
- Explaining a technical recommendation to a nontechnical stakeholder
The assessment should be proportional to the role.
A candidate should not have to spend six hours completing an elaborate exercise simply to prove they can perform a task that could be evaluated in 30 minutes.
Good skills-based hiring is rigorous.
It is also respectful of the candidate’s time.
Don’t Forget the Human Skills
The short answer is: technical capability gets someone into consideration, but communication, adaptability, collaboration, and judgment often determine whether that person succeeds within an organization.
This is especially important in IT.
Technical professionals rarely work in isolation.
They interact with:
- Executives
- Customers
- Vendors
- Project managers
- Security teams
- Finance departments
- Other technical teams
SHRM’s research found that organizations expect AI-driven changes to increase, rather than eliminate, the importance of both technical and power skills.
That matters.
The future IT professional is not simply someone who knows the technology.
It is someone who can use technology to solve problems for people and the business.
Where AI Fits Into Skills-Based Hiring
The short answer is: AI can help recruiters identify and organize skills, but employers still need human judgment to determine whether candidates can apply those skills effectively.
AI can assist with:
- Resume parsing
- Skills extraction
- Candidate matching
- Job-description analysis
- Interview scheduling
- Recruiting analytics
But there is a critical distinction between identifying a skill and validating a skill.
A resume may say someone has Python expertise.
An AI system may recognize Python as a match.
Neither proves that the candidate can solve the actual problem the organization needs solved.
That requires evidence.
It also requires human judgment.
As AI becomes more capable of generating polished resumes, cover letters, and even technical responses, verification becomes increasingly important.
The hiring process should therefore move toward demonstrated capability, not simply better keyword matching.
What a Skills-Based Hiring Process Should Look Like
In summary: a mature skills-based hiring process connects the business need to specific competencies, evaluates those competencies consistently, and uses evidence to make the final hiring decision.
A practical framework looks like this:
1. Define the Business Outcome
Start with the problem the new hire needs to solve.
Do not start with a resume.
Ask:
What will this person need to accomplish six or twelve months from now?
2. Identify the Critical Skills
Translate that outcome into specific technical and human capabilities.
3. Separate Essential From Trainable
Determine what the candidate must already know and what can reasonably be developed.
4. Rewrite the Job Description
Remove unnecessary barriers.
Make the actual skills and outcomes clear.
5. Source Broadly
Look beyond traditional candidate profiles.
Consider people with transferable skills and nontraditional career paths.
6. Screen for Capabilities
Use resumes as evidence, not as the final decision-maker.
7. Validate Through Interviews and Assessments
Ask candidates to demonstrate how they think, solve problems, communicate, and perform relevant work.
8. Evaluate Consistently
Use the same core criteria for comparable candidates.
9. Track Outcomes
Measure whether skills-based hiring actually improves:
- Time to hire
- Quality of hire
- Retention
- Performance
- Candidate experience
- Diversity of the talent pool
10. Refine the Process
Skills requirements change.
Your hiring process should change with them.
What Skills-Based Hiring Means for Staffing Partners
The short answer is: staffing partners have an opportunity to add more value by understanding the client’s actual business need and matching candidates based on skills, experience, culture, and potential rather than simply forwarding resumes.
This is where the philosophy behind The Morton Way becomes especially relevant.
Morton describes its approach as starting with listening: understanding a client’s staffing needs, challenges, company culture, and business goals before searching its talent network. The company also emphasizes that every IT job is different and requires the right people with the right skills.
That distinction matters.
A staffing partner should not simply ask:
Who has the right keywords on their resume?
The better question is:
Who has the capabilities, experience, mindset, and fit to solve this client’s specific problem?
That requires deeper conversations on both sides of the hiring equation.
It means understanding the employer.
And it means understanding the candidate.
Is Your Hiring Process Actually Skills-Based?
In summary: if your organization still relies primarily on degrees, job titles, years of experience, and resume keywords to decide who moves forward, your hiring process may not yet be skills-based.
Ask your hiring team these questions:
- Are we clear about the skills required for each role?
- Which requirements are genuinely essential?
- Which requirements could be learned on the job?
- Can candidates demonstrate their technical capabilities?
- Are interviews structured around defined competencies?
- Do we evaluate communication and problem-solving?
- Are hiring managers using consistent criteria?
- Do we measure quality of hire after placement?
- Are we excluding capable candidates because of unnecessary credentials?
- Are our job descriptions updated as the work changes?
If the answers are mostly yes, your organization is moving in the right direction.
If several answers are no, there is an opportunity to redesign the process.
The Bottom Line
Skills-based hiring is not about lowering the bar.
It is about making sure you are measuring the right bar.
A degree can demonstrate education.
A certification can demonstrate specialized learning.
A job title can provide context.
But none of them, on their own, guarantees that someone can solve your organization’s problems.
The strongest hiring processes go deeper.
They identify the capabilities the job actually requires, give candidates opportunities to demonstrate those capabilities, and evaluate them against consistent criteria.
That approach is especially valuable in IT, where technology and job requirements continue to evolve.
The organizations that adapt will have a significant advantage: a larger talent pool, better visibility into candidate capability, and a hiring process built around what actually drives performance.
The question is not whether skills-based hiring is here.
It is whether your hiring process is ready for it.