RecrutFlo logoRecrutFlo
Create account
← All articles

Recruitment operations

Candidate Salary Expectations: How Recruiters Capture Them

By Andre · · 15 min read

Candidate Salary Expectations: How Recruiters Capture Them

Geometric cards converging into one salary record

Candidate salary expectations are the pay a person wants for a role. To use them well, ask after you have shared your own range, pin down exactly what the number includes, and store it in a structured form (minimum, maximum, currency, period) so you can compare it across applicants. This guide covers how to ask, what to clarify, what the law allows in the US, and how to stop retyping figures from CVs and emails into spreadsheets.

Recrutflo
Keep Salary Details Searchable
RecrutFlo organizes candidate information from CVs and shared inboxes into searchable profiles, helping teams find details without retyping them.

TL;DR

  • Salary expectations are what a candidate wants to earn. Salary history is what they earned before. In the US, asking about the first is generally allowed, while asking about the second is restricted in a growing number of places.
  • Share the approved range first, then ask. It is fairer to the candidate and gets you more honest answers.
  • Always clarify four things: base or total pay, gross or net, pay period, and which bonuses or equity are included.
  • Record every figure as minimum, maximum, currency and period, so applicants can be compared like for like.
  • If expectations arrive in CVs and emails, extract them automatically into searchable profiles instead of retyping them.

Table of Contents

What salary expectations are and why recruiters ask

Salary expectations are the compensation a candidate is looking for, shaped by their experience, market data and industry standards. The Muse notes that recruiters ask mainly to see whether the candidate’s requirements fit the budget for the role, so nobody wastes time on a mismatch.

Indeed’s hiring guidance lists the other benefits: spotting mismatches early, checking your pay range against what the market expects, building trust, and keeping the process consistent from one candidate to the next.

The number is a signal, not a verdict. A salary guide from a staffing firm makes the point that salary data is a benchmark, not a rulebook: urgency, specialization, leadership scope, benefits and local labor conditions all move the final offer. Treat the stated expectation as the start of a conversation about the whole package.

Expectations versus salary history

These two questions sound alike and are treated very differently by the law.

Salary expectations Salary history
What it asks What the candidate wants to be paid in this role What the candidate was paid before
Typical US legal position Generally permitted Restricted in a number of states and cities
What it tells you Fit with budget and priorities Past pay, which may reflect past bias
Risk for the recruiter Low, if framed neutrally Real, depending on location

CNBC’s explainer says that laws in some jurisdictions restrict asking about salary history, while employers are generally allowed to ask about expectations. That distinction is the foundation of a compliant process.

The US rules that change how you ask

Rules differ by state and sometimes by city, and they change. Check the current text before you set a process, and ask employment counsel if you hire across several states.

Two practical consequences follow. First, write your screening questions around the future (“What are you looking for in this role?”), never the past. Second, if you publish ranges in postings, you already have what you need to share early in the conversation.

If you hire candidates outside the US, the rules differ again, so treat each country on its own terms.

How to ask for salary expectations clearly

The approach that holds up in practice is simple: give context before you ask.

Glints’s recruiter guide recommends sharing the approved range first, using plain questions without pressure, and explaining the relevant parts of the package. Writer Alison Green has argued in Fast Company that asking for a number before giving a range is often unfair, because the candidate does not yet know enough about the responsibilities or benefits to price the job.

A short script that works

  1. Open with the range. “The budget for this role is $X to $Y base, plus a bonus plan. Does that fit what you’re looking for?”
  2. Ask for their figure. “What base salary are you targeting?”
  3. Ask what is behind it. “Is that base only, or does it include bonus or other pay?”
  4. Confirm the period and gross or net. “Is that annual and before taxes?”
  5. Write it down in your own words and confirm. “So, $85,000 to $92,000 a year, base, before tax. Is that right?”

Where the question appears

Expectations reach you in several ways: an application form field, a line in a cover letter, a sentence in an email reply, a figure on the CV itself, or a phone screen. A form field gives you clean data. Everything else arrives as free text, and that is where inconsistencies begin. Standard messages help here, and our recruitment email templates cover several hiring stages, including the early screening reply where you can ask for these details in a consistent way.

