Start Here: The four fields that make a salary table usable
This is the core test for what to look for in salary by state data sources. If a source misses one of these fields, it still works as a rough reference, but it stops working as decision support.
| Check | What good looks like | Red flag |
|---|---|---|
| Geography | The table isolates one state at a time. | State, metro, and national figures sit in one blended number. |
| Pay definition | Median, mean, base salary, or total compensation is labeled. | The source just says “salary.” |
| Occupation match | The role ties to an occupation code or a narrow title cluster. | Unrelated jobs sit under one broad label like “business jobs.” |
| Freshness | The release date sits inside the last 12 months. | There is no update date or methodology note. |
The trap is small samples in narrow roles. A state has enough data for teachers, nurses, and broad office jobs far sooner than it has clean data for a niche software title or a rare specialty trade. One employer or one industry shift moves the middle fast, so the method note matters as much as the headline number.
A source with clean filters saves real time later. If you have to clean titles by hand, reconcile state and metro figures, or guess whether the number is base pay or total comp, the source is fighting the decision instead of supporting it.
How to Compare Salary by State Sources
Use source type before you use the number. Public labor data, census-style surveys, job postings, and employer pay bands answer different questions, and the wrong one creates bad confidence.
| Source type | Best use | Weak spot |
|---|---|---|
| Public labor data, like BLS-style occupational tables | Stable state comparisons and occupation ranking. | Release lag and limited detail on bonuses or equity. |
| Census or survey-based data | Broad labor-market context across states. | Less precise for narrow jobs and small states. |
| Employer job postings | Current hiring ranges and offer prep. | Openings, not filled jobs, and the listed range may overstate actual pay. |
| State labor or education agency tables | Public-sector, licensed, or in-state careers. | Coverage and update cadence vary by state. |
| Employer salary bands | Internal pay structure and negotiation context. | Company-specific, not market-wide. |
Public labor data gives you the steadiest floor. Job postings give you the freshest signal. Employer bands tell you how one company pays, not what the state pays. That difference matters when a title sits in a high-growth field, because active postings overweight firms that are hiring hard while undercounting quiet employers that fill roles internally.
A good source stack uses at least two of these views. One source sets the baseline, another catches the market’s current temperature. When both point in the same direction, the number earns trust.
Trade-Offs to Understand
Pick breadth or precision first. Salary-by-state data rewards simple comparisons, but every simplification strips out a real variable.
State averages look clean because they collapse complexity into one line. That same simplicity hides metro concentration, industry mix, and seniority spread. A state with a large finance hub or a heavy public-sector footprint will read differently from a state with the same job title spread across smaller employers.
Occupation-specific data fixes that, but it brings thinner samples. Thin samples create noisy year-over-year movement, especially in rare jobs. If the source does not show the occupation code or grouping method, the number reads precise while hiding a fuzzy foundation.
Base pay and total compensation need separate treatment. Base salary works for most straightforward roles. Total compensation matters more in sales, finance, tech, and executive tracks where bonus and equity shape the real offer. Mixing the two breaks every comparison, because a high total-comp role and a flat base-pay role do not sit on the same scale.
Fresh data and stable data pull in opposite directions. A posting range feels current, but it reflects recruiting strategy, not filled-role history. A public labor table feels slower, but it gives a better base for state-to-state comparison. For relocation planning, stability wins. For offer timing, freshness wins.
What Changes Which Source Wins
The right source changes with the decision in front of you. A relocation search, a field switch, and a remote offer all need different inputs.
| Situation | Start with | Why it wins | Watch out for |
|---|---|---|---|
| Relocating in the same occupation | Occupation-specific state data | It compares the same job title across locations. | Pay definitions that change between sources. |
| Switching into a new field | Entry-level state pay plus training-path data | It shows the floor, not only experienced pay. | State averages that overstate a first offer. |
| Remote role with location-based pay | Employer policy or posting range | The location rule controls the number. | State averages that ignore office-tier pay bands. |
| Public-sector or union role | Agency schedule or contract scale | Formal pay steps beat broad market estimates. | Hourly to annual conversion errors. |
| Niche occupation | Regional or multi-year data | Single-state samples stay thin. | A median built on too few employers. |
Remote pay is the biggest trap. Some employers anchor pay to the worker’s home state, some to the hiring hub, and some to a location tier that sits nowhere near the state line. A statewide average does not reveal which rule applies, so it answers the wrong question.
Union and public-sector roles follow a different logic. Step increases, grade levels, and service years define the path more clearly than market estimates do. If a source ignores those structures, it misreads the compensation plan.
What to Watch as Data Ages
Use a recent release for anything that changes your next move. Twelve months is the practical ceiling for salary planning. Older than that, the source works as context, not as a decision anchor.
Freshness matters because pay data drifts with inflation, labor shortages, and hiring cycles. A source that changes its methodology without flagging it breaks the trend line. Old and new figures do not belong in the same comparison unless the method stayed fixed.
Treat small shifts with caution when the source is rounded or sample-thin. A 1 percent to 3 percent change disappears fast in rounding noise and reporting lag. If the update date moved forward but the method did not, freshness wins. If the method changed, start a new comparison and do not stitch the numbers together as one clean trend.
This is where a lot of salary tables lose value. The interface stays polished while the data ages out underneath it. A dated, well-labeled source beats a prettier dashboard with stale assumptions.
Requirements to Confirm
Reject any source that misses two of these checks. One missing detail creates friction. Two missing details turn the number into orientation only.
- Release date, visible without opening a hidden methodology page.
- State-only geography, not a blend of state, metro, and national figures.
- Occupation code or narrow title cluster, not a broad category.
- Pay definition, clearly marked as median, mean, base salary, hourly wage, or total compensation.
- Method note, with source basis or survey frame.
- Sample note or coverage note, even if it is high level.
- Adjustment note, if the source inflates or deflates for year-to-year comparison.
If the source asks you to infer any of these from a chart alone, it is a convenience tool, not a reliable reference. Downloadable tables or filterable fields beat static graphics because they let you compare the same occupation across states without mixing titles by accident.
The cleanest rule is simple: if a source hides the date and the pay definition, do not use it for relocation, training, or negotiation.
When This Is Not the Right Path
Skip state salary data when the decision depends on the details inside one offer, not the market around it.
That includes equity-heavy roles, bonus-heavy sales roles, freelance and contract work, and tipped jobs. In those cases, the base salary number tells only part of the story. Bill rate, commission plan, stipend structure, overtime rules, and location policy all matter more than a generic state median.
This path also falls short for tiny occupations with very few employers in a state. One payroll change swings the result too hard. A regional comparison or a multi-year average does a better job there than a single-state snapshot.
If the job lives inside a step-scale system, use the scale itself. Teacher pay schedules, government grades, union contracts, and license-based ladders give a clearer picture than a general labor table. The state number stays useful as context, but it stops being the main answer.
Quick Checklist
Use this before you trust any salary-by-state source.
- The occupation matches your target role closely.
- The state is isolated cleanly.
- The source shows a release date within the last 12 months.
- The pay label is clear.
- The method note exists.
- Bonuses, equity, overtime, and commissions are separated or clearly excluded.
- The source fits the task, planning, switching fields, relocation, or negotiation.
If two of those answers are no, move to another source or treat the number as directional only. A clean baseline matters more than a flashy interface.
Common Mistakes
Do not treat one number as final truth. Compare at least two source types when the decision affects moving, retraining, or negotiating.
Do not mix base pay and total compensation. A role with a lower salary and larger bonus pool does not belong in the same bucket as a salary-only role. The source has to label the difference, or the comparison breaks.
Do not use national data to judge a state move. National averages flatten state-level pay differences, and they blur local industry concentration. A state-specific number solves that problem only when the occupation match is tight.
Do not trust a posting range as if it were a filled-job salary. Job ads reflect recruiting strategy. They also change fast, especially in hiring surges. That makes them useful as current market signals, not as the entire picture.
Do not skip the update date. A source without freshness is not a source for action. It is background noise with a chart.
Bottom Line
For broad career planning, use a recent public source with state-level data, occupation codes, and a clear method. For an active job search, pair that with current employer ranges or postings. For negotiation, prioritize the employer’s pay band, bonus structure, and location rule over any state average.
That split keeps the decision clean. State data handles the baseline. Employer-specific data handles the offer. The best source is the one that answers the next move without forcing a cleanup project.
FAQ
Is median or mean better for salary-by-state data?
Median works better for most job searches because it cuts through outliers and mixed seniority. Mean helps when the source uses a true payroll average and labels it clearly. If the source does not say which one it uses, do not treat the number as precise.
How recent should salary data be?
Within 12 months is the practical standard for planning, relocation, and training decisions. Data older than 24 months belongs in context only. If the source changed its method, start over with the newer version.
Do job postings count as reliable salary data?
They count as current hiring signals, not as filled-job pay. Use them to see what employers advertise now, especially for active searches and negotiation prep. Do not use them alone for state ranking.
What matters most for remote jobs?
The employer’s location-based pay rule matters most. Some companies pay by home state, some by office hub, and some by tiered regions. A statewide average does not show which rule controls your offer.
Should cost of living be part of the comparison?
Yes, but keep it separate from raw salary data. State pay shows the nominal offer, and cost-of-living adjustment shows purchasing power. Blending the two into one number hides both.
What if the occupation is rare in my state?
Use regional or multi-year data instead of a single-state snapshot. Thin occupations swing too hard on small sample sizes. One employer can distort the median.
Can public-sector salary schedules replace state salary data?
Yes, for public-sector roles, licensed roles, and contract-based tracks with step increases. The schedule gives a better answer than a broad market estimate. Use state salary data only as a background check on the number.
What is the biggest red flag in a salary source?
A missing date combined with an unclear pay definition is the worst sign. That source gives you a number with no timing and no context. It does not support a real decision.