This was an awesome post and I really enjoyed it. I hope to see more data driven analysis like this in the future. I actually try to respond to every recruiter email I get, even if they are obviously generic (though I have my limits). My one goal is for them to give me a number. I typically thank them, ask them how they found me (specifically what keywords they searched for, etc) and what the salary ranges are for the position. I usually frame it to "ensure I am staying market competitive". I'd say 50% of the time I get the dodge one way or the other, 40% of the time they are paying below what I'd expect to be paid for the position, and 10% is what I'd expect. Only one time was I surprised by the salaries thrown out and those were positions in NYC. That said, I'm going to get a little cynical, so be warned.<p>Keeping salaries secret has been a huge tool wielded by hiring managers and HR in order to suppress salaries for a very long time, especially with the way engineers are typically pigeon holed in to broad titles. I don't see that changing any time soon, as much as I'd like too. It'd solve a number of problems for our profession if that were so. I'd be interested to see what the differences are from the initial offer when reaching out and what the official offer is if a candidate accepts.<p>I'm guessing most businesses that use this platform have figured out the optimal number to get responses from recruiting emails and then used any leverage they can get in order to discount the engineers skills and experiences in order to get them in to a lower salary. Unfortunately engineers are notoriously bad negotiators and we start to buy in to their arguments and end up accepting bad deals and we don't realize it.<p>But, this is definitely a step in the right direction.