Skip to content
← All notes

Your job title matters less than your skills now, and hiring is catching up slowly

Roles are being unbundled into capabilities faster than job architectures can describe them, which is why the title on your contract explains less about what you do every year.

Careers7 min read

Two people with the same title at the same company now do measurably different work, and the gap is widening. One has absorbed three adjacent capabilities because the tools made it possible; the other has not.

The title did not change for either of them. It describes a bundle of tasks that stopped being bundled.

Why roles are unbundling

A job title is a shorthand for a group of tasks that used to make sense together, usually because they needed the same training or the same tools. Designers designed because design tools were hard. Analysts analysed because analysis was slow.

When the cost of a task collapses, its grouping stops being economic. A product person can now produce a working prototype, a designer can pull their own data, an engineer can write the customer-facing copy. None of them became a different profession. The boundaries just stopped being where they were.

What is left of a role is the part that still requires accumulated judgement, and that part is much narrower and much more specific than the title suggests.

A job title as a bundle of tasks that used to belong together because they needed the same tools, coming apart as the cost of each individual task collapses.
The title did not change. The bundle it describes did.

The practical consequence for your career

If your professional identity is the title, every one of these shifts feels like an attack. If it is a set of capabilities, they are opportunities to add one.

It also changes what to optimise for. A promotion that adds seniority to a shrinking bundle is worth less than a sideways move that adds a capability the market is short of. The title looks better on paper and the second one compounds.

  • Describe yourself by what you can do rather than what you are called. It is more accurate and it travels between companies.
  • Track capabilities you have evidence for, not ones you have been exposed to. Exposure is not capability and the difference shows up in an interview.
  • Look for the capability gap next to your current work rather than the next rung of the same ladder.

Hiring has not caught up, and that is a real problem

Most hiring still filters on titles and years, because those are cheap to filter on. This produces the familiar outcome where somebody who can obviously do the job is screened out for not having held its name before.

It is worse now, because the correlation between title and capability is weaker than it was. A filter that was rough five years ago is close to noise today, and every organisation using it is competing for a smaller pool than it thinks while rejecting people who can do the work.

The organisations that get ahead here will be the ones that assess capability directly. That is more work than reading a CV, which is exactly why it is an advantage.

A hiring filter built on titles and years of service screening out somebody who can plainly do the work, while the correlation it relies on gets weaker every year.
A filter that was rough five years ago is close to noise now.

Common questions

Are job titles becoming irrelevant?
Not irrelevant, but much less informative. A title still signals seniority and rough territory. It no longer reliably tells you what somebody can actually do, because the task bundles titles describe have been broken apart by tools that made individual tasks cheap.
What is a skills-based career?
Building and describing your working life as a set of demonstrable capabilities rather than a sequence of job titles. In practice it means tracking what you can do with evidence, choosing moves that add capabilities rather than only seniority, and presenting yourself by what you can do.
How do I present skills instead of job titles on a CV?
Lead with what you did and what happened as a result, not the role name. Attach evidence where you can: something you built, a decision you made and its outcome, a problem you were handed and what changed. Titles become context rather than the claim.

PDP Quest exists because of the problem underneath all of these: when output stops indicating capability, you need another way to know who can actually do the work.

See how verification works →