Watch how it opens
This is the live exchange — your AI counterpart pushes back exactly like the real person will.
What's a fair offer
Anchor 10–15% above their open with a specific, defensible figure (e.g. $168K), backed by market data for the role's scope. A round-number wish invites a token bump; a researched number moves the band.
Techniques you'll practice
- 1 Echo Repeat the operative phrase back to surface what's underneath it.
- 2 Flip It Turn the question around — ask what they'd do in your position.
- 3 Anchor Name a specific, researched number so the negotiation has a real reference point.
- 4 Tag It Label the constraint the other side is hiding so it can be addressed out loud.
These are NegotiateIt's eight techniques — Echo, Flip It, Silence, Anchor, Tag It, Get Ahead, Plan B, Narrow Down — built on research-backed methods: tactical mirroring & labeling (Chris Voss) and anchoring & BATNA (Harvard / Fisher–Ury). You drill them against an AI that reacts to what you actually say, so the move sticks under pressure.
What works — and what trips people up
Phrases that work
- "Based on the market for this scope, I was expecting something closer to $168K."
- "I want to say yes — help me get there."
- "It sounds like base is locked. Where else is there room — sign-on, equity, review timeline?"
- "If you were sitting where I am, with this market data, what would you do?"
Common mistakes
- Accepting the first number because it "feels generous" — the first offer is the anchor, not the ceiling.
- Reaching for a phantom competing offer you can't produce — a senior interviewer will call it instantly.
- Naming a figure you can't defend, then folding the moment they ask "why that number?"
- Treating base as the only lever and ignoring sign-on, equity refresh, title, and review timing.
- Filling the silence after your counter — say the number, then stop talking.
The setup
The difference between $145K and $162K is decided in the first ten minutes — and most of it comes down to what you say after she stops talking.
Read the full setup
The offer is on the table: $145,000 base, standard benefits, equity revisited after probation. Patricia Chen, the VP of Engineering, slid it across the table with a smile and the line that always works — "the team needs someone like you." It feels generous. It feels final. It is neither.
You did the research. The role is worth $160,000–$175,000 on the open market, and you know it. What you do not know — what Patricia will never volunteer — is that she has budget headroom she hasn't named, sign-on authority she hasn't mentioned, and a quarter-end deadline pressing on her harder than it's pressing on you. The previous candidate fell through last week. Her team has been without a senior lead for two months.
She respects directness. She loses patience the instant you reach for a phantom competing offer or a number you can't defend. This is the conversation where the difference between $145K and $162K is decided in the first ten minutes — and most of it comes down to what you say after she stops talking.
It's 11pm. The call is at 10am. You've rehearsed the opening line in the shower, in the car, in your head on a loop — and it still dissolves the moment you imagine her actually saying "that's the best we can do." That's the real problem. Not the number. The live exchange: the pause, the pushback, the second ask.
At a senior level the first offer is never the best one — it's the anchor, the opening move in a conversation the company expects you to continue. But the asymmetry is brutal. The VP across the table runs this negotiation every week. You run it once every two or three years. She has reps. You have anxiety.
The fix is reps. Practice the actual back-and-forth tonight — out loud, against someone who pushes back — so tomorrow's call is your second time, not your first. It's free, and it takes ten minutes.
Common questions
What's a good counter-offer for a senior engineering role?
Anchor to researched market data, not a round-number wish. If the band is $160K–$175K and the offer is $145K, counter near the top of the range with a specific figure — "$168K based on the market for this scope" — and let the number do the work. A defensible, specific counter signals you've done the homework; a vague "can you do better?" invites a token bump.
Should I name a number first in a salary negotiation?
If you have solid market research, anchoring first sets the reference point the rest of the conversation orbits. If you don't yet know the range, flip it — ask what they have budgeted for the role and let them anchor. The mistake isn't naming a number; it's naming one you can't defend the moment they ask "why that figure?"
What if the recruiter says the offer is final?
"Final" is usually a position, not a fact. Stay calm, label the constraint out loud — "it sounds like base is locked" — and pivot to the levers that aren't: sign-on bonus, start date, equity refresh, title, review timeline. Most "final" offers have room somewhere other than base. Your job is to find which lever still moves.
How do I negotiate without burning the relationship?
Negotiate the offer, not the person. Stay warm, stay specific, and frame every ask as a shared problem to solve — "I want to say yes; help me get there." Hiring managers expect a counter at senior level; a calm, well-researched ask reads as competence, not greed. What damages the relationship is games — phantom offers, ultimatums, going silent. Directness builds it.
Related scenarios
Free · 30-second signup.