Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's theoretically optimal not to give the first number.

The employer doesn't know how much you're making now, and can't legally ask (not in CA and NY anyway).

They have a theoretical top comp they're willing to offer for the position. Once you give them your number, their top offer becomes min(your_goal, their_top), which cannot be higher than their_top.

In simple terms, if you know your market value, and you tell them that number, you will never know of or benefit from their willingness to pay above that (often for good reason).

> For example, suppose both you and your counterparty know that the negotiation is going to be within the 100-150k ballpark. You tossing out 145k as the first number, will play much more to your benefit than allowing the recruiter to toss out 105k as the first number.

That would be the recruiter messing up. His initial goal is to get you in the door, unless your expected pay ranges do not overlap. In this case, they do, so saying a low number just means he's encouraging a potential fit to walk away.

A recruiter in this situation will typically state a range, and definitely won't just quote a number near the bottom of the range.



> It's theoretically optimal not to give the first number.

Only if you ignore transaction costs of the interview process. Unless you feel you can get their numbers before you start, it may be worth the time savings to give up some potential future leverage.


Not being the first to quote a number just means that - letting them bring up the first number.

It doesn't mean flying out for an onsite without knowing if they can match your pay. That's obviously silly.


Right, but employer normally won't offer a number pre interview. So the dynamics are tricky to expect them to give you a number while not offering one yourself. The article doesn't touch on how to pull that off. Have you been successful getting this info without giving your details up?


You're assuming that if you don't give the first number, the recruiter will give you a number that hints at "their_top". Realistically though, recruiters are very good at figuring out what your ballpark is, based on your experience/qualifications/market-conditions, and will toss out a number that's in the lower end of this ballpark, regardless of "their_top". At that point, not only do you not have any clue about their_top, but you've also allowed the negotiation to become anchored at a lowball number.


> Realistically though, recruiters are very good at figuring out what your ballpark is, based on your experience/qualifications/market-conditions, and will toss out a number that's in the lower end of this ballpark, regardless of "their_top".

Excuse my skepticism, but have you ever actually seen that happen?

Your supposition reflects lack of understanding of how both external and internal recruiters work, and how they are incentivized.

Their KPI is the number of candidates sourced by them who got hired. Which means they are two-way salespeople: they sell you on the position, and sell the employer on you.

Their key goal in the early stages is to ensure you go through the process if you are qualified. They have zero incentive to lowball you. If anything they can and sometimes do get in trouble for inflating a candidates' comp expectations.

So what you described, where a recruiter tries to preemptively negotiate you down, simply doesn't happen because it is counter-productive behavior for recruiter. He has absolutely no reason to lowball you, and every reason to make you aware of the highest pay you can possibly expect - because that will make you excited to come in for an interview.

> At that point, not only do you not have any clue about their_top, but you've also allowed the negotiation to become anchored at a lowball number.

This is negotiation between professional adults. The fact that the other party said a number doesn't obligate or "anchor" you in any way. You can simply say "sorry, but I'm looking for $X", or (more likely, if you have options) just assume the pay expectations aren't matching and walk away.

The risk of the latter happening is why you'd never see this "recruiter lowball" in reality.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: