16 ms·
I never answer questions about my past or expected salary, not to employers and not to recruiters. Most employers don't ask, and the few that have (perhaps by
by pmoriarty 10y ago
I never answer questions about my past or expected salary, not to employers and not to recruiters.
Most employers don't ask, and the few that have (perhaps by having a part of an employment form ask for previous salary) have never made my leaving that information out an issue.
Most recruiters, if they even ask, respect my decision not to talk about it, but I've been pressed hard on this by a handful of recruiters, and have had this be a deal breaker for a couple of them. One recruiting firm admitted that they were paid by the employers to get this information. I wasn't getting paid to give this information out, however, and it's worth more to me to keep it private as I'm placed at a disadvantage in negotiations if I name a number first.
It's still a seller's market for IT talent, and there are plenty of other fish in the sea, so if some recruiters can't accept that I won't name a number, it's their loss.
It's great that NYC is taking the lead on this, and I really hope the rest of the US follows suit.
- louisswiss 10y agoAgree with you in principle (your previous deal with company A is absolutely none of company B's business) but I would like to challenge you on one point: > I'm placed at a disadvantage in negotiations if I name a number first. ... This is unlikely to be true. Generally, in price negotiations it is advantageous to name a number first. This is known as anchoring and basically the theory is that the end result is better for you if the company has to wheedle you down from 170k than if they anchor the price at 100k and you have to argue them up from there. Plus, it saves a lot of wasted negotiation time on both sides if your price is just way too high for the company and this is clear from the beginning. (edit: I'm talking about expected salary in general, not disclosing your current salary level)
- vidarh 10y agoNote that this assumes your information about your market value is at least roughly in line with their information about your market value. If there's a big discrepancy in what you believe you're worth, then the benefit can easily flip the other way.
- alistairSH 10y agoThe parent is discussing prior salaries. You are discussing requested salaries. If specifically asked "What is your current salary?" you would typically respond with the actual current salary, not your ideal new salary.
- vidarh 10y agoIn this case the prior salary is used for anchoring purposes, by the expectation that the new salary should not be too much higher than the old salary. They're basically using it as a means to sanity check and calibrate their own assessment.
- sprafa 10y agoThe thing you might leave a job because you really, really disagree with that assesment!
- rhizome 10y agoby the expectation that the new salary should not be too much higher than the old salary From where does this expectation derive, and what makes it a good barometer of sanity? On the face it just sounds like the same rationale used for basing raises on percentage of an employee's initial salary. "3% over your last job" is not fair.
- vidarh 10y agoThe expectation derives from peoples lack of knowledge of what they're worth. It has nothing to do with fairness - it's about what they think they can get away with offering. Based on experience, almost nobody negotiates their offers, and if you see people talking about their job moves, people are often excited about, say, a 10% increase. That's why employers expect to be able to get away with anchoring it to your current salary.
- vkou 10y agoMy first job paid me $25,000 CAD a year. My next job paid me $90,000 CAD a year. (Investment bank) My next job paid me $160,000 USD a year. (Google) All numbers are all-in comp. All junior dev roles. Should the bank, and Google have offered me $33,000 and $40,000, so that the new salary isn't too much higher then the old one? Would that satisfy your notion of fairness? When new grads hired by the latter are getting paid $150,000/year? You are hired to do your new job, not the old one. What the old one paid has no relevance.
- emidln 10y ago> Plus, it saves a lot of wasted negotiation time on both sides if your price is just way too high for the company and this is clear from the beginning. This. I'm very upfront that if a company can't meet at least a particular dollar amount expected, it's not worth wasting both of our time. This saves a ton of time, and also serves as a nice red flag when a company agrees and then later tries to negotiate down at the last minute (if they're going to penny-pinch at the last minute, things like bonuses and vacation approval are basically never happening).
- pmoriarty 10y agoI never consider interviewing and negotiations a waste of time. It's very valuable practice, no matter what the outcome. Practice is how I get better at both. The more interviews I go on and the more times I negotiate salary, the better I get. Also, even if a company can't hire me at the moment due to real budget constraints, they might be able to do so in the future, or perhaps one of the people I interviewed and impressed enough to get to the salary negotiation phase will remember me when they move to another company and want to hire me then. If I name a number way out of their range first, though, they could reject me right off the bat, and I'd never get an interview in the first place, never get the practice, and never get a chance to impress anyone. All of these are worth more to me than the chance of a salary negotiation going sour because I wind up being too expensive. Besides, I'll always have the chance to decide whether I want to work for the company despite them being below my ideal salary. Salary isn't everything. As for anchoring, that might work if you're negotiating with novices, but many employers have professional salary negotiators (either HR or recruiters themselves) who know about anchoring, and they're not going to get fooled by such psychological tricks. If I don't reveal a number first, however, they are forced to name one, and then the ball is in my court, and I can negotiate up from there as I see fit. There's really no downside.
- pm90 10y ago> I never consider interviewing and negotiations a waste of time. It's very valuable practice, no matter what the outcome. Practice is how I get better at both. The more interviews I go on and the more times I negotiate salary, the better I get. This. I get the impression that most software devs don't make an effort to learn this incredibly valuable skill. It doesn't even have to be haggling, per se. Just asking for a higher salary is often going to increase it by thousands of dollars. It just boggles my mind at how so many people will leave so much money at the table...
- collyw 10y agoWhenever I have done that its been a "we can't right now" for such and such reason, have some extra responsibilities instead and make it feel like a promotion. It been easier to get another job with more pay.
- jnwatson 10y agoAnchoring only works if the potential employer is ready to buy. Many, many organizations will simply use the number as yet another filter, and you won't even begin discussions. By giving a number first, you're either too high and you won't have an opportunity to sell yourself, you're too low and you've literally already negotiated against yourself, or you're lucky and right at their expectation, which you could have gotten to by simply not giving the first number. I do agree with the wasted negotiating time thing.
- pc86 10y agoThis is why we publish salary ranges with our job ads but also require a desired salary within that range from candidates.
- sheeshkebab 10y agoThat's how us government jobs work too :)
- pc86 10y agoUnfortunately the negatives around government jobs far outweigh the benefits of having the salary a known quantity when you are applying.
- sitkack 10y agoIf only the rest of the industry was so mature.
- davemel37 10y agoEvery time I ever tried this, the candidates hover around the top of the range regardless of qualification and experience.
- jjnoakes 10y agoWhich is fine; if you can argue that their experience may not merit top of the range, you just negotiate down a bit...
- VT_Drew 10y ago>Generally, in price negotiations it is advantageous to name a number first. This is absolutely 100% wrong. In price negotiations you will almost always fair better if you force the other party to bring up a number first.
- louisswiss 10y agoSource? There is a large body of research which disagrees with you... Oechssler, Jörg; Roider, Andreas; Schmitz, Patrick W. (2009). "Cognitive abilities and behavioral biases". Journal of Economic Behavior & Organization. 72 (1): 147–152. doi:10.1016/j.jebo.2009.04.018. Jump up ^ Orr, D. & Guthrie, C. (2005). "Anchoring, information, expertise, and negotiation: New insights from meta-analysis". Ohio St. J. Disp. Resol., 597, 21. SSRN 900152 Jump up ^ Kristensen, Henrik; Gärling, Tommy (1997). "The Effects of Anchor Points and Reference Points on Negotiation Process and Outcome". Organizational Behavior and Human Decision Processes. 71 (1): 85–94. doi:10.1006/obhd.1997.2713. (edit as I can't reply to the child comment: Yes, you're right of course. Put it down to a mix of multitasking, iphone browser and university-instilled fear of using Wikipedia as a source)
- always_good 10y agoCitation soup doesn't really add anything to a discussion. Why not link to the Wiki article you copied the sources from? https://en.wikipedia.org/wiki/Anchoring https://en.wikipedia.org/wiki/Anchoring
- VT_Drew 10y agoSource right here: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ http://www.kalzumeus.com/2012/01/23/salary-negotiation/ (and it isn't a wikipedia article)
- enraged_camel 10y agoExactly. Whoever names a number first puts themselves at a significant disadvantage.
- 10y ago
- pc86 10y agoAnchoring only works in this way if there's no definitive market value for what you're selling. I know what a software architect commands in my geographic area. If you come in asking for 1.8x that, you're off the table as a candidate immediately (which you mention in the next point). No amount of anchoring will change that.
- louisswiss 10y agoAgreed. More likely, however, a software architect commands a range of salaries in your area (eg 80-130k with a few outliers either side). As an 'average' performer in this scenario, you would do well to anchor your 'value' at 120k and let them make excuses why 105k is more reasonable. The alternative (let them anchor you at 90k and then you have to explain to the recruiter why you are worth 15k more) will be trickier in most cases.
- Spooky23 10y agoIn places that don't use salary bands, many companies will hit you with previous salary + 10%. In one place that I worked at, salary for a common technical job title (n=100) varied by 50%. The mechanics were pretty obvious. People who worked their way up got screwed with the 10% raise bullshit, and people who came in through some other means were able to extract higher salaries. Where I find this stuff annoying is where there is no signal about the salary level. One placed I spoke to many years ago was advertising for a position that was probably worth $100-105k in the market, but they were hiring at $50k.
- komali2 10y agoI think you're confusing two sales concepts - first to talk, and anchoring. Anchoring is a more general marketing concept that works well in advertisements (crossing out a black $280 and putting a red $100 underneath it). Anchoring doesn't work so well for something much more fluid (and with much more at stake) such as a salary negotiation. In-person sales meetings (which is what an interview is, for both sides) are where "first to talk" come into play. It's a concept as old as war meetings between opposing roman generals. First to talk loses, period. Why? I don't know, but years of sales and recruitment has taught me that whoever slips is going to give the advantage to the other side of the table. You can only hurt yourself by giving a number. The company has set a budget, either you fit or you don't. Maybe the budget is higher than you expected and you take the job for way more than you would have asked for. Maybe it's less and you don't take the job. The key point is that company is not the only company you are dealing with - you can move on to another. And another and another, and as long as you don't give your number, you will win out. I can't share this data but when I worked at a bootcamp our analysis showed this as well. Students that gave their number got paid less. There's a big push for bootcamp transparency so hopefully that sort of info will get published soon.
- deleted 10y ago[deleted]
- Pyxl101 10y agoCompletely agree that giving previous comp information or comp expectations can only hurt you as an employee. The only thing giving this information will do is provide a company the information they need to pay you less than they might have otherwise. I think it is difficult for employees to judge what they're truly worth. Therefore, when most people give a number, that number will be lower than what an employer may be willing to pay (and perhaps lower than the company's initial offer would be). I would guess this holds doubly true for graduates of a bootcamp, or recent college graduates, who have less industry experience on which to base their judgment of business value.
- siliconc0w 10y agoThe problem is that most companies won't provide an offer until you've gone through interviews which are expensive for both parties. So this reasoning holds if you have an abundance of time, but you can generally figure out what their likely range is going to be. Do research, ask colleagues, etc. Anchor at the high end of that - you can also leave it vague by talking about 'total comp' which can includes subjective things like equity, location, vacation, etc. You may loose some value by doing this but it'll also mean you won't waste time and so you'll only be interviewing in places that are in your ballpark.
- ufmace 10y agoI disagree that it's to your advantage to try to anchor to a high number early on. The reason IMO is that, at the beginning of a negotiation, neither party knows much about the other. They don't know enough about you to know whether it would be worth paying you that much, and you don't know enough about them to know if you'd be willing to work for them for that much. Start naming numbers at the beginning, and both sides will name extreme numbers to play it safe, they'll be far apart, and no deal gets made if they both stick to those numbers. Let them see what you can do for them, and let them show you what it's like to work for them, then you should find it easier to come to an agreement on a number.
- Overtonwindow 10y agoAnchoring fails because let's say the position is wanting to hire someone at $70k and you state an expected salary of $75 - 80k, negotiable. That employer may decide it's not worth their time because you'll want too much, so why bother with even calling you in for an interview. Asking for a salary number from applicants up front is not just a way to undercut them, but it's a way to quickly weed out and only interview those who are willing to take bottom dollar.
- taurath 10y agoThey get the talent and experience they are willing to pay for, and deal with the recidivism rate that paying under market gets you.
- throwaway91111 10y agoThat isn't banned by this law, though.
- nebari 10y agoYour points are valid if we're talking about a neutral salary negotiation, i.e., prospective employer asks, "What salary range are you seeking?" In this case, however, the disadvantage comes from a fixed number - your previous salary - not what you'd like. In a situation where you were underpaid, declaring your previous salary will definitely put you at a negotiating disadvantage.
- pfarnsworth 10y agoYou're absolutely wrong. You're negotiating from a position of weaker information. You have no idea what the other engineers are being paid, all you know is how much you're being paid, and what you would like to be paid. Meanwhile the recruiter/hiring manager knows exactly how much they are paying all the other engineers. You are now tasked with trying to get as fair/high a salary as possible, without knowing what their threshold is for simply no longer continuing the negotiations, because as you said "the price is just way too high". By hearing the other side first, you can then gauge whether or not your desired salary is acceptable, or you can try to negotiate up.
- OrwellianChild 10y agoThe problem I have with this approach is that with many companies, particularly larger established ones like AmaGoogSoft, base salary is just one portion of a compensation package that might have contributions of up to 50% from stock, bonus, incentive pay, benefits/matching, and perks. If you start anchoring on one piece of that puzzle, it limits your ability to move on others. If the goal of negotiation is to maximize your total offer (which it should be), then the only reasonable answer to the question is "depends on total compensation factors".
- _pmf_ 10y ago> I never answer questions about my past salary, not to employers and not to recruiters. You answer it by accepting an offer or giving a ballpark number for negotiations.
- josho 10y agoHijacking this for visibility. If the recruiter asks repeatedly, a trick that I learned is to answer that it's in your employee confidentiality agreement not to discuss the terms of your employment. It's arguably a true statement as well (in case you were concerned about telling a white lie)--your employer could be considering your salary as confidential because they obviously haven't disclosed it publicly, so you are taking a very conservative approach on the confidentiality terms in most contracts. edit: the statement doesn't need to be legally defensible, it gives you an opportunity to redirect and ask what they are willing to pay for the position or to learn about their benefits package.
- nommm-nommm 10y agoExcept it's illegal to prevent employees from discussing salary.
- tzs 10y agoNot quite, at least nationally in the US. The National Labor Relations Act only bans prohibiting employees from discussing salary with other employees of the same company. Prohibitions on discussing salary with people outside the company are fine. Also, it does not cover contractors or supervisors. Some states may have more extensive prohibitions.
- throwaway9475 10y agoA) A recruiter isn't necessarily going to know that. B) Even if they did, companies do illegal things all the time and get away with it. Maybe it's technically illegal, but also maybe your company would come after you for something trivial and just ruin your life with litigation. I totally understand actually wanting to abide by an NDA even if it's unenforceable.
- adrr 10y agoIf it was true you couldn't disclose salary it would make lots of things really difficult like getting a loan.
- 10y ago
- scarmig 10y agoHas anyone run into issues for sharing a current salary that anchors the discussion too high? I could see how an employer might pass on a candidate who's actually interested in the job, just because they know they can't match what the candidate is currently making and it's likely a waste of time to spend hours evaluating someone who's making 50k more than what you could ever offer. Or is this purely theoretical and not seen in practice?
- jnwatson 10y agoFor me, all the time. I've negotiated well throughout my career, so I'm above a lot of pay bands. My concern is I hope to be doing this for another 25 years...
- mi100hael 10y agoIf you're at the top of employees, it might be time to become the boss...
- master_lincoln 10y agoTo fulfill the Peter's Principle?
- mi100hael 10y agoNah, I mean OP should start their own venture if they've run out of salary headroom and want more.
- dhd415 10y agoYes, though that generally falls into the category of "problems you want to have."
- suresk 10y agoYes, lots of times. Pay varies widely in our industry, and it isn't uncommon for a lot of companies to never pay above $X, where X is substantially less than your current salary. Earlier in my career, I was less willing to share salary information. But now that my compensation is above average, I always have the "I am paid toward the top of the range in this area, here is what I make now/would be looking for, so that we don't waste our time" conversation very early in the recruiting process and it ends up being a pretty good filter. They are usually pretty open about saying "yeah, that's more than we can offer, thanks for your time", so if it were one of the few types of jobs I'd be willing to take a paycut for, it seems like there'd be an opportunity to let them know you are open to making less and go from there.
- manyxcxi 10y agoI've never gotten a lot of grief about disclosing past salary. I generally try to set the anchor and conversation around what I want to be making to join their company. I have (very fortunately) never been in the position where I _had_ to leave or accept an offer on anything but my own terms, I feel that when you're negotiating from that position, the complete lack of pressure to accept a lower number becomes pretty apparent to the people on the other side of the conversation from you. Or I'm dense enough to not realize they were trying to wheedle me down and just flat didn't entertain the notion. I've got a business partner (came from high on up in the land of the big four) that during a salary negotiation of our own he floated the idea of asking for our candidate's current salary, AND PROOF. Apparently over 'there', especially as you get higher up, it's completely commonplace. Having spent his whole career over there, it didn't occur to him that maybe people would rather just walk away from your company simply for asking than to answer the question. Luckily, he's a great guy and after my half hour soap box tirade he came around to realizing that in an environment where people are _actually_ practicing a craft and have what would resemble real skills[0], they don't put up with it. - [0] Not to say people working for the big megacorp accounting firms don't have real skills, but no, yeah, that's actually what I meant. I kid, I kid.
- akud 10y agoTo me asking for the previous salary - especially asking for proof - shows a lack of respect for the candidate. It's on the employer to quantify the value a skilled employee brings to the organization. I've walked away from offers because I didn't like the way they negotiated.
- matwood 10y ago> To me asking for the previous salary - especially asking for proof - shows a lack of respect for the candidate. Totally agree. It really sets up a us vs. them before the employee even starts work.
- najati83 10y ago> it's worth more to me to keep it private as I'm placed at a disadvantage in negotiations if I name a number first Can't you just... lie about it? Make up some high number so you're at an advantage instead of a disadvantage.
- always_good 10y ago> Most employers don't ask, and the few that > have have never made my leaving that information > out an issue. That is some serious English gore.
- ryandrake 10y agoI've had a handful of potential employers ask straight up for my current salary, and they ALL got squirrely when I refused to disclose it. Currently batting zero with companies that ask for (and I politely decline to give) that info. EDIT: Also I kind of disagree with your assessment that it's a "seller's market" for IT talent. A lot of companies appear to be fishing for good deals, but is there really that much actual hiring going on? A lot of companies saying they're looking for talent does not a hot job market make.
- stale2002 10y agoThen you avoid the question by saying stuff like "oh, my salary range is this" or "I've received offers for this amount". Or just make up a number. Companies bluff all the time in negotiations. You should do it to.
- Pyxl101 10y agoI'd recommend reading Patrick McKenzie's (patio11's) article on salary negotiation for engineers: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ http://www.kalzumeus.com/2012/01/23/salary-negotiation/ Yes, they may all get squirrelly when you refuse to give that information, but this is often simply a tactic to pressure you into giving the information up. Stick to your guns. One tactic I would recommend is to say, "I'd prefer not to discuss previous comp or comp expectations at this stage. I'd first like to get to know the company and learn about the opportunities for me there. If we decide that we're a mutual fit, then we can figure out the comp. I can be flexible on the comp, and it's only one factor I'll consider alongside others like how passionate I am for the project, my team, and the company mission, and the opportunities I see for further personal growth." Your objective at this phase is to get past recruiting and into the interview process with potential fellow employees and hiring managers. Once there, if you do well and are a good fit, then they will start pulling for you. The force that a hiring manager brings to bear on that outcome is much greater than recruiting, and if the HM thinks you're awesome and wants to hire you, then the fact that you haven't given previous comp or expected comp to recruiting probably won't matter. Recruiting may respond to this tactic by asking, "OK, let's say we match you with a completely ideal job, project, team, etc. What would your expected compensation be in that best-case scenario?" This question is a trick designed to get you to reveal your lowest comp number, i.e., the lowest compensation you'd accept if all the other aspects of the job were awesome and made up for it.
- sitkack 10y agoBoth Google and Oracle made it a condition of getting hired. Meaning they were ready to walk away if previous pay wasn't disclosed. Oracle even wanted scans of W2s ...
- lightbritefight 10y agoTwo big fish in a colossally big ocean. Million of employers out there, many willing to pay at or near the same range without those onerous requirements.
- ssambros 10y agoHow long ago was that? I have interviewed onsite last year with every company in the Big 4 and some smaller others, and none of them made an issue out of me not disclosing my previous salary even during offer negotiations.
- Arizhel 10y ago>Oracle even wanted scans of W2s ... Yet another bullet-point in why not to ever work at Oracle.
- mahyarm 10y agoIs that after or before you have a finalized offer in your hands?
- sitkack 10y agoIt was after a written offer, during the background check.
- pmoriarty 10y agoEverything is negotiable.
- cynicalkane 10y agoGoogle didn't do this to me, and I've never heard of them demanding past salary from anyone I knew.
- 10y ago
- cordite 10y agoSome organizations use a month to month standard salary table for position which are not negotiable. Leaving the question as more for surveying the industry than a negotiating piece. However this is not often revealed until after the answer is given. I very much doubt that many organizations do this, though I have experienced it myself.
- collyw 10y agoI was like that a few years back, when I felt I was underpaid. I am now on an above average salary for the location I am in (though I still feel underpaid - Spain!) If I disclose my salary early it saves a lot of time wasting though it probably limits what I can ask for or will be offered.
- deleted 10y ago[deleted]
- dboat 10y agoIn the interviews I've been to, it is not unusual to have them ask you how much you are expecting for a salary. I've thought about this before and I don't see a way to refuse to answer that question without breaking the flow and tone of the interview. Do you recall any specific responses you've made to that question which allowed you to avoid answering it but still yielded positive results?
- pmoriarty 10y agoI simply say that I don't discuss that until I have an offer in hand.
- OJFord 10y ago> Most employers don't ask In the UK, they don't need to. > It's great that NYC is taking the lead on this, and I really hope the rest of the US follows suit. There's a lot of positive remarks in this thread, that I don't really understand. I see the advantage if your current salary is unusually low, but it cuts both ways: without knowledge of the company, (and within an industry) salary contains more information than job title.
- foota 10y agoI think part of the idea is that you still have the option to use your current salary as part of negotiation. If they make you a low offer just come back with "I make X right now, you need to at least match that".
- switch007 10y ago> In the UK, they don't need to. Yeah they just phone your reference and ask. Sigh.
- andy_boot 10y agoand the reference will tell them to get stuffed. Leaking salary details of employees to a competitor will get you fired.
- callmeed 10y agoIf you don't mind me asking, what's your reservation with revealing it? Is it more of a privacy/principle? Or do you actually lose an edge in salary negotiations by revealing it?
- jonathankoren 10y agoThe idea is that the first person to give a number loses, since that anchors the conversation. As an employee, it's an counter to the asymmetry of information. Employers know their own salary structure, and even have access to anonymized salary survey information. Employees don't have this information. Conversely, encouraging employees to not talk about your salary to other employees is another tactic to keep the information asymmetry. If you're underpaid, you'll never know it, and that's how they like it.
- komali2 10y agoI remember with Ticketmaster I got into an actual eight minute long back and forth during a recruitment call about my "number." Eight minutes is a long time on the phone. It went something like her: "Just so we have an idea of your range..." me: "I understand why that information would be helpful to you, but I can assure you that if everything else is a good fit, salary is the last place we'll find ourselves disagreeing." Back and forth. Eventually I had to just cut her off and let her know it wasn't a good fit. I've never had a problem winning the "give us your number" battle before, I honestly have to admire the tenacity of that recruiter. Seems like Ticketmaster genuinely cannot hire without getting that information.
- mcv 10y agoAs a freelancer, I'm fairly up-front about my hourly rate. If they want to pay it, I'm happy. If they don't, that's fine too. If there are other interesting aspects about the project that make up for the lower pay, we can negotiate. But it saves me time not having to talk to clients who can't afford me. But freelancing is a different market than salaried employment. I think for salaried positions it's up to the employer to be open about their pay range.
- kafkaesq 10y agoAs a freelancer, I'm fairly up-front about my hourly rate. The law doesn't address your expected or preferred rate (for your next gig); but rather, about disclosing your past rates. Which is a huge difference. (Actually, the rule applies to employment negotiations only, and has no effect on freelance discussions, per se. However, it seems it may give significant moral support to those on the freelance side who are, frankly, pretty tired of this pesky sales tactic).
- peripitea 10y agoI've found it easier to just lie in these situations by giving a number that's significantly higher than what I'm currently making, and more in line with the top end of what I think they're willing to pay me/what I would be willing to work for. It has worked quite well for me. Obviously this only works if you are comfortable lying in this scenario. I don't normally like to lie, but I see no moral issue with it in a situation like this where the system is intentionally rigged against you. They are systematically depriving people of pay; I'm not going to lose sleep over a small lie that rights that wrong.
- brianwawok 10y agoI have seen places as a final step of an offer ask for proof of previous wage. Not super common in software, I know people in law and a few other fields that always have to do it...
- peripitea 10y agoAnswered more in depth in response to sibling comment, but fuck those places! Politely decline their request (they have no right to that info), or if you're comfortable doing so, continue the lie by forging your paystub or whatever ridiculous form of proof they ask for. This is a ridiculous request and should be treated as such.
- nunez 10y agoThere is no need to lie. Also, it can set you up for failure if that info comes back during a background check. Just say how much you want up front.
- peripitea 10y agoSaying how much you want is different from saying how much you currently make. It may be numerically the same, but there are big differences in how that information is treated. One of several examples: A recruiter who has been told to offer you up to 100k will probably not go back to the hiring manager if you just say "I want 120k"; they will tell you that's outside of the range for that position. But if you say "I make 120k and would need to earn at least that to consider leaving", that is much easier for them to escalate. This is something I've seen happen at two different companies, on the hiree and hiring manager side. The background check thing feels mostly like a boogie man to me. It's convenient for recruiters that engineers believe that, but I've never seen it happen in practice. And if it did (how does this even manifest? they require you to send them a paystub? they can't compel your previous employer to divulge this info), you should be outraged! It's none of their business what your paycheck at your previous employer looked like or contained. I would respectfully decline to provide this information, and if they insisted I would edit or photoshop it, and give serious thought about whether this is the type of employer you want to work for. You should be indignant about the fact that an entity you are planning to devote the majority of your waking life to for the next few years is comfortable with systematically fucking you over like this.
- paulddraper 10y ago> It's great that NYC is taking the lead on this How do you rectify this with constitutionally protected free speech? Is freedom of speech meant only for the little guy?
- jgalt212 10y ago> I never answer questions about my past or expected salary, not to employers and not to recruiters. That's great for you, but a prospective employer refused to put an official offer package together for me until they had proof of my recent salary. And no, there weren't other contemporaneous offers on the table at the time, nor were there other employers in my industry whose practices greatly differed from above. In short, I think this a great consumer protection rule. Not really consumer, but little guy/girl protection rule.