skip to content

What is anchoring in a job offer negotiation, and why does the first number named matter?

level: juniorimportance: must knowfreq 50%

answer

  1. The first number does work
  2. Everything after gets judged against it
  3. A vague ask leaves their figure standing
  4. Specific target, stated justification

basics

~20 s

Anchoring is the pull the first concrete number exerts on everything said afterwards: later figures get judged as moves away from it rather than valued fresh. Whoever anchors sets the range the rest of the conversation happens inside.

solid answer

~50 s

Anchoring is the way the first concrete number in a compensation conversation becomes the reference point for every number after it. If a recruiter names a base first, your counter reads as a move off their figure; if you name first, their reply reads as a move off yours. That is why a counter has to carry a specific target rather than a vague `can you do better` — a vague ask leaves their number as the only concrete figure on the table, so it wins by default. The anchor you set should be a justified target for the level, not a percentage applied to their offer: `Given the level and the market data I have, I was targeting the upper part of the band — can we get there?` Anchor high enough to leave room, grounded enough that you can defend it.

go deeper

for a junior

Know what anchoring means and that the first concrete number shapes the rest. Practically: do not blurt a figure you have not thought about, and never counter with a vague 'can you do better' — it leaves their number as the only real one.

for a middle

Be able to explain the mechanics: later figures are read as adjustments from the anchor, ranges tend to get worked from their bottom, and an anchor holds only as long as you can say why it is that number. Turn a benchmark for the level into a single defensible figure.

for a senior

Show judgment about whether to name first at all, based on how good your information about the level and scope actually is. Calibrate the anchor so it leaves room to move without becoming a number you would have to abandon under one question.

for a principal

Own the tradeoff between a high anchor and your own credibility: pull too hard and you spend goodwill you may need for scope, start date or the working relationship afterwards. Expect to sit on the other side too, where the anchor you set for a candidate becomes a precedent for the team.

## The mechanism An **anchor** is the first concrete number placed into a compensation discussion. Once it exists, both sides stop valuing the role from scratch and start reasoning by *adjustment from that number*: every later figure is read as a move toward or away from it. This is why the same final base can feel like a win or a loss depending purely on where the conversation started. Two practical consequences follow. 1. **The side with no number on the table has no gravity.** If a recruiter has named a base and you have not named a target, the only concrete figure in the room is theirs. A reply of `can you do better?` does not change that — it asks them to move away from their own anchor by an amount they choose, which is almost always small. 2. **Whatever you say becomes the ceiling of what you are offered.** Name a target and you will rarely be offered more than it. Name a *range* and, in common practice, the bottom of that range becomes the number the employer works from. If you would only be happy at the top of a range, say the top as a single number. ## Who names a number first The honest answer is *it depends on who holds better information*, and the deciding factor is whether you have a defensible benchmark for that level. - **Let the employer go first when you are guessing.** Early in a process, before you know the scope of the role or the rung it is being filled at, a number you invent can only hurt you: too low and it caps you, too high and it burns credibility you will need later. Asking what range the role is budgeted at costs nothing. - **Go first when you have a benchmark you can say out loud.** If you have gathered comparable figures for the level, the location and the kind of company, naming a specific target early sets the frame while the employer is still deciding what to put in the offer — which is easier than moving an offer that has already been approved. Rules about asking for salary history, and about whether a pay range is disclosed or published, vary considerably by jurisdiction and by employer policy, and they change over time. Treat that as something to check for your own location rather than as a universal entitlement, and never assume an employer is obliged to share a band with you. ## What makes an anchor defensible An anchor works because it is *justified*, not because it is large. A number you cannot explain invites the recruiter to discount it, and a number attached to a reason invites them to argue about the reason — which is a conversation you can win. Good justifications are things that are true and checkable in the abstract: the level and scope the role is being filled at, the benchmarks you gathered for that level and location, the responsibilities that came up in the loop, and what you would be leaving behind. A generic percentage applied to their offer is not a justification; it is arithmetic performed on their number, and it silently concedes that their number is the correct starting point. ## Worked example: a platform role A candidate is interviewing for a platform engineering role. On the offer call the recruiter names a base first and describes it as sitting in the middle of the band for the level. That figure is now the anchor. The weak reply is `it is a bit lower than I hoped — can you do better?` It carries no number, no reason and no priority, so the recruiter is left to guess both what would close the candidate and how much guessing costs them. The strong reply is a **counter email** with exactly three moving parts: one specific ask, one justification, and one line that keeps the relationship warm. The ask is a single base figure the candidate can defend for that level. The justification is the benchmark and the scope of the role as it was described in the loop. The warm line makes clear the candidate wants the job, so the recruiter can take the ask upstairs as an approval request rather than as a threat. ## Common mistakes - Reacting to the first number in the moment. Thanking the recruiter, asking when they need an answer, and coming back in writing is always available. - Anchoring on total package when you mean base, or the reverse. Say which component your number refers to. - Treating the recruiter's first figure as a ceiling. In many processes the first offer is an opening position with approval headroom behind it, though how much varies enormously by employer. - Producing a number under pressure that you then have to abandon. An anchor you retreat from teaches the other side that your numbers are decorative.

  • If a recruiter asks for your expected number before any offer exists, how would you decide whether to give one?
    It turns on whether I can defend a figure for that level. If I have gathered comparable benchmarks, I name a single target with the reason attached. If I am still learning the scope, I ask what range the role is budgeted at and say I want to understand the level first. Whether ranges are shared or asked about varies by employer and by location, so asking is worth doing rather than assuming.
  • Does anchoring still matter when the employer has already published a pay range for the role?
    Yes, and the published range is itself the anchor. It bounds the conversation, so the work shifts from setting the frame to positioning inside it: you argue for a specific point in that range on the strength of the level and the scope, rather than arguing the range is wrong. A published range also gives you concrete language, since you can name the part of it you are targeting instead of inventing a figure.

saying these in an interview costs you the question

  • Countering with 'can you do better' and naming no number at all
  • Naming a target you cannot justify for the level
  • Applying a generic percentage to their figure instead of a researched target
  • Giving a range, then being surprised the bottom becomes the offer
  • Treating the recruiter's first figure as a hard ceiling

context