Big Tech Offer Negotiation Starts Before You Have an Offer

A candidate who says "I was thinking around $180K base" in a recruiter screen has just answered a question the recruiter wasn't technically asking. The recruiter asked about compensation expectations. The candidate answered with a ceiling. By the time the offer letter is generated, that number is likely somewhere in the vicinity of what the candidate said, and the recruiter will reference it as though it was a mutual agreement.

The conventional picture of offer negotiation shows a candidate receiving a number, pausing thoughtfully, and then countering. That picture is wrong about where the leverage lives. The recruiter has already selected a compensation band, already submitted it for approval, and already framed the offer internally before the candidate hears a dollar figure. The call where the offer is delivered is a presentation, not an opening bid. Candidates who treat it as the start of negotiation are entering a conversation that began weeks earlier without them.

This matters most to candidates who are close to an offer or already have one in hand, who sense something is off about the number but don't know whether asking for more will blow up the deal. It also matters to candidates who haven't started the loop yet, because the highest-leverage moments in any big tech negotiation are the ones that precede the formal offer by weeks.

What the Recruiter Is Doing in That First Call

Recruiter screens serve two purposes simultaneously. One is qualification. The other is compensation calibration. Most candidates prepare for the first and ignore the second entirely. When a recruiter asks "what are your compensation expectations," they're collecting an input that will shape band selection. The candidate who answers directly has handed the recruiter a data point that functions as a floor for the company and a ceiling for the candidate.

The better move is to redirect. Something like: "I want to make sure we're aligned on the market range for this level before I anchor on a number. What does the band look like for this role?" That's not evasion. It's a request for information that the recruiter often has and that the candidate needs. A recruiter who responds with a band has just told you where the ceiling is. A recruiter who declines to share one has still told you something: that the band is either very wide or that there's a reason they'd rather not show it. Either way, you've avoided setting a ceiling on yourself before the loop has even started.

Candidate accounts from completed loops at companies like Google and Meta suggest that recruiters do reference early compensation conversations during offer delivery, framing band selection around "what you mentioned earlier" as a reason for where the number landed. This is worth taking seriously as a reported pattern, even without a controlled dataset behind it. The mechanism is straightforward: recruiters are calibrating offers to align with stated expectations because it reduces friction later. If you gave them a number, they used it.

Competing Offers Are a Timing Problem

Most negotiation advice treats a competing offer as leverage to deploy after the offer arrives. That's the wrong sequence. The value of a competing offer is highest at the moment the recruiter is preparing to submit compensation for internal approval, not after the letter has been generated. Once an offer is finalized internally, revising it upward requires the recruiter to go back through approval channels. That adds friction, and friction is a reason not to move.

Disclosing a competing offer before the formal offer is generated gives the recruiter something different: a justification to request a higher band in the first place. Candidate reports from loops at Google and Meta suggest this sequencing matters, with earlier disclosure associated with faster response times and higher initial offers, because recruiters can cite the competing offer as a reason for the request rather than having to reopen an already-closed process. This is a candidate-reported pattern, not a published policy. But the underlying logic holds regardless: leverage is worth more before the decision is made than after.

The practical implication is that if you have a competing offer, or expect one within weeks, you should disclose it during the debrief period, when the recruiter is still assembling the package. Not in the first screen, where it becomes a vague data point too early to act on. Not after the letter arrives, where it becomes a retroactive problem. The window is specific.

Level First, Salary Second

At the major tech companies, your level determines your equity band, your bonus target percentage, and whether you're eligible for RSU refresh grants at all. Salary is one line in a compensation structure where the other lines often dwarf it in long-term value. Candidates who negotiate a base salary increase without first confirming or contesting their level are optimizing the smallest variable.

Levels.fyi compensation data shows that adjacent levels at companies like Google carry meaningfully different total compensation, with the gap between L5 and L6 substantial enough that a salary negotiation within the wrong level can leave significantly more on the table than even a successful counter would recover. The exact figures vary with market conditions and individual package construction, but the directional point is consistent: the level question is worth raising before the salary question.

If you're uncertain what level you were assessed at, ask. Recruiters will often tell you, and the answer shapes every subsequent conversation. A candidate who pushed for L6 consideration when hired at L5 is in a structurally different position than one who negotiated a $15K base increase at L5 and never asked.

The most consequential negotiation variable in a big tech offer isn't the salary line. It's the level that determines every other line in the package.

What Actually Moves Numbers

Vague asks are the most frequently declined. "Is there any flexibility?" is a question the recruiter can answer with "let me check" and then report back with nothing, because there was nothing specific to justify taking internally. The recruiter needs a rationale they can bring into an approval conversation, not a feeling that the candidate would like more.

To illustrate how this works in practice: a candidate who says "I've looked at current market ranges for this level and I'd like to discuss the upper end of the band. My competing offer is at $X in total comp, and I'd like to know if there's a path to closing that gap" has given the recruiter three things to work with. A specific ask. A market rationale. A competing data point. That's a package the recruiter can actually present. Compare that to "I was hoping for a bit more" with no number attached. One of those gives the recruiter something to do. The other doesn't.

The same logic applies to the anchor reset, which is the move a candidate needs when they've already given a number in an early screen that's now too low. The framing is something like: "I've done more research on the market range for this level since we spoke, and I want to make sure we're looking at the full band before anything is finalized." That's not a retraction. It reopens the conversation without requiring the candidate to admit a mistake, and it invites the recruiter to share band information the candidate can then use to recalibrate.

If you're preparing for a loop and want to make sure your resume is positioned for the right level before the recruiter screen even happens, a resume review can identify where your experience sits relative to the level benchmarks recruiters are calibrating against. Level misreads often start before the first call.

The Window Between Verbal and Signed

Once you have a verbal offer, you're in the last functional negotiation window. It's narrower than most candidates realize, but it's real. The move that works here is a single, specific, well-reasoned ask, not a series of requests. Recruiters who receive multiple rounds of asks from one candidate have less internal goodwill to spend on each subsequent one, and goodwill is part of what gets revision requests approved.

Pick the variable that matters most. Name a specific number or ask a specific question. Give a rationale the recruiter can use. Then wait for a real answer before moving to anything else. Candidates who structure the conversation that way report more movement than those who accept immediately or counter without a clear basis for the ask. The offer being in hand doesn't mean the leverage is gone. It means the window is defined.

If you're at this stage with a specific offer in hand, share your situation at interview101.com/submit. The details of your loop, your level, and any competing offers you have will shape which of these moves applies to your case.