The Interview-Loop Pay Conversation, From Screen to Offer Setup

Managing pay across an interview loop is one job, not one question. This guide is for a candidate who is in an active loop right now and wants to reach the offer without being screened out on budget or anchored to a low number before they have leverage. It stages the whole conversation across every gate - recruiter screen, hiring-manager round, later rounds, and pre-offer - with what to say, ask, deflect, and record at each, plus the point at which a range mismatch should end the process.

Most public articles grade one canned reply to "what are your salary expectations?" in isolation. A live loop is a sequence of gates, each with a different person, a different amount of your leverage, and a different risk. Answer well at the screen and badly at the panel and you still re-anchor yourself downward. This is the reusable procedure you run from the first call to the offer setup.

Why compensation shows up first, and what that tells you

Compensation almost always lands at the recruiter screen, the opening stage of the loop, and often near the top of the call. One recruiting-prep source describes it as frequently the second question out of the gate, asked up front on purpose so nobody burns an afternoon on a number that was never going to work. Google's published software-engineering loop confirms the screen covers background, role fit, compensation expectations, and timeline together.

The reason matters more than the timing. The screen is a budget filter, not a fit test. A mismatch is the cheapest thing to disqualify on early, and doing it first protects the recruiter's calendar, not yours. That is exactly why the deflect-then-ask move exists: you are not dodging a fit question, you are declining to hand over information that only helps the other side.

The information asymmetry is mechanical. Whoever names a real number first has given the other side something they wanted. A recruiter who tells you the range first has shown you their ceiling. A candidate who names a figure first has shown the recruiter their floor. That asymmetry, not etiquette, is why asking for the band beats answering with a number.

There is one large exception. In a growing minority of markets, the law shifts the first move to the employer. Where a posting must carry a range, the anchor is already published and you simply read it. So before you rehearse any script, check whether your location has already answered the question for you.

Who actually runs your screen

The person quoting your band is usually scarce senior talent operating inside a fixed budget, which means they often cannot move the number alone. That single fact reshapes how you handle a gap: you ask them to advocate upward, you do not haggle with them on the screen as if they set the ceiling.

In Refolk's index of professional profiles, the US shows 113,366 profiles under recruiter, technical recruiter, and talent acquisition titles, against 3,685 at Head, Director, or VP of Talent Acquisition level. That works out to roughly 31 frontline recruiters per senior talent-acquisition leader. The recruiter on your call is far more often a frontline coordinator than a budget owner.

Table B - US recruiting workforce shape (who holds the budget)

Column source: both counts from Refolk's index, from separate title queries; the leadership share is derived and approximate because the two queries use different title lists.

Market also changes who you meet. The same index returns 7,423 comparable UK recruiter and talent-acquisition profiles, roughly 15.3 times fewer than the US. In a thinner market you are more likely to deal with an agency recruiter or a generalist, which changes who owns the band and how directly they can escalate it.

Table A - Recruiter/TA workforce, US vs UK

Column source: profile counts from Refolk's index (recruiter, technical recruiter, and talent acquisition titles); the multiple is derived.

If you want to see who runs the screens in your target segment before you get on a call, you can search for them directly. Refolk reads public professional records so you can find the people who hold the budget in a specific market and stage.

Whether your jurisdiction has already answered the question

Where the law forces disclosure, you deflect less and read more. Pay transparency laws exist in 27 US jurisdictions per one tracker, and 18 states plus DC per another, so the count depends on the source and date. What matters for your loop is the trigger point, because triggers differ sharply.

Some laws mandate a salary range in every job posting, others require disclosure only on request or after an interview, and a third category forces a range automatically at a set point such as when an offer is made. That spread means the same move is right in one state and wrong in the next.

Table C - Pay-range disclosure trigger by jurisdiction

Column source: postercompliance (CA, CO), paycom (HI), fingercheck (DE). Trigger and threshold as published on those pages.

Salary-history bans are a separate category, covering 18 states plus DC per one list, and Massachusetts passed the first in August 2016. These matter because of a trap: a history ban forbids the employer from asking your past pay, but it does not forbid you from volunteering it. The protection is one-directional.

The full loop, stage by stage

Run the same discipline at every gate, but the move changes because your leverage and the person change. The table below is the map; the procedure that follows is how you execute it. Most loops run two to five distinct stages before an offer, and a typical five-stage shape is recruiter screen, hiring manager, skills assessment, onsite or final panel, then reference check.

The funnel percentages track the survey distribution of how many rounds loops run: three interviews is the most-cited average before an offer, 22 percent say four, and 9 percent report five or more. Read the stages as the points where pay can come up, not as fixed volumes.

The two-tier deflection

At the screen, use a two-tier script. Tier 1 is the question-for-a-question. Tier 2 is only for when the recruiter will not proceed without a number.

Tier 1 (opening move):
"I'm happy to talk about pay. Could you share the range you've budgeted for this role?"

