The Most Common Job Title in Tech Covers 1% of the Jobs

The Most Common Job Title in Tech Covers 1% of the Jobs

Type "software engineer" into a job search. Whatever comes back, you have just addressed about one percent of the market.

We normalised the title on all 16,001 open roles across the 791 tech companies currently hiring, measured on 17 September 2026, and the shape of what came out explains a frustration a lot of people have with searching for work and cannot quite name.

10,964 titles for 16,001 jobs

That is the headline. Sixteen thousand jobs, and nearly eleven thousand distinct titles to describe them.

The most common ones:

"Software Engineer", the single most common job title in the industry, accounts for 172 roles. That is 1.1% of the board.

The two columns are worth reading against each other, because they come apart badly. Those 172 Software Engineer roles are spread across 53 employers. The 56 Head of Engineering roles come from three, because one company opened 54 of them in a single batch. A title can be common because many companies use it or because one company uses it many times, and those are entirely different facts about the market.

All ten titles above, combined, are 829 roles. That is 5.2% of everything open.

The long tail is not a tail, it is the body

Here is the number that reframes it. Of those 10,964 distinct titles, 10,386 are used by exactly one company.

Those titles are attached to 12,085 open roles. So 76% of everything available carries a job title that no other employer in our set uses.

Not variations on a theme. Unique strings. "Mission Software Engineer". "AI Deployment Strategist". "Product Sourcing Engineer". "Sr. Forward Deployed Engineer (FDE) - Financial Services". "Software Engineer 3". Somebody's internal ladder vocabulary, published outward as if it were a category.

The market does not have a title taxonomy. It has 791 private ones.

Why search feels broken

This is the mechanical reason keyword job search underperforms, and it is worth being precise about because the usual advice ("use more keywords!") does not survive contact with these numbers.

If you search "Software Engineer" you see 172 roles out of sixteen thousand. You do not see the Mission Software Engineer at a defence lab that would have been your best offer, the Forward Deployed Engineer role that is 70% the same work, the Senior Backend Engineer at a company that just words it differently, or the "Software Engineer 3" that is your level under a different ladder.

You could add synonyms. Add the nine next most common titles and you are still at 5.2% coverage, and you have now also pulled in nine titles' worth of roles that are not your job.

The three quarters of the market with a single-company title is unreachable by keyword in principle. You cannot search for a string you have never seen, and there are 10,386 of them.

This is a stronger version of the problem than we expected to find. When we first looked at this the unreachable share was around half. It is now three in four, and the count of distinct titles has grown faster than the count of jobs.

Titles are not levels either

The seniority words are doing less work than they look like they are.

"Staff Software Engineer" appears at 41 companies, and at some of them staff sits above senior, at others it is a parallel IC track, and at a few it is what they call a strong senior to avoid a promotion conversation. "Member of Technical Staff", which shows up at four companies in our set, spans everything from new grad at one to principal-equivalent at another. It is a title that deliberately carries no level information, which is the point of it.

So the title tells you neither the work nor the level with any reliability. It mostly tells you which company wrote it.

What actually works

Search the company, not the title. This is the whole reason we built Remoet the way we did, so read the following knowing we are not neutral. Companies are a stable, finite, comprehensible set. There are 1,121 of them in our data and maybe forty you would seriously want. Titles are an unbounded vocabulary invented independently by each of those companies. Picking the axis with 1,121 values over the one with 10,964 is not a preference, it is arithmetic.

Star the companies whose stack and product you want, and read everything they open. Forty companies is a list you can actually hold. When one of them posts a Mission Software Engineer role, you read it, because it is them, and you never needed to guess the noun.

Search the stack instead of the title. If you do want to filter across the whole market rather than a shortlist, technology names are far more standardised than job titles. "Go" means Go everywhere. "Staff Engineer" means six things.

Read the requirements, not the header. Obvious, and most people still filter on the title in the search results before ever opening the post. The header is the least standardised part of the document.

Let something else read them. This is the honest case for pointing an agent at job data rather than a search box: an agent can read 16,001 descriptions and reason about whether the work matches, which is exactly the task a keyword filter cannot do and a human does not have the hours for. If you want that, connect one and describe the job you want rather than guessing its name.

Caveats

Our normalisation lowercases and trims but deliberately does not merge different titles, so "Senior Software Engineer" and "Sr. Software Engineer" still count separately, and they really are separate rows in our data: 139 roles against 7. That inflates the 10,964 somewhat. It does not change the shape: even generous merging leaves the top title around one percent.

Counting a title as "used by one company" is sensitive to that same issue in reverse, so treat the 12,085 roles as roughly three quarters of the board rather than exactly 76%.

We track 1,121 companies weighted toward product companies with real engineering orgs. A sample heavy on enterprises with formal job architectures would look more standardised than this. A sample heavy on startups would look less.

And the tail grows. Every company that invents a ladder adds titles to the world and none are ever retired.

A small prediction we are willing to be wrong about

Job titles have been getting less standardised, not more, and we think that continues, because a distinctive title is cheap and does recruiting work. "Forward Deployed Engineer" now appears at 43 companies with 82 roles behind it, a title that barely existed a few years ago and spread because it sounded like something.

If that is right, keyword search gets worse from here, and the only searches that survive are the ones anchored to things with fixed vocabularies: companies and technologies.

If it is wrong and the industry converges on a shared ladder, come find this post in a year and tell us. Preferably on Discord, where we will be the ones who have to admit it.