We are recruiting new engineers and having a discussion about whether to include salary information in job descriptions or not.<p>I would love to know what the general consensus and expectations of the HN crowd towards this issue is.<p>Many thanks and Happy Hacking.
I've said it before and I'll say it again: if you can't be up-front about what you're going to pay a person for doing a job and offer the same to everybody, that's a red flag and it tells me you're looking to screw somebody. Tells me everything I need to know about you right there, and that's an instant hard-pass.<p>Should be legally required by federal law to post salary for any job ad regardless of platform of publication.
Tech jobs vary wildly in pay, but their marketing language doesn't. This makes it very hard to know what's worth your time. The reality is, if you're making >$100k and a recruiter comes offering "a great opportunity to work at the next big thing!" but their top range is $90k, then there's almost no chance you'll choose to go there.<p>Since pay is paramount to the employment arrangement, why wouldn't I expect that to match up near the beginning?<p>I will add a small note: if a recruiter reaches out with a job that doesn't mention salary, I won't outright ignore it, but asking for a range is always in my first reply. If that isn't answered then things stop there.
FWIW in case you didn't know:<p>> Pay Transparency: [European] Commission proposes measures to ensure equal pay for equal work [...]<p>> Pay transparency for job-seekers – Employers will have to provide information about the initial pay level or its range in the job vacancy notice or before the job interview. Employers will not be allowed to ask prospective workers about their pay history.<p><a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_21_881" rel="nofollow">https://ec.europa.eu/commission/presscorner/detail/en/ip_21_...</a> / <a href="https://news.ycombinator.com/item?id=30429182" rel="nofollow">https://news.ycombinator.com/item?id=30429182</a>
I get so many contacts from recruiters that I'm never going to follow up on almost any of them.<p>Is salary information absolutely essential? No. But if I'm not pretty confident talking to you is a good use of time, you'll never hear from me, and not providing salary information is a great way to keep me uncertain.<p>I can think of two exceptions. For my first job I didn't really care about salary - my main goal was to get good experience and get into the field. Also, there weren't a ton of recruiters constantly spamming me. Alternatively, if you're a large well known company and I'm interested, then I'll just google to figure out what sort of salary to expect. In that case you don't have to explicitly tell me.<p>In all other cases, if you leave out the salary, I'll probably ignore your job.
It depends on the company size. If it’s a large company, I expect rigid and well-defined salary bands, so it would be nice if they’re published. For a smaller company, I don’t expect salary bands, and I treat the relationship more like a contractual one.<p>Any contract price is negotiable by definition (“meeting of minds”), and whether or not the job description provides an initial anchor price does not change that. So if it’s negotiable either way, then IMO it actually seems unfair for the company to name the salary because it means they’re providing the initial anchor.<p>It also depends on me. If I’m the head of a machine learning lab at Stanford, the salary is negotiable at the big company too.<p>So all in all, I’d say I expect companies to publish a range of salary, or at least include some indication they’re serious. If I see them in TechCrunch I know they have enough to pay me, and if I’m worried about their runway then maybe I should work at a big company with rigid salary bands.
If you aren't willing to tell me up front how much you're prepared to pay, then I can't be bothered to apply.<p>This is especially the case for tech recruiters: tell me who you represent and how much they're prepared to pay, or I will mock you.
A reasonable range would absolutely be great but I understand why disclosing any salary information would be challenging for the company as it changes how compensation negotiation is done but will also affect the overall culture. Ultimately, you need to continue your first principles thinking and put this hypothesis to the test.
Honestly I don’t mind either way. I know how much FAANG pays, funded startups who have a clue pay the same salaries but have illiquid variable comp through stock. I’m OK doing startup stuff with my startup friends and working at a hyper growth stage company for less liquid comp for no other reason than I think it’s fun. Just like how some people like country music and I like heavy metal, just pure preference.<p>Now if the company is a big company, not an interesting job, and there’s no salary listed, I’ve played that game before already. I’d rather just grind leetcode and go to Google then apply.<p>I’d encourage everyone to figure out what kind of role and culture they’d like first, then find the job. You’ll be happier for it, and any company is more than happy to throw a bit extra money at someone who’s a perfect fit.
Yes, but I would be more happy if it wasn't straight up "advertised" in the ad, but was readily answered when asked without expectation.<p>What?!<p>Here's my thought - doing it like this it keeps it slightly competitive. Sure if it's easy to ask for the salary range, people can and will ask. But do you want to be fighting loads of people for a particular job due to the dreamers with low skill /chance clogging up the machine because they saw a shiny 180k salary?<p>Okay, but why readily answered when asked? Because it's a huge time suck. If I have to jump through 11 hoops only to find out it's for 20k less in the 0 hour it's wasting all our time.<p>Let's not forget, we work for an organization to be paid. At the end of the day the marketing of a job for a held hostage pay range isn't going to fly 9/10 times.
Yes. Without a range being advertised, I think it's too easy for companies to foster pay inequality by hiring new engineers for more than they're paying their existing engineers with similar experience/responsibilities.
While I am accustomed to the current situation, in which one must often simply guess and hope, I would <i>greatly</i> prefer to have more information up front. I don't see how you can lose by giving people more information.
For those in California, Assembly Bill 168 was passed in October, 2017, effective January 1, 2018. Section 432.3 was added to the Labor code, which includes:<p>(c) An employer, upon reasonable request, shall provide the pay scale for a position to an applicant applying for employment.<p>Source: <a href="https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180AB168" rel="nofollow">https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml...</a><p>Disclaimer: I don't know if/how that provision may have changed since 2018.
I live in a state where salary ranges must be included in any job posting. The reality of it is that many employers still don't comply. Many of those that do give very broad ranges.<p>Even those that give a salary with a reasonably tight range still never include equity compensation. That makes salary info nearly meaningless.
As an experienced dev I get plenty of recruiter contacting me. If you aren't going to tell me what I can earn, then there is a good chance that it's a waste of my time going through the process to find out it isn't enough.