[huntsman]

I feel this hard rule of never mentioning a salary as candidate is too simplistic.

There's certainly the risk of lowballing yourself if you don't understand your market worth but there's also the opportunity to anchor the starting point of the negotiation.

Learning the strategies for successful negotiations is a skill a recommend everyone to look into. Skills in this area can have a very high payoff in your professional and personal life.

[Mikho]

Technically, considering both a company and a candidate are in the same ballpark as to salary range, salary expectation is the only leverage a candidate has left for further negotiations. There is no reason to give away every single leverage. Everything else a candidate will provide during the interview process. Expected salary is the only thing left unknown to a recruiter.

[huntsman]

My point is that being first to name a number isn't necessarily "giving away" your leverage. If you give too low a number you certainly may be, but naming a number could also Anchor (https://en.wikipedia.org/wiki/Anchoring) the negotiation at a higher point.

Lets say you've done your research and you know the company pays $160k-$200k for this position and you've done interviews and they want to hire you.

They want a number from you of expectations.

Sure, saying $160k is dumb and you've lost out. Refusing to say anything might get you $180k.

But if you are confident in your knowledge of the ranges putting out $240k as your starting number may be a good strategy. Sure if you got it wrong they might have offered you more but unlikely. But more likely the recruiter is now in the position to try and negotiate you down to their salary range vs you having to negotiate them up.

All of this is somewhat situation dependent but my point is that absolutist advice on never be the first to name a number is not always correct.