The Spoken Pay Question Reference, One Row per Phrasing You Hear

You are mid-loop. A recruiter, a hiring manager, or someone making small talk in the hallway asks about money, and the exact wording matters more than any generic script suggests. This reference splits the pay conversation into the distinct spoken phrasings you actually hear, so you can jump to the one line you just caught, know what it probes, know whether it is even legal to ask you, and pick a redirect that does not read as evasive. It is for candidates in an interview loop who want to identify a prohibited question in real time and respond in seconds, not memorize a monologue.

Most pay guidance treats the salary conversation as one question with one scripted answer. That is the mistake. The blunt version ("What are you currently making?") and the casual version ("Were you well-compensated in your last role?") are the same probe, but they land differently, and the legal line runs straight through the middle of both. Read the rows below, know your jurisdiction, and you will handle the exchange faster than the person asking.

What the question is actually probing

The single fact that decides everything is the tense of the verb. Present or past tense about your pay is a history probe; future tense is an expectations question, and every reviewed ban law targets the first and not the second.

That distinction is not a nicety. It flips legality on one word. "What are you targeting?" is lawful in all 22 ban states. "What are you making?" is not. The same 30-second exchange changes character depending on whether the verb points backward or forward. Before you respond to anything, classify what you heard into one of these families.

The disguised row is where careful candidates still lose. FindLaw, a named legal publisher, lists "Were you well-compensated in your last role?" and "Did your previous salary meet your needs?" as interview questions disguised as casual conversation that still violate the law. It does not matter whether they ask for exact dollar amounts or use checkboxes for salary ranges; a friendly tone does not launder a history ask. Any reference to your past or current pay is a history probe. Answer the tone and you have handed over the number the law was trying to protect.

Is it even legal to ask you

There are 22 salary-history ban states including the District of Columbia, and they restrict what you used to earn, not what you expect going forward. That is why an expectations question stays lawful in every ban state, while a history question is prohibited in all of them.

As of the most recent review, 22 American states and 23 American municipalities have adopted some form of a salary-history ban. The states include California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Nevada, New Jersey, New York, Oregon, Rhode Island, Vermont, Virginia, Washington, and D.C., among others. Massachusetts was first, signed in 2016 and effective July 2018. Virginia is the newest and the broadest: its statewide history ban and its range-posting rule both took effect July 1, 2026, and it requires all private employers to post a wage or salary range in listings.

Two cautions before you cite a law in the room. First, voluntary disclosure is usually still permitted, but only without prompting. The law lets you volunteer your history "as long as it is being done without prompting from the prospective employer," and an employer may not pose an "optional" salary-history question to nudge you into it. Second, not every state protects you. Michigan enacted a law prohibiting its cities and counties from imposing salary-history bans, so private employers in Michigan may legally ask about prior compensation, and Wisconsin bars local bans too. Texas has no private ban. Assuming a law exists when it does not is its own failure.

New York carries one wrinkle worth knowing. One source states that New York bans employers from requesting salary history and from asking about expected salary ranges. Multiple legal sources disagree and say expectations questions remain permitted in New York: you can safely be asked about your expectations for the role, the salary range, and whether the offer aligns with your needs. Treat New York expectations questions as lawful but be aware the point is contested, and if the phrasing edges toward your history, it is prohibited.

Who is on the other side of the question

You almost always face a recruiter, not a compensation expert, and that changes which redirect works. In Refolk's index of professional profiles, US professionals hold about 26 recruiter titles for every compensation specialist, which means the person asking usually reads from a script and cannot deviate far from it.

That ratio is the whole reason "What's the budgeted range for this role?" works so often. The recruiter running your screen has the range written down. They are clearing a filter, not architecting your pay, so a question that lets them read the number back to you is easy for them to answer. The comp specialist who actually set the band is rarely in the room during early rounds.

Counts are from Refolk's index of US professionals; shares are derived by dividing into the total recruiter count. The read: candidates meet a recruiter roughly 26 times more often than a comp specialist (111,248 / 4,293 = 25.9x, derived). Knowing who tailors your materials to a given posting is part of walking in prepared; Refolk writes your resume from your own history and scores how well you fit before you ever reach the pay conversation, so you arrive already knowing your own range.

You are talking to a script-reader with the range written down, so ask them to read it to you.

The redirects, matched to the phrasing

The safe move is never a flat refusal and never a naked number. For a history ask you decline and pivot to the role; for an expectations ask you flip to the employer's range before you name yours. A hard "I won't say" reads as evasive, and evasive responses make it look like you are dodging.

Alison Green of Ask A Manager recommends redirecting a history question to the range you are seeking, with language like: "I keep that information confidential, but the range I'm looking for now is..." For an expectations ask, the deflect-and-flip is to ask for their budget: you are not refusing to answer, you are redirecting to information that helps both parties, and many recruiters will share the range when asked this way.

History ask, ban state:
"I don't think that's something to get into with the new law, but one thing I'd like to talk about is the range you've budgeted for this role."

