Newthistle consulting logo
Frameworks
ReSCUED
PACE
Newthistle consulting logo
Frameworks
ReSCUED
PACE

Menu

Newthistle consulting logo
The letters CV in white on a black background.

Category: General

The Fallacy of "X Years of Experience" in Job Postings

Are we stuck in an outdated hiring paradigm?

I recently came across a study that reinforced my dislike of one of the most common requirements in job postings: "X years of experience." This statement is often meaningless and not helpful for finding the right candidate. Why? The number of years in a role is not an indication of expertise.

Research shows that after the initial learning curve, many professionals don't significantly improve their skills just by accumulating more years on the job. What matters is the quality of that experience and continuous learning. Orlando Bloom, in a recent TV show, Learned to fly a wingsuit. This usually takes at least 200 jumps and many months of practice. Bloom did it in two months.

How do you think that the mechanic with 20 years of experience working on classic cars, would fare if asked to service the complex supercars of today?

Expertise is about Pattern Recognition. True experts don't just have more time in a field; they've developed superior pattern recognition through deliberate practice and feedback. For some, this can happen in 2 years; for others, it never happens even after 20 years.

Strict year requirements can exclude talented individuals who may have gained equivalent skills through non-traditional paths or intensive, quality experiences in less time.

In many industries, especially tech, the landscape changes so quickly that someone with fewer years but more recent, relevant experience might be better suited for a role.

Sometimes, fresh perspectives from those with less traditional experience can drive innovation and new solutions.

Instead of asking for "X years of experience," what if we focused on:
Demonstrable skills and achievements
Problem-solving abilities
Adaptability and learning capacity
Relevant project experience

It's time for our hiring practices to evolve to match the dynamic nature of modern work.

#Hiring #TalentAcquisition #WorkforceDevelopment #HR

Are we stuck in an outdated hiring paradigm?

I recently came across a study that reinforced my dislike of one of the most common requirements in job postings: "X years of experience." This statement is often meaningless and not helpful for finding the right candidate. Why? The number of years in a role is not an indication of expertise.

Research shows that after the initial learning curve, many professionals don't significantly improve their skills just by accumulating more years on the job. What matters is the quality of that experience and continuous learning. Orlando Bloom, in a recent TV show, Learned to fly a wingsuit. This usually takes at least 200 jumps and many months of practice. Bloom did it in two months.

How do you think that the mechanic with 20 years of experience working on classic cars, would fare if asked to service the complex supercars of today?

Expertise is about Pattern Recognition. True experts don't just have more time in a field; they've developed superior pattern recognition through deliberate practice and feedback. For some, this can happen in 2 years; for others, it never happens even after 20 years.

Strict year requirements can exclude talented individuals who may have gained equivalent skills through non-traditional paths or intensive, quality experiences in less time.

In many industries, especially tech, the landscape changes so quickly that someone with fewer years but more recent, relevant experience might be better suited for a role.

Sometimes, fresh perspectives from those with less traditional experience can drive innovation and new solutions.

Instead of asking for "X years of experience," what if we focused on:
Demonstrable skills and achievements
Problem-solving abilities
Adaptability and learning capacity
Relevant project experience

It's time for our hiring practices to evolve to match the dynamic nature of modern work.

#Hiring #TalentAcquisition #WorkforceDevelopment #HR

More Posts

May 12, 2026

Your AI ROI Is Probably Wrong

Headline savings, systemic drag, and the calculation that decides what your company is actually worth in eighteen months

May 6, 2026

The Unit of Value Problem

Every AI deployment rests on a hypothesis, usually implicit, that the process being automated produces something worth producing. The business case says: this currently costs X in labour; AI can do it for Y, where Y is less than X; therefore deploy. That calculation contains a buried assumption that almost no one examines.

May 2, 2026

When AI Arrived Before Management Did

Boards want the optics. CEOs want the announcement. Neither wants the unglamorous work that has to happen first. So they skip it, sign the cheque, and act surprised when the wheels come off six months later.

May 12, 2026

Your AI ROI Is Probably Wrong

Headline savings, systemic drag, and the calculation that decides what your company is actually worth in eighteen months

May 6, 2026

The Unit of Value Problem

Every AI deployment rests on a hypothesis, usually implicit, that the process being automated produces something worth producing. The business case says: this currently costs X in labour; AI can do it for Y, where Y is less than X; therefore deploy. That calculation contains a buried assumption that almost no one examines.

May 12, 2026

Your AI ROI Is Probably Wrong

Headline savings, systemic drag, and the calculation that decides what your company is actually worth in eighteen months

NeWTHISTle Consulting

DELIVERING CLARITY FROM COMPLEXITY

Copyright © 2026 NewThistle Consulting LLC. All Rights Reserved

NeWTHISTle Consulting

DELIVERING CLARITY FROM COMPLEXITY

Copyright © 2026 NewThistle Consulting LLC. All Rights Reserved

NeWTHISTle Consulting

DELIVERING CLARITY FROM COMPLEXITY

Copyright © 2026 NewThistle Consulting LLC. All Rights Reserved