# The Recurring Salary Ask, One Loop Carried to a Number

*You will know exactly what to say when salary is asked at the recruiter screen, the manager round, and pre-offer, and how each answer moves or locks your final number.*

- Canonical URL: https://www.refolk.ai/candidates/guides/recurring-salary-ask-one-loop
- Pillar: Interviewing
- Format: Teardown
- Published: 2026-08-24
- Last reviewed: 2026-08-24
- Reading time: 16 min

You keep getting asked your salary expectations. First on the recruiter screen, then again in the hiring-manager round, and now a third time as the offer nears. This guide carries one real loop through all three asks - the words used, the numbers on the table, and the wrong turn that anchored a candidate low - so you can follow along on your own case rather than re-read general advice you already deflected with once.

The reader here is mid-loop. You have a floor in mind, you have deflected already, and you want to see how each successive answer moves or locks the final figure. So this is a teardown, not a lecture. I will name the mechanism at each fork, show the number it produced, and mark the false turns.

## Why the same question comes back three times

Being asked salary repeatedly is a budget filter, not a sign you answered wrong. The recruiter is checking band fit before spending panel time, and a common practitioner pattern is that recruiters ask roughly three times before they open with a number of their own.

The scarcity behind the repetition is structural. In Refolk's index of professional profiles, there are 20,467 US technical recruiters against 346,159 US software engineers, which works out to about 16.9 engineers per recruiter. A single recruiter is running many requisitions at once - practitioner accounts put it at 20 to 40 or more - so the salary question is a fast disqualifier they reach for early and often. Read the repetition as routine, not as an invitation to renegotiate against yourself.

**16.9 - US software engineers per US technical recruiter in Refolk's index**

346,159 engineer profiles against 20,467 recruiter profiles - one recruiter screens many candidates fast, and salary is the fastest filter.

That aggregate ratio also frames your leverage honestly. Individual candidates are plentiful, so eloquence alone moves the number less than alternatives do. Firms settle at the higher end of a range when they think you are outstanding, and more so when you already have a competing offer. The three-asks pattern is where you protect your range; the counter at the end is where a real alternative earns you the top of it.

> **Note:** The recruiter usually cannot set the number
>
> The recruiter filters you against a band; the hiring manager and finance set the band. Negotiating hard with the person who can only screen you wastes the leverage you should be spending later.

## The worked loop: one candidate, three asks, one number

Here is the case I will carry the whole way. The role is a backend software engineer position. The posting range, learned later, was $60,000 to $100,000. The candidate's own floor - the number below which they would decline - was $90,000. That single fact is the load-bearing detail, and it is where the loop went wrong.

The mechanism to watch is anchoring: the first figure introduced into a negotiation tends to pull the final outcome toward it. A meta-analysis by Orr and Guthrie (2005) reported a .497 correlation between initial offers and final negotiation results. The effect does not vanish when people are experts or warned - even real estate agents who knew about anchoring still let arbitrary listing prices move their valuations (Northcraft and Neale, 1987). So whichever number lands first, yours or theirs, sets the reference the other side adjusts insufficiently away from.

#### The recurring ask across one loop

| Stage | Figure | Note |
| --- | --- | --- |
| Recruiter screen | 3 asks | reverse to budget, then a tight range if pressed |
| Hiring-manager round | 1 ask | restate the range, do not re-anchor down |
| Pre-offer wrap-up | 1 ask | refined figure at top of range |
| Written offer | 1 counter | negotiate up at least once |

*The same question narrows the number at each stage, and the earliest answer casts the longest shadow.*

In the documented case, the candidate stated $90,000 at an early ask. That was their floor - about $10,000 under the top of the posting's stated range. Four more interviews followed, and the offer came in near the number they had named. The floor had become the ceiling. Nothing they did in the later rounds recovered the ground given away in that one sentence.

> Name your floor as your range and the floor becomes the ceiling.

## Ask one: the recruiter screen

