Should you give a salary range or a single number?

A range, with the bottom set at your actual target rather than at your walk-away figure. Recruiters hear the bottom of a range as the number you will accept and the top as ambition, so a range that runs from your minimum to your dream lands you at your minimum. Keep the spread to roughly fifteen to twenty percent so it still reads as researched rather than hopeful.

What do you say if the recruiter refuses to share the range?

Give the number rather than pushing a second time. Say: based on what I have seen for this scope I am targeting X to Y base, and that is subject to the full package. One deflection reads as professional calibration. A second reads as a stall, and the recruiter still has to confirm you sit inside the band before booking engineering time against you.

What should you put in the desired salary field on an application form?

If the field accepts text, write Negotiable, or Open, based on the full package. If it demands digits, enter the bottom of your researched range rather than a placeholder such as 0 or 1, which some screening filters read literally. Some forms accept a range inside one text box, so use it when you can. Field behaviour is configured per employer, so check what the box takes before you submit.

Is it bad to name a number first on the first call?

It is a disadvantage you can price in, not a mistake. Whoever speaks first sets the anchor, which is exactly why you try once to get their band instead. When that fails, the fix is not silence. It is making sure the number you say has your target at the bottom and a stated condition attached, so the figure can move upward when the scope or the level changes.

Can you raise your salary expectations later in the process?

Yes, if you tie the change to new information rather than to a change of mind. Say: when we spoke I was working from the scope in the posting, and now that I have seen the on-call load and the team size I would put this closer to X. That is precisely why the first figure should be phrased as based on this scope from the start.

How to Answer Salary Expectations on a Recruiter Screen Call

Deflect once, then give a number. Ask whether the role has a band, because information you get for free costs you nothing. If the recruiter will not share it, name a researched range whose bottom is the figure you actually want, and attach the wording that keeps it non-binding: based on what I have seen for this scope, and subject to the full package. One deflection reads as calibration. A second reads as a stall, and the recruiter still has to confirm you fit the band before spending an engineer's afternoon on you.

The two mechanics that decide this call

The recruiter screen is not a negotiation, it is a budget-matching call. The recruiter holds a band they did not set and must confirm you sit inside it before booking further rounds. That is why flat refusal fails. You are not outmanoeuvring anyone, you are being filed as unconfirmed and quietly deprioritised.

The second mechanic costs money. Whatever range you say, the bottom becomes the number the recruiter writes down and the top a note about your ambition. Nobody opens at your ceiling. So the bottom of your range must be your target, the figure that makes you say yes without a pause, never your walk-away number. If you would leave at $150,000 and you want $175,000, the range starts at $175,000. Put your floor in the range and you will be offered your floor.

The decision tree, four branches

What is happening	Your move	Why
A range is posted, or volunteered	Anchor in the upper half of their band, then ask where the level lands	They spoke first. Fighting the band is pointless, positioning inside it is not.
No range posted, they ask you first	One deflection, phrased as a levelling question	Free information. Plenty of recruiters tell you the band when asked once.
They deflect your deflection	Give the range at once, target at the bottom, condition attached	A second push costs goodwill and wins nothing they were not already withholding.
The form demands a number	Text field: `Negotiable`. Numeric-only: the bottom of your range	A written figure is read by a filter, not a person, and follows you to offer stage.

Branch 1: a range is posted

Several US states require a range in the advert, and European rules have widened as member states transpose the EU pay transparency directive, though what applies depends on where the role is based. When a band exists, use it out loud. Quoting their own number back is the cheapest credibility on this call.

“I saw the posted range of $160,000 to $200,000 and that works for me. Based on the scope you have just described, particularly owning the payments service, I would be looking at the upper half, so around $190,000 base, and that is subject to the full package. Where in that band are you seeing this level land?”

The closing question hands the turn back, and the answer tells you whether the top of that band is genuinely available at your level.

Branch 2: no range posted, and they ask first

