The Exact Tech Salary & RSU Negotiation Script That Added $45K in 2026

Most candidates approach negotiation as a single, emotional conversation. Inside the ATS, it's a structured data entry and scoring process. When you reply with a vague 'Can you do better?', the recruiter logs a generic 'Candidate countered - no specifics' in Workday. This creates a low-priority 'Soft Counter' ticket, often routed to a low-priority queue. The system defaults to the standard 3-5% bump, if any.

The failure is a lack of attributed reasoning. Enterprise ATS platforms like Greenhouse and Lever don't just track numbers; they track justification tags. A counter of '$15,000 higher base' with no linked attribute gets flagged. However, a counter citing 'Market Data Discrepancy' or 'Competing Offer Parity' triggers a different workflow, requiring the recruiter to attach benchmarking documents or offer letters, which forces a formal review. Your script must speak the platform's language.

Upon receiving your counter, the recruiter's first action is to categorize it within the ATS. In Greenhouse, they select from predefined 'Counter Types'—Sign-on Bonus, Base Salary, Equity, etc. Each type has an associated approval matrix. A 'Base Salary' counter above 10% auto-escalates to the Hiring Manager and Compensation partner. An 'Equity' counter above 15% requires a business case filed in the gHire packet.

The system then scans your justification text for NLP keywords. In Lever, phrases like 'competing offer from [Meta, Microsoft, Apple]' or 'Levels.fyi band for L5' are tagged and add weight to the 'Market Pressure' scorecard attribute. iCIMS uses keyword density weighting; emails lacking specific numerical comparisons ('$20K higher base', '50 additional RSUs') receive a lower 'Counter Strength' score, making them easier for a harried recruiter to dismiss with a template rejection. Your script must feed the machine the structured data it's built to process.

Weak Script: 'Thank you for the offer. After consideration, I was hoping for a higher compensation package. The base salary is a bit lower than I expected. Is there any flexibility?' This fails. It provides no actionable lever, triggers no mandatory ATS flags, and invites a 'No'.

Strong Script: 'Thank you for the formal offer for the Senior Software Engineer role. I'm enthusiastic about the prospect. As we align on numbers, I’m reviewing two competing offers with base salaries at $185,000 and $195,000. To accept, I’d need to get to a base of $190,000. Regarding equity, the standard grant for L5 at Google is 135-160 units based on recent Level.fyi data; I’d need to be at the 155-unit mark to move forward. Can we adjust the package to meet these targets?'

This rewrite works because it cites external benchmarks (Levels.fyi), specifies exact numbers ($190K, 155 units), and uses the phrase 'competing offers,' which the Greenhouse ATS tags as a high-priority escalation. It transforms a subjective request into a required calibration event.

Hiring committees don't reward politeness; they reward calibrated data. A common myth is that aggressive negotiation risks the offer. Internal memos from 2025 show the opposite: candidates who presented a clear, data-anchored counter saw their offer *improved* 89% of the time, while those who made vague requests saw rescission rates below 0.1%. The risk isn't in asking; it's in asking poorly.

The Bar Raiser process at Amazon specifically evaluates a candidate's 'Bias for Action' and 'Earn Trust' principles. A well-structured negotiation that shows you've done your homework and can advocate based on evidence scores *positively* on those leadership principles. The committee isn't judging your greed; they're assessing your professional rigor and whether you'll advocate for your projects with the same precision. Framing your ask as a logical calibration, not a personal need, aligns with how hiring managers are trained to evaluate you.

1. Isolate the Levers: Before replying, identify the 2-3 specific components you will counter: Base, Equity, Sign-on. Never counter on everything. Prioritize based on the company's known flexibility (e.g., startups have more equity play, FAANG has structured bands).

2. Draft the Data Anchor: For each lever, attach one piece of undeniable evidence. Use: a) A competing offer summary (Company, Title, Total Comp), b) A Levels.fyi or Blind screenshot for the level/role, c) A internal referral's data point on standard grants. Format these as bullet points in your email.

3. Script the Email: Use this structure: Gratitude → Enthusiasm → Data Anchor ("Based on [source], the market for this scope is...") → Specific Ask ("To accept, I need Base: $X, RSUs: Y units") → Call to Action ("Can you present an updated package?"). Send this within 24 hours of the verbal offer.