At the screen, deflect once by reversing to the role's budget, and give only a tight range if pressed. The first ask almost always lands here, on the 15 to 30 minute pre-screen call, before real interviews begin. This is the highest-value place to hold, because it is the earliest number and therefore the strongest anchor.

The escalating language, in order, looks like this. First deflection: "Sorry, what was the budget of the role again?" Second: "I understand you want to know my expectations, but may I know the budget for the role, please?" If the recruiter comes back a third time, do not refuse - flat refusal reads as evasive and can screen you out. Give a range instead.

**Screen-stage salary responses, in escalation order**

```
First ask (reverse it):
"Before I give you a number that might be off from how you've scoped this, what range is budgeted for the role?"

Second ask (acknowledge, then reverse again):
"I understand you need my expectations to move forward. Can you share the band you're working against so I can tell you honestly whether we're aligned?"

Third ask (give a tight range, top-weighted):
"Based on the market for this scope, I'm targeting $105,000 to $112,000, and I'd want to confirm the responsibilities before pinning it down. Is that within the role's range?"
```

*Use them in sequence. Stop as soon as they name a band; only reach the range if they ask a third time.*

Two disciplines make that range safe. Keep the spread under $10,000 - a wide range lets the employer hear only the bottom, which functionally re-anchors you at its floor. And set the low end at a number you would be happy to accept, never at your walk-away floor. If your stated low end is a number that would make you unhappy, raise it before you say it out loud.

In the worked case, this is the exact step that failed. The candidate skipped the reversal, treated the recruiter's pressure as a demand for their bottom line, and offered $90,000 - their floor. Had they reversed to the budget, they would have learned the range topped out at $100,000 and could have stated $95,000 to $100,000 without ever exposing the floor.

> **Watch out:** Do not state your floor as your low end
>
> Your floor is the number you would decline below. If you say it out loud as the bottom of a range, the employer treats it as your expectation and adjusts down, not up. State a range whose bottom you would gladly sign.

## Ask two: the hiring-manager round

At the hiring-manager or panel round, restate the range you already gave and do not reopen it unless the scope you have since learned is genuinely larger. The second ask often surfaces here, days or weeks after the screen. The trap is subtle: repeating a low screen number here locks it in, and re-answering from scratch invites a fresh, lower anchor.

If a range was agreed at screening, there is no reason to reopen it. The one legitimate exception is scope discovery - if the round revealed the job is materially bigger than described, you may say the range moves with it. Otherwise, restate and move on:

**Hiring-manager restate line**

```
"On compensation, I mentioned $105,000 to $112,000 to [recruiter] earlier and that still fits. If anything, hearing today that this role owns [the on-call rotation / the data pipeline / the team's roadmap] puts me toward the top of that."
```

*Adapt the range to match what you said at the screen. Only invoke the scope clause if the job genuinely grew.*

This round is also where you gather the justification you will need at the offer. Note the responsibilities that were not in the posting. Each one is evidence you can attach to your pre-offer number so the figure arrives with a reason, not just a demand.

## Ask three: the pre-offer wrap-up

At the pre-offer stage, present a refined single or near-single figure at the top of your researched range, grounded in the responsibilities you have now discovered. This is the third ask, and by now you have earned the right to be specific. The coaching consensus across stages runs from a wide-open range at the screen to a tight, justified number here.

The table below is the precision ladder. Match your answer to the stage; giving a single hard number too early hands over your anchor, while staying vague too late reads as unprepared.

| Stage | Expected precision |
|---|---|
| Recruiter screen | Tight range, spread under $10k; ask for their band |
| Hiring-manager round | Restate the range; do not re-anchor down |
| Pre-offer | Refined single or near-single figure at top of range |

There is a real disagreement in the sources about ordering. Most say the ask lands at the screen; Indeed's employer-facing guide advises interviewers to discuss salary expectations after the qualitative interview questions. You cannot control which order your loop uses, so the rule is about behavior, not timing: whenever the ask lands, deflect the first, restate the second, and refine the third.

#### What each ask is actually for

