Korn Ferry Says 61% Now Do Two Jobs. Title Boolean Just Broke.

Korn Ferry's Workforce 2026 report buried the single most important number for sourcers this year: 61% of workers are now doing the responsibilities of more than one role. If your Boolean string still starts with ("Senior Product Manager" OR "Sr. PM"), you are filtering out the majority of qualified people and calling the remainder a candidate pool.

What Korn Ferry actually found

Korn Ferry surveyed more than 16,000 professionals across 11 countries and found the one-worker-one-job assumption has collapsed across knowledge functions. The workload did not disappear when roles were cut. It got redistributed onto the people who stayed.

The headline numbers from Workforce 2026:

• 61% of respondents are now performing the responsibilities of more than one role.
• 62% report significantly heavier workloads over the past two years.
• 52% of AI users say AI has increased their workload rather than reduced it.
• 44% of U.S. employees report cutbacks in manager levels at their organization.
• Employee motivation fell from 71% in 2024 to 61% in 2026.
• 43% of U.S. managers say they are too busy to deliver meaningful results.

Challenger, Gray & Christmas has flagged AI as the most-cited reason for layoffs every month since January 2026. Korn Ferry's read is the honest one: AI removes some of one person's workload, not all of one person's job. The remainder gets shoveled onto whoever is left. That "whoever is left" is the person you are trying to source, and their LinkedIn title has not caught up.

61%

Why title-based sourcing is now the wrong default

Title-based sourcing gates a search on an exact job title string, usually inside a Boolean expression. It worked when titles described scope. Korn Ferry's data says they no longer do, and Pin's audit of more than 100,000 real recruiter searches shows the industry has not adjusted.

Pin found that:

• 95% of recruiter searches hard-require a job title.
• 91% hard-require a location.
• 89% of searches that name skills leave every single one of them optional.

Read that back slowly. Title is a gate. Skills are decoration. Meanwhile, 70% of employers now claim skills-based hiring is their policy (Recruiterflow), and 71% say they apply it at least half the time. This is the skills-first paradox: the policy has moved, the muscle memory at the search bar has not.

The cost is quantifiable. National University's compiled data puts the pool-expansion effect of dropping title as a hard filter at 15.9x in the U.S. If that number is even directionally right, teams still title-gating are fighting each other for roughly 6% of the market.

The mechanism: title compression, not title inflation

The distortion in 2026 is not that titles got puffed up. It is that titles stopped growing while scope kept growing. A "Senior PM" in 2019 was a Senior PM. A "Senior PM" in 2026 is often doing the work of a Senior PM plus an Engineering Manager plus a data analyst, on the same title and often the same band.

That matters for Boolean strings in two directions:

1. Under-sourcing seniority. You search "Senior PM" and miss the person who was promoted in scope but not in title. Their profile still reads "Product Manager."
2. Mis-routing across functions. You search "Engineering Manager" and miss the Senior Engineer who has quietly been doing EM work for eighteen months since the last delayering, because their title never changed.

With 44% of U.S. employees reporting fewer manager layers, both misfires are now the rule, not the exception. LinkedIn's Green Skills Report showed the same decoupling in a different domain: 53% of green-skilled hires in 2025 went into traditionally non-green job titles. Skills went where the work went. Titles stayed where the org chart put them.

The math on Refolk's PM index

Refolk's index of U.S. professional profiles makes the gap concrete. Roughly 27,600 people in the U.S. hold the exact title "Senior Product Manager" right now. The number who also advertise the analyst or engineering-management work Korn Ferry says they are doing is much smaller.

Two things fall out of this table.

First, only about 23% of U.S. PMs advertise SQL as a skill. If Korn Ferry is right that a majority now do analyst work, roughly three quarters of the PMs doing it are not saying so on their profile. Skill-tag search will not save you either, because they are too busy to update their profile. That is literally what Korn Ferry says.

Second, the hybrid-skill PM population is roughly half the size of the exact-title Senior PM population. That is a lot of candidates to leave on the floor because their title string does not match yours.

This is the exact gap Refolk closes: describe the person in plain English ("PM at a Series C infra company who has clearly been running the roadmap and the SQL for at least two years") and get a ranked shortlist across GitHub, LinkedIn, and the open web. No Boolean, no title cage.

What to source on instead of titles

Source on described work, evidence, and adjacency. Titles become one weak signal among many, not the gate. The swap, one for one:

