# The Interview Pay-Question Decoder, Question by Question

*You can match any pay question to its type, name what it screens for, and give a safe answer that neither anchors you low nor triggers a filter.*

- Canonical URL: https://www.refolk.ai/candidates/guides/interview-pay-question-decoder
- Pillar: Interviewing
- Format: Reference
- Published: 2026-08-22
- Last reviewed: 2026-08-22
- Reading time: 8 min

A money question just landed in a live interview and you need to know what it is actually testing before you answer. This reference is for candidates from the recruiter screen through the final round who want to match any pay-adjacent question to its type, name whether it is a budget knockout, an anchoring probe, a leverage probe, or a total-rewards probe, and deliver a safe answer. Jump to the row you need; every one tells you what the question screens for, the safe answer pattern, and the specific way it misleads you.

Most published guides handle one move: the current-salary decision, the staged expectations answer, or the written application field. So a candidate who gets asked "are you flexible?" or "what would it take?" has nowhere to jump. This is the full catalog of every money question asked out loud, one row each.

## Who is actually asking the pay question?

The first pay question is almost never asked by a pay expert. It is asked by a recruiter running a budget filter, and that changes what a good answer looks like.

In Refolk's index of professional profiles, there are roughly 24 times as many recruiters as dedicated compensation specialists in the United States. That ratio is the single most useful fact for reading a live pay question: the person on the line is confirming you fit a band, not modeling your total rewards.

| Role / market | Count |
|---|---|
| Recruiters, US | 109,586 |
| Compensation analysts and managers, US | 4,589 |
| Recruiters, UK | 6,992 |

**23.9x - US recruiters per dedicated compensation specialist**

Derived from Refolk's index; the first pay question is almost always a budget filter, not a comp analysis.

A recruiter typically spends 15 to 30 minutes on a screen confirming you have the must-haves, that your salary fits the budget, that you seem easy to work with, and that you are interested. Phone interviews run roughly 15 to 40 minutes. Nobody on that call is optimizing your equity mix. Read the question as a filter, clear it, and save the mechanics for the people who own the offer.

> **Note:** The screener is not the decision-maker
>
> The recruiter is usually not the hiring manager and rarely the technical expert. A clean deflection-then-range clears their filter without dragging you into comp mechanics they cannot resolve anyway.

## The four types of pay question

Every money question asked out loud falls into one of four types. Name the type first, because the type dictates the answer far more than the exact wording does.

No single published source offers this taxonomy; it is a synthesis grounded in the intents each question is documented to carry. Here are the four, with the giveaway phrasings.

- **Budget knockout.** "What are your salary expectations?" "What's your desired compensation?" A filter to avoid advancing candidates who want more than the budget holds. Land way over and the interview ends there.
- **Anchoring probe.** "What are you currently earning?" "Just give me a number." A maneuver designed to anchor you to the lowest possible figure, because whoever names a number first tends to lose control of the bargaining zone.
- **Leverage or timing probe.** "Do you have other offers?" "Are you interviewing elsewhere?" A read on where you are in your search and how fast they need to move.
- **Total-rewards probe.** "Are you flexible on salary?" "What would it take?" A test of whether base is your only lever or whether you will trade it against equity, bonus, and benefits.

#### Reading a pay question in order

1. **Stage** - Which round you are in sets your leverage
2. **Type** - Budget, anchor, leverage, or total-rewards
3. **Intent** - What the asker screens for
4. **Move** - The safe answer pattern for that combination

*Identify the type before you draft a word of your answer; the type carries more weight than the phrasing.*

The "desired compensation" phrasing is worth flagging because it means the same thing as expectations: it is a budget knockout, usually appearing early, and it wants a number it can filter against. Treat it exactly as you would "what are your salary expectations."

## Stage changes the answer more than the words do

The same question deserves a different answer depending on when it is asked. Speed early, deliberation late: at the screen you have no leverage and are clearing a filter, so you deflect once and give a range; by the time a hiring manager clearly wants you, you hold your anchor and tie every number to scope.

Pay expectations can surface as early as the first phone screen, so be ready from the moment you apply. But readiness at the screen means having a range, not defending it to the last dollar. That comes later.

| Stage | Leverage | Recommended move |
|---|---|---|
| Recruiter screen | None | Deflect once, then give range low-anchored |
| Hiring manager | Growing | Restate at upper end, tie to scope |
| Final / pre-offer | High | Hold anchor, use silence |

There is a real disagreement in the published guidance here. Some sources argue you should postpone all numbers until a formal offer; others say be ready to give a range at the screen. The stage split reconciles them: postponing works once you are wanted, but at a screen with no leverage, endless postponing gets you filtered as evasive. Deflect once, then answer.

> **Rule:** Spend the anchor once you are wanted
>
> Deflect at the screen, anchor at the final round. An early anchor raised pay in the research but lowered trustworthiness ratings, so you pay a reputational cost if you drop a hard number before they have decided they want you.

## The row-by-row decoder