1. **Screen ask** - Budget-fit filter - protect your anchor, learn their band
2. **Manager ask** - Scope confirmation - restate, gather justification
3. **Pre-offer ask** - Number lock - state a refined figure last, at the top
4. **Written offer** - Negotiation - counter with your justification attached

*The same question serves a different purpose at each stage, so the right answer changes even though the words repeat.*

## The follow-along procedure

Run your own loop against these five steps. They match the case above: prep, screen, manager round, pre-offer, and counter.

#### Carry your loop from prep to signed number

1. **Set your floor and range before the loop** - Research the market range and set a floor you will not go below, then build a tight target range above it. Check whether your state or city bans salary-history questions. Done when you have a target range, a floor, and know the local legal rule.
2. **Handle the recruiter screen ask** - The first ask lands on the 15 to 30 minute screen. Deflect once by reversing to the role's budget; if pressed a second or third time, give a tight range with the spread under $10,000. Done when you have learned their band or stated only a range, never a single low number.
3. **Hold the line at the hiring-manager round** - The second ask often comes here. If a range was agreed at screening, restate it and do not reopen unless the scope you have since learned is materially larger. Done when you have not re-anchored downward.
4. **Present a refined figure pre-offer** - The third ask is the wrap-up before an offer is drafted. Present a refined single or near-single figure at the top of your researched range, grounded in the responsibilities you have discovered. Done when your number is stated last and justified by scope.
5. **Counter the offer at least once** - When the written offer arrives, counter it rather than accepting the first number; 42% of hiring managers are comfortable with increases in the 10% to 25% range. Pair the ask with justification. Done when the offer is accepted at or above your target.

Step one carries a legal wrinkle worth its own moment. Salary-history bans exist in 21 states and territories plus 22 cities and counties, but they cover past or current pay, not your expectations. So the ban does not shield you from the number-first question. The table below shows how the rule varies by example jurisdiction.

| Jurisdiction | Rule for candidate |
|---|---|
| California | Statewide ban on pay-history questions |
| Maine | Pay history only askable after an offer |
| Michigan | No ban; local bans prohibited |
| Virginia | Statewide ban effective July 1, 2026 |

Maine is the strictest: employers may ask about compensation background only after an offer of employment and salary has been made. Michigan runs the other way, barring cities and counties from imposing bans, so private employers there may legally ask about prior pay. Virginia's statewide law takes effect on a set date, so if you are reading this near that boundary, confirm the current status against a running legal list rather than trusting the date alone.

> **Rule:** Bans cover history, not expectations
>
> Even in a ban state, decline your past pay but still handle the expectations question. Refusing to answer either one reads as evasive. Know which your statute covers before the call.

## How this goes wrong: the failure modes

Most lost money traces to one of a handful of specific errors, and the first one is the trap the worked case fell into. Here is each failure, what it looks like, and the check that catches it.

- **Giving your floor as your range.** The documented case named $90,000, their floor, inside a $60,000-$100,000 posting, and the floor became the ceiling. Check: is your stated low end a number you would be unhappy accepting? If yes, raise it.
- **Treating expectations as history.** In ban states you can decline history but must still handle the expectations question. The false positive is refusing to answer at all and reading as evasive. Check the specific statute for what it actually covers.
- **Re-anchoring at the hiring-manager round.** Repeating a screen number that was low locks it in, and re-answering fresh invites a lower anchor. Check: only restate; renegotiate the range solely if scope grew.
- **An aggressive first anchor backfiring.** Early anchors raised pay but lowered employability and trustworthiness ratings in the research. Check: pair the number with justification, not just a big figure.
- **Fake application-form numbers.** The "0" or "999999999" placeholder tactic can auto-reject you in ATS filters. Check whether the field is a hard filter before using placeholder values.
- **Assuming the recruiter has budget authority.** Recruiters filter against a band; the manager and finance set it. The false positive is negotiating hard with someone who cannot move the number.
- **Never countering at all.** More than half of workers, 55%, do not ask for a higher salary when offered a new position. Check: did you counter at least once?

