> but here is an alternate ending: they regrade the job req to meet your requirement. They won't always be able to do this, but when they can you win big.
I find it very unlikely that a company that cannot even afford my minimum rate is going to turn around and "win big" unless winning big means getting what I already have with less job security on top (if I am pushing well beyond the salary range - I am the first one to go when the money runs dry).
I am not a celebrity programmer who is worth keeping around just for the bragging rights, I survive by selling the value I add at discount. If this value is unfavorable then neither myself nor the counterparty benefit from such a business.
I really don't agree with this. I've gotten a ton of value out of seeing what works--and even when I don't go to work for somebody, I've usually stayed in contact and made a lot of acquaintances that way.
But I treat interviewing as a game, and a game I enjoy; last time I was looking I interviewed at thirty-five places just to keep meeting people.
There isn't always "1 truth". There are multiple ways to answer most development questions. A range of answers are usually acceptable. A reaffirmation that an answer is effective is a change for me. It's an additional weight for those answers that are successful (even if I have to reason out to the interviewer why). That's just my algorithm.
In the long run $30k won't break them, if it does then they have bigger problems. Most firms that intend to gain a competitive advantage realize they should pay a little extra to attract talent. Be that talent.
More importantly, it does not even have to be in any error band as all it takes to suffer from anxiety over being paid too much is to believe your own estimate. It is not worth it for me as there are plenty of jobs where I'd get just as much or more and be confident the company can afford it.