History ask, anywhere:
"Before we talk about salary, I'd like to learn more about the role and what you're solving for."

Expectations ask, early screen:
"Could you share the budgeted range for this role? That'll help me confirm we're in the right ballpark."

Expectations ask, forced to go first:
"Based on the market for this scope, I'm targeting the [X to Y] range, and I'm flexible on the total package."

Offer stage:
"Thank you, this is exciting. I'd like to review the full package and come back to you tomorrow with any questions."

Range-posting laws hand you the anchor for free. In the states that require a good-faith range in the posting - California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, and Washington, plus D.C. - the employer has already published the number. That is not a $0 to $1,000,000 dodge; it is close to what the job really pays, so you can negotiate against a real figure instead of guessing. Remote work exports the strictest rule: a company in a no-law state often posts ranges and drops history questions anyway because the role could be filled from Colorado or New York, so candidates in non-ban states increasingly get ban-state treatment.

The step-by-step, from question to response

Run this as a fast decision tree. The order below is roughly consistent across the practitioner sources; the only genuine disagreement is between flipping to the employer's range first and giving a researched range immediately when pressed.

On steps four and five: some scripts flip to the employer's range first, while other sources accept giving a researched range immediately if you are pressed. Both are defensible. The deciding factor is whether a posted range already exists. If it does, negotiate against it. If it does not, flip first, and only name your own number when they will not name theirs.

How this goes wrong

The failure modes are specific and mostly quiet. They rarely feel like mistakes in the moment, which is exactly why they cost money. Here are the documented ways candidates lose the pay exchange, and the check that catches each one.

• Misreading tense. "Did your previous salary meet your needs?" sounds friendly but is a history probe. Treating it as small talk and answering is the false positive. Check: any reference to your past or current pay is history, regardless of tone. FindLaw flags exactly these as disguised violations.
• Assuming voluntary disclosure is safe. Volunteering your number can trigger adverse selection, and once said it can be used against you. Check: never offer a past figure unprompted. The law forbids the employer from prompting it, but the downside of blurting it falls on you.
• Over-wide range. A 60k to 120k range reads as "I don't know my worth," and they anchor at the floor. Check: keep the spread tight and top-anchored, because whoever names a number first gives an anchor.
• Anchoring low in the screen. Early filter answers become the number of record. Check: only give a range you would accept the bottom of.
• Refusing flatly. A hard "I won't say" reads as evasive. Check: always pair the decline with a redirect to the role or their range.
• Assuming your state banned it. Michigan and Texas have no private ban, so citing a nonexistent law backfires. Check: confirm your specific jurisdiction before you invoke the law.
• Confusing verification with a pay ask. A background check confirming dates, titles, and rehire eligibility is not a pay-history violation. Check: distinguish "confirm employment" from "confirm compensation." Note that Illinois makes it unlawful to seek wage history even during a reference check.
• Instant-accepting an offer. Signals they overpaid. Check: pause and evaluate the full package, because the instant yes tells them they could have gone lower.

The matrix below sorts your options by the two variables that actually govern the decision: whether the question points at your past or your future, and whether you are being asked to go first or being handed a range.

Why silence is safe and secrecy is a myth

You are not legally required to answer a pay question, and refusing to state your history cannot lawfully be held against you in the ban states. About 50% of American workers report that their employers prohibit or discourage discussions of wages, which conditions people to assume they must comply. That conditioning is wrong on the law.

In the ban states it is unlawful for an employer to discriminate against you because you decline to answer the salary-history question. The federal protection for discussing wages and the state bans mean your silence carries no legal penalty. Combine that with the recruiter-to-comp-specialist ratio from Refolk's index, and the picture is clear: the person asking usually cannot punish a redirect and often has the range they are supposedly protecting.

The penalties for asking illegally fall on the employer, not you. Here is what that looks like where it has been documented.

You will not enforce these in the interview, and you should not threaten them. But knowing the asymmetry changes your posture. The employer carries the legal risk; you carry only the risk of anchoring yourself low. Recording the wording and timing of an unlawful ask, as the last procedure step says, is what makes any later complaint credible.

What to do next and how to keep it current

Turn this reference into a one-page card you carry into every loop, then re-check the two facts that move. The card is your jurisdiction row and your researched target range; both go stale, and both are cheap to refresh.

Two things are genuinely time-sensitive, so check them rather than trusting a remembered value. First, the ban list grows: Virginia's combined ban and posting rule took effect July 1, 2026, and municipalities keep adding their own, so re-confirm your jurisdiction against a current running list before a search. Second, your market range drifts, so rebuild it from live sources each cycle rather than reusing last year's number.

If you want to see who will be running your screens, Refolk can surface the exact people on the other side of the pay question before you ever pick up the phone.

The reference does not change what you are worth. It changes how fast you can protect it. When the question comes, classify the verb, check your row, and redirect. The rest is just holding your range.