61–70 of 544 posts
I think they should post salary minimums instead of a range - that huge range is just eye candy. Oh, but not enough people will be interested at the minimum? Then your minimum wasn't good enough and isn't actually the minimum.
> No need to waste time with 7 rounds of interviewing only to find out the salary is 50% of what I currently make. You can just ask at the end of the first interview. I've never had a problem doing so.
I don't like having to ask.
We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
A lot has changed since 2014. Any more recent metrics on this?
> No need to waste time with 7 rounds of interviewing only to find out the salary is 50% of what I currently make. You can just ask at the end of the first interview. I've never had a problem doing so.
I'm generally in favor of posting salary ranges. I like to know how the company values the positions they are hiring for, and I don't really want to talk to a recruiter at all if it's not going to be a salary match, so I like the idea of being able to screen better as a candidate.
But now that I've been on the hiring side, there's some flexibility I think we lose if we post those ranges: what do you do if you like a candidate, but not for the role they applied for? Perhaps their skills and background are not quite what you're looking for in this role, but you know another team has an open rec and this candidate is perfect. Or, maybe you've posted for a particular seniority range and you like the candidate but they are more/less senior than the posting, and you want to scale the position up or down to meet them. Neither of these scenarios (which seem to happen with regularity) preclude putting the range in the job description, but then the redirect or rescope feels bait-and-switchy when it's really not.
We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
This is essentially Tinder “swipe left or right” and it should treated that way.
We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
You might not be wrong, but a higher salary makes me less miserable than a lower salary
We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
as you say, the salary is a sign of respect from your employer, and including that number in the job ad is an easy way to signal to prospective employees exactly how much you respect them.
We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
Care to mention what they are? Because I suspect your ranges are out of line with industry standards that have risen quite rapidly.
I know because I've started responding to any recruiters that sound interesting asking for comp ranges and they are all below my current base, let alone TC.
If the upper bound of your range doesn't exceed $350k there is no chance that any of the senior engineers I know will apply and honestly to get something to think about leaving a job they are moderately happy with you'd have to have that be the lower bound of your range.
But I suspect you're posting ranges that are less than or barely over 200k at the upper end.