Why Skills-Based Hiring Requires Better Job Analysis From the Start

Why Credential-First Hiring Can Miss Qualified Candidates

Degrees and years of experience became common hiring filters partly because they’re convenient. They provide a quick way to reduce a large candidate pool.

The trouble is that credentials don’t always tell employers exactly what a person can do.

The U.S. Bureau of Labor Statistics reported that a bachelor’s degree was formally required for 17.7% of civilian workers in 2025, while 39.3% worked in jobs requiring a high school diploma. Requirements also vary widely by occupation. For example, bachelor’s degrees were required for 83.9% of fundraisers and 82.9% of marketing managers.

 

Those requirements may be appropriate for some roles, but employers need to ask a more useful question: Which parts of the job genuinely depend on knowledge normally developed through that credential?

A marketing role, for instance, might require the ability to interpret campaign data, write clear copy, manage paid media budgets, use analytics software, and present results to stakeholders. None of those requirements becomes clearer simply by saying the applicant should have a marketing degree.

That’s why the benefits of skills-based hiring depend heavily on how well employers define and evaluate the capabilities tied to performance.

 

Credentials can still provide useful information. The point isn’t that employers should remove every education or experience requirement. It’s that each requirement should have a reason connected to the work.

 

Start With the Work, Not the Candidate Profile

One of the easiest ways to weaken a skills-based hiring effort is to begin by asking, “What type of person do we normally hire?”

That question tends to reproduce the existing hiring profile.

A stronger starting point is: What does this job require someone to accomplish?

Job analysis works backward from the role itself rather than from the background of previous employees.

HR teams can begin by reviewing:

• The tasks performed regularly
• The tasks that carry the greatest consequences if performed poorly
• Tools, systems, software, or equipment used
• Decisions the employee must make independently
• Problems the employee is expected to solve
• Communication responsibilities
• Performance targets
• Knowledge that must be present on day one
• Skills that can reasonably be developed after hiring

That final distinction is particularly useful.

Employers often overload job descriptions with requirements that would be helpful but aren’t actually necessary for entry into the role. A hiring manager might ask for five years of experience because previous employees had five years of experience, not because five years is required to perform the job successfully.

A careful job analysis forces the organization to separate “must have” capabilities from abilities that can be learned through onboarding, coaching, or experience.

 

Translate Job Tasks Into Specific Skills

Once the work has been mapped, the next step is translating tasks into skills.

That sounds simple until teams try to do it.

Consider a recruiter position. Listing “communication skills” as a requirement tells candidates and interviewers very little. The phrase could refer to writing job ads, interviewing candidates, negotiating offers, advising managers, handling rejection conversations, or presenting hiring data.

Each activity calls for a different type of performance.

Instead of broad labels, a skills profile might identify capabilities such as:

• Conducting structured candidate interviews
• Writing clear candidate communications
• Evaluating evidence against hiring criteria
• Explaining compensation and job requirements
• Using an applicant tracking system
• Managing several open requisitions
• Advising hiring managers on candidate evaluation

The same principle applies to technical roles.

Rather than stating that a candidate needs “data skills,” an analyst role might specify spreadsheet modeling, SQL querying, dashboard interpretation, data cleaning, and presentation of findings.

Specificity makes assessment possible.

If employers can describe the skill precisely, they can begin asking how a candidate might demonstrate it.

 

Define Behavioral Competencies Without Making Them Vague

Technical capability is only one part of performance.

Many jobs also require judgment, collaboration, reliability, adaptability, listening, or leadership. These behavioral competencies can belong in a skills-based model, but employers need to describe them through observable actions rather than personality labels.

“Good communicator,” for example, is hard to assess consistently.

“Explains technical information to nontechnical colleagues in clear language” is easier.

“Team player” is similarly broad.

“Shares relevant information with colleagues, responds constructively to feedback, and coordinates work across functions” gives interviewers something more concrete to examine.

This approach also helps reduce the chance that interviewers simply select people who communicate, think, or present themselves like existing team members.

Candidates still have to explain their abilities effectively, of course. Resources offering CV writing tips can help applicants present evidence of their experience and capabilities clearly. Employers, however, have the larger responsibility of deciding what evidence they actually need.

 

Set Proficiency Levels Before You Assess Candidates

Knowing that a skill is required isn’t enough. Employers also need to define how well someone must perform it.

Take spreadsheet skills.

Does the employee need to enter information into an existing workbook? Build formulas? Create financial models? Automate recurring calculations? Review someone else’s work for errors?

Those represent very different proficiency levels.

A useful framework might describe skills as:

Foundational

The person understands basic concepts and can complete straightforward tasks with guidance.

Working

The person can perform common tasks independently and handle routine problems.

Advanced

The person can handle complex situations, troubleshoot problems, and adapt the skill to unfamiliar assignments.

Expert

The person can guide others, design methods or standards, and solve difficult problems that go beyond normal job requirements.

Not every organization needs those exact labels. What matters is having shared definitions.

Without proficiency standards, two interviewers may interpret “advanced Excel” or “strong project management skills” very differently. One might expect pivot tables; another might expect financial modeling and automation.

Clear proficiency definitions also make job architecture and employee development easier because employees can see what progression looks like.

 

Use Outcomes to Check Whether a Skill Belongs

A strong job analysis also connects skills with outcomes.

Ask: What result should this skill help the employee produce?

A salesperson’s CRM knowledge should support accurate pipeline management. A payroll specialist’s regulatory knowledge should contribute to accurate, compliant payroll processing. A customer support employee’s product knowledge should help resolve customer issues effectively.

Linking skills to outcomes prevents skills profiles from becoming long wish lists.

