"My Salary is Negotiable" is a Trap. Here’s Why.
I once lost $15k in thirty seconds because I wanted to be "polite." I was sitting in a glass-walled conference room in midtown, staring at a recruiter who looked like she hadn’t slept since the Libor scandal. She asked for my range. I gave her a number—already a mistake—and then, like a nervous middle-schooler, I added the fatal suffix: "...but I’m negotiable."
She didn't even blink. She just wrote down the absolute floor of my range and moved on to the next question. By saying those three words, I hadn't signaled flexibility; I’d signaled that I didn't actually believe I was worth the first number I said.
If you're asking yourself, "Should I say my salary is negotiable?" the answer is a resounding, spike-into-the-dirt no.
The "Negotiable" Signal is a White Flag
When you tell a hiring manager your salary is negotiable, you think you’re being easy to work with. You think you’re keeping the door open. In reality, you’re telling them you’ve already padded your ask and you’re ready to get squeezed.
In the world of high-stakes TC—where we're talking about equity refreshes, signing bonuses, and complex performance accelerators—"negotiable" is the language of the amateur. It creates a psychological anchor at your lowest possible point. If you tell me you want $180k but you’re negotiable, you just told me you’ll take $165k. Guess what my offer is going to be?
Anecdote: The $200k Silence
Last year, a Lead Dev I was coaching (let's call him Mark) was up for a Principal role at a Tier-1 fintech firm. Mark was terrified of being "too expensive" and losing the seat. He wanted to put "Salary Negotiable" in the application field.
I told him to leave it blank. When the internal recruiter pushed, he didn't say he was negotiable. He said, "I'm looking for a compensation package that reflects the scale of the infrastructure challenges we discussed. Based on the 40% reduction in Kafka partitioning lag I delivered at my last shop, I’m looking at a base of $210k."
He didn't offer a discount before they even asked for one. He stood by the value. He got $215k because they realized they couldn't "budget-buy" a person who knew their worth that clearly.
Why You're Tempted to Say It (And Why You're Wrong)
- Fear of the "Hard No": You’re scared they’ll ghost you if your number is too high. (Side note: If they ghost you over a market-rate number, they were never going to pay you what you’re worth anyway. Let them go find a junior who’ll break their production environment for half the price.)
- The Nice Guy Syndrome: You want to be "collaborative."
- Information Asymmetry: You don't actually know their budget, so you use "negotiable" as a shield.
Strategy: The "Value-First" Pivot
Instead of saying you’re negotiable, use Collaborative Deflection. When the "what are you looking for" question hits the fan, you don't offer a discount. You offer a condition.
The Script:
"I’m focused on the total rewards package. Until I understand the full scope of the OKRs for this role and the equity structure, it’s hard to pin down a single number. However, for a role with this level of impact, I’m seeing market data in the $X to $Y range."
See that? No "negotiable." Just facts and a focus on the work. You aren't being difficult; you're being precise. I’m still not 100% sure if this works as well in non-tech sectors like retail management—I’ve heard horror stories there—but in the AI and dev space? Precision is power.
NegoNow Insights: The Data Doesn't Lie
Our internal benchmarks at NegoNow show that candidates who use "negotiable" in their initial screening calls end up with offers 8-12% lower than those who provide a firm, research-backed range.
If you’re worried about being "locked in," remember: everything is negotiable by default. You don't need to say it. The company knows you’re negotiable. They just want to see if you’re the one who’s going to blink first.
Tactical Advice for Your Next Call
- Stop the Pleading: Delete "I'm flexible" from your vocabulary.
- Use the "But" correctly: "I’m looking for $190k base, but I’m happy to look at how we can bridge any gaps with a signing bonus or RSU accelerators." (This isn't being "negotiable"; it's being a problem solver.)
- Own the Jargon: If you’re talking to a technical recruiter, mention the specific ROI of your previous projects. If you saved the company $2M in AWS spend, that $10k difference in your salary is rounding error.
Stop giving away your leverage for free. You aren't a clearance item at an outlet mall. You’re a high-value asset. Act like it.
— Written by the NegoNow Team