How This Page Was Built
- Evidence level: Editorial research.
- This page is based on editorial research, source synthesis, and practical decision framing.
- Use it to clarify fit, trade-offs, thresholds, and next steps before you act.
- It is not personal career coaching, legal advice, or a guarantee of employer outcomes.
Start With the Main Constraint
Match the job before you match the state. A salary table by state tells you less than people assume when the title, seniority, or pay structure shifts. A software engineer, operations manager, and lab technician in the same state do not live in the same compensation band, even when the state median looks neat on paper.
Use this first filter:
- Same title and same level, or the data gets noisy fast.
- Same pay structure, meaning salary versus hourly versus OTE.
- Same location pattern, meaning on-site, hybrid, remote, or relocation.
- Same must-have costs, meaning commute, licensing, parking, child care, or travel.
The state median works best as a baseline because the average gets pulled by high earners. Median gives you a cleaner middle point for setting a floor. If the only data you have rolls several job families together, treat it as directional. It still helps you avoid lowball offers, but it does not define your final number.
A practical floor looks like this: state median first, then a 10% to 15% adjustment if the offer leaves you paying for weak health coverage, a smaller retirement match, or a longer commute. That adjustment keeps the floor tied to reality instead of to a neat spreadsheet.
The Comparison Points That Actually Matter
Use the most specific data source that still matches the role. Broad salary data gives speed. Narrow salary data gives accuracy. The wrong move is using narrow-looking numbers that do not match the actual job structure.
| Data point | Best use | Weak spot | How to use it in a floor |
|---|---|---|---|
| State median for the same role | Baseline floor | Hides metro premiums and low-cost pockets | Start here, then raise the floor 10% to 15% for weak benefits or fixed costs |
| 25th percentile | Entry-level roles, career pivots, or jobs with strong training | Undercuts experienced candidates | Use only when the role truly includes training and low ramp friction |
| Posted salary range | Company-specific negotiation | Range width hides level mismatch | Anchor near the lower half only after title and scope match |
| Metro or city pay data | Dense urban jobs, relocation, or long commute decisions | Harder to find and easier to misread | Replace the state figure when housing and commute drive the budget |
| Guaranteed cash only | Bonus-heavy or equity-heavy offers | Leaves out upside | Use this as the minimum acceptable offer, then add variable pay separately |
The sharpest mistake is comparing a state median for one job against a posted range for another. That creates false precision. Match title, level, and pay type first, then compare numbers.
The Decision Tension
The simple method is fast. The precise method is cleaner. The trade-off is friction.
A state median floor gets you moving. It works when the role is standard, the commute is stable, and the benefits package is normal. The downside is bluntness. It ignores the cost of a long drive, a weak health plan, a lower 401(k) match, and any bonus that shows up once instead of every paycheck.
A tighter method uses base pay, benefits value, commute cost, and location. That gives a better floor, but it also slows the decision. It helps most when the offer sits near your limit, or when the job adds expenses that do not show up in salary tables.
One simple alternative works well for stable office jobs: use the state median, then ask one question. If the offer covers your recurring costs without leaning on a sign-on bonus, it clears the floor. If it only works because of one-time cash, the floor is too low.
How to Match Salary by State Data to the Right Scenario
Different offers need different reads. A relocation offer does not need the same math as a remote internal move or a first job after school. Use the right scenario, or the state data turns into noise.
| Scenario | Use this data | Ignore this | Floor rule |
|---|---|---|---|
| Entry-level local role | State median and 25th percentile | Top-of-range pay and bonus hype | Set the floor near the median unless training is unusually strong |
| Remote role with a fixed tax state | State median for your tax and living location | Employer HQ location | Use the state where your budget actually lives |
| Relocation offer | Destination state and metro data | One-time moving stipend | Do not lower the floor because of a temporary moving payment |
| Internal promotion | Your current salary plus state market data | Title change without scope change | Require a real bump if the job adds responsibility |
| Commission-heavy sales role | Base pay, OTE, and quota pace | State salary median alone | Set the floor on guaranteed cash, not on upside |
A one-time relocation stipend does not raise your recurring floor. It pays for the move, not the next three years of rent, taxes, and groceries. Treat any temporary payment as separate from the minimum acceptable offer.
What to Recheck Later
Refresh the number when the job changes shape. A state salary floor loses value when the role picks up on-call time, travel, licensing, or a longer commute. It also loses value when the offer shifts from salary to salary-plus-variable comp.
Treat a salary table older than 12 months as directional only. Labor markets move faster than annual planning cycles in many roles, and a stale table gives a false sense of certainty. The clean fix is simple: update the role match, check the pay structure again, and reset the floor before you reply.
This matters most after a title change. A new title without new scope does not justify a bigger floor. New scope without new pay does justify a harder line.
What to Verify Before You Commit
Verify the structure, not just the number. A strong base salary with weak benefits and a punishing schedule sits below a slightly smaller number with predictable hours and a better match.
- Same pay type, meaning salary, hourly, or OTE.
- Same job level, not just the same title.
- Same location assumptions, especially for remote and hybrid roles.
- Same guaranteed cash, not bonus promises.
- Same recurring costs, including commute and licensing.
- Same workload, especially travel, on-call time, and overtime expectations.
If variable pay makes up more than 20% of the package, set the minimum on guaranteed cash only. That keeps the floor from leaning on a bonus plan that changes every year. If the offer includes a sign-on bonus, count it as first-year support, not as part of the minimum acceptable offer.
When Another Path Makes More Sense
Use a different benchmark when the state number hides more than it reveals. Hourly jobs, contractor roles, and union roles need different math. Their floor lives in rate, schedule, and contract terms, not in a state salary median.
City data also beats state data once the metro dominates your budget. That matters in places where housing, parking, and commuting change the whole equation. A broad state number gives a weak answer when one city drives most of the pay pressure.
Commission-heavy roles need OTE and quota math. A base salary floor without a quota check misses the point. If the role depends on quota pace, the real question is whether the plan supports the number on paper.
Quick Decision Checklist
Use this as the final pass before you accept or counter.
- The role title and level match the data.
- The pay structure matches the data source.
- The state median sets the baseline.
- The floor rises 10% to 15% when benefits or costs are weak.
- Variable pay stays separate from guaranteed cash.
- One-time bonuses do not lower the floor.
- Metro data replaces state data when location drives the budget.
- Three or more no answers mean the number is too crude.
Common Misreads
The biggest mistakes are simple, and they cost time.
| Misread | Why it breaks the floor | Cleaner reading |
|---|---|---|
| The top of the posted range is the goal | The range often spans multiple levels | Anchor to the lower half after title and scope match |
| Bonus money counts the same as salary | Bonus payouts change and do not repeat evenly | Set the minimum on guaranteed cash |
| Remote means location-free | Taxes, commute, and housing still shape the budget | Use the location that actually drives your expenses |
| One state number covers every city | Metro pay and housing pressure shift fast | Switch to city data when the commute or rent does the damage |
A second mistake is using the same floor for every stage of your career. Entry-level jobs and lateral moves have different negotiation logic. A floor that works for a first role becomes too low once you add experience, licenses, or management scope.
The Practical Answer
Use salary by state data as a starting floor, not as the final word. Match the role and level first, then set your minimum at the state median and adjust up when the offer adds fixed costs or weak benefits. Switch to metro data, guaranteed cash, or contract terms when the role makes state data too broad.
The cleanest floor is the one that fits the job you will actually do, in the place you will actually live, on the pay structure you will actually receive.
Frequently Asked Questions
Should I use the median or the average salary by state?
Use the median. The average gets pulled by high earners and distorts the middle of the market. Median gives a better base for a minimum acceptable offer.
Do I count bonus and equity in my floor?
Count them separately. Set the minimum acceptable offer on guaranteed cash, then add bonus and equity after the base number clears your floor.
What if the role is remote but the company is in another state?
Use your actual tax and living location, not the company’s HQ. Your recurring budget follows where you live, not where payroll sits.
When does salary by state data stop being useful?
It stops being useful when the role depends on one city, one contract, or one compensation structure that the state table blurs. At that point, move to metro data, hourly rate, OTE, or contract scale.
How do I handle a relocation package?
Separate the one-time package from recurring pay. A moving stipend covers the move. It does not justify a lower base salary floor.
What if the state data is for a broad job family, not my exact title?
Use it as a bracket, not a target. Broad job-family data sets the rough zone, but your exact title and level set the real floor.
Does a higher cost of living always mean a higher minimum acceptable offer?
Yes, when your recurring expenses rise with the move. If housing, commuting, or taxes increase, the floor rises with them. If your costs stay flat, the state number stays useful longer.