How to Negotiate Without Torpedoing the Deal
Before we begin:
After more great feedback, I’m going to keep running my free linkedin/resume reviews for all founding subscribers. Email me your subscription confirmation as well as your resume/linkedin to randomrecruiter3@gmail.com
Check out getvibeprep.com - a new app I’m working on but still in early innings. Feel free to DM me here directly or on X for feedback and input. Still a work in progress!!!
In this issue:
A real call from this morning where a strong candidate got himself dropped
What a recruiter actually hears when you draw a hard line on money early
The difference between anchoring high and pricing yourself as a risk
How “depending on experience” is doing more work than you think
The exact way to fight for the top number without becoming a flight risk
When walking away is the right call, and when it just makes you look unstable
I lost a candidate this morning. Good one, on paper. And he did it to himself in under two minutes, while I sat there listening to him do it.
I want to walk you through exactly how, because almost everything that went wrong is invisible from the candidate’s side. He thinks he got punished for asking for money. He didn’t. I’ll show you what actually happened, what I heard, and how you avoid being him.
The Setup
I’m working a senior software engineer role. C++ and Python, large bank here in New York. The range is 180 to 225, and I put that range right in my outreach, same as I always do, with “depending on experience” attached to it. That phrase matters and we’ll come back to it.