If nobody can explain how a proposed requirement contributes to job performance, it may not belong in the hiring criteria.

This is particularly important as jobs change.

According to the World Economic Forum’s Future of Jobs Report 2025, which includes responses from more than 1,000 employers representing over 14 million workers, employers expect 39% of workers’ existing core skills to change by 2030. The same report found that 63% of employers viewed skills gaps as a major barrier to organizational change.

 

Static job descriptions are poorly suited to that rate of change.

Employers need role profiles that can be reviewed as tools, processes, and responsibilities shift. 

 

Qualifications and Skills Aren’t the Same Thing

Skills-based hiring also requires employers to recognize that qualifications and demonstrated proficiency provide different information.

The OECD notes that roughly 40% of adults across OECD countries hold a tertiary qualification. Yet its literacy and numeracy assessments, which span more than 30 participating countries and economies, show substantial variation between formal educational attainment and tested proficiency.

 

That gap helps explain why credentials shouldn’t always operate as a proxy for capability.

Two candidates with the same degree may perform very differently on the skills required for a job. Likewise, someone without a degree may have developed relevant abilities through work experience, apprenticeships, independent study, military service, certifications, community work, or other paths.

This becomes particularly visible in emerging fields.

A study published in Technological Forecasting and Social Change analyzed about 11 million UK job vacancies posted between 2018 and mid-2024. Demand for AI roles rose by roughly 21% as a share of job postings between 2018 and 2023, while mentions of university education requirements for AI jobs fell by 15%. AI skills were also associated with an estimated wage premium of around 23%.

 

When technologies evolve faster than traditional education pathways, employers may need to pay closer attention to demonstrated ability.

 

Choose Assessments That Match the Job

Once a company knows which skills it wants, the next question is how to evaluate them.

The assessment method should reflect the skill.

If a role requires writing, ask candidates to complete a short writing task. If it requires interpreting data, give them a small dataset and ask what conclusions they would draw. If it involves customer conversations, a structured role-play may reveal more than another résumé screen.

Possible assessment methods include:

• Work samples
• Structured interviews
• Job simulations
• Technical exercises
• Portfolio reviews
• Case exercises
• Skills tests
• Scenario-based questions
• Structured reference checks

Employers should also consider how much assessment is reasonable.

A two-hour unpaid project for an entry-level role may create unnecessary candidate burden. A five-minute generic online quiz may provide too little information. The goal is to collect enough evidence to make a better decision without turning the application process into unpaid work.

Job analysis helps because it tells employers which capabilities deserve assessment and which can be evaluated later.

 

Build Interview Questions From the Skills Profile

Skills-based interviews work best when questions are tied directly to the capabilities identified during job analysis.

Suppose a customer success role requires the ability to manage an unhappy customer while protecting a long-term relationship.

Instead of asking, “Are you good at handling difficult customers?” an interviewer might ask:

“Tell me about a time a customer was unhappy with a result. What did you do, and what happened afterward?”

The interviewer can then evaluate the response against predetermined criteria such as listening, diagnosis of the problem, clarity of communication, judgment, and follow-through.

This produces more useful evidence than relying heavily on conversational chemistry.

Structured scoring also helps different interviewers assess the same skill using the same standard.

 

Let Job Analysis Improve Onboarding Too

The value of job analysis shouldn’t stop when a candidate accepts an offer.

A well-built skills profile can become a starting point for onboarding.

If the company already knows which capabilities a new employee needs, it can assess which ones the person brings and which need development.

That allows onboarding to become more targeted.

A new hire might already possess strong reporting and data-analysis skills but need training on the company’s systems. Another may know the software well but need coaching on stakeholder communication.

Instead of giving every employee the same generic onboarding path, teams can use the role’s skills profile to identify meaningful development priorities.

The same information can later support internal mobility, career development, succession planning, and training decisions.

 

Keep the Skills Profile Current

A job analysis isn’t something an HR team should complete once and store indefinitely.

Roles change.

Software replaces manual steps. Managers redistribute responsibilities. New regulations appear. Customer expectations shift. AI changes how some tasks are completed. A role that required one set of skills two years ago may now require another.

Organizations can review skill profiles during:

• Annual workforce planning
• Performance review cycles
• Major technology implementations
• Team reorganizations
• Changes in regulation
• Recurring hiring difficulties
• Updates to training programs
• Significant changes in business strategy

Hiring data can provide useful signals too.

Are candidates consistently failing the same assessment? Are managers hiring people who technically meet the stated criteria but struggle after joining? Are employees repeatedly being trained on a capability that wasn’t listed in the original job description?

Those patterns may indicate that the job analysis itself needs revision.

 

Skills-Based Hiring Starts Before the Job Ad

Employers sometimes treat skills-based hiring as a recruiting tactic: remove degree requirements, add a few skills to the advertisement, and widen the candidate pool.

The research suggests that approach isn’t enough.

Skills-based hiring works only when organizations can clearly define the work they need performed and identify credible ways for candidates to demonstrate their ability to do it. Job analysis provides that structure.

Start with tasks. Translate those tasks into specific technical and behavioral capabilities. Define the proficiency level required. Connect each skill with a measurable outcome. Then use that information to shape assessments, interviews, onboarding, and development.

Credentials may still have a place, particularly when licenses, formal education, or regulated qualifications are directly tied to the work. But employers shouldn’t use credentials simply because they’re easier to screen.

As skill requirements continue to change, the organizations that build clearer job profiles will be better equipped to recognize talent from a wider range of backgrounds.

Removing a degree requirement can open a door. Good job analysis tells employers who is actually prepared to walk through it.