Traditional hiring often begins with filters.
Which degree does the candidate have?
How many years have they worked?
What was their previous job title?
These questions can provide useful information.
But they do not always tell employers whether someone can actually perform the work.
Skills-based hiring focuses more heavily on what candidates can do and whether those abilities match the responsibilities of the role.
START WITH THE WORK
Before deciding what candidates must have, define what they will actually need to do.
Ask:
● What tasks will they perform?
● Which problems will they solve?
● Which tools will they use?
● Which decisions will they make?
● Which skills are essential from day one?
● Which skills can be learned after joining?
This makes the hiring criteria more connected to the real job.
SEPARATE SKILLS FROM CREDENTIALS
Sometimes a credential is genuinely required.
For example, certain regulated professions require specific qualifications or licenses.
But in other roles, employers may automatically request a degree even when the actual work mainly depends on skills.
Ask whether the qualification is:
● Legally required
● Technically necessary
● Strongly useful
● Simply traditional
This distinction can widen the candidate pool.
JOB TITLES CAN BE MISLEADING
The same work can have different titles across organizations.
One company might use:
“Customer Success Executive.”
Another might use:
“Client Relationship Officer.”
Another might call the role:
“Account Support Specialist.”
If recruiters filter only by exact titles, they may miss candidates performing very similar work.
SEARCH FOR CAPABILITIES
Instead of looking only for titles, examine skills.
For example, a marketing role might require:
● Google Ads
● Campaign reporting
● Conversion tracking
● Audience targeting
● A/B testing
● Content optimization
These capabilities may appear across several different job titles.
ASSESS WHAT ACTUALLY MATTERS
If a role requires writing, give candidates an appropriate writing task.
If it requires data analysis, evaluate analytical ability.
If it requires customer communication, examine how candidates respond to realistic customer scenarios.
Relevant assessment gives employers stronger evidence than assumptions based entirely on credentials.
DISTINGUISH ESSENTIAL FROM TRAINABLE
Not every skill needs to exist before someone joins.
Create two categories.
Essential on day one:
● Core technical ability
● Mandatory licenses
● Critical communication requirements
● Safety knowledge
Trainable after joining:
● Internal software
● Company processes
● Internal reporting systems
● Product-specific knowledge
This prevents employers from creating an unrealistic “perfect candidate” profile.
USE STRUCTURED CANDIDATE INFORMATION
Candidate comparison becomes easier when hiring teams review consistent information.
Useful areas might include:
● Skills
● Experience
● Education
● Certifications
● Availability
● Location
● Salary expectations
● Work preferences
● Relevant achievements
Structure makes it easier to compare people based on the requirements that actually matter.
DO NOT IGNORE EXPERIENCE
Skills-based hiring does not mean experience becomes irrelevant.
Experience can show that someone has used a skill in real situations.
The difference is that experience should provide evidence rather than functioning only as a numerical filter.
Instead of asking:
“Does this person have exactly five years?”
ask:
“What level of responsibility have they actually handled?”
YEARS OF EXPERIENCE ARE NOT PERFECT MEASURES
Two candidates may both have five years of experience.
One may have repeated the same limited responsibilities for five years.
The other may have progressively managed larger projects and more complex problems.
Time matters.
But responsibility, outcomes and skill development matter too.
LOOK FOR EVIDENCE OF RESULTS
Ask candidates to show what they accomplished.
Evidence might include:
● Increased sales
● Reduced errors
● Improved turnaround time
● Completed projects
● Process improvements
● Customer results
● Portfolio work
● Technical projects
● Certifications supported by practical work
Results can make skills easier to evaluate.
CREATE MORE REALISTIC JOB REQUIREMENTS
Skills-based hiring can also improve job descriptions.
Instead of writing:
“Five years of experience required.”
you might identify what those five years are supposed to prove.
Perhaps the real requirement is:
● Managing enterprise clients
● Leading a small team
● Building monthly reports
● Working independently
● Handling complex negotiations
Writing the actual capability makes the vacancy clearer.
WATCH FOR UNINTENTIONAL FILTERS
Every additional requirement reduces the candidate pool.
Sometimes that is necessary.
Sometimes it is accidental.
Review whether criteria such as:
● Specific degree
● Specific job title
● Exact number of years
● Experience in one narrow industry
are genuinely required.
Removing unnecessary filters can uncover candidates who would otherwise never reach the shortlist.
KEEP ASSESSMENTS RELEVANT
Skills-based hiring should not mean giving every candidate hours of unpaid testing.
Assessments should be:
● Relevant to the role
● Reasonable in length
● Clearly explained
● Consistent
● Focused on useful evidence
More testing does not automatically mean better hiring.
USE HUMAN JUDGMENT
Skills data can improve hiring decisions.
It should not remove context.
A candidate may have:
● Unusual career experience
● Transferable skills
● International experience
● Freelance work
● Projects outside traditional employment
● Career changes
Good hiring teams consider the complete picture.
FINAL THOUGHTS
Skills-based hiring asks a simple question:
Can this person perform the work?
Degrees, job titles and years of experience can help answer that question.
They should not always be the entire answer.
Start with the responsibilities.
Identify the skills.
Collect relevant evidence.
Then evaluate candidates using criteria connected to the job itself.
Hiring becomes stronger when employers search for capability rather than only familiar labels.