If you're hiring for almost any role, you've probably noticed how often the same patterns play out. The job ad lists a title and a number of years. Candidates apply. Many of them have the title and the years, and yet the hires don't always work out the way you hoped. Some of the strongest people you've worked with came from lateral moves, career changes, or non-traditional paths that wouldn't have made it through your current screen.
The mismatch usually isn't that you're hiring badly. It's that the standard hiring process selects on signals that are easy to read but only loosely connected to whether someone can do the work.
The fix is to shift the lens slightly: from 'who has held a similar title before' to 'who has demonstrated the capabilities the role actually needs.' It sounds obvious, and most hiring managers say they already do it. The job ad and the screening process often tell a different story.
What title-based hiring is actually selecting for
When you screen on title plus years of experience, you're selecting for two things: people who've worked at organisations that used a particular job title, and people who've stayed long enough in roles that nominally match. Neither tends to be a strong signal of capability on its own.
Job titles vary wildly across organisations. A 'senior analyst' at one company is doing serious work that includes managing junior staff and shaping methodology. At another, the same title is glorified spreadsheet maintenance. The title alone doesn't tell you what the candidate has actually been doing.
Years of experience is similarly weak as a signal. Two people with five years in the same role can have radically different skill development trajectories: one has been growing the whole time, another has been doing essentially the same thing repeatedly. Years measures duration, not depth.
The hidden cost is who you're filtering out. Career changers with strongly relevant capability that doesn't fit a standard title. Returners after a few years out who don't have continuous title progression. People who've done unpaid or non-traditional work that built exactly the capabilities you need. People from different industries whose work translates more than you'd think. The better hires often live in this group, but title-based screening doesn't see them.
What capability-based hiring looks like
The shift is to write your job ad around what the person needs to be able to do, screen for evidence of those capabilities, and assess them in interview using realistic examples of the work.
Three concrete changes get most of the way there.
Rewrite the job ad in capabilities, not in title and tenure. Instead of '5+ years experience as a customer success manager', write 'We need someone who can build trusted relationships with mid-market accounts, spot churn risk before it becomes urgent, and translate customer feedback into something the product team can act on.' A capable candidate from a different background can read that and recognise themselves; a candidate with the right title but weak capability will struggle to claim it.
Screen on evidence of capability, not on signals of conformity. Replace 'preferred education' and 'preferred years' filters with prompts that surface evidence. 'Tell us about a time you handled an account in serious trouble. What did you do, and what changed?' tends to get you better information than a CV scan, and it works equally well for traditional and non-traditional candidates.
Build the interview around realistic problems. A 30-minute conversation about what someone says they'd do tends to be weaker than a 30-minute structured exercise where they actually do something close to the work. The exercise doesn't need to be elaborate. A short case, a piece of writing, a small problem to talk through. The aim is to see the capability operating, not just hear it described.
What changes about the candidate pool
When you make these shifts, the pool tends to widen in specific directions.
You start seeing candidates with relevant capability who came from adjacent fields. The marketing manager who shifts into product, the teacher who moves into UX, the nurse who moves into operations. Their CVs don't pattern-match the standard hire, but their capabilities often outperform.
You start seeing returners and career changers who'd been screening themselves out. They're often older, more grounded, and bring perspective that pure-pedigree hires don't have.
You also tend to see fewer false positives among the candidates who would have looked perfect on paper. The ones with the right title and the wrong capabilities don't make it as far through the process. That's a feature, not a bug.
The risk people sometimes worry about is volume: won't capability-based hiring mean too many applicants to manage? It can, in the first round. But the screening exercises tend to take less time per candidate than CV review when designed well, and they give you better information. You're trading a high-throughput, low-signal screen for a slightly slower, much higher-signal one.
Where to start
You don't need to overhaul your whole process. The simplest first move is to pick one role you're hiring for now, rewrite the job ad around what the person needs to be able to do, and add one screening question that asks for evidence of one of the key capabilities. Run that pilot. Compare the candidates you get to the ones you would have got with the old version.
Most teams that try this find the candidates they invite to interview look measurably stronger. The follow-on shifts (interview design, screening tools, even how you define seniority internally) tend to follow naturally once the first move pays off.
Hiring for capability rather than title isn't a radical reinvention. It's a small shift in what you're reading the candidate for, applied consistently. The people you want to hire tend to be more visible when you're looking for the right thing.