Job titles are lying to your sourcing search.
Every sourcing search starts with a title, and that is the problem. A job title is often the least reliable field on a modern résumé—and it is the field most recruiting filters trust first.
Wellfound has watched this mismatch widen across 13+ years of hiring data and 100M+ candidate-company connections. The teams hiring best have shifted from searching for what people were called to searching for what they can do. According to Wellfound's data, recruiters who search by skills over titles make 12% better hires.
TL;DR
- Job titles are inconsistent. The same title can mean radically different work across companies, stages, and team structures.
- Skills are closer to the work. Skills, projects, company context, and stage experience are stronger evidence of what a candidate can do next.
- Titles should start a search, not control it. Use them as an initial hypothesis, then expand by skills and context.
- Skills-first sourcing can uncover hidden candidates. Wellfound's data shows recruiters who search by skills over titles make 12% better hires.
Why does title-based search fail in modern hiring?
Because titles stopped describing the work.
Modern teams are flatter and roles are broader. A "software engineer" at a 30-person company might own infrastructure, a product surface, and part of the data stack. Meanwhile, title inflation and title chaos run in opposite directions across companies: one company's "staff engineer" is another's "senior engineer," and "founding engineer" can describe almost anything.
A title query therefore creates two errors at once:
- False positives: candidates whose titles match but whose experience does not.
- False negatives: candidates whose experience matches but whose titles never said so.
You pay for the first error in screening time. You pay for the second in qualified candidates you never see.
What is skills-based hiring?
Skills-based hiring evaluates candidates using evidence of what they can do—not just degrees, credentials, or previous job titles.
For sourcing, that means looking beyond a title match and asking more useful questions:
- What systems, products, or workflows has this person likely worked on?
- Which skills transfer to the outcomes required in this role?
- What company stage and team environment have they experienced?
- How selective were the teams they joined?
- Which adjacent titles could describe the same underlying work?
This is why skills-based hiring is more than adding a self-reported skills filter. The goal is to evaluate the work behind the label.
What does the data say about skills-first hiring?
The headline result is clear: recruiters who search by skills over titles make 12% better hires, according to Wellfound's data.
That result makes sense when you view a title as a lossy compression of experience. A title reduces years of projects, responsibilities, teammates, technologies, and business context to two or three words. Skills are closer to the actual work, and the work is what transfers to the next role.
The labor market makes this even more important. New-grad hiring is down 30%+ from pre-pandemic levels while companies prioritize seasoned builders. Experienced generalists are exactly the candidates whose titles compress worst because they have done more than any single title can hold.
How do you search by skills when résumés do not list them?
The practical answer is to infer skills from context.
Candidates describe their skills inconsistently, and a self-reported skills section is marketing—not measurement. The stronger signals often sit outside the résumé.
Across 500M+ enriched profiles, Wellfound infers skills using context such as:
- Teammate data: what the people around a candidate were building can reveal the work they were likely doing.
- Company categories: experience at an infrastructure company implies different technical muscles than experience at a marketplace.
- Company stage at the time of employment: building at seed stage can require a different operating range than working inside a mature organization.
- Hiring-bar signals: the selectivity of prior teams adds context about the environments a candidate has passed through.
No single signal proves fit. Together, they help recruiters form a much richer hypothesis than a title alone—and they can be applied across an entire pipeline in a way manual research cannot.
What does a skills-first sourcing search look like?
It looks like running several hypotheses about experience instead of one query about titles.
On Wellfound Reach, multiple sourcing agents can test different angles for the same role:
- One searches for a target skill profile across adjacent titles.
- One looks for alumni of companies that built similar systems.
- One targets candidates with experience in the company categories relevant to the role.
- One emphasizes stage experience or hiring-bar signals.
The candidates surfaced by these searches are often the candidates conventional title filters miss. Adonis's Head of Recruiting saw candidate quality outperform agencies within two weeks, including candidates no conventional search would have uncovered. Xander continuously refined its criteria against a highly selective bar and found two viable candidates in under six weeks.
How can recruiters build a skills-first sourcing workflow?
Start with the role's outcomes, then work backward to evidence.
- Define the outcomes. Write down what the new hire must accomplish in the first 6 to 12 months.
- Translate outcomes into skills. Identify the technical, functional, and operating skills required to deliver those results.
- List adjacent titles. Brainstorm the different titles that could contain the same work across industries and company stages.
- Add context signals. Use company category, company stage, team history, and hiring-bar data to sharpen the search.
- Run parallel hypotheses. Test several skill and context combinations instead of forcing every candidate through one Boolean query.
- Refine from evidence. As strong candidates emerge, update the search criteria around what actually predicts fit.
This approach makes sourcing iterative. Each promising candidate improves your understanding of the market and the role.
Should recruiters stop using job titles entirely?
No. Job titles are a useful starting hypothesis and a terrible final filter.
Use titles to seed a search, then let skills, stage experience, and team context decide who belongs in the pipeline. The discipline is refusing to let the easiest field in the database become the gatekeeper for the hardest decision your company makes.
Frequently asked questions
Are job titles still useful in recruiting?
Yes. Titles are useful for forming an initial candidate pool, but they should not be used as the sole qualification filter. Expand the search using skills, outcomes, adjacent titles, and company context.
What makes a skills-first search different from keyword search?
Keyword search looks for words a candidate explicitly wrote. Skills-first search looks for evidence in the candidate's work history, teammates, company category, stage experience, and prior hiring environments.
What is the biggest benefit of skills-based sourcing?
It helps recruiters find qualified candidates who would be excluded by rigid title filters. That means fewer false negatives and a broader, more relevant talent pool.
How can a small recruiting team search by skills at scale?
Use parallel sourcing agents to test different skill and context hypotheses for the same role. Wellfound Reach applies inferred skills, company-stage experience, and hiring-bar signals across 10M+ opted-in candidates and 500M+ enriched profiles.
The takeaway
Titles are labels; skills are evidence.
The 12% hiring advantage goes to teams that search the evidence. The practical path is enrichment: inferred skills, company stage at the time of employment, and hiring-bar signals built from Wellfound's 13+ years of hiring data.
Your next great hire's title probably does not match your search. Their work does.