1. Replace title strings with work descriptions. Instead of "Senior PM" OR "Sr. Product Manager", describe: "owns a roadmap, writes SQL against production data, presents to a VP at least monthly."
2. Replace skill tags with artifacts. Skill tags are self-reported and, per the PM/SQL gap, badly under-reported. Look for evidence: GitHub commits, published RFCs, conference talks, patent filings, dbt PRs, Kaggle notebooks.
3. Replace seniority strings with tenure and scope proxies. "Senior" as a title is noise. Years in role, size of team implied by their posts, and whether they are cited in company blog posts is signal.
4. Replace one-title Boolean with a scope band. For an EM search in 2026, include Staff Engineers, Tech Leads, and Principal ICs at companies that delayered in the last 18 months. Korn Ferry's 44% delayering number tells you which orgs to prioritize.
5. Replace "current title" with "current work." WARN filings, layoff lists, and public reorg posts tell you who is quietly doing three jobs at a company that just cut a layer.

Boolean sourcing filters on the 39% who still have a clean single-role identity and calls it a candidate pool.

Where this hits hardest: PM, EM, and data

The compression is worst in three functions where AI has both cut roles and pushed adjacent work down onto the survivors. If you source into any of them, rewrite your defaults this quarter.

• Product management. PMs are absorbing analyst work (SQL, dashboards, experimentation) and, at delayered orgs, EM work (sprint planning, hiring, one-on-ones). Companies where Refolk sees this concentration acutely include Google, Databricks, Google DeepMind, Klaviyo, and CoreWeave. Search on ownership of a shipped roadmap plus a technical artifact, not on "Senior PM."
• Engineering management. With managerial delayering, the "EM" you want is often a Staff Engineer whose team quietly re-orged under them. Their title says IC. Their week does not.
• Data. Analyst work has been split between PMs, ops folks, and AI. "Data Analyst" as a title string under-samples the population. Look for dbt commits, Looker LookML changes, and internal-tool authorship.

The recruiter behavior gap

The gap between what recruiters say and what they do at the search bar is now the single biggest lever in sourcing. Pin's numbers show it. Korn Ferry's numbers explain why closing it matters more than ever.

• Employers claiming skills-based hiring: 70% (Recruiterflow)
• Employers applying skills-based hiring at least half the time: 71%
• Recruiter searches that hard-require a title: 95% (Pin)
• Recruiter searches leaving all named skills optional: 89% (Pin)

The policy is skills-first. The behavior is title-first. And CEOs still think this is fine: 79% of them claim improved efficiencies from AI, versus about half of the individual contributors actually using it. The people running headcount planning are looking at a dashboard that says "productive." The people doing two jobs are looking at their calendar.

For sourcers, the practical move is to stop treating "current title" as a required field. Treat it as a weak feature in a ranking function. That is a bigger cultural change than a tooling change, which is why most teams will not make it, and why the teams that do will out-source them.

15.9x

FAQ

Is title-based sourcing dead for every role?

No. It still works for tightly scoped, regulated, or credentialed roles where the title genuinely maps to the work: staff nurse, tax attorney, air traffic controller, actuary at a specific level. It has broken down for the knowledge-work majority where Korn Ferry's 61% figure applies: PM, EM, data, marketing ops, revenue ops, most of engineering. Rule of thumb: if AI is plausibly changing the shape of the job, title has stopped being a gate you should trust.

How do I explain this to a hiring manager who still writes "Senior PM, 8+ years" as the intake spec?

Show them the two numbers side by side: 61% of workers doing more than one role, and 95% of recruiter searches hard-gating on title. Then show the pool math from your own tooling. When a manager sees that "Senior PM" returns 27,000 profiles and "PM doing analyst plus roadmap work at an infra company" returns a smaller but qualitatively better set, the intake spec rewrites itself. The conversation is about scope, not titles.

Does dropping title as a hard filter blow up my funnel with unqualified candidates?

Only if you replace it with nothing. The point is not "no filters." The point is that the filter should be described work and evidence (artifacts, tenure, scope proxies) rather than an exact string match on a self-reported title. Ranked shortlists built this way tend to be smaller and more qualified than title-gated lists, not larger and noisier, because described work is a stricter constraint than a title string, not a looser one.

What is the fastest way to test this on a live req?

Take your next open req, run your normal title-gated Boolean, and save the top 20. Then describe the same role in one paragraph of plain English, including the work you actually expect the hire to do in their first 90 days, and run it through a tool that sources on described work. Compare the two top-20 lists side by side with the hiring manager. The overlap is usually under 30%, and the described-work list is usually the one the manager wants to interview.