Comparing Pay Across Occupations When Job Titles Don't Match

If you're weighing a career change, the first instinct is to compare job titles — but company titles are a bad unit of comparison. A “Senior Engineer” at one company can mean a completely different job, at a completely different pay level, than a “Senior Engineer” at another. To compare pay honestly, you need to compare the actual occupation, not the label on an offer letter.

Why job titles don't line up

There's no standard that requires two companies to use the same title for the same work. Titles get inflated for recruiting purposes, vary by company size and industry, and drift over time. Two people with the title “Manager” can have entirely different scopes of responsibility and pay. Comparing self-reported salary data by title — which is exactly how Glassdoor, Payscale, and Levels.fyi organize their numbers — inherits all of that inconsistency.

What a SOC code is

BLS classifies every job in its surveys using the Standard Occupational Classification (SOC) system — a single controlled taxonomy of roughly 800 detailed occupations, each defined by the work actually performed, not by any one employer's internal title. Every occupation on this site is tagged with its SOC code for exactly this reason: it's the one identifier that means the same thing regardless of which company's job posting you're reading.

Before comparing pay across a potential career change, find the SOC code that actually matches the work you'd be doing — not the closest-sounding title. O*NET's occupation search (built on the same SOC taxonomy) is the practical starting point: search by the tasks and duties involved rather than a job title, and you'll usually land on a more accurate match than title-matching would give you.

Compare the whole distribution, not just one number

Once you have the right occupation on each side, look at the full 10th–90th percentile range for both, not just the median. A career change into an occupation with a wide pay spread might start lower but have more upside than one with a tight, capped range — information a single “average salary” headline hides entirely.

A second lens: O*NET Job Zones

O*NET assigns every occupation a Job Zone from 1 to 5, describing how much preparation — education, training, experience — the work typically requires. It's not a wage measure, but it's useful context alongside pay: a comparison between two occupations in very different Job Zones is a bigger leap (more retraining, a longer runway) than one between occupations in the same zone, even if the pay gap looks similar on paper.

Informational only, not professional or financial advice.