The Interview Pay Answer Standard, Graded Before You Speak

Before you say a pay number to a recruiter or an interviewer, you get one chance to say it right. This guide is for candidates moving through a live loop, from the recruiter screen to the final round, who want a fixed bar to grade the exact sentence they are about to speak. It gives you a pass-or-fail rubric you can re-run at every stage so your answer stays consistent and never sets a ceiling on your eventual offer.

Most pay-answer advice is a list of sample scripts. Scripts do not tell you whether the specific words in front of you pass or fail, or why. A standard does. The difference matters because the leak, the low anchor, and the cross-stage contradiction all happen in the moment before you speak, and once the words are out the ceiling is set.

What a passing pay answer looks like

A passing pay answer is a researched range about 10 to 15 percent wide, with the floor set at or above your target, labeled as base, that volunteers no past or current pay figure and matches what you said at every earlier stage. If your sentence fails any one of those, it fails the whole standard, because a single leak is enough to cap your offer.

The logic behind each clause is simple. A single number forces a yes-or-no response and risks citing a figure too low, while a range gives the employer room to land somewhere you are satisfied with. If you name a number that is too low, you cap your offer at that number even if the budget was higher. Practitioners converge on a tight band: keep the range about 10 to 15 percent wide, for example $110K to $125K rather than $100K to $140K, and set the bottom at the minimum you would genuinely accept so even the low end is an acceptable outcome.

That case is the whole argument in one line. She anchored first, below her market floor, and the process settled near her number rather than the band's. Anchoring is the tendency to give too much weight to the first number put on the table and then adjust inadequately from that starting point. Your job is to make sure the first number the employer weighs is a defensible range, not a low single figure.

The four documented ways a pay answer caps your offer

Four failure modes are named consistently across practitioner sources, and every one of them is a way a candidate sets their own ceiling. Learn them as the four things a passing answer must never do.

The first is the single number, which forces a yes-or-no and anchors the offer to that figure. The second is the low anchor, where a number that feels modest sits below budget and caps you there. The third is volunteering current or past pay, which anchors the negotiation to the wrong figure and caps your raise. The fourth is inconsistency across stages, where a later answer contradicts what you already stored, and the recruiter may take the earlier, lower figure for budget approval.

This is the mechanism most candidates miss. The stored number, not the spoken one, sets the ceiling. Applicant tracking system fields persist across rounds, and a minimum entered early is retrieved at offer. That is why the discipline has to hold from the very first conversation, and why a "better" number offered later does not undo a low one given earlier.

The range and anchor rules, from the practitioner sources

The rules that separate a credible range from a self-capping one are narrow and well agreed. A range about 10 to 15 percent wide reads as research; a spread like $70K to $150K reads as a guess and undermines the credibility the number is meant to project. The table below is the working reference.

Two more phrasings self-cap even inside a range. Putting your target at the top of your range means the best plausible outcome is the number you actually want, with no upside. Sounding apologetic invites the employer to discount you. A passing answer sets the target at or near the bottom, so the whole band lives above your walk-away.

A tight range reads as competence. A meaninglessly wide one reads as guessing, and it undermines the very credibility the number is meant to project.

The stage rule: where the number is revisable and where it binds

The same number carries a different weight depending on where you are in the loop. On a recruiter screen the number is a screening input you can defer; at the offer it is a negotiating position. Grading your answer without grading the stage is how consistent people still get capped.

Sources disagree on how hard to deflect on the screen, and the disagreement is worth respecting. Some say deflect firmly because the earlier you are, the more room you have to avoid committing. Others warn that in practice recruiters ask directly and will not move to the next stage without a figure. The safe reconciliation: deflect exactly once by asking for their band, and have a researched range ready to give the moment they push. That way you neither anchor early nor screen yourself out.

The law protects the question, not your mouth

Salary-history bans restrict what the employer can ask and use; they do not stop you from disclosing, and a volunteered figure remains usable. Asking "what are your salary expectations" is usually legal and part of the process, while "what did you make at your last job" violates the law in a growing list of jurisdictions. But the protection is on their question, not your answer, so the discipline has to be self-imposed.

As of a 2026 review, 18 states plus Washington, D.C. restrict employers from asking about or relying on an applicant's pay history statewide. New York goes further and restricts questions about expected salary ranges, not just history. The jurisdictional detail varies enough that the only rule that travels everywhere is to never volunteer a past figure.

Because coverage changes, do not memorize a list. Re-check your own state and city before the loop opens, and treat the volunteering ban as absolute regardless of what you find. Legal protection covers the question, not your mouth.

The total-comp check: base is not the whole picture

A passing answer labels its number as base and leaves bonus, equity, sign-on, retirement, and benefits open, because collapsing everything into one figure discards the largest levers. If the prompt says "salary," read it as base unless it explicitly asks for total compensation. The risk runs both ways: a base number read as total undersells you, and a high number that secretly bundles equity gets read by the recruiter as base.

