5 ms·
Salary expectations questions – How should you answer them? (2020)
- dijit 2y agoUnless you end up with someone like me who has a budget and always pays the max. I usually ask "what do you expect to be paid" to understand if I'll make them happy or sad when discussing what I'll actually offer. This is not foolproof and has caused some issues with people coming in as very good negotiators and thinking my inability to budge is because I'm being hard-line, when in reality it's because- as mentioned, I always offered the max for a role. The second issue is that not all people are equivalently valuable, but I think solving that in the salary is terrible, because salary should cover your compensation for responsibility. If you have to reward someone valuable then it should probably be via bonus' imo.
- SoftTalker 2y agoI think salary + performance bonus is generally a good way to go. I've only had one job that did that. The base salary wasn't remarkable but there was a bonus that had a component that was calculated based on the overall performance of the company that year, and a component that recognized individual performance. So everyone got a bonus, but high performers got more. You used to see bonus compensation in most financial companies. I'm not sure if that's still the case.
- AlotOfReading 2y agoA former employer did 40% bonuses. It made for a nice holiday surprise even when they decided "the company didn't meet expectations" and gave everyone half bonus. Eventually they decided to "align with market expectations" and coincidentally started hemorrhaging staff.
- reaperducer 2y agoEventually they decided to "align with market expectations" and coincidentally started hemorrhaging staff. At my fist full-time job out of college (non-tech), the company gave everyone an extra paycheck as a Christmas bonus. The next year, everyone got half a paycheck as a Christmas bonus. The next year, everyone got a spiral-sliced ham as a Christmas bonus. Before the following Christmas came around, the majority of people had gone to the competition across town.
- SoftTalker 2y agoLet me guess: the year after that it was a jelly-of-the-month club. The gift that keeps on giving the whole year.
- Fargren 2y ago> Unless you end up with someone like me who has a budget and always pays the max. Why don't you disclose the value to the candidate then, rather than asking what's their expectation?
- paulddraper 2y agoBecause it helps you position the offer, and emphasize/sell certain parts. Salary, equity, title, working hours, etc. More information always helps.
- Thorrez 2y agoFargren is asking why a recruiter would want to to withhold information. Your answer is "More information always helps." That doesn't answer the question.
- itronitron 2y agoYeah, the company can tell the candidate the salary they will pay for someone in the role. If that doesn't match the candidate's needs then the process stops. If the candidate's performance during the interviews shows they can't function effectively in the role, the process stops.
- paulddraper 2y agoThey are asking why the information is shared in that order.
- deleted 2y ago[deleted]
- the_gipsy 2y agoAre you not allowed to disclose salary first? Sorry to be blunt, but if you are allowed, then this sounds incredibly stupid.
- dijit 2y agoI can disclose, but when I have people start trying to negotiate as if it's a starting position, they get really happy with the number and then irreconcilably annoyed when they realise the number doesn't change. Hindsight and looking externally on the situation would have you think that you'd react differently, but it's a 5/5 repro rate. If I think the money is enough then I'm quite happy, but if they expect more then I have to emphasise other parts of the job (remote first structure for example, and flexible working hours) - I wouldn't need to do that if their request was lower than what I offer.
- Thorrez 2y agoWhy not disclose it and also say "it's not up for any negotiation".
- dijit 2y agothat is exactly how it's presented, I give my methodology and how I arrived at the number (market rate in munich + 20%) and then give the number with exactly this caveat.
- pm90 2y agoRemember that people go by what others do. There is 0 penalty for lying about the fact that the number is not negotiable and so recruiters will do that often. So job applicants are conditioned to try to negotiate even if told quite clearly that its the “final number”.
- Thorrez 2y agoI'm not surprised that people still try to negotiate. I am surprised that they're irreconcilably annoyed when negotiating fails.
- StableAlkyne 2y ago> If you have to reward someone valuable then it should probably be via bonus' imo. That, and it should be individual, instead of the "based on how the company performed" thing many do. A star engineer who overhauls cuts your server costs in half shouldn't get dinged because someone in sales couldn't be effective
- throwaway8754aw 2y agoI tell recruiters what I want to make from the beginning (my first reply to them on LinkedIn or wherever they reach out) yet say that's what I'm making now ..how competitive is this opportunity? Either they can match or increase it. If they can the conversation continues and the pay is set in stone never to be discussed again thru all interview processes.
- dijit 2y agoThird-Party Recruiters are actually great, they're super expensive for the company who you hire through, but they're the only people motivated to make sure it's a good fit and are neutral on it. You'd expect that they would be incentivised to place you somewhere bad so that you're a repeat customer, but there's something that seems to make this not true, perhaps reputation?
- SoftTalker 2y agoYeah if they put you in a crappy job or it's not what they represented it was, you'll never use them again and you'll tell your network not to use them. They are motivated to place you in a job, since that's how they get paid, but they want you to be happy with it.
- wordofx 2y agoRecruiters only get paid if a candidate stays beyond a period of time. If the candidate does not work out the recruiter needs to find a replacement. Recruiters won’t deal with shit people because if they don’t stay or are prone to not working out they are a burden. In terms of money it’s usually a percentage of the salary. So if the recruiter works on 10% then they have incentive to get you as much money as possible.
- borplk 2y agoIt's quite logical to think that they have an incentive to get you as much money as possible but in reality it's often not quite correct. Their stronger incentive is to establish a relationship with a business and to continue feeding them candidates at an attractive price point for the business. The marginal amount of extra commission that they make on your increased salary is not that significant.
- KingOfCoders 2y agoOnly talk about past salary if it was 20% above market.
- slwvx 2y agoStacey Vanek Smith wrote "Machiavelli for Women". She said in radio interviews about the book that she wanted to put in the book the suggestion that if an interviewer asks what you make, an interviewee should reply with the real value plus 10%. Apparently legal people at her publisher did not allow her to put this in the book. I think it's reasonable to ask what an interviewee expects to make, but not reasonable to ask what an interviewee makes now.
- romanows 2y agoThat's fascinating, I wonder why that suggestion would be any more dangeous than any other advice. Too bad she didn't just put in a footnote describing why she can't suggest asking for 10% more.
- phil21 2y agoLying about this these days seems rather risky to me. Some employers may not care, but some will. The Worknumber product from ADP (and it's equiv from Paychex) covers a vast range of white collar employees. Perhaps most. Your new employer has a very good chance of seeing precisely what your current salary is down to the paycheck level going back years to even verify raises and title changes. Replying with what you require to make to take the job seems like a much safer bet to me.
- analognoise 2y agoYou can opt out of that I think, can’t you? Might be wise to do before you interview.
- FireBeyond 2y agoYou can opt out of The Work Number. It's a bit of a convoluted process, but not byzantine - I did it a few months ago, involves filling out a form by hand and scanning it or mailing it, but I did get written confirmation that I'd been opted out.
- 2y ago
- Apreche 2y agoI don’t know if this is the best advice, but here’s what I tell prospective employers that ask for my compensation expectations. I tell them I live in NYC, and with my current compensation I can comfortably afford the preposterous rent.
- Uehreka 2y agoIt’s very cool that you can get away with that.
- eastbound 2y agoThe real important question is the subsequent one: — What are your salary expectations? — $X — Ok! That means if we propose Y, would you envision it? — Yeah, maybe, because I’m out of choice / No because I already have an offer at $X-1. Source: I’m hiring (and yes, Y enters into consideration because most candidates overestimate their skills, but I always go for X if the candidate is as expected).
- sklivvz1971 2y ago> most candidates overestimate their skills In reality most candidate are just bad at estimating their own skills (in both directions) and of course they know almost nothing about the match between the skills and the position.
- voytec 2y agoI've talked to several recruiters and HR people who were prepared for quite a different answer than I gave to this question. I got the feeling that several interviews were carried out afterwards out of politeness or because the recruiter "had to" do it, but the interview ended before it began. Than, there's either ghosting or almost immediate (like up to an hour past the interview) copy-paste email along the lines of "we decided to go with another candidate". A few recruiters however were open that they've checked the salary for similar position in my country's capital city (Warsaw) and it's much lower than what I'm asking. Pointing out 20+ years of experience and listing accomplishments seems less important for a lot of businesses, than paying as little as possible. I got a few links to these "check salary for [level] [position] in [city]" websites from recruiters. All these seem to be crafted in a way that undervalues employees by artificially lowering country-wide salaries to ridiculous levels.
- FirmwareBurner 2y ago>Pointing out 20+ years of experience and listing accomplishments seems less important for a lot of businesses, than paying as little as possible. If paying as little as possible wasn't that important to them, they wouldn't be hiring in Warsaw in the first place, but in the Bay Area, Seattle, Zurich, London, Sydney, etc
- dtnewman 2y agoFrom my experience, this is not necessarily true. Some companies might have the budget to pay at the 50th percentile in New York, or the 95th percentile somewhere else, and would prefer to do the latter
- voytec 2y agoI'm not interacting with companies seeking cheap labor in Poland - like Intel. Despite their quite active recruiters, all conversations with whom end up at "company policy doesn't allow me to discuss salary range". I've set up a small business with EU tax id over a decade ago and I'm issuing invoices to European countries (EU and Schengen) and North America. It's a trade-off of giving up European employment safety, pension, some quality of life when working in different timezone, benefits and job security, to work for higher salary. But it only makes sense until some business decides that they would like a contractor from Poland with a Polish salary.
- scarface_74 2y agoI don’t negotiate. If I’m already working and looking for a job because I want more money, I know my market value and the percentage increase it would need to be for me to leave. I’m also at the point in my life where I know the amount of money I need to meet my short term and long term goals- pay bills, travel extensively with my wife and save for retirement. But after that I start optimizing for other things - fully remote, enough paid time off to enjoy travel, smaller company (I’ll never work for BigTech company again), interesting work that keeps me up to date with technology, etc.
- Joel_Mckay 2y agoIn general, vertical movement in the tech sector is near zero these days. Thus do a search on the government published wage ranges for the mean/maximum listed for your region (this is what HR does anyway.) The mistake people make is forgetting to sum up the liabilities of working at some firms: 1. Commute time/costs from home at rush hour (3 hours a day is equivalent to a 30% to 40% pay cut) 2. Cost of both temporary and permanent housing (urban metropolis are economically hostile if you are paying over 27% of your income on your home) 3. Cost of insurance and healthcare (property crime, environmental disasters, and pollution) 4. Location specific risks like Crime/Violence, or Hazmat (money is meaningless if you are not enjoying life) 5. Never bluff in game theory... just explain the options... than follow through and just leave for the competition. Tip: If you compete with desperate demographics to be at the bottom, than your quality of life may be far lower than expected. Sometimes taking a $10k income cut makes more sense, than being a poser in a high tax bracket city. i.e. the amount of cash in your hands after taxes can actually be higher. It is complicated for sure, but employee retention is usually a function of location, skill uniqueness, and wage rates. Best of luck =3
- MichaelZuo 2y agoHuh? Thousands of people are promoted every year in the big tech companies into seven figure positions. And many many tens of thousand into mid six figure positions. How is that ‘near zero’?
- Joel_Mckay 2y agoThe vast majority of tech workers leave firms in under 3 years, move laterally, or are mission critical with meaningless title changes. If you find 6 different division managers that entered the same facility as coders, than I may agree. You won't, but I respect your youthful idealism. =)
- MichaelZuo 2y agoRight, but the vast majority of tech workers by definition must be in the bottom 95% of workers.
- wrs 2y agoGood time to direct people to the classic work in this genre: https://www.kalzumeus.com/2012/01/23/salary-negotiation/ https://www.kalzumeus.com/2012/01/23/salary-negotiation/
- goldeneye13_ 2y agoI always recommend this article: https://www.kalzumeus.com/2012/01/23/salary-negotiation/ https://www.kalzumeus.com/2012/01/23/salary-negotiation/ I think this topic is super important and I’m really glad I didn’t follow advice of saying your “expected salary or expected +20%”. Here my anecdotal SWE salary history: Worked at a startup for a bunch of years making 90k by the end Got offered a place at FAANG. Recruiter pushed me a little bit on expected salary but I didn’t give one using all the approached from the linked article. They offered me 250k. I would have never ever assumed that I can be payed this much. Instead of accepting I again followed the advice and asked for time to think. I had no counter offers but spoke to the recruiter thanked them for the offer and asked if there’s room for improvement. And they were nice and reasonable, they said yes if there are counter offers or you are leaving unvested stock behind. I was leaving unvested stock in an unprofitable startup, but I wrote the amount and vesting schedule and got offer bumped by 25k. After working there I considered going to trading shop. Used the same approach and they offered 400k. Again this number seemed insane at the time. So I asked for more, this time I had much lower counter offer. But I could use it as some form of leverage. They upped the offer by 150k by the end (this is sign on+ salary+guaranteed first year bonus). I am writing this not to show off the numbers, but to show other engineers that your idea of how much you should be payed could be completely wrong. Let the employer give information first and don’t back yourself into the corner by revealing your ignorance of market or minimum comp you are willing to take.
- chamomeal 2y agoThat is absolutely bonkers. The range of developer salaries is so huge. Congrats on moving far above 90k!! What kind of work experience would you say was most valuable in climbing that ladder? Open source stuff? Anything you could show off?
- goldeneye13_ 2y agoI think what made the difference in both places is that I had good projects I could talk about and the tell a good story of this is the business problem, this is what we did, this is how I contributed, this is the result. I know this is not super helpful and sounds like standard STAR stuff. I was lucky because I was given a chance to deliver large and important projects and I think this is what they liked. This comp is high but once you get into l7 and above or get senior roles in trading firms numbers become even more crazy.
- vitus 2y agoOne other thing to have in your back pocket: In certain jurisdictions, it's actually against the law for employers to ask you for your current salary during the interview process (pre-offer), as that can perpetuate wage discrimination. (This is different from asking about salary expectations.) It looks like 17 US states have a ban that applies to all employers: https://www.hrdive.com/news/salary-history-ban-states-list/516662/ https://www.hrdive.com/news/salary-history-ban-states-list/5... (The relevant laws in DC, NC, PA, VA only apply to local government, and AL's law is somewhat weaker in that it only prohibits rejecting a candidate based on not providing salary history.) Notably, many of these laws are worded as a prohibition on seeking salary history, and do not differentiate between asking the candidate directly and querying third-party databases like The Work Number.
- sklivvz1971 2y agoHere's the thing: - the candidate has a range of salary they expect or need - the company has a range of salaries that they can pay If these don't overlap there's no point going forward unless the range of the company is higher. If these do overlap, it's worthwhile proceeding. Then it's a matter of skill. If you apply and ask for the top range in my salary band, and you are truly exceptional, I'll do my best to match it. But the ask needs to be commensurate to the skills you demonstrate in the interviews. The higher the ask, the stricter the criteria to match. If you get to the end of the process without disclosing the salary, and you pass all interviews, I'll offer you for what I think you are worth. If you have an ask and did not disclose it, you might have just wasted everybody's time. Believe it or not, negotiating a salary higher than your worth is a terrible idea. It might sound good, but it sets you up for failure.
- zdragnar 2y agoNothing is more insulting to someone than knowing in advance that their expectations are far beyond your own, putting them through hours of interviews, then offering half the salary they asked for plus funny money equity. I try to be as up front as possible with my expectations, but I've also got the seniority / experience to match what I'm asking for. Yet, people still try to low ball me as if I'm making up numbers. I made the mistake once of taking a job after they low balled me, then met my asking salary after I flatly said no. If you ask for a specific number or a range, and they offer you below that range, just walk away. Even if they come back with what you wanted, they'll resent your salary and have inflated expectations above reality. They've already demonstrated they didn't take you seriously. Just walk away.
- em-bee 2y agoEven if they come back with what you wanted, they'll resent your salary and have inflated expectations above reality that is something i worry about when i see a high offer. in part it's imposter syndrome, but also a lot of job descriptions are like we want the best, and you are super fast and an excellent this and perfect that, able to work in a high pressure environment, etc. these claims are so meaningless. they don't tell me anything about what it is really like to work there. who really wants to work in a high pressure environment with the expectation to be a rock star developer?
- bitfilped 2y agoThe premise of this isn't really true is it, at least in the US? Don't most companies have your Equifax Work Number during the interview process?
- lethologica 2y agoThis whole game is so stupid to me. It really feels like the employer is trying to screw over the potential employee before they’ve even joined. My default answer to these questions is now “what’s your budget?” And if they return with a non answer, or try and push me to give a number without giving one themselves, I walk. I can’t think of anywhere else where the seller (in this case the employer “selling” a position) of something hides the price and expects the buyer (the potential employee) to magically come up with number that meets their criteria. What a dumb game we’ve developed for ourselves.
- aster0id 2y agoIt's a dumb game, sure. But I'd say it arises from opposing incentives, not necessarily from a real desire on the company's part to screw you over. How important is feeling "not screwed over" at the beginning of an employment important for you? Does it trump a great work environment and interesting things to work on? How sure are you that your subjective feelings during negotiations match how the employer actually is objectively? It would seem intuitively obvious that there must be correlations between being screwed over in the beginning and then having a bad experience later on during the actual job as well. But I'm personally wary of blindly following intuitions in matters that relate to money. Being able to just "walk away" from decidedly some of the highest paying jobs in the world (irrespective of the feeling of being low balled) is a privilege too. Anyway, in my own personal experience, I was screwed over during the offer phase of a previous job, and the job was not great either - terrible wlb and politics, but I did learn a lot and became very efficient at my work. As a bonus I stopped caring about my work outside of being necessary for paying my bills, while still maintaining decently high quality output. I had the opposite experience with my latest job - the recruiter was professional and empathetic, and I had a great offer experience. The job itself is great as well. So yeah, maybe there are correlations, but I'm still just one data point and so I'm not keen to generalize yet.
- hn_throwaway_99 2y ago> It really feels like the employer is trying to screw over the potential employee before they’ve even joined. I mean, on the flip side, the employee wants to get as much salary as possible. You say this is a "dumb game" that we've developed, but nearly all negotiations work this way, and a lot of it is fundamentally dependent on leverage: how much does the company really want to hire the person, and how much does the person need the job. I will say, having hired a lot of software engineers in my time, that I never see it as a bad thing if a potential employee gives a very high number. Similarly, I think it's totally reasonable for an employee to ask "what's the salary range for this position" and to expect an honest answer. But I have seen employees "negotiate themselves out of a job" because they've read too many "principles of negotiating" books and somehow act like we're negotiating over the end to the Ukraine War. Basically, if folks are going to be a total pain in the ass before the job has even started, I'm pretty sure I don't want to work with you (and every single time I've "overridden my gut" and thought "well, maybe this person won't be so bad, after all they're great technically", I e come to regret it). As you point out, the employee is obviously free to walk as well - in my opinion, it's probably better for everyone if things reach a "hmm, someone is going to be unhappy with this decision" moment that folks walk away.
- hinkley 2y agoOne of the places I applied to had a required field with salary expectation. I almost backed out of the whole process. I don’t think it was an accident that it was the very last field in the submission process. I forgot to write down which one it was in my notes. So that’s less data I’ll have if they call me back.
- em-bee 2y agofrom the applications i looked at at least one third if not half of them had such a field
- hinkley 2y agoI'm sure as my sense of urgency and my sense of selectivity head in opposite directions I will think back to this comment. So far I've been picky and have seen more like 10% and most of that in the last couple weeks. It may also depend which job site or application tool you're using.
- 2-3-7-43-1807 2y agoif submissions like these make you feel like a loser. i'm in germany and make 65k. and yet i can still look myself in the eyes in front of the mirror every morning. so, don't let this drag you down.
- comprev 2y agoFAANG salaries for developers are often double, if not treble, those of upper management where I work. There's absolutely no reason to feel like a loser on €65k. In tech it's easy to forget just how lucky we are with salaries.
- XajniN 2y agoWould you be interested in moving to the Czech Republic for a better salary?
- 1oooqooq 2y agothis article feels like ancient history from the dark ages. what job post today doesn't include salary range?!
- sentientslug 2y agoA job posting in any state or country where it’s not legally required? Of which there are many?
- gilbetron 2y agoX = desired salary "If you offer 2*X I'm definitely in, I would have to do some soul searching if it is less than X, though."
- JohnFen 2y agoWhat I personally do is two things. Before I've even had an interview, I have an acceptable salary range in mind. I usually ask for the top end of that range and have room to negotiate down, so when I'm asked that question, I have an answer at the ready. The other is that I never reveal my past salary. Revealing it is a trap in so many different ways, and it's none of their business.