4 ms·
I've used what I consider the golden guide of salary negotiation for a software engineer that has been linked on HackerNews[1]. I've applied these guidelines i
by Pooge 8mo ago
I've used what I consider the golden guide of salary negotiation for a software engineer that has been linked on HackerNews[1].
I've applied these guidelines in my own negotiations and it worked very well for me. I would've undersold myself by at least 15% if I went ahead and answered the salary question first. I declined politely to give a number first—even saying "it's not in my interest to answer that first, as you most likely understand".
Those guidelines work for all jobs that have high added value, I would say.
[1]: https://www.kalzumeus.com/2012/01/23/salary-negotiation/ https://www.kalzumeus.com/2012/01/23/salary-negotiation/
- d4mi3n 8mo agoThis guide has aged surprisingly well, but I’d add to this: the above response is about as good as you can get—it is firm, non-combative, and moves the conversation forward. Don’t antagonize your recruiter. You want them to advocate _for you_ when a prospective employer is drafting an offer. Work with them to give them the ammo they need to make that happen.
- Pooge 8mo agoWould you say I was antagonizing him with my response? Because he was an in-house recruiter (and not a headhunter) and I got along with him pretty well.
- randomtoast 8mo agoReads like an LLM response.