The goal is not to predict the exact salary you will get. The goal is simpler: figure out whether your case is ready to be heard. If the state anchor, job level, and pay structure line up, you can speak with more confidence. If they do not, the tool should push you toward a better comparison before you name a number.
How the tool should be used
Start with the state that actually controls pay, not the state that is most convenient to name. That can be the office state, the headquarters state, the job site state, or the company’s remote pay rule. Then add the role level, the compensation mix, and the timing of the ask.
A good setup usually includes:
- the state tied to the pay rule
- the job title and level
- current pay, target pay, or offer amount
- the reason for the ask, such as a review, promotion, or outside offer
- one or two proof points that show added scope or results
The state anchor matters because the same title can mean very different pay from one place to another. Level matters because entry, mid, senior, and lead roles are not interchangeable. Timing matters because a live offer or scheduled review creates a stronger opening than a casual request with no deadline.
If you put in a vague title, an old salary note, or the wrong location rule, the result can look stronger than it really is. Clean inputs usually give a cleaner read.
What the score is really telling you
Use the score as a readiness signal, not as a promise. A higher number means your comparison is better formed and easier to defend. A lower number means the ask is still leaning on weak context.
| Score | What it says | Best move |
|---|---|---|
| 0 to 3 | The comparison is loose and the anchor is weak. | Tighten the state rule, role level, and compensation mix before opening the conversation. |
| 4 to 6 | You have a usable start, but one or two pieces still need support. | Ask for a range, gather one stronger comparison, or wait until the context is clearer. |
| 7 to 8 | The state anchor and the role level line up well enough to speak directly. | Enter the discussion with a target number and a fallback number. |
| 9 to 10 | The case is strong and the timing is on your side. | Push for the part of the package that matters most, whether that is base pay, bonus, sign-on, or title. |
A strong score does not mean you will get everything you ask for. It means you have a cleaner case and less risk of sounding random. The weaker the score, the more likely it is that your comparison needs another pass.
The pieces that matter most
A state comparison only works when it is tied to the right pay rule. These are the parts that deserve the most attention.
1. The state anchor
Ask first: which state actually sets the pay? Some employers use the job location. Some use the office that owns the role. Some use headquarters. Some use a remote policy with its own rules. Your home state only matters if the employer uses it.
2. The role level
A title alone can be misleading. Two jobs with similar names can sit in very different bands if one is entry-level and the other is senior. Level gives the number context. Without it, state data can point you in the wrong direction.
3. The compensation mix
Base salary is only one part of the package. Bonus, commission, sign-on pay, and equity can change the meaning of the number. For a negotiation, the full package matters more than a single figure.
4. The timing
A live offer, annual review, promotion review, or transfer window changes the strength of the ask. The same number can feel very different when it is attached to a deadline and a clear decision point.
Where state salary data helps most
State-level pay data is most useful when the job has a clear location rule and a standard salary structure.
It helps especially when you are:
- comparing a new offer against pay in a specific state
- preparing for a review after taking on more responsibility
- moving into a new role that has a clearly defined level
- comparing remote roles when the employer pays by office state or headquarters state
- deciding whether your current pay is behind the local range for your role
This is the kind of situation where a state benchmark can sharpen your ask. You are not relying on a vague national average. You are using a comparison that is closer to how the employer may already think about pay.
When state-only data is not enough
Some jobs need a different comparison method.
- Commission-heavy roles: base pay may be only part of the real earnings picture.
- Tip-based roles: pay can vary too much for a simple state comparison to carry the whole conversation.
- Union or public sector roles: step systems, contracts, or grade ladders often matter more than a state average.
- Licensed or regulated roles: experience, credentials, and formal pay steps can shape the range more than geography.
- Internal promotions: internal equity and the new level usually matter more than your old salary.
If one of these fits your situation, use the state number as a reference point, not the only reference point. The safer move is to compare against the real pay structure of the role.
How to prepare a stronger negotiation
A good negotiation packet does not need to be complicated. It just needs to be clear.
Use this order:
- Pick the pay rule that actually applies.
- Match the role level before comparing numbers.
- Separate base pay from bonus and other extras.
- Add one clear reason the role deserves a higher number.
- Decide your target and your fallback before you speak.
That last step matters more than people think. If the first number is pushed back, you should already know what you are willing to accept next. That keeps the conversation steady instead of reactive.
A simple opener can sound like this: I want to align the offer or review with the state-based range for this level and the scope I am covering. That keeps the conversation tied to the job, not to guesswork.
Who should use this tool, and who should skip it
This tool is a good fit if you have:
- a clear role title and level
- a state rule that actually affects pay
- a live offer, review date, or promotion window
- enough job detail to compare one role against another
You should skip a state-only read if your pay is mostly driven by:
- commission, tips, or other variable earnings
- a contract or union step system
- a pay band tied to grades rather than geography
- an unclear location policy where the state does not really tell you much
In those cases, the state is background information, not the main anchor.
The simple takeaway
Use the checker when you want to know whether your pay conversation is ready or still needs more support. If the state rule is clear, the role level is clear, and the timing is real, the score can help you open with more confidence. If the inputs are fuzzy, the tool should tell you to pause and build a better case first.
The best negotiation is not the one with the loudest ask. It is the one that fits the role, the state rule, and the moment.
FAQ
Does my home state matter most?
Only if the employer uses your home state as the pay rule. Many companies use the office location, job site, headquarters, or a remote policy instead.
Can I use this before a promotion conversation?
Yes. It is especially useful when you are moving into a new title or level and want to see whether the state-based comparison supports a stronger ask.
Is a higher score always better?
A higher score usually means the comparison is easier to defend. It does not guarantee the outcome, but it does mean your case is better organized.
What if the role is remote?
Use the employer’s location rule first. Remote does not automatically mean home-state pay.
What if I only have one salary example?
You can still use the tool, but treat the result as a starting point. One example is better than none, but it is not as strong as a comparison that also matches level and compensation type.