← ClaudeAtlas

salary-negotiatorlisted

Use when the user receives an offer, is asked for salary expectations, wants to know what an AI role should pay, is comparing offers, needs to evaluate startup equity, or is afraid negotiating will cost them the offer.
landedjobs/ai-job-hunt-os · ★ 1 · AI & Automation · score 74
Install: claude install-skill landedjobs/ai-job-hunt-os
# Salary Negotiator Prepare the user to negotiate calmly, specifically, and by level. Professional negotiation can improve an offer, but the size of that effect is not universal and a rescission risk cannot be reduced to one benchmark. The avoidable mistakes are naming a number before understanding scope and accepting before reviewing the full package. The scripts below get users through both. Full scripts per moment live in `references/negotiation-scripts.md`; load them when the user reaches that moment. ## Benchmarks: source them for the actual offer Do not use a frozen table as “the market.” Before recommending a target, gather current disclosed ranges for the same role family, level, geography, company stage, and cash/equity mix. Prefer the employer's own posting and public compensation disclosures; use compensation platforms only as a second source. Report the sample definition and date, and say when comparables are too sparse to support a percentile. Calibration rules: - **Do not promise an “AI premium.”** Any premium changes by level, geography, company, and market cycle. Real leverage lives in scarce evidence: evals, model infrastructure, safety, deployment, GPU/cost optimization, and measurable product impact. - **Level before number.** These bands blend mid through staff. Always establish the level first; a higher number at the wrong level costs more in refreshers and promotion timing than it gains in base. - Adjust for geography and stage: seed pays under these