> Our salary offerings are very aggressive to the developer's benefit
Your example covers the case of "mid-range salary", overqualified applicant doesn't want the job, but wasn't going to get hired anyways because overqualified. Parent's example covers "very high salary", underqualified applicant wants the job just because the number is high. Given the "salary offerings are very aggressive", then why would we be talking about a "mid-range salary" case.
The ones that actually pay top of market rate I reach out to, not the other way around.
(Especially since it's only a problem if the higher pay motivates more bad applicants that are hard to distinguish from good applicants. If it encourages 100 people who have no relevant experience to apply, that brings the average down, but it doesn't increase the probability of making a bad hire.)
When you put a range of $100-120k, the very high quality candidate who won't accept an offer less than $150k doesn't apply.
Or, put another way:
> It could simultaneously be true that including a good salary range increases the number of applicants who are good fits for the role, and also true that including a good salary range decreases the average quality of candidates.
Part of "good fit" could be "willingness to accept compensation in range". If the job range says $10/hr, the average quality of applicants will go down because the MIT Ph.D.'s won't apply-- but you weren't going to hire them at $10/hr anyways.