The components a passing answer must leave room for are standard: annual bonus targets, equity grants, sign-on bonuses, retirement contributions, health and wellness benefits, paid time off, professional development budgets, and relocation support. Benefits and perks alone can account for 33 percent or more of total compensation. A clean phrasing keeps them open: prefer a range because compensation depends on factors like equity, bonus structure, and benefits.

Tech candidates lose the most here. Senior roles can carry bonuses worth one to three times base, and with benefits above a third of the package, a single base figure throws away the biggest negotiable levers. The fix is one clause: say the number is base, and name that bonus and equity are open.

Who runs your screen changes the script

The recruiter across the table is not a uniform figure, and their knowledge of the budget band varies by who they are and where they work. In Refolk's index of professional profiles, the US pool of people currently titled Recruiter is large, but it splits into segments with different reach into pay decisions. Knowing the shape of that pool tells you how much budget-band knowledge to expect on the other end.

Two things follow. First, technical recruiters, who often know engineering bands precisely, are only about 23 percent of the general US recruiter pool in Refolk's index, and they cluster at named firms such as Experis, K2 Partnering Solutions, Snowflake, Google, and Blue Origin. A screen run by one of them may probe your number more sharply, so your range needs to be defensible, not aspirational. Second, market thinness abroad changes leverage: Refolk's index shows 14.1 times more US than UK recruiters titled Recruiter, and a thinner market means fewer parallel processes, so a hard deflection carries more screen-out risk where you have fewer other shots.

If you want to see who actually runs the screens for the roles you are chasing, Refolk will find them from a plain description.

Grade the sentence: the procedure

Run this before you speak, at every stage. It takes a few minutes the first time and under a minute once the range is set. Each step ends in a done condition you can check.

The deflection line is worth drafting word for word, because you will use it under pressure. Here is a version that asks for their range without sounding evasive, followed by the range you give if they push.

Deflection (use first): "Happy to discuss pay. To make sure I'm in the right zone, what range is budgeted for this role?"
If pushed for a number: "Based on my research for this level and location, I'm targeting a base of [floor] to [ceiling]. The exact figure depends on the full package - bonus, equity, and benefits - so I'd want to look at those together."
Never say: any current or past salary, a single exact number, or a range wider than about 15 percent.

How this goes wrong: the failure modes and their false positives

Every failure mode below has a false positive, a version that feels like a good answer while it caps you. The check column is what to verify on the sentence itself. This is the part of the standard you re-read most.

The most dangerous ones share a trait: they feel cooperative or confident in the moment. A round number feels safe, honesty about current pay feels helpful, a wide range feels flexible, and a better number given later feels like progress. Each is a trap.

Here are the specific false positives to catch:

• Low anchor disguised as modest. A safe-feeling round number that sits below budget. Check: is the low end still above your researched market floor? The £58,000 case cost £7,500 a year this way.
• Single number treated as a range. "$130,000" feels specific and confident. Check: does the answer contain two bounded figures? A range of $120,000 to $140,000 is stronger than $130,000.
• Meaninglessly wide range. "$70K to $150K" looks flexible. Check: is the band 10 to 15 percent wide? A wide spread reads as unfocused; a tight band matched to the level reads as credible.
• Volunteering current pay. Honesty feels cooperative. Check: does the sentence name any past or current figure? If yes, it fails even where asking is legal.
• Base and total-comp confusion. A high number that secretly bundles equity gets read as base. Check: is the figure labeled base with variable pay left open?
• Cross-stage contradiction. A better number given later that beats your application field. Check: does it match what is stored? Recruiters may take the earlier, lower figure for budget approval.
• Deflecting into a screen-out. Principled silence when the recruiter gates on a number. Check: after one deflection, do you have a researched range ready? Recruiters often will not advance you without a figure.

Refolk can carry your set range across every application form and stage so the consistency check passes by default rather than by memory, and can flag when a later answer would contradict an earlier one.

The pre-answer checklist

Run this the moment before you speak the number, at every stage. If any item is unchecked, do not say the sentence yet.

Keeping the standard current

The rubric is stable, but two inputs under it change, so re-check them before each loop rather than trusting a saved list. First, the jurisdiction rules move: Virginia's restriction takes effect July 1, 2026, and coverage tends to expand, so confirm your state and city before you interview. The volunteering ban, though, never changes and never needs re-checking.

Second, your market band ages. Pull fresh role, level, and location data before every search, because a range you set months ago may now sit below the market floor and quietly become a low anchor. Set the band once per search, grade every answer against it, and re-derive it when the market or your level moves. The discipline is not in remembering a number. It is in re-running the same seven checks on every sentence before it leaves your mouth.