loading...

re: The Basics of Salary Negotiation VIEW POST

FULL DISCUSSION
 

At one of my previous jobs, I negotiated a +$10k/year increase at the very beginning, before signing the contract – and it worked the "no questions asked" way throughout the following 5 years I spent in the company.

Which sounds contrary to the "Don’t Say a Number" advice. But every case is unique.

 

You bring up a good point. The part about not saying a number has multiple parts. You can absolutely negotiate at any point and be the first to say a number. The reason I advise against it has to do with the number you start from.

Too many devs think of their current salary and then negotiate from there. Companies have a salary range that is often invisible. So when a dev starts with a number they often put themselves too low in the salary band. If they go too low outside the run the risk of looking incompetent, if they go too high they are unaffordable.

When the company gives the number, on the other hand, they will pick one based on their internal range, their internal urgency, and how willing they are to continue looking. This generally leads to them picking a higher number than most devs will, and then you can negotiate up another 10%.

 

In the same time... I have cases with companies saying e.g. 90k and then being able to raise up to 135k throughout the negotiation process. Which also indicates for me that a company can start way lower than they are prepared to pay.

 

Thats a lot of money, good job buddy!

code of conduct - report abuse