Decode what the number really means

“I’m looking for 90” can mean five different things. The Glints guide advises confirming whether the figure is base salary or total compensation, whether bonuses or equity are included, the pay frequency, and whether it is gross or net. It also says to separate fixed pay from variable payments such as bonuses and commissions, and to clarify the conditions attached to the variable part.

Use this checklist for every candidate:

Question Why it matters Example of the confusion
Base or total compensation? A $100,000 total could be $80,000 base plus $20,000 bonus Candidate quotes OTE, you compare to base
Gross or net? Net figures are lower than the budget they are compared to A $70,000 take-home equals a higher gross ask
Annual, monthly or hourly? Magnitude alone can mislead “45” could be $45 an hour or $45,000 a year
Currency Remote and international applicants 85,000 in dollars or in another currency
Range or single number? A range shows flexibility “$80,000 to $90,000” versus “$90,000”
Fixed or variable? Commission and bonus are conditional Guaranteed bonus vs target bonus

When the period is not stated, do not guess if the number could plausibly be read two ways. Ask.

When expectations are missing, vague or above budget

Missing. Many CVs and emails never mention pay. Do not read silence as flexibility. Add a short follow-up to your acknowledgment email or screening call, and mark the field as unknown in the meantime so it does not look like zero.

Vague. Phrases like “competitive” or “market rate” tell you nothing. Offer the range and ask whether it works, then record the answer.

Above budget. SEEK’s career advice for candidates suggests the employer side of the exchange: explain the budget constraints and ask how the candidate arrived at the figure, or whether there is flexibility. Glints adds that you should clarify which responsibilities or package components are shaping the number before you decide how to proceed. Often the gap closes through the package: bonus, remote days, review timing, development budget.

A sensible rule of thumb is to treat the figure as one input next to skills and availability, not a filter that silently removes people. If you auto-reject on pay alone, you lose candidates who would have accepted a well-explained offer.

When expectations are missing, vague or above budget

Record expectations so you can compare them

A comparison only works if every record looks the same. Store each expectation as four fields:

  • Minimum
  • Maximum (same as the minimum if the candidate gave a single number)
  • Currency
  • Period (year, month, hour)

Then add two optional fields: whether it is base or total, and gross or net. Convert to a single period (annual is easiest in the US) in a separate column, rather than overwriting what the candidate said. Keep hourly rates apart from salaried roles unless you convert them with a stated assumption, and leave anything in an unknown currency out of comparisons until you have checked it.

This matters most for agencies and teams that run a shared inbox, where the same candidate may reply to three different people. Our guide on data quality for a recruiter inbox pilot explains how to measure whether the extracted fields, salary included, are accurate and complete enough to rely on.

What the comparison looks like in practice

Suppose a role budget is $75,000 to $90,000 base. Three applicants reply:

Candidate What they wrote Normalized record Fit
A “Looking for 80-85k” $80,000 to $85,000, annual, currency assumed USD, confirm Inside range
B “$42 an hour” $42, hourly, contract vs salaried to clarify Needs a conversation
C “Around 95, including bonus” $95,000 total, base not stated Ask for the base split

The example is illustrative, not data. Notice that all three need one follow-up question, and that without a structured record you would not see that pattern across a hundred applicants.

Where salary expectations hide: CVs and shared inboxes

In small teams and agencies, applications land in a shared mailbox as PDF and Word attachments with the pay detail buried in an email body, a cover letter or a footer. Someone reads it, copies it into a spreadsheet, and the figure becomes stale or wrong. Searching later for “everyone under $90,000 with Spanish and warehouse experience” is then impossible.

Parsing fixes the retyping, but it only works if the extraction produces consistent fields. If you are building the process from scratch, start with how to turn the CVs in your inbox into a searchable candidate database, and decide which fields (salary expectation, availability, location, languages) you want captured on every profile. For teams that sort mail with rules first, our walkthrough of Outlook rules for capturing resumes shows when it makes sense to add parsing.

Our perspective

We built RecrutFlo for teams that receive CVs by email and do not want to adopt a heavy applicant tracking system just to find out who is affordable and available. Salary expectations are the clearest example of why. They sit in free text, they are phrased a dozen ways, and they decide in minutes whether a conversation is worth having.

Our view is that the recruiter should keep the judgment and the software should take the typing. RecrutFlo connects to your existing inbox, detects CV attachments, reads PDF, DOC and DOCX files, and extracts structured information including contact details, experience, skills, languages, location, salary expectations and availability into a searchable profile. You do not move your mailbox to a new platform, and you do not need an onboarding call or an implementation project to start.

Our perspective

We also think the check should stay human. An extracted figure is a starting point you can confirm with a candidate in one line, not a number to act on blindly. That is why the profile keeps the source document next to the data, and why duplicates are flagged, so the same person who replied twice does not appear with two different expectations.

For small and growing businesses, that combination is what keeps hiring organized without paying for features you will not use. If you want to see how an inbox-first approach compares, read our piece on a recruitment inbox versus a traditional ATS.

— Marco

Put it to work with RecrutFlo

If salary expectations, availability and skills are scattered across CV attachments in a shared mailbox, you can test the workflow on the Free plan and move up when volume grows. Paid plans are Starter at 19 € per month, Professional at 49 € per month and Business at 149 € per month, and extra processing runs are sold one-off: +100 for 9 €, +500 for 29 € and +1,000 for 49 €. Plan limits and current details are on the RecrutFlo pricing page.

Recrutflo

You can also see how it works on the RecrutFlo homepage, including the mailbox connections available today.

Search your candidates by what they asked for

Once expectations are stored as fields, they become filters. A recruiter can narrow a database to people within a budget, then layer on skills, languages and role. Location works the same way, and our article on searching candidates by location shows how CV data becomes map results. Combine the two and a request like “customer support, bilingual, within commuting distance, under our ceiling” takes a minute rather than an afternoon.

One caution on access: salary expectations are sensitive personal data. Limit who can see them, keep an audit trail of who opened what, and review the permissions on the mailbox itself. Our checklist of shared inbox permissions covers the four to check first.

A simple process you can adopt this week

  1. Agree the pay range for the role before you post it, and publish it where the law requires.
  2. Write the screening question around expectations only. Remove any form field or script line that asks about current or past pay.
  3. Share the range before you ask for the candidate’s number.
  4. Clarify base or total, gross or net, period and currency every time.
  5. Record minimum, maximum, currency and period in the profile, not in a note.
  6. Follow up on missing or unclear figures within a day or two.
  7. Review the spread of expectations every quarter. If most strong candidates sit above your range, the market is telling you something about the budget.

FAQ

Is it legal to ask candidates about salary expectations in the US?

Generally yes. Employers are usually permitted to ask what a candidate expects, while asking about salary history is restricted in some jurisdictions. Rules vary by state and city, so check the current law where the role is based and speak to employment counsel if unsure.

Should I share the salary range before I ask for the candidate’s expectation?

Yes, in most cases. The candidate then answers with context, and you avoid anchoring them low. Some US jurisdictions already require ranges in job postings, such as Washington for employers with 15 or more employees, so sharing early also matches where the rules are heading.

How do I handle a candidate whose expectation is above budget?

Explain the budget, then ask how they arrived at the figure and whether there is flexibility. Look at the full package too: bonus, benefits, schedule and growth can narrow the gap. If the gap stays large, thank them and keep the profile for future roles.

How do I compare expectations given in different formats?

Store each as minimum, maximum, currency and period, then convert to one period, such as annual, in a separate field. Keep what the candidate wrote alongside it. Confirm anything ambiguous, like “45” with no period, before you rely on it.

Can software pull salary expectations out of CVs automatically?

Yes, parsing tools can extract fields such as salary expectations from CV files and emails into a searchable profile. RecrutFlo does this for CV attachments arriving in a connected shared inbox. Treat the result as a starting point and confirm important figures with the candidate.

Sources

Recommended