Tier 2 (only when pressed for a number):
"Based on my research for this role and level, I'm targeting a range of [X] to [Y]."
- Give a range, never a single figure.
- Place your actual target at the BOTTOM of that range.
- Never lead with your true minimum.

At the hiring-manager round, if asked again:
"I provided a range earlier in the process - has that changed anything on your end?"

The reason the range matters: a single number becomes your floor, and the offer builds down from budget rather than up. State X to Y, with your target at the bottom, so the whole band pulls the offer upward.

The procedure, screen to offer setup

Run these steps in order for one loop. Each has a rough time cost and a clear "done" state so you know when to move on.

One order disagreement is worth naming. Some sources advise deferring salary talk until after an offer; screening-call practitioners and forum threads argue for confirming the band on the first call to avoid a wasted loop. My read is that the two are not in conflict: you ask for the band at the screen to filter, and you confirm it in writing pre-offer to protect it. You commit your own number only at the offer.

Ask for the band to filter, confirm it in writing to protect it, and commit your own number only at the offer.

There is also a genuine leverage window near the end. References have become a pre-offer gate that can add several days, so there is a real interval between "finalist" and "offer" in which to confirm the band in writing before any number is committed. Use it.

What to record, and why

A formal capture checklist is not standardized in the public sources, but the discipline is what keeps you consistent across weeks and multiple interviewers. Log four fields per pay exchange so no later stage catches you contradicting yourself.

Stage: (screen / HM / panel / pre-offer)
Who asked: (name and role)
Exact wording: (what they said, quoted)
Band quoted: (their range, or the range you gave)

How this goes wrong

The failure modes below are where a well-prepared candidate still loses the number. Each has a tell and a check. Give this section real weight, because knowing the trap is most of the fix.

• The posted range is soft. A band on a posting can be tiered or wider than the real budget, so it is a guide, not a promise. What it looks like when it lies: a wide public range that collapses to a narrow real budget at the offer. Check by asking the recruiter to confirm the band live.
• You blurt a number under pressure. The most common failure. Someone with a clear target opens their mouth and a lower figure falls out. The tell is that you feel obligated to fill the silence. Check: rehearse the Tier 1 line verbatim before the call.
• You put your target at the top of the range. A "confident" high number reads as out of budget and gets you screened out. What it looks like when it lies: you think you are anchoring high, but you are triggering a filter. Fix: put your target at the bottom of the stated range.
• You give a single figure, not a range. One number becomes your floor and the offer builds down from budget. Check: always state X to Y.
• You answer comp with the wrong person. Some firms restrict pay talk to the recruiter or HR, and re-answering to a panelist can re-anchor you. The tell is a technical interviewer asking about money mid-round. Check: route pay questions back to the recruiter.
• You treat a dodged band as neutral. A recruiter who will not share a range after you ask is a signal, not a delay. One account ran the full onsite and was then rejected on a too-low offer. Check: ask once; if it is dodged twice, weight it as a red flag.
• You assume the law protects you. Salary-history bans forbid the employer asking, not you volunteering. The tell is thinking "they legally can't ask, so I'm safe." Check: do not volunteer your past pay even where asking is banned.

Reading a gap: escalate, or walk

A gap between your target and their budget is usually a lever, not a wall. A candidate whose expectations sit 20 percent above the top of a budgeted range may trigger an up-level or added budget rather than a rejection, because the recruiter can advocate for more or reslot the role. The walk-away is the employer's refusal to share a band, not the gap itself.

The matrix below sorts the two variables that actually decide your move: how large the gap is, and whether the recruiter will name a band at all.

Because the recruiter is one of roughly 31 frontline people per talent-acquisition leader, escalating a 20 percent gap means asking them to carry it upward, not negotiating with them as if they set the ceiling. Frame it as a request they can take to the budget owner.

Remember also what moves a candidate at equal base pay. In one published salary survey, 64 percent said work-life balance and remote perks could move them even at equal base, and 63 percent said the same of bonuses and profit-sharing. If the base band is fixed, that is where a gap can still close, which is why you confirm total-comp components pre-offer, not just the base.

Before you call the loop done

Run this checklist before your final round and again before you respond to any offer. It is the fastest way to catch a pay mistake while you can still fix it.

Keeping this current

Two things in this procedure move, and both are checkable locally. First, the jurisdiction rules: the count of transparency and salary-history-ban states shifts as new laws take effect, and trackers disagree on the total. Before each loop, re-read the current posting requirements for the state the role is in rather than trusting a remembered number. Newer disclosure states keep being added, so the map you used last quarter may already be stale.

Second, the market range. Comp bands drift by role, level, and location, so refresh your target and floor from current public benchmarks before every new loop, not once a year. When you tailor an application to a specific posting, that is also the moment to lock in the range you will defend, and Refolk can pull your history and the posting together so your prepared number matches the role you are actually applying to. The procedure stays fixed; the numbers you carry into it should be current every time.