You get one attempt. Keep it short, frame it as calibration rather than as withholding, and end on a question so the silence belongs to them.

“Happy to talk numbers. Before I do, it would help to know how you are levelling this one, because senior means quite different things across companies. Do you have a band approved for the role?”

If they give the band, you are in branch 1. If they give a level instead, take it into branch 3.

Branch 3: they deflect your deflection

This is the branch most advice skips and the one that actually happens. The recruiter says some version of “I need to hear your expectations first”. Do not push twice. Concede in half a sentence, then spend your breath on the number and the condition.

“That is fair. Based on what I have seen for this scope, I am targeting $175,000 to $205,000 base, and that is subject to the full package. If the equity and bonus are strong there is some flexibility in the base, and if the level turns out to be higher than we have been discussing I would want to revisit it.”

Four phrases are load-bearing. Based on what I have seen for this scope sources the number to research and to the job as described, so it moves when the job changes. Targeting is softer than requiring without being vague. Base stops the recruiter comparing a total-comp figure of yours against a base-only line of theirs. Subject to the full package makes everything conditional on equity, bonus, sign-on and remote policy, the clause you lean on two rounds later.

It is also what lets you correct an undershoot without looking erratic: “When we spoke I was working from the scope in the posting. Now that I have seen the on-call rotation and that this role owns the migration, I would put it closer to $215,000.”

Branch 4: the form field that will not take words

These fields are configured by whoever set the job up, so behaviour varies by employer. Test the box first. Free-text fields are common and accept Negotiable or Open, based on the full package. Some take a range in one box, the best outcome available. A strictly numeric field is the awkward case: enter the bottom of your researched range, not a placeholder such as 0 or 1. A placeholder sometimes reads as a signal to a human and sometimes gets taken literally by a cost filter, and nobody tells you which.

Setting the bottom of the range, worked

Figures are illustrative, substitute your own market and currency.

Collect four comparable numbers, not one average

Posted ranges for the same title at the same company in a transparency jurisdiction, live ranges from two competitors hiring the same level, and a levelling site for your city. Averages by job title are near useless: the title spread is wider than the pay spread.

Write down the target before any rounding

The number at which you accept without hesitating. Say comparable bands for a senior backend role run roughly $165,000 to $205,000, and the figure you would take on the spot is $185,000. That is the target.

Range equals target, to target plus fifteen to twenty percent

$185,000 to $215,000. The bottom sits comfortably inside their band, so you are never screened out on cost. The top sits just above it, which reads as ambitious rather than uninformed.

Say the whole line out loud once, timed

It should take about twelve seconds. Longer means you have started justifying, and justifying invites a counter. Deliver the number, then stop talking.

One more thing to settle beforehand. In several US jurisdictions employers may not ask what you currently earn, and where they may you can decline: “I would rather anchor this on the role than on my last one” is a complete answer. Rehearse it with the rest of the screen, using the company Q&A generator to build the bank.

Where a live copilot is the wrong tool for this question

Being straight about it: salary is the worst possible fit for real-time assistance, ours included. The bottleneck is not phrasing, it is arithmetic you should have finished the day before, and no model knows your rent, your notice period, your unvested equity or the figure you would walk away from.

There is a mechanical limit too. OfferPilot AI hears the interviewer through your computer's playback loopback, so it works on a Zoom, Teams or Meet call and captures nothing if the recruiter rings your mobile, which is how many first calls happen. It is Windows 10 and 11 only. The overlay is excluded from screen capture at the operating-system level, so it stays out of a shared screen or recording, but does nothing about a webcam, a lockdown browser or anyone in the room with you. For this question the useful move is analogue: target, range and conditional clause on paper beside the keyboard. It earns its place in the technical rounds after this one, compared in our copilot roundup.

Decide the target first, quote the range second, let the condition carry the rest. The candidates who get squeezed on a screen are rarely the ones who said the wrong number, they are the ones who had not chosen one.

“What are your salary expectations?” on the first call