You're Not Searching for "A Job." That's the First Problem.
- Susan Morrow
- Dec 26, 2025
- 6 min read
Updated: Jan 18
What should you search for when looking for a job?
Most people default to job titles: "marketing manager," "data analyst" or "project coordinator." That's the obvious starting point. It's also where the problems begin.
Titles are abstractions. They collapse wildly different work into the same label and use different labels to describe the same work. If you're searching by title alone, you're working with broken categories. That's the reason qualified people miss relevant opportunities and waste hours scrolling through roles that were never a fit.
Why don't job titles map to actual work?
A "Project Manager" in construction manages physical builds, coordinates subcontractors and navigates permit timelines. A "Project Manager" in software runs sprints, writes user stories and manages backlogs. A "Project Manager" in healthcare oversees system implementations, trains staff and manages vendor relationships. The skills overlap slightly. The day-to-day work is entirely different.
The reverse problem is just as common. Someone handling payroll, benefits and HR administration might be titled "Office Manager," "Administrative Coordinator," "HR Generalist," "Accounting Assistant" or "Operations Specialist" depending on which aspect of the work the employer emphasized. At a small company, one person does all of it. At a larger company, there might be dedicated teams for each function. The title gives you no reliable signal about the actual scope of the role.
But the problem runs deeper than titles. Job descriptions use mismatched language too. Job search engines check for keywords throughout the posting, not just in the title. That should help. It doesn't, because keywords have the same problems as titles.
Search for "client relationships" and you'll miss postings that say "account management," "customer success," "stakeholder engagement" or "partnership development." Those can be synonyms, but job search engines treat them as different things. You have to guess which term the employer chose.
Keywords also mean different things in different contexts. "Project coordination" in event planning means vendor management and logistics. "Project coordination" in software means sprint planning and backlog grooming. Same phrase. Completely different work.
Job search engines can find every document containing the words you typed. They can't tell you which role actually matches your background or your desired role. They just match text strings.
Why are job titles getting more confusing?
Yesterday's labor market categories are being forced onto today's reality. Job classifications were built for an economy where roles stayed stable for decades. That economy no longer exists. World Economic Forum research indicates that 39% of key skills required in jobs will change by 2030. Emerging skills and new roles get misclassified because they don't fit legacy categories. Hybrid roles disappear into whichever single category they're filed under.
In practice, many employers reuse job descriptions repeatedly. It's time-consuming to update them. The people who know the roles best are hiring managers, and they have the least time and incentive to rewrite postings. So descriptions get recycled, language drifts and the gap between what's written and what's needed widens.
For small and medium businesses, the problem is worse. How can a 50-person company be expected to regularly audit and update position descriptions to match evolving terminology? They can't. So they write something reasonable, post it and hope qualified people find it.
Does skills-based hiring solve this problem?
Have you heard about the trend of "skills-based hiring"? The idea is that jobs are described and filled by skill descriptions instead of titles or credentials. Platforms like LinkedIn rolled out features to search by specific capabilities. Employers pledged to prioritize what you can do over where you went to school.
In practice, it hasn't worked. Not surprisingly, the same problems we see with titles and keywords also show up when using terms for skills. What one platform calls "stakeholder management," another might label "relationship management" and a job posting might describe as "cross-functional collaboration." Same capability. Three different terms.
And "skills" themselves are conflated requirements. A posting might ask for "data analysis" (a capability), "experience with Salesforce" (a tool), "experience in healthcare" (a domain) and "Bachelor's degree in statistics" (a credential). Job search engines treat each of these as separate, unrelated keywords. They can't distinguish between what you can do, what tools you've used, where you've worked or what degrees you hold.
Here's what makes this especially frustrating: large language models are literally built to solve this kind of mismatch. They excel at recognizing that "I coordinated cross-functional teams" maps to "stakeholder management" and that financial modeling skills transfer across industries.
If even a small fraction of today's investment in AI was applied to normalizing job posting language and helping workers translate their experience, it would create enormous public benefit. But instead the attention just remains on how AI will eliminate jobs instead of how AI could improve career mobility and economic opportunity.
So we continue to force employers and workers to translate skills manually. Enterprises are exploring AI recruiting tools to manage screening volume, but those tools don't solve the fundamental language problem. An employer's talent system can't change how candidates describe their skills; they just add another layer of partial analysis on top of an already broken system.
What does this problem look like when you actually search?
Say you have five years of experience managing client relationships in a professional services firm. You've onboarded new clients, resolved escalations and identified upsell opportunities. You search "Account Manager" because that's the title you know.
Half the results are for software sales roles requiring experience with specific sales enablement tools you've never used. A quarter are for advertising agencies looking for people to manage campaign budgets, which you haven't done. The rest are a mix of customer success roles (close to what you do but titled differently) and account management roles in industries you don't know.
You refine the search. Add your industry as a keyword. Now you get fewer results, but they're still scattered. Some want people who've managed enterprise accounts. Some want regional account oversight. Some are actually business development roles mislabeled as account management. You try "Client Manager." Different results. Some overlap with "Account Manager" but not entirely. You try "Relationship Manager." More different results. You try "Customer Success Manager." Even more.
Four searches. Four completely different result sets. You still haven't found the clean list of roles where your experience is directly relevant.
Who gets locked out by title-based search?
Job search tools create structural barriers for anyone whose language doesn't match the exact terms in a posting.
Career changers get filtered out because their previous titles and terminology don't overlap. Someone moving from teaching to corporate training has directly relevant skills in curriculum design, facilitation and assessment. But if the job posting asks for "L&D experience" and their resume says "classroom instruction," job search engines don't connect them.
New graduates face the same trap from the opposite direction. They have the degree the posting requires but no job title to search by. They see "Marketing Coordinator" and "Marketing Associate" and "Marketing Specialist" and have no way to know which roles are actually entry-level or what the real differences are.
Small and medium businesses suffer too. They're trying to find qualified candidates but their postings may use slightly different terminology than what candidates are searching for. They're not intentionally hiding opportunities. They just can't afford to hire someone whose job is optimizing job descriptions for search algorithms.
The tools available to identify jobs are broken for everyone. They just break differently depending on where you're coming from.
What’s the real cost of broken job search tools?
Clarity about what you want doesn't translate into an ability to find it. You know your capabilities. You know the problems you solve. But if you can't describe your value using language that happens to overlap with how a posting was written, job search engines treat you as irrelevant.
This isn't a matter of learning to search better. The categories themselves don't work. Titles are too vague and too inconsistent. Keywords fragment across synonyms and evolve faster than descriptions get updated. The job you want exists. You're qualified for it. Job search tools can't connect you to it.
And even if they could, a lot of hiring happens somewhere else entirely. Even if job boards fixed search tomorrow, you'd still be looking at an incomplete picture. The roles you can find represent a fraction of how people actually earn a living.
