A recruiter opens a new search for a Senior Machine Learning Engineer.<\/span><\/p>\n The first instinct is familiar: add the exact title, select the location, enter several required technologies and run the search. The results look precise. They also leave out an Applied Scientist who has deployed the same models, a Data Scientist who owns production ML pipelines and an AI Engineer whose company uses a newer title for almost identical work.<\/span><\/p>\n Nothing is technically wrong with the search. Yet some of the strongest candidates may never enter the result set.<\/span><\/p>\n This is becoming a bigger problem in 2026 because work is changing faster than job titles can describe it. LinkedIn\u2019s<\/span> Work Change Report<\/span><\/a> estimates that 70% of the skills used in most jobs will change by 2030. Since 2022, the rate at which LinkedIn members add new skills to their profiles has increased by 140%.<\/span><\/p>\n The title on a profile is still useful. It is simply no longer strong enough to carry the whole search.<\/span><\/p>\n A job title looks like structured data. In reality, it is often a company-specific label.<\/span><\/p>\n A Product Manager at one organization may own discovery, roadmap and commercial strategy. At another, the same title may describe delivery coordination. A Customer Success Manager can be a relationship manager, implementation specialist, expansion seller or all three. \u201cAI Engineer\u201d may mean model development, LLM integration, MLOps, automation or conventional software work with one AI feature.<\/span><\/p>\n The market is also creating titles faster than recruiting taxonomies can stabilize them. Indeed Hiring Lab found in July 2026 that employers across the United States and Europe are<\/span> adding AI to job titles far beyond software and data roles<\/span><\/a>. The title changes first. The shared understanding of what it means comes later.<\/span><\/p>\n Three problems follow.<\/span><\/p>\n Exact-title sourcing assumes that people with the same label perform comparable work. That assumption becomes weaker when companies use different seniority systems, divide responsibilities differently or introduce fashionable titles without changing the underlying job.<\/span><\/p>\n Searching for \u201cGrowth Manager\u201d may return lifecycle marketers, paid acquisition specialists, product-led growth operators and sales-focused business developers. The title alone cannot tell you which version you found.<\/span><\/p>\n Two candidates may have highly similar experience but use different titles because of geography, industry, company size or internal conventions.<\/span><\/p>\n A search for \u201cBackend Engineer\u201d can miss Software Engineers, Platform Engineers, JVM Engineers or Payments Engineers who have the architecture and production experience the role requires.<\/span><\/p>\n A title says where someone sat in an organization. It does not show what they built, improved, owned or influenced.<\/span><\/p>\n Skills-first sourcing looks underneath the title: technologies used, problems solved, environments worked in, business outcomes, scale and progression across roles.<\/span><\/p>\n TestGorilla\u2019s<\/span> State of Skills-Based Hiring 2025<\/span><\/a> found that 63% of employers said finding great talent had become harder, while more than half identified determining whether candidates had the right technical and soft skills as the most difficult part of hiring.<\/span><\/p>\n The market may contain suitable candidates. The search logic may simply fail to recognize them.<\/span><\/p>\n Skills-first sourcing does not mean removing job titles from the search.<\/span><\/p>\n Titles remain useful signals for function, seniority and career direction. The mistake is treating them as hard borders rather than starting points.<\/span><\/p>\n A better search combines:<\/span><\/p>\n The distinction between core and contextual skills is not just a recruiter convenience. The 2026<\/span> TalentCLEF research challenge<\/span><\/a> treats job-person matching and the classification of core versus contextual skills as separate technical problems. Finding a skill in a profile is not the same as understanding how important it is to the role.<\/span><\/p>\n Job descriptions often combine real requirements, team preferences, inherited text and a wish list from several stakeholders.<\/span><\/p>\n Before searching, reduce the role to one sentence:<\/span><\/p>\n This person must be able to do X, in Y environment, at Z level of complexity.<\/span><\/p>\n For a senior backend engineer in payments:<\/span><\/p>\n Design and operate high-throughput backend services in a regulated product environment, with ownership of reliability and production decisions.<\/span><\/p>\n This gives the search a functional center. It is more useful than copying 18 requirements into filters.<\/span><\/p>\n Divide the brief into three groups.<\/span><\/p>\n Core skills<\/b> are required to perform the work. For the payments example, these might include backend system design, production ownership, API architecture and relational data.<\/span><\/p>\n Supporting skills<\/b> improve relevance but can be substituted. Kafka may be useful, but another event-streaming system can indicate the same underlying capability.<\/span><\/p>\n Evidence signals<\/b> show that the skill was applied. Look for migration work, uptime ownership, distributed systems, transaction volume, security requirements or technical leadership.<\/span><\/p>\n This prevents a common error: converting every useful detail into a mandatory condition.<\/span><\/p>\n A title family is a small group of titles built around the different ways the same work appears in the market.<\/span><\/p>\n For the backend example:<\/span><\/p>\n The goal is not to list every possible variation. \u201cSenior Backend Engineer,\u201d \u201cLead Backend Engineer\u201d and \u201cJava Backend Engineer\u201d may already be covered by a broader base title, depending on how the search engine handles matching.<\/span><\/p>\n Build title families around distinct meanings, then let seniority, skills and profile evidence do the remaining work.<\/span><\/p>\n Start with the role outcome, title families and two or three core skills. Review the first results before adding more conditions.<\/span><\/p>\n Then ask:<\/span><\/p>\nWhy job titles are becoming unreliable search boundaries<\/b><\/h2>\n
The same title can hide different capabilities<\/b><\/h3>\n
Different titles can describe the same capability<\/b><\/h3>\n
Titles describe position, not proof<\/b><\/h3>\n
Skills-first sourcing is not title-free sourcing<\/b><\/h2>\n
\n
A five-step skills-first sourcing strategy<\/b><\/h2>\n
1. Start with the work, not the vacancy wording<\/b><\/h3>\n
2. Build a simple skill architecture<\/b><\/h3>\n
3. Create title families, not a title wall<\/b><\/h3>\n
\n
4. Search broadly, then add precision in layers<\/b><\/h3>\n
\n