[tossaway1]

I share if the candidate asks. In the end the candidates requirements come out though. If I say X, they'll often say, oh I really need Y. I can work with that. If they just walk away when I say X, that's fine too -- it wasn't a good fit.

[Riod]

That's not a fit issue. They just don't want to work for that wage. Find someone who will. Why do they have to ask? If you're really interested in efficiency, state it upfront, atleast the lower and upper bounds.

[tossaway1]

It doesn't matter to me who asks first, just the the discussion is had to avoid wasting time if it's likely to be a problem. Sometimes they ask about salary range, sometimes I ask about salary requirements.

Debating whether a disconnect on $$ is a "fit" issue seems kind of silly. If it's not a job they would take because of pay, it's not a good fit for them.

[Riod]

Precision matters. Fit is a poorly used term to basically mean, we don't want you for reason X but don't want to tell you that.

[tossaway1]

Precision matters, but you're just nitpicking based on your interpretation of "fit". I guess you're thinking of it as whether the candidate is "fit" for the position. My use of it was referring to whether it was a fit for what they're looking for (where money is obviously an important factor).

[Riod]

Simple solution. Set up an Ask HN: What does job not being a good fit mean to you. See how many people say it relates to cultural fit vs pay.