Match the question you were asked to its type, then use the pattern. Each entry names what it screens for and the specific way it misleads.

### "What are your salary expectations?" / "What's your desired compensation?"

**Type: budget knockout.** It screens whether your number fits the budget; land way over and the interview ends. **Safe pattern:** at a screen, deflect once ("Could you share the budgeted range so I can see if we're aligned?"), then give a researched range with your target at the bottom. **How it misleads:** it feels like an invitation to state your worth, but it is a filter. Naming a stretch number here gets you cut, not negotiated with.

### "What are you currently earning?" / "What did you make at your last job?"

**Type: anchoring probe.** It screens for a number to set the offer below. **Safe pattern:** redirect to expectations. "I'd rather focus on the value of this role. Based on the market, I'm targeting [range]." In jurisdictions with a salary-history ban, this question is legally off-limits, and you can say so. **How it misleads:** it is framed as routine paperwork. It is not. Your past pay is a floor they can nail you to that has nothing to do with this role's budget.

### "Just give me a number."

**Type: anchoring probe.** It screens whether you will name the first figure and lose control of the zone. **Safe pattern:** give a precise number at the top of your researched range, not a round one. Anchor with $118,500, not "around $120K," because recipients judge precise offers as more knowledgeable and counter them less aggressively. **How it misleads:** the pressure to be decisive pushes you to blurt a round, low, safe number. Precision and research beat speed.

### "Are you flexible on salary?"

**Type: total-rewards probe.** It screens whether base is your only lever. **Safe pattern:** pair flexibility with a researched number. "My base target is [number]; I'm open to discussing the full package around it." **How it misleads:** "I'm flexible" alone signals either no research or that you can be lowballed. Flexibility without a number is an invitation to the bottom of the band.

### "What would it take to hire you?"

**Type: total-rewards probe, tilting toward anchor.** It screens for your walk-away and your priorities. **Safe pattern:** answer in package terms tied to scope. "For the scope we discussed, base in [range], plus [equity/bonus] gets me excited." **How it misleads:** it flatters you into over-disclosing your true minimum. Answer with your target, not your floor.

### "Do you have other offers?" / "Are you interviewing elsewhere?"

**Type: leverage or timing probe.** It screens where you are in your search and how fast they must move. One recruiter says they were taught to ask this to see whether the candidate needs to hurry a decision or has time to evaluate others. A senior director at recruiting firm Hunt Club put the loyalty myth to rest: "If I'm not interested in you, I don't care if you're interviewing with someone else." **Safe pattern:** "I have other opportunities I am actively pursuing," which is true and creates urgency. **How it misleads:** it feels like a loyalty test, so candidates either downplay their search or name a competing figure. Naming a competing number before they want you hands them an anchor to beat down.

```pull
The other-offers question is a timing tool wearing the costume of a loyalty test.

## Frequently asked questions

### How do I answer salary expectations in an interview without lowballing myself?

Give a researched range, not a single figure, with your real target at the bottom so the whole band reads as reasonable. On a recruiter screen, deflect once by asking for their budgeted range, then hand over your range if they press. Use a precise number rather than a round one, since precise offers are judged as more knowledgeable and draw less aggressive counters.

### The recruiter asked my salary range on the phone screen. What do I say?

Treat it as a budget filter, not a negotiation. Deflect once: "I'm flexible depending on the full scope. Could you share the budgeted range so I can see if we're in the same ballpark?" If they still need a number, give your researched range with your target near the bottom. Deflecting forever reads as evasive to experienced recruiters, so deflect only once at the screen.

### What does 'are you flexible on salary?' really mean?

It is a total-rewards probe testing whether base pay is your only lever or whether you will trade it against equity, bonus, and benefits. Saying only "I'm flexible" signals no research or that you can be lowballed. Pair any flexibility with a researched number: name your base target, then say you are open to discussing the full package around it.

### How should I answer 'do you have other offers?'

Signal demand honestly without naming figures. Say "I have other opportunities I am actively pursuing," which is true and creates timing pressure. It is usually a timing tool, not a loyalty test. Never name a competing offer's number before they have decided they want you, because that hands them an anchor to beat down and can dent their read of your trustworthiness.

### Is it legal for an employer to ask what I currently earn?

It depends on jurisdiction. Salary-history bans restrict employers from asking what you used to earn or using it to set an offer. As of August 12, 2026 one tracker lists eighteen states plus D.C. with statewide restrictions, with Virginia effective July 1, 2026. Massachusetts passed the first ban in August 2016. Expectations questions are legal everywhere. Confirm your specific state before your call.

### What if they say I'd be 'maxed out' at their number?

Treat it as a negotiation move dressed as a warning, not a fact. The company itself declared what the seat can pay when it set the range, so hold your anchor rather than shaving it. A suspiciously wide posted band, like $70,000 to $180,000, is a hedge, and the real budget often sits near the bottom, so push them to name the level-specific figure.

---

*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/interview-pay-question-decoder*