Préparation à la négociation salariale : stratégie d'ancrage, BATNA et scripts d'objection en un seul prompt

1. Anchoring Strategy

Your offer is $145,000 base with a 10% target bonus and $80,000 in RSUs vesting over 4 years. Levels.fyi shows P4 engineers at this company median at $158,000 base. Your anchor: $175,000 base. This is 10.8% above market median — aggressive but defensible given your 6 years of directly relevant distributed-systems experience and the fact you're coming in at a level above your current title. Opening at $175K gives you room to land at $162–165K and still outperform the median.

2. Justification Narrative

• You've shipped two services handling >50M requests/day at [CURRENT COMPANY] — directly comparable to their stated scale requirements in the JD.
• Your last project reduced infrastructure costs by 34%, which maps to their public focus on cost efficiency in the engineering blog.
• You have production experience with their exact stack (Go + Kubernetes + Postgres), meaning no ramp-up period.
• You're interviewing with two other companies at the same level — which signals market validation of your experience tier without naming specifics.

3. BATNA Analysis

Your BATNA is a second offer at $155,000 base from [COMPANY B], which you expect to receive within the week. You don't need to name the company — signaling that you are "in final-stage conversations with another company at a similar level" is both true and sufficient. If this offer doesn't move above $160K total base, your alternative is financially comparable and you should take it.

4. Negotiation Script

[THEM]: "We're excited to extend this offer at $145,000."
→ [YOU]: "I'm genuinely excited about the role and the team — the distributed systems problems you're working on are exactly where I want to spend the next few years. I'd like to discuss the compensation. Based on market data for this level and location, and given my directly applicable experience, I was expecting something closer to $175,000. Is there flexibility to get there?"

[THEM]: "That's above our band for this role."
→ [YOU]: "I understand bands exist for a reason. Can you tell me where I'd land in the band, and whether there are ways to make up the difference through equity or a signing bonus? I want to find a structure that works for both of us."

[THEM]: "We've already given you our best offer."
→ [YOU]: "I appreciate the transparency. I'm in late-stage conversations elsewhere at a similar level, and I want to join your team — but I need the total package to reflect my market value. If the base is fixed, let's look at the equity schedule or a one-time signing bonus to close the gap."

5. Follow-Up Email Draft

Subject: [YOUR NAME] — Compensation Discussion Follow-Up

Hi [RECRUITER NAME],

Thank you for taking the time to discuss the offer today. I wanted to follow up in writing to confirm where we landed:

- Base salary: $[AGREED FIGURE]
- Target bonus: [BONUS %]
- Equity: [RSU GRANT AND VESTING SCHEDULE]
- Signing bonus: $[AMOUNT IF APPLICABLE]
- Start date: [DATE]
- Remote policy: [POLICY AS AGREED]

I'm excited to move forward and look forward to receiving the updated offer letter reflecting these terms.

Best,
[YOUR NAME]

6. Red-Lines Checklist

• Walk away if the final base offer is below $155,000 AND there is no signing bonus or equity top-up to compensate — your BATNA is financially equivalent.
• Walk away if the equity cliff is longer than 12 months with no acceleration clause — at your seniority, a 1-year cliff is market standard.
• Walk away if they won't confirm the remote policy in writing — verbal agreements on remote work have not held up historically, and this is non-negotiable for your situation.