Walk through a company's office and you will still find plenty of familiar labels: software engineer, marketing manager, financial analyst, sales director, HR specialist.
At the same time, employers and HR departments increasingly talk about something that sounds very different: skills-based hiring.
The idea is simple enough. Instead of deciding whether someone is suitable for a job mainly from their degree, previous job title or years of experience, employers try to identify the skills the work actually requires and look for evidence that candidates have them.
So are companies really getting rid of job titles?
Not in the way that phrase suggests.
Skills-based hiring is becoming more common, but most organizations aren't simply deleting job titles and replacing them with lists of skills. The bigger change is that skills are being added to the systems that already organize jobs, pay, recruiting and career progression. The job title may still exist, but it is no longer expected to tell the whole story.
That distinction matters because the company's HR software, salary structure and employment records still need a way to describe the position a person holds.
What skills-based hiring actually means
Traditional hiring often uses things such as a degree, previous job title, employer or number of years of experience as clues about what a person can do.
A candidate might have five years of experience as a marketing manager, for example, so an employer assumes that person knows how to manage campaigns, analyze performance data and lead projects.
Skills-based hiring tries to make that connection more direct.
Instead of asking only, "What was this person's previous job?", the employer can ask, "What can this person actually do, and how well can they do it?"
The OECD's 2026 research describes skills-first hiring as putting demonstrated skills at the center of recruitment, while qualifications and experience remain complementary information. It also describes a broader skills-first approach that extends into performance, career development and training. Microsoft made a similar case from the employer's side in a conversation on why job titles matter less in 2026 — and what matters instead.
That is different from saying that job titles have become useless.
A title is still a piece of information. It just isn't necessarily the best description of someone's complete capability.
Why job titles are still hanging around
There is a practical reason companies can't simply throw job titles away.
Organizations have to organize people.
They need to know who reports to whom, which department someone belongs to, what level they occupy, what compensation structure applies to them and which responsibilities belong to their position.
Enterprise HR systems are built around this kind of structure.
SAP SuccessFactors, for example, describes job architecture as a way to standardize job families, roles, responsibilities and descriptions across HR processes including recruiting, performance management, succession and compensation. Its employee systems also use pay grades and salary structures.
So a company can become much more interested in skills without eliminating the underlying job structure. That is exactly the shift workplace reporters have been describing: the future of work is expected to be shaped less by job titles and more by skills, judgment and adaptability — a change in emphasis rather than the abolition of the label.
Think about what happens when a company hires a data analyst.
The employee might have skills in SQL, statistics, data visualization, Python and forecasting.
Those skills tell the company something valuable about the person's capabilities.
But the organization may still need to record that the employee occupies a particular role at a particular level with a particular compensation structure.
The skills describe what the person can do.
The job architecture describes where that person sits inside the organization.
Those two things can coexist.
So what does an ATS do with skills?
This is where the idea becomes much more concrete.
An applicant tracking system doesn't necessarily have to choose between job titles and skills.
Modern recruiting systems can work with both.
LinkedIn's Recruiter tools, for example, allow recruiters to search using skills and identify both explicit skills listed by candidates and implicit skills extracted from profile information. Skills can also be mapped to job postings.
LinkedIn's ATS integrations provide another example. Its Recommended Matches system can use job titles, locations and skills attached to a job requisition when suggesting candidates.
That tells us something important.
The practical version of skills-based hiring isn't necessarily:
JOB TITLE → DELETE
It's closer to:
JOB TITLE + JOB REQUIREMENTS + SKILLS + EVIDENCE
The title remains useful as an organizing label, while skills provide more detailed information about the work and the person. Some HR commentators go further and argue that skills, outputs and micro-roles will eventually replace traditional hiring altogether — but that remains a prediction, not a description of how most systems operate today.
This is also why the idea that ATS software simply "stops looking at job titles" is too simplistic.
A job title can still be useful, even when skills matter more
Consider two people whose official title is "Software Engineer."
One might spend most of the week working on backend systems with Python and databases.
The other might specialize in cloud infrastructure, security and distributed systems.
Their job title is identical.
Their skill profiles aren't.
A recruiter searching only by title could miss that difference.
A recruiter searching only by skills could discover it.
This is one reason skills taxonomies have become useful in large recruiting systems. LinkedIn, for example, standardizes both job titles and skills so different descriptions can be grouped and searched consistently.
A person might call themselves a "Software Engineer," "SWE" or "Software Developer." The system can map those variations to standardized titles while also extracting skills from their profile and experience — the mechanics behind what career analysts mean when they say job titles are becoming less important than skills-based hiring.
The technology doesn't have to eliminate the title.
It can make the title less important as the only signal.
Does skills-based hiring change how people get paid?
This is where the slogan becomes much harder to implement.
If a company says skills matter, somebody eventually has to decide what those skills are worth.
Suppose two employees have the same broad job title.
One has basic data-analysis skills.
The other can build complex forecasting models, automate data pipelines and train other employees.
Should they automatically receive the same pay?
A skills-based compensation system could recognize differences in capability, but it needs rules for doing so.
Companies still need salary ranges, pay grades, job levels or some other method for maintaining a consistent compensation structure.
SHRM has described skills-based pay as a model in which compensation is determined partly by an employee's specific skills and abilities rather than simply their job title or position.
But that doesn't mean every skill receives its own price tag.
In practice, companies can combine skills frameworks with existing job architecture and compensation structures.
That is one reason the transition is complicated.
It isn't enough to say, "We pay for skills."
The company needs a consistent way to define a skill, assess proficiency, determine its value and apply that system fairly across employees.
What happens to promotions?
Traditional careers are easy to visualize.
You start as a junior employee.
Then you become mid-level.
Then senior.
Then perhaps manager or director.
Each step usually comes with a new title, more responsibility and a different salary range.
A skills-first model can make progression more granular.
Instead of looking only at whether someone is ready for the next title, a company can track which capabilities the employee has developed and which ones are still missing.
The OECD describes skills-first talent management as extending beyond hiring into performance assessment, career progression and personalized skills development. Skills frameworks and proficiency levels can be used to support career pathways.
That doesn't necessarily mean promotions disappear.
It can mean that the organization has more information about what qualifies someone for progression.
Someone might develop leadership skills without immediately becoming a manager.
Someone else might become highly specialized without moving into people management.
The traditional ladder can therefore become less rigid without disappearing altogether.
What would a genuinely skills-based organization look like?
This is different from a company simply adding a "Skills" section to its job advertisements.
A more complete skills-based organization would connect several systems.
A simplified version might look like this:
Job structure
What work exists and what level of responsibility does it involve?
↓
Skills framework
What capabilities are needed to perform that work?
↓
Assessment
How does the company know whether someone actually has those capabilities?
↓
Hiring
Which candidates can demonstrate the required skills?
↓
Development
Which skills does each employee need to build?
↓
Career progression
What new responsibilities or opportunities become available as capability increases?
↓
Compensation
How does the organization's pay structure recognize differences in responsibility, contribution and skills?
That is much more demanding than removing a degree requirement from a job advertisement.
The OECD makes this distinction explicitly. Removing degree requirements alone does not create a full skills-first system. Employers also need ways to define skills, assess them and use them throughout talent management.
Is skills-based hiring actually replacing degrees?
Not completely.
This is another place where the public conversation can get ahead of the evidence.
The World Economic Forum's Future of Jobs 2025 report found that employers expected work experience to remain the most common method of assessing candidates between 2025 and 2030. Skills assessments were also expected to be used by 48% of employers surveyed, while 43% expected university degrees to remain a hiring requirement.
So the direction is not simply:
Degrees out, skills in.
It's more like:
Degrees + experience + skills assessments + other evidence
with the relative importance of those signals changing depending on the job.
LinkedIn has also reported an increase in paid job posts that did not require a degree, from 22% in 2020 to 26% in 2023.
That's a meaningful shift, but it still leaves most paid job posts requiring or accepting a degree in some form.
Do certifications matter more than college degrees now?
Sometimes, but there isn't a general rule that certifications have replaced degrees.
A certification can provide evidence of a particular skill. A degree can provide a broader educational foundation. Neither automatically proves that someone can perform a specific job well.
The OECD's 2025 research makes this distinction particularly clear. Skills-first hiring is concerned with what people can demonstrate, regardless of whether those skills came from formal education, informal learning, work experience or other routes. It also discusses micro-credentials, digital credentials and skills assessments as ways of making skills more visible.
The value of a certification therefore depends heavily on what it represents and how relevant it is to the work.
A certificate saying someone completed a course isn't necessarily equivalent to evidence that the person can perform the underlying task.
A work sample, portfolio, assessment or demonstrated experience may provide stronger evidence in some situations.
How do you put a skills-based career on a resume?
You don't necessarily stop listing your job titles.
In fact, removing them can make your experience harder to understand.
A better approach is to make the skills visible alongside the traditional career history.
Instead of:
Marketing Manager, 2022 to present
you might show:
Marketing Manager, 2022 to present
Skills demonstrated:
- Campaign strategy
- Paid search
- Analytics
- Budget management
- A/B testing
- Team leadership
Then provide evidence of what you actually did.
For example, saying that you "managed digital marketing" tells the employer relatively little.
Explaining that you planned campaigns, analyzed conversion data, managed a budget and built reporting systems gives the reader evidence of the skills behind the title.
That fits the direction of skills-first hiring without pretending that your previous job title never existed.
So why are companies having trouble adopting this?
Because skills are harder to standardize than job titles.
"Accountant" is a recognizable category.
"Advanced financial modeling" is more complicated.
How advanced?
Compared with whom?
How was it tested?
Does the person know the theory but lack practical experience?
Can they perform the skill independently?
Can they teach it?
Can they apply it in a completely different situation?
A company needs answers to those questions if it wants to use skills as a serious basis for hiring, promotion or pay.
The OECD identifies skills assessment as one of the major implementation challenges. It also points to the need for common skills language, reliable assessment and systems that allow people to communicate and verify what they can do.
That is the part that often gets lost in the simplified version of the trend.
Replacing the word "job" with "skill" doesn't solve the measurement problem.
What about legal and administrative systems?
This is another reason the job title isn't simply going away.
Employment systems have administrative requirements that aren't solved by a skills profile.
For example, in the United States, the Department of Labor's guidance on overtime classification makes clear that an employee's job title by itself does not determine whether they are exempt or nonexempt. The analysis depends on compensation and actual job duties.
That example is useful because it shows the difference between a title and the underlying work.
A title may be convenient.
The actual duties can matter more.
That doesn't mean a company can throw the title away and run everything from a skills list. It means the title is only one piece of a much larger employment record.
The exact legal requirements also vary by country, so there is no single global HR architecture.
The real change is happening underneath the job title
The most accurate way to describe the shift is not that jobs are disappearing.
It's that the job title is losing some of its monopoly over how companies understand workers.
For decades, a job title could act as a shortcut for almost everything.
It suggested what you did.
It suggested your seniority.
It suggested your department.
It could influence how recruiters interpreted your experience.
It could be tied to your salary structure.
It could form part of your career progression.
Skills-based systems separate some of those functions.
A title can tell you what someone's role is called.
A skills profile can tell you what that person can actually do.
A job architecture can tell you where the role fits.
A compensation system can determine how it is paid.
An assessment can provide evidence of capability.
And a project or work history can show how those skills have been used.
That is a much more complicated system, but it can also describe a person more precisely. It's why career writers now argue that employers are paying more attention to skills, adaptability and impact than to job titles alone — a rebalancing of signals rather than the death of the title.
Verdict: Is it true that companies are throwing away job titles for skills?
Mostly false, if "throwing away" means eliminating job titles entirely.
Mostly true, if it means companies are increasingly trying to make skills more important than titles when deciding who can perform work.
The evidence from the OECD, LinkedIn, WEF and HR technology systems points toward a hybrid model rather than a clean replacement. Skills are increasingly being used in recruiting, candidate matching, assessment, development and career progression, while job architecture, titles, levels and compensation structures remain part of how organizations actually operate.
So the future of work probably isn't a company where nobody has a job title and everyone simply carries a digital list of skills.
It's closer to a company where the title tells you where a person sits, while the skills data tells you what that person can actually do.
And that distinction may end up being more important than the title itself.