The way the Hired platform works is that companies must submit an initial salary offer when they start the interview process, and so all interview requests have salaries attached to them. Of course these offers can be negotiated later, but for the vast majority of our hires on the platform, the final base salary is equal to or higher than the initial offer given at the interview stage. Therefore we feel confident that this salary data is representative (if not a slight underestimate) on 2015 salaries for software engineers.
That's a fair approach, although I agree that it adds a little bit of ambiguity around the process. As noted in other threads, there can be metagaming around the salary process on the employer side, so caution is still necessary.
I'm glad you've had a great experience on Hired and that it has changed your life for the better.
I'm surprised that your experience is that the initial salary offers (at the interview request stage) are significantly different than your final salary offer, because I can tell you that this is not the experience of most people on our platform. The majority of the final salary offers are equal to or greater than the offer given at the interview request stage. On average the final salary offers are slightly higher than the interview request offers across all Software Engineering Hires on the Hired platform.
The numbers are more or less the same anywhere when you look at averages, if you look at glassdoor for bay area it's likely the same.
So why use interview requests in the data at all? The fact that some joker company offered me 90k on hired when everyone else was offering 130+ shouldn't pull the average down.
So I checked the methodology and found something odd.
> The salaries included reflect more than 80,000 interview requests and job offers from the past year
Why are interview requests and job offers lumped together? Wouldn't there be disproportionally more interviews by definition? As a result, it's very hard to gauge the sample size of the salary data.