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
You search for your job title in a wage table and either nothing comes back or the figure looks nothing like your world. The usual reason is not that the data is missing. It is that you searched for a title when the data is organized by something else entirely. That single mismatch is the most common reason people conclude no figure exists for their work.
A job title is invented by an employer. It signals seniority internally, it helps with recruiting, and it follows no standard of any kind. One company’s Analyst II is another’s Senior Analyst and a third’s Associate, all doing comparable work. Nobody is doing anything wrong; there is simply no authority that governs the words.
An occupational code describes what the work actually is, under a national classification, defined by duties rather than by branding. It exists so that pay can be compared across employers who each name things differently. Wage data is published by code, and job adverts are written with titles. Bridging the two is the step almost nobody takes, and it decides whether the figure in front of you describes your job at all.
Why matching by title fails
Titles inflate, and they inflate unevenly. A small company hands out Director because it costs nothing and helps with recruiting, while a large one reserves it for a level with real budget and headcount. Search for Director and you get an average across both, describing neither of them. The number is arithmetically correct and practically useless.
Titles also drift by industry in ways that are invisible from outside. Producer means one thing in broadcasting, another in manufacturing and another again in insurance. A search on the word returns all three mixed together with no way to separate them. The classification was built to solve exactly this, which is why it uses duties instead.
How to find your actual code
Ignore your title completely and describe your week instead. What do you spend the largest share of your time actually doing? The classification is built around duties and the definitions are published in full, so read the descriptions rather than scanning the names. The right code often has a plainer, older-sounding name than anything on your business card.
If two codes look plausible, read both definitions carefully rather than picking the better-sounding one. Frequently one definition says explicitly that a particular task belongs to the other code, and that sentence settles it. This takes about fifteen minutes and it is the single highest-value quarter hour in the whole exercise. Everything downstream depends on getting it right.
The all-other trap
Several codes end in the words all other, and those are catch-alls for work that fits nowhere specific. Their wage figures are averages across genuinely different jobs that share nothing but their failure to fit elsewhere. They are the least meaningful numbers in the entire dataset. Recognizing one is important, because they look exactly like every other row.
If your best match is an all-other code, treat the figure as a rough orientation rather than a benchmark. Lean harder on advertised ranges for roles that resemble yours in your metro, which are current and specific in a way the catch-all cannot be. Say plainly which one you used if you quote it. A stated limitation is far more persuasive than a false precision somebody can puncture.
When your job spans two codes
Plenty of real jobs sit between two codes, and that is a finding rather than a problem with the classification. A role that is half analysis and half management genuinely belongs to two different occupations with different pay levels. The classification is describing something true about your job that your title conceals. That is worth knowing before anybody quotes you a single figure.
Look up both codes and compare them. If they differ substantially, you have learned something you can use: your pay should reflect the mix, and the argument for the higher figure is that you do that work as well. That is a concrete case somebody can engage with, built on duties you both already agree you perform. It beats a vague claim about wearing many hats by a wide margin.
Level is missing entirely
The classification describes the occupation and says nothing about seniority within it. A junior and a principal doing the same kind of work share a single code, and the difference between them appears as the spread rather than as separate rows. Nothing in the data distinguishes them, and nothing was ever intended to. That is why the percentiles matter so much here.
In an occupation running about 2.22 times from the tenth percentile to the ninetieth, which is the typical figure, most of what people think of as level lives inside that range. A median of $75,000 in that shape implies roughly $51,000 at the bottom and $113,000 at the top. Your level is a position in that distribution rather than a separate table. Finding your position is the actual task.
Neither the title nor the code sets the pay
Worth being clear about what each of the three things in play actually controls. Your employer sets the title, a national standard sets the code, and the market sets the band that the money comes out of. The first is marketing, the second is measurement, and only the third moves your salary. Confusing the first with the third is how people end up negotiating about words.
That is also why a title change with no money attached is a weaker win than it sounds. The band is set by what employers in your area are paying for that work, and a new label does not move it. Conversely, a plain title in a well-paid band beats an impressive one in a poorly-paid band every time. Ask which band a role sits in, not what it will be called.
Using the code once you have it
Look up the full percentile spread for that code in your metro rather than nationally, because geography moves pay more than most people expect. Then place yourself by duties and years rather than by title, and sanity-check the result against advertised ranges for roles you would genuinely apply for. If the published range and the advertised ranges disagree sharply, you have probably matched to the wrong code. Re-reading the definitions is far quicker than arguing with the data.
In the conversation itself, the phrasing matters as much as the number. The published median for this occupation in this metro is a checkable statement about defined work. People with my job title earn a certain amount invites a discussion about whose title, at what company, doing what. Anchoring to duties is also harder to deflect, because the duties are the one thing you and your employer 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.