The regret data shows how common these are. In a Resume Genius survey of 1,000 US workers and 1,000 hiring managers, 57% of workers regret how they negotiated, while a CareerBuilder figure puts 73% of employers as willing to negotiate. Most candidates leave money the other side had already budgeted to give up.

**57% - of US workers regret how they negotiated their salary**

Against 73% of employers who say they would have negotiated - the gap is money left on the table, not money that was never there.

The anchoring trap and the aggressive-anchor trap pull in opposite directions, which is why the judgment matters. Plot your first number against how well you can justify it.

#### Where to place your first stated number

Horizontal axis runs from Low number to High number. Vertical axis runs from Weak justification to Strong justification.

| Quadrant | What it means |
| --- | --- |
| Under-anchored, no reason | Worst money outcome - you set a low ceiling for nothing |
| High but unsupported | Reads greedy - raises pay but lowers trust ratings |
| Low and justified | Leaves money on the table but stays likeable |
| High and justified | Target - top-of-range ask backed by discovered scope |

*An aggressive number without justification costs likeability; a low number without justification costs money.*

## Benchmark your number before the screen

Before you set the range in step one, benchmark it against real peers who recently moved. Your target range is only credible if it reflects what people with your profile actually got, not a posting midpoint or a gut number. Peers who changed jobs in the last year are the sharpest comparable, because their number reflects the current market and a live negotiation, not a stale salary survey.

The friction is finding those peers. Public profiles carry titles, employers, and move dates, but assembling them into a usable comparison by hand is slow. This is where a plain-language search over Refolk's index removes the legwork: describe the peer group and get back people who match, so you can see who moved, from where, and to what kind of company.

Ask me this: `Find senior software engineers in the San Francisco Bay Area who changed jobs in the last year` - [run the search](https://www.refolk.ai/start?q=Find%20senior%20software%20engineers%20in%20the%20San%20Francisco%20Bay%20Area%20who%20changed%20jobs%20in%20the%20last%20year).

*Returns peers who recently negotiated a real move, so you can ground your target range in current comparables rather than a posting midpoint.*

You can also point the same tool at the other side of the table. Searching for the technical recruiters and talent leads who run screens at your target companies tells you who will ask the salary question and what they source for, which lets you walk into the screen already knowing the band's likely shape. If you want the screening logic behind who is asking, [Refolk](/candidates) also tailors your resume and scores your fit for each posting, so the number you name at the screen sits on a story that supports it.

Note the leverage math again while you benchmark. In Refolk's index, US technical recruiters outnumber their UK counterparts by about 30.5 times - 20,467 against 672 - which tells you nothing about your pay directly but everything about how differently these markets are staffed. Where recruiters are thin, more of the negotiation runs through the hiring manager; where they are dense, the screen filter is sharper and the three-asks pattern more mechanical.

| Segment | Profiles | Derived ratio |
|---|---|---|
| US Software Engineers | 346,159 | 16.9 engineers per US recruiter |
| US Technical Recruiters | 20,467 | baseline |
| UK Technical Recruiters | 672 | US = 30.5x UK |

## Before you take the next call

Run this check before your next salary conversation, whichever stage it lands at. It is the shortest path from this guide to a number you will not regret.

#### Salary-ask readiness check

- [ ] My floor is written down and I will never state it as the low end of a range.
- [ ] My screen range has a spread under $10,000 and a bottom I would gladly accept.
- [ ] I have a reversal line ready to ask for their budget before I give a number.
- [ ] I know whether my state or city bans salary-history questions and what the ban covers.
- [ ] I have benchmarked my range against peers who moved in the last year, not a posting midpoint.
- [ ] I have noted the extra responsibilities from each round to justify my pre-offer figure.
- [ ] I have a counter planned for the written offer, aimed within the 10% to 25% range.

Keep this current by re-checking two things. The salary-history legal landscape shifts as new statutes take effect, so verify your jurisdiction against a running list rather than a fixed date. And your target range decays as the market moves, so re-benchmark against fresh peer moves each time you enter a new loop. The method holds; the numbers under it do not.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/recurring-salary-ask-one-loop*