Ask HN: Is there evidence for anchoring in salary negotiations?
When it comes to negotiating pay, two opinions are offered:
- Don't name a salary; let the employer make the first offer, because it may be higher than what you'd have asked for.
- Anchor by naming a high salary, as high as can you say with a straight face given your skills.
Is there quantitative evidence of these when it comes to salary negotiation?
I came across one that says that "I'm looking for $100K, but negotiable" is better than saying "I'll even work for $1 but I'm looking for a fair salary" but I'm not asking about anchoring high vs anchoring low. I'm asking about anchoring vs not being the first to name a price.
Is there any source of information more reliable than some random person's opinion?
(
5 comments
| 8 points
| on HN
)
I'm given a budget and that's my absolute ceiling. If there's a high anchoring I just pass because there's nothing I can do - the budget is the budget.
So in short, you can try anchoring high if you know that will be at least in the ballpark of the budget for that position even if it's at the higher end.
This has a few implications-
- Anchoring might work to some degree since the company have some freedom in deciding the salary
- If you cross the upper range one of two things can happen- you will be declined and get (or not) a counter offer, or you'll be bumped to the next job level (engineer to senior etc.) if the company really appreciates you.
- Future salary raises are also bound to the same ranges, this means that if you start at the top you will have lower raises, or more pressure to move to the next level