In limited experience, I've been unclear if this strategy changes when dealing with companies that actually list the salary range (generally when required per some recent state laws).

▲

alistairSH 3 hours ago | parent | next [-]

Most of the time, I'd just answer "I'm ok with your published range, we can proceed." or similar.

But, I've also seen ranges that span hundreds of thousands of dollars. Like "Software engineer: $150k-$250" which is a ridiculous range that makes it almost meaningless. I mean, what are they thinking - any candidate worth their time is going to aim for the $250 end...

▲

sebzim4500 2 hours ago | parent | next [-]

Even that range is much better than nothing. A person making 300k knows not to bother with the process and a person making 100k knows that it is definitely worth applying.

▲

onionisafruit 3 hours ago | parent | prev [-]

GitHub’s current Senior Software Engineer listings have a range of $124k - $329k

	▲	alistairSH an hour ago \| parent [-]
		That feels like malicious compliance to me. I'd expect vastly different capabilities and output across the spread. At least in my region, the low end of that is somebody a few years out of college. And the high end is... well, pretty much nobody with that title is making that much.

▲

mooreds 3 hours ago | parent | prev [-]

Yeah, I think if they have published a range and you are comfortable with it, you can say "I reviewed the range on the website and am comfortable with it".

If you are not comfortable, then I'd be clear why, with data, upfront. "I saw the range on the website and it seems low based on X, Y, and Z. Is that range flexible?"

Whether the answer to that is yes or no, you'll be in a better spot whether to decide to move forward.