Since candidates will always ask for the top of the band, I'd expect either very tight bands and candidates get moved to "more appropriate" openings or bands covering 3 standard deviations so employers can claim the range is in good faith, but still leave room for negotiation.
Maximum salary: $1,000,000 per year.
Legal compliance achieved, while still effectively maintaining confidentiality of salary info.
The range must: "extend from the lowest to the highest salary the employer in good faith believes at the time of the posting it would pay for the advertised job, promotion or transfer opportunity."
It's amazing how some people lazily assume they're so much cleverer than everyone else.
A good heuristic is to assume you're just plain wrong if you think you've discovered a way to weasel out of a law with only five seconds worth of thought.
So unless you can read minds, it'd be hard to prove that the employer doesn't believe this is the salary range.
And besides, 10K to 1M is a pedantically large range to illustrate this dynamic. Realistically a lot of companies could provide a range from $60K to $300K for software developers - both of these are salaries I can attest to firsthand. This isn't as stark as a 100:1 range, but a range of 5:1 is still a wide enough range such that expected salaries are still effectively unknown.
I wonder what it would take to update these laws to require total comp disclosure instead of simply salary disclosure.
This is the wrong target. Large companies are generally fine with these sorts of laws. It's the small companies who now have another of ten million disclosure laws they have to follow, laws which vary from county to county.
Remember that it applies only to salary (not total compensation) and it applies to jobs done in NYC, not jobs done for companies whose headquarters are in NYC.
For my first salary role I took half the advertised pay as I knew less than half of what they wanted.
With this crap I'd just not get the job.
https://www.denverpost.com/2021/06/26/colorado-remote-work-j...
https://www.theatlantic.com/politics/archive/2021/07/remote-...
Sounds good to me.
When your given range and that range don't roughly coincide, they'll ask why—and then fine you for your bullshit "are you a mind reader?" response.
And then you can point out to entry level software developers and much more senior ones and demonstrate that such a wide range is not only feasible, but already exists between employees.
If it actually does do that, then spell out why that's the case (e.g. what's the penalty for hiring someone for a salary outside the posted range)?
The OP makes it sound like this is only to address certain information asymmetries in salary negotiation:
> Currently, New York City employers are allowed to withhold pay information until the end of the hiring process.
> Advocates of the bill argue that this forces applications into unequal negotiations throughout the hiring process without the critical piece of knowledge around salary.
> “Lack of salary transparency is discriminatory and anti-worker,” said Rosenthal. “Every New Yorker should have the right to determine whether they will be able to support themselves and their family when they apply for a job. It is time to level the playing field, and restore some dignity to New Yorkers seeking employment.”
> ...Job postings without salary range information can be reported to the city’s Commission on Human Rights.
Based on the article, I see no reason why someone would be prevented from consenting to pay below the position's current minimum, so long as they have full knowledge that is what they are in fact doing.
As they say, the path to Hell is paved with good intentions, I see no reason why an HR department would take the risk.
When I was in my early 20s I had no degree or real experience. With misguided laws like this I wouldn't of been offered a job. It's not on your employer to pay you 100k for your first job. You endure making a bit less for a while.
Then about 3 years later you get your 100k job
The other path to Hell is to not act on good intentions.
> With misguided laws like this I wouldn't of been offered a job.
No, you're just making that assumption.
1. The most likely => you don't get any offer.
2. You mutually agree to take a lower offer. It's a lower offer, but it's also much, much greater than zero. You got your foot in the door, can develop your skills, earn an income, and make progress in your career instead of continuing to interview.
But they don't need to hire in NYC, and companies look at other regulations when deciding head count.
For example, you'll see a lot of startups freeze hiring at employee #49, since in the US (and other countries), there's a ton of HR requirements that kick in, including submitting IRS documents on magnetic tape.
One of Netscape's early advantages was that since they knew they would hire thousands of people, they skipped over all of the entry-level HR systems and started with enterprise-level systems. It was controversial at the time, but turned out to be the correct decision (the first exec was from SGI, so knew what growth looked like.)
I think the most likely scenario if you don't meet the qualifications is you get ghosted.
With salary requirements, maybe people will waste less time on pointless applications, and there will be less ghosting.
That's not how it works.
There is going to be an evidentiary standard (such as "preponderance of the evidence" -- it won't be "beyond a reasonable doubt") applied by an administrative law judge.
The judge can very well decide he CAN read minds -- unless YOU can read minds, or he decides to tell you, you won't know.
Even judges understand there is a difference between "entry level" and "senior."
And on the subject of the window, most places have much narrower bands than that for a role. It might be that wide for all engineers, but not for senior engineers for example.
I haven't read the background for this law, but I guess it's meant to help people earning less than $100k, and people with less power to negotiate an initial offer.
Only if you ignore unintended consequences
Some people seem to think the hand-waved threat of "unintended consequences" should be enough to kill any policy they happen to dislike. It's not.
I'm tired of the broken record fearmongering about unintended consequences, especially when it's paired (as it always is) with no constructive alternative to address the problem in question. It's an unpersuasive attempt at preventing improvement to the status quo.
If you don't have the courage to ask how much the job pays on the first call that's your problem. If you agree to a certain wage that's what you agreed to.
So? The kind of information asymmetry that this regulation addresses is an actual issue, whether you want to acknowledge it or not.
> If you don't have the courage to ask how much the job pays on the first call that's your problem.
That's not the problem something like this is meant to solve. Rather, it's probably meant to deal with situations like when an employer low-balls someone who doesn't know what they're worth, and they take the offer because they don't know any better. Eventually someone like that will probably get wise, but this gives them a much cheaper shortcut to that knowledge.
By the way, your whole story makes no sense. If you weren't qualified why did you even get an interview?
There's plenty of opportunity in this country if you're willing to work for it.
The question is: how do you get an interview _for a position_ where you don't meet the requirements _for that position_?
So if it's a startup, then you don't meet the lowered requirements of that startup.
It doesn't make sense. They wouldn't interview you if you didn't meet their requirements.
That job changed my life, I'd rather just accept some people are going to make more and some are going to make less then create a dystopia where you need 10 pages of documentation to justify every hiring. There's no way this law is going to work out the way people think it well, if anything it encourages less full-time work. If you run the risk of being audited by a fairness officer, why not just outsource it instead?
Why not lean on consultants more?
As discussed elsewhere, many companies are just not hiring people from Colorado, which has a similar law. I can't find a better example of this not working.
They demonstrably didn't, since they interviewed/followed up. That's why your story doesn't add up.
Not doubting whatever you say happened, just your interpretation doesn't make sense.