Wage surveys are organized by occupation code, which describes what the work is. Job titles are invented by employers and describe how a role is marketed. Matching yourself to the data means asking what you actually do most of the day, not what your offer letter calls you — and the answer is frequently a code with a plainer, older-sounding name than your title.
Two different things with the same name
A job title is invented by an employer. It signals seniority internally, it is used in recruiting, and it follows no standard whatsoever. One company’s Analyst II is another’s Senior Analyst and a third’s Associate.
An occupational code describes what the work actually is, under a national classification, defined by duties. It exists so that pay data can be compared across employers who each name things differently.
Wage data is published by code. Job adverts use titles. Bridging the two is the step almost nobody takes, and it decides whether the figure you are looking at describes your job.
Why matching by title fails
Titles inflate. A small company hands out Director because it costs nothing and helps recruiting; a large one reserves it for a level with real scope. Look up Director and you get an average across both, describing neither.
Titles also drift by industry. Producer means something different in broadcasting, manufacturing and insurance, and a search on the word returns all three mixed together.
How to find your actual code
Ignore your title and describe your week. What do you spend most of your time doing? The classification is built around duties and the definitions are published, so read the descriptions rather than scanning the names.
If two codes look plausible, read both definitions carefully. Frequently one says explicitly that a certain task belongs to the other, and that sentence resolves it.
The all-other trap
Several codes end in “all other”, and those are catch-alls for work that fits nowhere specific. Wage figures for them are averages across genuinely different jobs, and they are the least meaningful numbers in the whole dataset.
If your best match is an all-other code, treat the figure as a very rough orientation and lean harder on advertised ranges for roles that resemble yours.
When your job spans two codes
Common, and it is a real finding rather than a problem with the classification. A role that is half analysis and half management sits between two codes with different pay levels.
Look up both. If they differ substantially, you have learned something useful: your pay should reflect the mix, and the case for the higher figure is that you do that work too. That is a concrete negotiating argument rather than a vague claim about wearing many hats.
Level is missing entirely
The classification describes the occupation, not the seniority within it. A junior and a principal doing the same kind of work share a code, and the difference between them shows up as the spread rather than as separate entries.
That is why the percentiles matter so much here. In an occupation running 2.22 times from the tenth to the ninetieth — the typical figure — most of what people think of as level is inside that range.
Using the code once you have it
Look up the full percentile spread for that code in your metro rather than nationally. Then place yourself by duties and years, not by title, and check whether the range makes sense against advertised roles you would actually apply for.
If the published range and the advertised ranges disagree sharply, you have probably matched to the wrong code, and re-reading the definitions is quicker than arguing with the data.
Why this matters in a negotiation
“The published median for this occupation in this metro is X” is a checkable statement about defined work. “People with my job title earn X” invites a conversation about whose title, at what company, doing what.
Anchoring to duties rather than to a label is also harder for an employer to deflect, because the duties are the thing you both already agree on.
Common questions
Why can I not find my job title in the wage data?
Because the data is organized by occupation code, not by title. Titles are invented by employers; codes describe the work. Search the code definitions by what you do rather than by what you are called.
Is there a senior version of my occupation code?
Usually not. Seniority shows up inside the percentile spread rather than as a separate code, which is why reading the distribution matters more than reading the median.
What if two codes both seem to fit?
Look at which tasks take up most of your week. If you genuinely split between two, read both figures — the published number for either describes you only partly.
My title says Manager but I do not manage anyone. Which code applies?
The one matching the work. Titles carry no weight in the classification, and this mismatch is common enough that it is worth checking before concluding you are underpaid.
What if my occupation is too new to have a code?
The classification lags new work by years. Read the two or three nearest codes together — they bracket the role even when none of them describes it.
Why can't I look up pay by job title?
Titles are invented by employers and follow no standard, so a search averages across genuinely different levels and industries. Wage data is published by occupational code.
How do I find my occupational code?
Ignore your title and describe your week. The classification is built around duties and the definitions are published — read them rather than scanning names.
What if my job spans two codes?
Look up both. If they differ substantially, that is a concrete negotiating argument: your pay should reflect the mix because you do both kinds of work.