Turn one seed title into every variant a search should cover, choose which groups to include, add a seniority band, and get the OR block in the syntax of the platform you actually search on. No sign-up.
One job is advertised under dozens of names. The US Department of Labor’s O*NET database records an mean of 53.4 job titles per occupation, counted directly from release 31.0: 54,269 titles across 1,016 occupations. Most sit between 10 and 100. Software Developers carries 93. Human Resources Specialists carries 100.
The same gap shows up in live hiring data. Indeed’s Hiring Lab reported in July 2026 that the UK’s official occupational classification has 412 detailed unit groups, while Indeed sees around 6,000 normalised job titles with at least five postings in a quarter, roughly fifteen times as many labels as the taxonomy has categories. A peer-reviewed analysis of 42 million US job postings found over three million distinct job titles, and after cleaning, about 43% of the titles that survived appeared in exactly one posting.
This tool answers with both. When your seed matches an occupation, you get the titles the Department of Labor actually records for it, marked as official and citable. A model then covers what a taxonomy cannot: the titles a taxonomy has not caught up with. O*NET has no entry for Product Owner, for instance, and one benchmark study put the ceiling for linking a real vacancy title to a taxonomy label without ambiguity at about 65%, on a 2,000-vacancy sample. Taxonomy alone is incomplete; a model alone is unaccountable. The tool labels which is which so you can tell them apart.
Searching Senior Engineer misses Sr. Engineer, Staff Engineer, Lead Engineer and Principal Engineer, who are all the same hire at most companies. Pick a band and every title in your block is expanded across the prefixes that band actually uses, rather than you typing them by hand and forgetting two.
This page includes information from the O*NET 31.0 Database by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA). Used under the CC BY 4.0 license. O*NET is a trademark of USDOL/ETA, and O*NET® is a trademark of USDOL/ETA. HeroHunt has modified some of this information: the set was filtered to recruiting-relevant occupations, parenthetical forms were split into separate titles, duplicates were removed and each list was ranked by closeness to the occupation label. USDOL/ETA has not approved, endorsed, or tested these modifications. The original database is published at onetcenter.org.
You will see confident claims that searching a single title loses a specific percentage of candidates. We went looking for the source of that figure and there is none: the companies who could measure it publish taxonomy sizes, never retrieval losses. So we have not invented one, and when our own first attempt at an equivalent statistic turned out to be an artefact of plural occupation names, we deleted it rather than shipping it. What is above is what we can stand behind.
Turn a role into a Google or Bing query that searches public profiles across eleven networks, including LinkedIn, GitHub and Google Scholar.
Describe the role in plain English and get a correct nested boolean string, ready for every platform.
Paste a string, fix what silently breaks it, and rewrite it for the platform you are searching on.
HeroHunt expands and matches title and skill variants automatically, so you search every synonym across live candidates in one pass instead of running ten separate strings.
