When is a skill not a skill?
How can we expect early talent to know how to navigate a skills-based approach without it being clearly defined?
Ask a careers adviser, a hiring manager and an HR system to define "skill," and you'll get three different, confident answers. That's the problem early talent is being asked to navigate in today's job market, mostly without being told it exists.
Even the academics can't agree
It's tempting to assume the confusion is a workplace problem. That somewhere in the academic literature, "skill," "behaviour," "competency" and "capability" are cleanly defined, and it's only industry that's got sloppy with the language. It isn't true. Competency has been studied formally since the 1970s, and the literature still hasn't converged on a single meaning. A 1982 review of the field concluded there was "no clear and unique agreement about what makes competency". That judgement has aged well with a recent academic survey of the field still counting multiple, sometimes contradictory, scholarly definitions in circulation.
The most influential of them, from management theorist Richard Boyatzis, defines a competency as an "underlying characteristic of an employee". He specifies that it could be a motive, a trait, a skill, an aspect of self-image, a social role, or a body of knowledge, resulting in effective or superior job performance. It doesn't distinguish a competency from a skill. It absorbs the skill into itself, along with five other quite different things, calling the resulting bundle by one word. If the foundational academic model treats "skill" as one ingredient inside "competency" rather than a separate category, it's not surprising that a graduate reading a job advert can't tell which one is actually being asked for.
Broadly, four rough distinctions do recur across the literature and across UK policy frameworks:
Skill — a demonstrable, teachable capability: Excel, coding, financial modelling. Discrete and, in principle, testable.
Behaviour — a tendency in how someone acts, not what they can do: collaborative, decisive, resilient.
Competency — Boyatzis's composite mentioned above: a skill, applied, with the right behaviour and knowledge, in context.
Capability — the vaguest and most strategic of the four, often describing something an organisation wants ("digital capability") that sits above any one person's evidence trail.
The UK's own apprenticeship system has, at least, tried to hold two of these apart formally. Every apprenticeship standard historically approved by the Institute for Apprenticeships and Technical Education (IfATE) was built around Knowledge, Skills and Behaviours (KSBs). "Skill" is defined specifically as "the practical application of knowledge," and "behaviour" defined separately as the "mindsets, attitudes or approaches needed for competence". It's a genuinely useful precedent; a real, statutory UK framework that refuses to let skill and behaviour collapse into each other. But it covered apprenticeships specifically. Most entry-level job specs, degree outcome statements and CVs still use all four words as if they're interchangeable, and nobody tells the graduate that a "capability" being asked for on a job advert might actually need to be evidenced as a "skill" in the application form.
The case for employers borrowing IfATE's language
This is where the KSB model is worth more attention than it usually gets outside apprenticeship circles, and where the picture has actually moved on since apprenticeships were its only use case. IfATE closed as a standalone body on 1 June 2025, and its functions, including the KSB framework and the occupational maps built on top of it transferred into Skills England, the new executive agency now responsible for the UK's skills system. The KSB discipline hasn't disappeared, it's been absorbed into something bigger.
That something bigger is the UK Standard Skills Classification (SSC), which Skills England launched their Version 1.0 in April 2026 and has already updated since, with further revisions expected on a rolling basis. It isn't a rival to IfATE's work, it's built directly on it. The SSC's own development report confirms that IfATE's KSB data was one of the core datasets used to construct the classification, alongside sources like UK job vacancy data and the US O*NET framework. In other words, the same institution now owns both the proven, apprenticeship-tested skill/behaviour discipline and the attempt to scale that discipline into a common language for the whole labour market.
Two details make this genuinely useful for employers rather than just a standalone government process. First, it's free! The SSC is published under the Open Government Licence and accessible through the UK Skills Explorer tool, so there's no cost or procurement barrier to using it. Second, it's open. The underlying classification data can be explored, downloaded and mapped against, rather than sitting behind a vendor's proprietary taxonomy. That combination of a national, IfATE-descended vocabulary that's both free and open removes the excuse for employers who say a common language would be nice in theory, but too expensive or too locked-down to actually adopt. There's nothing stopping a graduate recruiter from mapping their own job specs to the SSC's skill groups and occupational skills today, and letting graduate hiring borrow the same definitional discipline apprenticeships have had for years.
It's worth being honest, though, about how far the SSC has actually got in speaking the early talent industry career dialect specifically. The classification maps well against other established systems. It matched successfully against 100% of the equivalent ESCO skills used across the EU, and 97% of O*NET's US framework. But when it was checked against the skills vocabulary used by the Graduate Futures Institute in its own graduate job profiles, only around 43% matched cleanly. That's a markedly weaker connection than the international comparisons, and it's a telling one. The one classification explicitly built to unify the language of skills across UK education and employment still doesn't fully join up to create a consistent common language. The gap the SSC was designed to close hasn't closed yet, and adoption will be a challenge due to the myriad of skills-based systems in the market for employers.
The graduate market has stopped waiting for the definitions to settle
While the terminology argument sits unresolved, the market it's meant to describe has become considerably less forgiving of getting it wrong. Adzuna's July 2026 figures put UK graduate vacancies at 8,383, the lowest recorded since the firm began tracking the measure in 2016, and a 45.6% fall on the same month the previous year. Competition for what's left has intensified alongside the shrinkage, although there is debate on the validity of the data used, and more specifically, the narrative that often accompanies the data without being able to evidence any causation.
Zoom out further and the trend isn't a blip. Reporting drawing on Adzuna data found entry-level roles (graduate jobs, apprenticeships, internships and junior no-degree-required positions combined) have fallen by 32% across the UK since the launch of ChatGPT in late 2022, with entry-level roles now making up around 25% of the total UK job market, down four percentage points over the same period. Whatever the precise mix of causes, the practical effect is the same; fewer roles, more applicants per role, and a shrinking margin for a graduate to waste effort demonstrating the wrong thing because a job spec's language was ambiguous.
Skills-based hiring is also constrained by whatever the ATS says a skill is
Here's the part of the shift that early talent are least likely to be told about. Skills-based hiring is now the dominant public commitment among UK and global employers. Recent industry research puts the figure at 85% of employers now saying they use it, up from 81% just two years earlier, with over half having publicly dropped degree requirements. Whilst that sounds like a positive move towards a more consistent approach that can be mapped across various entry pathways, employers are not linking it to the government frameworks that are being created.
But skills-based hiring isn't a philosophy applied by a human recruiter reading each application afresh. In practice, it's operationalised through an applicant tracking system (ATS), software with its own built-in skills taxonomy, its own keyword logic, and its own definitions, baked into the vendor's data model of what counts as a match. Unless an organisation actively reconfigures that system to reflect its own internal definitions of skill, behaviour and competency, the ATS's definition wins by default and it is very often still keyword-matching against a resume, not genuinely assessing capability. Research on hidden and overlooked candidates has found that roughly only one in five qualified applicants make it past automated screening.
That means a graduate can do everything right; correctly translate a vague job spec "capability" into a specific, evidenced "skill," phrase it clearly, back it with a real example and still be filtered out before a person ever reads it. The organisation gets to say it does skills-based hiring, but it has never gone through the exercise of defining, classifying and mapping skills to create credible inference. The candidate also has no way of knowing which internal definition, if any, the software behind the application form was actually built around and how skills connect to work.
Nobody has taught early talent how to play the new game
Put the threads together and the shape of the problem is clear. Academically, "skill" has never had a settled definition, and the most cited competency model on record folds it into a complex bundle rather than separating it out. Practically, the framework that does draw a hard line, the KSB discipline now absorbed into Skills England's SSC, is free, open, and increasingly economy-wide, but still hasn't reached most employers' job design. And operationally, even where employers say they're hiring on skills, the software making the first cut is running its own definition, which the candidate can't see and the employer may not have thought to check.
None of that is a reason to expect universities, employers and software vendors to converge on one universal glossary, they're solving different problems and probably always will. But it is a reason to stop assuming early talent can intuit their way through it. Nobody currently tells early talent that "skill" means something different depending on whether they're reading a degree outcome, a job advert, or the taxonomy sitting inside the ATS that will actually screen their application. In a market with fewer graduate vacancies and multiple applicants chasing each one, that's not a small gap to leave unexplained.
So here's the challenge, squarely for employers rather than early talent, if you're going to take a skills-based approach then show your working. That means being explicit, on the job spec itself, about which requirements are skills, which are behaviours, and which are the vaguer "capability" language that's really describing something aspirational rather than something that's demonstrable. It means auditing your own ATS to find out what its taxonomy actually rewards, rather than assuming "skills-based hiring" is the answer. And it means giving candidates something they almost never get; an example of what evidence for a given requirement actually looks like, so they're not left guessing whether a "capability" statement needs a CV bullet, a portfolio piece, or a paragraph of reflection. None of that requires waiting for a national skills classification to mature, because it's already here for any employer willing to map their own language to it. It requires employers to admit that their own interpretation of "skill" isn't self-evident, and to do the courtesy of explaining what they require without ambiguity.
The 43% match rate between the SSC's data and graduate job adverts is a useful reminder of just how much of this burden currently falls on the person with the least power to fix it. A young person navigating today's job market is being asked to translate between several overlapping vocabularies at once; the academic language of their degree outcomes, the employer's job spec language (skill, behaviour, competency, capability, used interchangeably), the ATS's internal keyword taxonomy, and now, potentially the SSC's own classification, which doesn't yet map cleanly at an industry level. Every one of those translation gaps is invisible to the graduate until an application fails for reasons nobody explains. Early talent isn't struggling to navigate a skills-based approach because they lack the skills. They're struggling because the map they'd need to navigate it doesn't fully exist yet and until it does, the people setting the requirements owe candidates more clarity than "we hire on skills" currently gives them.
