Great, then you know the good faith range and you're good to go.
> then I should reject you so you can re-apply for the other role
In my experience this happens all the time at big corps and the government. Except it's not a rejection, just an "oh actually we have this other open job on the books that would be a better fit - let's transfer you over to that"
No of course not. You simply offer the better role at the higher salary. Or if they turn out to not be good, you tell them that you are going to deny them this role because they are not qualified, but you'd be happy to offer the lower role if they are interested. In fact, I'll bet this will happen a lot as a workaround for this law.
The goal of this law, and others like it, is fixing the bottom end of the range to prevent low ball offers from employers that know women and minorities (and others) frequently undervalue themselves.
Those are going to be two vastly different numbers. Which one are you looking to pay for? If you have budget for a superstar, why would you settle for just-over-the-bar talent?
I kind of find myself suspecting that what you're really hoping for is that you'll find someone who has superstar talent, but doesn't know their market rate, so you can hire them at just-over-the-bar money.
What I can see happening is that more corporations start doing SDE 1/2/3/4/5/6/7/8/9/10/11/12, with different ranges, and most of the interviews are at 7-10 and are "releveled" at 3-5. We will end up in the same place we started but with more games.
You're no-true-scotsmanning 'superstar' here to assume, I suspect, that one of the attributes of a superstar is being in the know, and so on top of the industry and job market that they are aware how much their skills are worth.
For a certain class of superstar that may be true, but there are many, many very strong developers who are working in backwater job markets and have not looked for jobs in a while who literally have no idea what typical total comp offers from serious tech companies in hot markets are like.
There are plenty of high skilled people who have been blown away by an offer they thought was incredibly generous, only to discover they were actually lowballed.
Been there done that - Not incredibly low balled. But probably 10%. But as you learn the industry, have a network of former coworkers who don’t mind sharing salaries and external recruiters, it gets easier and you just job hop. This is mostly on the enterprise/Corp dev side of development where most developers work.
It’s quite easy to find out compensation for the larger more well known tech companies at places like levels.fyi.
Before anyone thinks I’m putting down “enterprise developers”, that’s what I did my entire career from 1996-2020.
For all intents and purposes, that’s still what I do. I now also write a shit ton of yaml, HCL, PowerPoint slides, and PRFAQs at $BigTech and “consult”.
And you're getting this data from, where exactly?
Having done a fair amount of hiring over decades... because you don't know who will show up.
The minimum bar of the job description is who I need at least. But occasionally someone shows up who is insanely perfect, hitting on every optional wishlist item. I'll pay a lot more for that person, but I can't count they will apply because I can't wait a year for the perfect person to show up. So I'm also happy to hire someone at the minimum bar if that's how it goes.
> Then they need better data. A great way to get that would be looking at all the other job listings with salary ranges if they don't already have access to back channel data.
You're missing the point: the variable is the candidate, not the role. I know the market rate for a candidate that is just over-the-bar for my role, and I know that market rate for a super-star who can not only do this role, but is probably already capable of doing the next one.
> Then it should be multiple listings with different requirements, even if the only difference is years of experience.
So, what if you apply for a role that turns out to be wrong for you based on my assessment of you then I should reject you so you can re-apply for the other role? That's ridiculous.