As an employee, sounds like not my fuckin problem. I'm not about to go through 3 phone screens, a take-home test, a full-day onsite, etc. just for the privilege to be low-balled or even worse denied.
> I think it will be about $X
Oh! So looks like it's not that hard to ball-park a number off the top of your head. I don't get this "how the world really works" junk. How the world "really works" right now is that job searchers are having their time wasted and don't have tools to determine what the market for various positions looks like. For work that apparently amounts to texting the on-staff recruiter I couldn't care less.
> if the ad doesn't specify salary...just don't apply.
So all job postings before these laws have been put into effect? Looks like someone doesn't understand how the world really works.
RTFA. The job range has to be "in good faith" if the job posting encompasses a range of experience levels, that's allowed. The range just has to be "in good faith". That's such a low bar to clear and from your own hypothetical the work required from the employer is basically nil.
Actually, they're getting paid for the their time. I'm not. I'm actually burning my time.
> Recruiters should be talking about numbers in the first interview.
I'm going through the recruitment process right now and the numbers out of the gate are always lowball figures (possibly personalized to me), because of two reasons.
Because they want to see if you accept it or not. I'm sure a lot of people coming into the bay area from other cities/countries will be like "wow, 185k, that's awesome" & they'll figure it out that the company was willing to pay upto 350k for the same work.
Secondly, publicly advertising salaries have a big impact on the people who are already in the building. This is pretty much already a problem when you bring in an H1B who has to put their salary into the DoL database and post notices in the offices with their pay. But this is only base pay, not including bonuses or stocks, so it's easy to cap the base pay and fill it up with bonus packages.
So the companies are legitimately balking at this because they'll have to pay their existing employees more if they put out an attractive posting, but if they put a lowball figure nobody would even show up to interview - only people who already make lower than the lowball figure will show up & then try to negotiate upwards.
I'm currently interviewing and this is a weird dance, sort of like buying a car.
I've only got a single response to someone asking "Is this range acceptable" - "I'm looking at multiple offers and being the second best offer is no good for you and I'm not negotiating before an interview or comparing offers. It's your bid, not my ask".
I guess it's a position of privilege to deal from. My need to go to back to work isn't economic, I'll just languish if I don't find a job & become truly feral :)
Let's phrase this properly: companies are balking because they'll have to pay existing employees market rate.
Them: "What's your number"? You: "$350k." Them: "Ok, cool lets move forward." or "That's a lot of money and we can't pay that much. Thanks for meeting with us."
I'm assuming that you've done your homework and know what a reasonable top of the range is. If that's the case, just say what your number is and let them decide if it's too much.
It's very possible for a candidate to be thinking something like "I'm currently making $200K. I think it's possible I could get $300K, but $250K would probably be acceptable, and I might even settle for a lateral move of $200K if I find the position really appeals to me." What should they say? $300K and possibly price themselves out? $200K and possibly lowball themselves?
I was surprised with how much I was able to get away with negotiating my first tech job. It was a little bit of back and forth, a recruiter was involved, and I could just poker face my way into a six-figure job.
If they say 200k are you want to just say 250k and see if you get it.
Like everything it's just quicker and easier if you rip off the band-aid and just do it.
I’m nowhere near the Bay Area, I know what Bay Area salaries are by looking at publicly available sites.
I also know while I never made above $160K until starting at my first “FAANG” two years ago working remotely, there is no way in hell I would accept less than $250K - $300K to ever give up my big house in the burbs in a much lower cost of living area and that’s only because my kids have already graduated and my wife and I could stay in a smaller place and not worry about the school system.
Well I personally would never work a job where I had to go into an office again.
>Actually, they're getting paid for the their time. I'm not. I'm actually burning my time.
nit: "they" refers to the business, not the employee conducting the interview.
I'm ok being denied. You set the bar and I don't meet it, fair enough... far worse is wasting my time when a simple discussion about salary at the start (at least after the first interview) could have saved us both time.
These benefits that we're experiencing by being able to just walk away from an onslaught of recruiters begging anyone with +5yoe don't apply to other job sectors or even entry-level positions in tech!
Can you bring it up early? Yeah. Should it be in the job listing? Absolutely. I've yet to see a convincing argument otherwise.
Make it the law that you post how much you're willing to work for on your LinkedIn profile and that you have to supply it to employers at the start of an application process so neither side is wasting time.
Seems like that would address all your complaints just as well.
The point of this legislation is to push salaries up by forcing employers to reveal their hiring budget up front. That way, prospective employees can more easily shop around for the highest salary.
Would it be nice to know in advance, yes. Is it necessary for me to know in advance so long as I can get it during the fist contact? No.
Maybe I got lucky but I've always been able to figure out the rough range they were thinking of paying before the first real interview. In case of recruiters, sure, they want to talk to you first and that's 15 minutes you'll never get back.
Personally I just don't move ahead unless I have some signal about salary to not get into that situation.
There's no black and white, fits all, thing. Never is that simple. The only fair thing I saw so far is along the lines of if there's any indication that company is decent and you're interested in a role, if you pass a filter to get a call: do the short intro about the company and the people and the role, do the short intro (after company intro, that's important because you can tune your self-presentation) about yourself and then go a bit back and forth on the expectations from both ends, including financials. If all things are aligned then you proceed forward. If there's no talk about financials on that call, not worth it or if there's no indication there's an honest answer we have to see since we're talking about outside of what we initially even asked for but here we are - offered more. Getting low-balled there, in such environments, is hard since the day you start you get to feel and know that you, indeed, were.. and what did company accomplish with that then? Nothing good. Overall, that's about half an hour or so IF there's indication that company has good reputation. If not, or a startup, or you're just shotgunning it across to get to the high score (and hopping) - there's no help, it's a gamble where number indicated will help but will also close a lot of real good opportunities.
This salary range thing won't fix that. Ready? The job listing is now "$100k to $200k depending on experience." If you are making $140k and hoping to make $160k the range doesn't help you at all. You still better talk about salary up front!
I make $60k because my company underpays and I don't work in tech where jobs tend to be very cushy and compensation information abounds! I start seeing job listings for my position with a floor of $80k. Wow I just made $20k more thanks to reducing information asymmetry!
For a real example, I had plenty of recruiters and companies that _refused_ to "talk numbers" until the end of the process. Now that I'm further along in my career and finances I have the luxury of being able to shop around and kick companies to the curb that don't suit me.
When I was first leaving college and had no income and little/no savings? A huge power imbalance in favor of the companies and I personally didn't feel comfortable pressing about salary. A law like this that I could have pointed to to just say "you have to tell me, them's the rules" could have had immeasurable impact on my career.
This law obviously doesn't solve every situation, but you must be able to see the information asymmetry and power imbalance that exists that this will help resolve?
> So all job postings before these laws have been put into effect? Looks like someone doesn't understand how the world really works.
I think it does actually work like this a lot of the time. Either the candidate doesn't bother to apply, or they apply because they got a salary estimate from another source.
A relatively unknown company that isn't posting salary info is kind of a red flag.
I feel like I'm living in an alternate reality than others in this thread. Even in tech I've had to put in a ton of legwork to find salary estimates for jobs and often the data was very incomplete. Combine the weirdness with roles/titles that companies can have, how do you search for salary info for "assistant to the guru of front-end"? Am I a devops engineer, SWE.Is there different pay for being on-call?
Not to mention it being even worse for everyone I've talked to that doesn't work in tech. Basically everyone I know has gotten the best salary info from the source, during the interview process.
In the rare exceptions, they are actively looking to leave their current job and are worried about cash-flow or even more extenuating circumstances like deciding whether or not to change careers.
I've _never_ seen a company offer salary information (numbers) in the job listing unless it was explicitly required by law (CO, soon to be CA and NYC, government jobs, etc).
In the September HN who's hiring thread, two of the first four posts include salary info. Remote, and NYC.
I didn't disagree with your main assertion, only with your use of absolutes. You said:
"So all job postings before these laws have been put into effect?"
and:
"I've _never_ seen a company offer salary information (numbers) in the job listing unless it was explicitly required by law"
If I asked you to tell me how much you'd pay for a shirt, you'd either have to give me a wide range, or start asking questions to understand what you're getting. A formal tux dress shirtfront? A dirty old Hanes undergarment?
I’ve had overqualified people apply for a position, what happens is I don’t hire them in that position, I open up a new “named hire” for a higher salary.
Ridiculous. They already have to get enough information to make an offer and negotiate at some point.
> The fact is that many employers don't actually know what they would be willing to pay someone.
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.
> It is also true that a single job ad might be aiming to employ a number of people at various positions of seniority and experience.
Then it should be multiple listings with different requirements, even if the only difference is years of experience.
> So it does not surprise me that governments would legislate to require job ads to do the same - essentially because of ignorance about how the world works.
The way the government does it is more equitable, so it makes sense that they are trying to legislate that to the private sector.
> If it makes you mad that job ads do not list salary, then there are good reasons and you will just have to get over or it not apply for that job. It's that easy - if the ad doesn't specify salary and that is a key requirement for you, don't get angry, just don't apply.
This is exactly the problem. If they aren't required to list it, they won't. And this is harmful to people who aren't good negotiators. And also harmful to women and minorities, as countless studies have shown they are chronically underpaid in large part because they aren't willing or able to negotiate.
That's why there is a push to force companies to list the salaries.
> Far more important is to know the salary target that you are aiming for.
You're right! The best way for me to know what salary to target is with lots of data about how much similar jobs pay. A great way to get that is job listings with salary ranges, since I don't have access to data like the person offering the job does.
> 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.
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.
Not a gotcha, just curious what were the factors that made you take that decision.
I think people would be more willing to accept this if the application process was not such a complete cluster fuck 99% of the time.
So many sites want you to upload a resume, and then also re-type the whole thing into some clunky form so that the company can seemingly index it or search it or whatever
Then after your resume has been randomly selected for review you get to waste more time with useless recruiters and/or HR people for some kind of preliminary screening process that makes little sense.
If you're lucky enough to actually start to enter a real interview process you can plan to sink another 2-8 hours of your time before the discussion of salary ranges is even remotely danced around.
Finally, after a ton of hassle you learn that the company wishes to pay approximately minimum wage for this position and wants to pay you in IOU's, bottle caps, or gift vouchers (only a slight exaggeration sometimes).
If a company cannot give a salary range that is even +/- 20%, perhaps they're not actually ready to make a job posting and invite people to hopelessly waste their time on the application process.
They know, they know. They just don't want to be the first one to put numbers out there, because they want to low ball as much as they can.
If it's genuinely true that a company has no idea what they might pay someone they want to hire, they're just not ready to hire someone. "It's that easy."
It sounds like you've missed the point of the responses then. They aren't telling you that you're wrong, they're telling you that how recruiting works needs to change.
Well, not for long, if I live in NYC and this rule passes.
>It's that easy - if the ad doesn't specify salary and that is a key requirement for you, don't get angry, just don't apply.
If this type of regulation spreads, we can just turn this into a nifty fliparoo counter-argument: It's that easy - if not posting a salary range is a key requirement for you, don't get angry, just don't post. Maybe ask the HR manager to do a quick skills upgrade and program in C# themselves.
Looks like that's not going to be the case anymore.
One of the reasons I want to know the salary range upfront is that it tells me the bare minimum they are paying for that position. Companies love lowballing candidates, so I usually don't apply for an offer that doesn't pay at least the minimum I'm looking for.
> Far more important is to know the salary target that you are aiming for.
It's also important to know the company's budget. I don't enjoy working at places that can't afford a $200/year IDE license, to name a common example. Fat salaries often come with fat budgets.
edit: regarding your edit, which companies have you recruited for? I would bet my own career that you’re wrong to suggest that recruitment works like this for more than 10% of companies.
Recruiters are usually paid based on a percentage of the salary. It's actually in the interests of the recruiter that you are paid as much as possible, strictly speaking.
In reality, my goals as recruiter are:
* happy client
* find a new employee who the employer is super happy with six months down the track
* find a new employee who wants and enjoys this job, and will thus stay
* at a salary that the new employee is happy with, that will not have them looking over their shoulder thinking they have udnersold themselves
* at a salary that will ensure we are not beaten to the punch by another higher paying employer
* at a salary that fits the goals of the employer
The idea of "getting an employer a bargain" implies that I don't care about the job seeker. Believe it or not, I do. When someone comes to me who is a great developer, and is asking under market rates, I discuss that will them and let them know where I think market rate is for their skills and experience.
It might sound cliched, but my job is to negotiate a deal that everyone is happy with, and every gets what they want. Anything less will fail because the employee feels they are underpaid, or the employer feels they overpaid.
I believe the above approach to dealing with salary gets everyone what they want. And yes, I the more it is the happier I am, but it would be very much against my interests to manipulate that.
Seems like a recruiter is much more likely to double his compensation by spending half as much time per hire versus paying twice as much, given that salaries are relatively inelastic. Similarly, real estate agents are incentivized to get a pretty good price but mostly optimize for lower effort per sale.
Similar studies for real estate agents who are also paid on commission shows that this is not true. It’s more about velocity than optimizing a single candidate.
https://freakonomics.com/2008/02/real-estate-agents-revisite...
Simply because recruiting is a very low barrier job - you get countless bad recruiters... even at reputable recruitment agencies - horrible child-recruiters.
There is a reason real estate agents homes sell for more than anyone else's -- because they know the real value of the market and have an incentive to go high when it's their own home. Recruiters are the same.
Different incentives for all three parties.
Obviously for them, being able to close more candidates at a "high enough" salary is preferable.
The HN crowd is exactly the opposite type of people who would benefit from this. Job definitions become fixed. You want to try your next project in Rust? Implement a new database? Start learning the customer-facing side of things? Too bad, the job description didn’t include that, and your salary range is locked in to the job description.
There is a chance your duties get so out of whack that you request HR to reinterpret your pay, but not only is that a laborious and somewhat arbitrary process, but it seems both HR and management are incentivized to not rule in the employees favor.
So make the salary range bigger.
Employers should make a separate job ad for each pay grade, and they should provide a detailed explanation of how they determine salary. If the range is $150k to $250k, what are the criteria to make $250k? What's the difference between someone who makes $150k and $175k? That information belongs in the job posting.
Also, an increase in the minimum of the pay range can help people who were hired at lower pay rates know when new hires are getting paid more. Businesses love having this arbitrage opportunity, which is why the common advice is to change employers to maintain market rate pay.
Do you think it's true that you may be biased a certain way? Perhaps not in favor of job seekers?
> It is also true that a single job ad might be aiming to employ a number of people at various positions of seniority and experience.
Perhaps include separate descriptions for junior/senior roles?
> If it makes you mad that job ads do not list salary, then there are good reasons and you will just have to get over or it not apply for that job.
Why do you expect the candidate to have to change their mindset?
> Far more important is to know the salary target that you are aiming for.
Wouldn't having these ranges let a candidate become more informed about their salary target? Markets and salary ranges change over time, this would let them know what is current.
I’ve hired hundreds or low thousands of people. Corporate, government, SMB. Never did i go into that process without a budget target or salary band with budget. I would say that to a contract shop or recruiter to avoid having a budget of $100, a bid for $101, and a contractor making $28
Or, we could pass laws forcing companies to do this, and companies could get their shit together and figure out how much they're actually willing to pay.
The nice thing about market capitalism is that companies, for the most part, are fairly flexible. They may not be enthused about posting salary ranges, but if the law says they have to, they'll find a way to make it happen.
It's not entirely unlike how so many businesses prophecy doom and gloom when there's a minimum wage increase, or street parking gets replaced by bike lanes, but then the thing happens and it's generally fine.
I've been the team lead and talk to my team lead about this a lot and I know of no serious tech companies that don't actively think about employee retention and recruiting a huge part of which is compensation. Leadership at my company spends a serious amount of time discussing and revising our TC targets.
Any company that doesn't know what "they would be willing to pay someone" is a huge red flag for me as a candidate, and I can be quite confident that they aren't willing to even reach the salary component of my comp let alone meet or beat TC.
Sorry to call you out, but I simply don't believe the answer is anything but "it depends on a range of factors". Unless it is a government job, but even then, likely it depends on a range of factors, and often even government clients flex their budget to meet their recruiting goals.
And if they find someone who is outside that range, they will bump them up to the next role with the bigger range.
When I worked at eBay the salary bands for each level were well defined and shared internally. If they needed to pay you more than the top of the range, they bumped you to the next level to do it.
It would be very easy for them to publish the ranges publicly.
There is an internal document that specifies each level and the exact comp bands for each role (like all companies there is a range of salaries but it is specified, and again this is the practice a multiple companies I've worked at). There is a lower and upper bound of salary for level, target bonuses are fixed at a percent for ranges of levels and the same goes for equity grants.
The details of what defines each level of seniority is clearly spelled out in terms of typical ranges of previous experience, responsibilities of the role, reporting structure, assumed level of autonomy etc. These are also calibrated across teams at each review cycles and continually kept up to date.
During interviews there are set guidelines for how well a candidate performs given the target level of the role they are applying for an assess which level is appropriate.
This is not the same as saying
"don't actually know what they would be willing to pay someone."
and
"it depends on a range of factors"
At every company that is not sub 100 employees that "range of factors" is clearly defined. I honestly have a hard time believing you've worked recruiting for any major tech company and haven't come across similarly detailed documentation regarding levels, comp bands, and evaluation of candidates.
Most importantly, the ad should reveal the position's maximum salary, so job seekers know how much money is on the table. Ideally, median and average salaries would also be listed.
Noble goal that I feel is completely naive about human psychology.
I believe that exceedingly few of us have sufficient self-awareness and humility to see a range of e.g. "100-200k", and recognize easily that our performance and skill and history and capability is worth 120k, and will not feel scammed and underappreciated.
The prevailing wisdom on HN is empathically NOT "be happy with what you're worth", it's "ask for more more more", completely prior to any discussion of person's actual history, skillset, contribution, productivity, etc. And that's OK! We are human beings and inherently selfish and if we don't look after ourselves, who will? But it's disingenuous to then pretend that publication of a salary range will have any outcome other than all candidates expecting the top or slightly above... and I personally feel that will only result in employers pushing down the salary to match the average candidate.
If they interviewed around and all offers they received were around ~120k, then it should be a wake up call that their expectations do not match reality.
They often drag on for weeks, sometimes months, before an actual offer letter is in hand. And at the same time we're told that there's a shortage of us software engineers.
I can tell you it wasn't like this in the 90s. For better or for worse.
So don't be surprised that many of us are becoming incredulous that in addition to all of this, we can't get an upfront answer in advance about how much you will eventually pay me.
(I've also been confronted, very late in the process, with "your requested range is unreasonable because look at this compensation survey we bought from a third party" -- and that survey was full of complete lies because it listed total comp for Google L4 in my region as literally 1/2 of what I was making as an L4 at Google.)
So, I dunno, unless the job market really goes tits up and we're all suddenly begging for work, seems like your side of the industry -- the recruitment side -- needs to get its act together. I'm seeing growing dissatisfaction with the whole process and people are getting sick of the song and dance.
The important thing is, there are plenty of companies that don't pretend to be FAANGs, and don't interview like that. Odds are pretty good that working for them won't be like working at a FAANG either, which (imho) is also a good thing.
Why TF would you waste so much time to then have all of that crap?
The way it works in most companies that are big enough to have, like, distinct departments for HR and finance, is that teams have staffing budgets that are set out quarterly or annually, and if the team is expanding they will set those numbers to be big enough to cover the cost of the additional headcount they plan to add. Then the HR organization will probably have a compensation policy, which sets out ranges of rates for particular roles by level and geography. So your budget for a role lines up to certain job levels you can afford to hire at.
So by the time you're writing a job description looking for '5 years of react experience, located in NY' or whatever, you're pretty much narrowed in on a salary range that depends on 1) what your HR compensation guide says is the minimum compensation you pay for a level N software developer in that geo, and 2) the absolute maximum of your staffing budget allocated to the role.
If you can't turn that into a salary range for job advertising purposes, you're not a serious business.
Yes, they hay budgets and salary guidelines.
All of that is negotiable as a hiring manager. Just a matter of how many levels up the chain you need to go to get the approval and whether you (hiring manager) can convince them, which depends on how strong the candidate is.
Hiring requires money. If you have to go ask someone else for that money, they are the one doing the hiring.
Companies might not have HR hire until 50 people or so. Level of how much compensation levels or bands are figured out (and how big of a mess they are) varies in companies.
Even large companies, you might have variety of starting salaries, because you had to get the person in, which then needs fixed over time.
Also each new type of role you open, you might not have the bands figured out right at the time you write the job post. Your comp benchmarks might say 75th percentile is $160k. Then you talk to folks and seems like most are making $170k or more. Then you end up finding someone more or less senior but you would like to hire them and have to adjust the comp based on their experience while balancing it against other people and roles at company.
IMO comp is one of the hardest things to get right. You might do a comp philosophy that everyone gets paid $200k and you don’t negotiate but then you lose candidates and then overpay some people.
Then someone might still complain that if it’s fair that iOS engineer makes the same as Android engineer, even though market rate is higher for iOS engineers (and eventually the iOS engineers might leave to get a better paying job).
Bonus: you find out before you have to go to the trouble of interviewing and extending an offer.
If it makes recruiters and employers mad that they have to include salary ranges in their job listings, that's just too bad, and they will just have to get over it and follow the law.
Thankfully legislators are cracking down on this type of entitlement that's coming from recruiters and employers alike.
With few exceptions, what you wrote is not accurate. Most companies have salary bands for every position based on level within the band. Companies know both the position and level they have in mind for a candidate before the first on-site interview, and often before the initial screen. The interviews reveal what the leveling should be, and sometimes indicate a different role is more appropriate. The vast majority of companies will not negotiate outside those relatively tight bands for most IC and other low level (management) roles.
So having a target salary in mind is fine for an assessment of an offer, but not all that helpful if the goal is to not waste time up front. Some exceptional candidates might successfully negotiate for a bump in in-band level or even position, but it’s rare.
I'm a CTO, for context.
> The fact is that many employers don't actually know what they would be willing to pay someone. … I say "I think it will be about $X, but lets put a job ad up and indicate it's top of range $ and see who we get."
As someone pointed out, it sounds like this isn't too hard to do. I've hired people, I've come up with salary ranges. It took some thought, I didn't particularly enjoy the process, but it's possible.
> It is also true that a single job ad might be aiming to employ a number of people at various positions of seniority and experience.
"We're hiring for 10 widget programmers, x senior, y mid, z junior. The salary ranges for these are … and will depend on the skills and experience of the individual candidate"
> It's that easy - if the ad doesn't specify salary and that is a key requirement for you, don't get angry, just don't apply.
I've skipped job adverts in the past because the salary wasn't specified. People care about the wage, it's an incredibly important part of what work is, getting paid, it's one of the largest parts of the deal. Pretending that the wage doesn't matter because your company is special, or because people shouldn't be in it for the money is BS that basically everyone can see through and coming to that realisation will allow companies to have a much better understanding of the relationship they have with with their current and future employees.
Or, if the wage is important after all and you just couldn't be bothered to work it out? I guess just put a bit more time in and work it out. Or don't, and be skipped over.
As someone who sometimes hires people, I'd very much prefer it if all the people that applied had already self-selected on something as simple as the red line that is what people will expect to earn. I really don't want to have to trawl through a load of resumes for people, selecting them for interview, doing the first round etc. only to discover that they want n*2 more than we're offering.
Bullshit. Maybe some start-up with no HR. But, any moderately sized company is buying salary info, working with compa ratios, and has internal salary ranges mapped to positions.
LOL. I've never listed a position without knowing the salary range ahead of time. That range comes from our comp/ben team in concert with somebody from finance.
Recently I had a company reach out to me and after asking me many questions about my background for an hour, the recruiter asks me, "What is your salary expectation?". I said I would rather not say but would be happy to let them know if their range is acceptable to me. The recruiter rambles a bit about how they recruit from all over the world and then tells me that is not how they operate and I must give a number. I refused and they hung up. Of course it is their prerogative if they don't want to provide the number or need my number up front. But then they can be upfront about it early in the call. They should not waste my time for an hour and drain my energy in the process.
Everyone gets paid at least the bottom of the range. After proving competent they must be on the 33% mark. Some are paid above the top of the range but it's rare.
A given job family has different titles, broadly Junior-'Vanilla'-Senior-Principal. A junior might be on 25-45, vanilla on 35-55, a senior on 40-65, a principal on 55-80, or whatever (triple those for US wags I guess). That fits the "more experienced" part. You could advertise for a principal and find someone who just about scrapes in, so pay them 55, find someone great and offer them 80.
When advertising externally though, this information is not available - unless you know someone who already works there, which is crazy.
I’ve worked in a hiring manager capacity for close to a decade, and we absolutely know the bands, despite them being quite wide.
Companies that are well run can succeed without hiding information from their employees… and it’s a huge waste of time to interview somebody whose expectations are totally mismatched
Should they all have better data, better perspectives, and better job specs? Sure thing. I agree. You'd hire much better people, that's for sure.
On the other hand, should we regulate them into compliance on this matter? Ironically, it seems like a great opportunity to add inefficiency and possibly even have a net negative impact on salaries.
I say, let them ship crappy job descriptions and let the market sort it out.
It adds the inefficiency of a job poster spending 5-60 minutes figuring out a salary range.
It removes the inefficiency of hours and hours and hours of interviews from people that wouldn't have applied if they knew the salary range.
It's not like hiring someone is cheap. Companies can and should put this effort into ads.
To put it more simply: the socialist in me thinks it's good for workers -- the liberal in me thinks it's good for fairer competition in the labor market. Win-win.
My aversion to bureaucracy makes me hate the idea of the government adding more red tape, especially on something as trivial as poorly written job posts. I feel like we learned nothing from GDPR cookie banners.
But nonetheless, I don’t think your point is invalid.
I guarantee you startups < 100 people do not actually have formal hiring budgets. A lot of people here haven't actually been employers before, and this comment is spot on when it comes to the reality.
Posting a salary range for many positions would only have the effect of making it look like you'd be able to get less than you actually could, because employers would always need to post the bottom of the range (since these laws have a maximum range you're allowed to post), which is dumb.
If they are looking for some super specific and rare skill, why not make a separate ad for that rare position? In that case if they are ready to pay 5x the market rate, they can put that in the salary range without influencing ranges of "normal" positions.
The way you describe employers, they could really use the push.
Separate it into multiple job ads, with well defined requirements and salary ranges.
The role of the interview in that case is to simply determine if the candidate fits the desired requirements or not.
If a candidate applies to the position that doesn't fit their skills this will come up during the interview and the recruiter can tell the candidate that they are better suited for another position and inform them that the interview will continue as if they applied for the lower/higher position.
The company obviously knows how much they want to pay a candidate with certain skills and experience. So by making more detailed job descriptions there is no problem with posting salary ranges. Or if for some reason a company really insists on having one job ad for multiple positions of varying experience then they can put a salary range table where they state salary range for each possible position that a candidate might end up in after a successful interview process.
The need for "more C# engineering skills on the team" might filled by a junior engineer for $X, a mid-career engineer for $1.5X, a senior engineer for $2X, or a rock star for $5x. (e.g. If you land a rock star, you might be able to focus on something else for your next hire.)
So, as a company, you put out a job posting for a C# engineer and say "the pay depends on how good you are." You don't want to lose the senior engineer by listing a pay range of $X and you don't want to miss the junior engineer by listing $2X. Not every hiring situation is as easy as "I need this exact cog for my machine and I'm willing to pay exactly X."
Not sure why a law is needed here. (I assume the intent is more to prevent discrimination than to un-frustrate tech job seekers, though I can't really see how it would do that.) I guess the easy solution for employers will be to either just list a very large range, or to post the same listing with several different comp bands. Either way they can still discriminate to their hearts' content during hiring.
I've been a techie in the same company for 20 years; then I've become a lead and therefore hiring manager last few years.
I'll open a seat for something I need, and may be able to specify a range of levels/bands that we are acceptable; but the salary hugely depends on the person - primarily their skills, experience, knowledge, history, as well as (again unpopular but realistic) how well they interview. I may have a team of 5 ops managers and need a sixth one; I'm OK hiring a junior band 6 out of school to fully train up for salary X, or a reasonably experienced one for band 7 or 8 for salary Y; and if I happen to receive a resume for an exceptionally, uniquely qualified candidate with expertise with client or type of client and/or software/system/business we're working for, I might be willing to hire them as band 9 for salary Z.
With that in mind, what's the end-game here?
a) Publish full range of all possibilities - e.g. $60,000 -> $150,000? That's is true and accurate but it's not useful (and see human-psychology disclaimer below).
b) Publish a specific smaller range, and miss out on good candidates on both sides of the range.
To your point, government publishes their rate but that is because they aim, intentionally and knowingly, to mediocrity and not meritocracy. The bell curve is artificially flattened. It's a different system and goal. But I'm OK if my teams have a bell curve! Nobody is born at the edge, and I'm usually on projects big enough that I can train people up :)
(As well, what most people won't admit, is that very few of us are happily aware of our actual performance and will happily take salary that matches it - e.g. in the medium of range for medium of performance; so large companies may well end up moving to a boring average, depressed salaries for all, because if I publish range of e.g. 60-150k, how many people will willingly admit they only have experience/history/skills for e.g. 85k?)
This is very useful. For example, anyone wanting more than a minimum of $60k can skip applying.
> b) Publish a specific smaller range, and miss out on good candidates on both sides of the range.
I do not see how this is possible, especially on the lower side. No one is going to skip past your job listing because the minimum pay is higher than they expect, and no one is limiting you on how high to set your max pay.
They act this way even if "doing the thing" would be right, easy, good, productive, whatever.
I've never had a recruiter balk or push back on answering even for the roles I decided not to pursue. A recruiter doing so would be a huge flashing red light for me.
"If it makes you mad that job ads do not list salary, then there are good reasons and you will just have to get over or it not apply for that job.
It's that easy - if the ad doesn't specify salary and that is a key requirement for you, don't get angry, just don't apply."
Or the state could just pass a law making it a required field...
You’re not exactly just “the messenger” here. You posted several paragraphs explaining that a good chunk of your livelihood depends on this phenomenon of “not sharing data about pay.”
A messenger’s salary is independent of the opinionated slant of the information he conveys.
Seems like there's a third option: vote for legislation to make this practice illegal.
Companies want to pay (give) as little as possible while asking for (demanding/getting) as much as possible. More news at 11:00.
And when I do this, I expect the recruiter to have an idea of the salary range for that position and be able to put it in the job posting. Otherwise we'll be looking for another recruiter.
It's that easy.
The point of laws such as these is to change how recruitment works. The fact that the hiring manager/person will offer more to a 6'4" person from their alma mater[1] more than a random person of average height with the same skillset is problematic - even if it is "how recruiting works"
1. Unconscious bias is a well-studied phenomenon.
Why would an employer spend any time thinking about the salary they’re willing to offer when there is no penalty for not doing so. The party that does suffer are the applicants who have to sit through many rounds of interviews before finding out the max salary the job is offering is a fraction of what they’re being paid right now.
The lack of transparency is a classic neutral-lose situation, where the neutral party has the power in the relationship dynamics. It’s the perfect situation for the govt to step in and require transparency.
Generally it is assumed that the messenger is a relatively neutral party, like a courier or a postman. A recruiter has a lot of input into how that message is delivered and some insider knowledge, so they aren't completely neutral. I imagine companies want recruiters to take a few shots for them.
> Go ask your team lead/CEO/CTO how recruiting works.
Salary ranges are posted in all job advertisements.
I've known for a long time it drives people nuts that job ads don't have salary, or have a wide salary range.
The fact is that many employers don't actually know what they would be willing to pay someone. Until they have met them, assessed them, heard what they salary target is and weighed it up against their skills and experience and calibrated it against the team.
The conversation almost always goes like this: Employers come to me and say "we want a great senior C# .NET developer". I say "what do you want to pay?". They say "don't know, we just want someone great, what do you think we need to pay to get the right person?". I say "I think it will be about $X, but lets put a job ad up and indicate it's top of range $ and see who we get."
It is also true that a single job ad might be aiming to employ a number of people at various positions of seniority and experience.
Government agencies are required to carefully define salary ranges because that is the way they work. So it does not surprise me that governments would legislate to require job ads to do the same - essentially because of ignorance about how the world works.
If it makes you mad that job ads do not list salary, then there are good reasons and you will just have to get over or it not apply for that job.
It's that easy - if the ad doesn't specify salary and that is a key requirement for you, don't get angry, just don't apply.
Being angry about it or feeling that employers/recruiters are playing some sort of manipulative game is ignoring the reality set out above. And when you come into a position that requires recruiting, likely you'll speak to your recruiter and say "what do you think we'll need to pay for someone like this?".
Far more important is to know the salary target that you are aiming for.
EDIT: lots of unhappy responses to this, but don't shoot the messenger. Go ask your team lead/CEO/CTO how recruiting works.