10 ms·
"Time and again, he says, employers seem to lose interest after he answers a question that they ask early on: 'What was your last salary?'" I never answer that
by pmoriarty 11y ago
"Time and again, he says, employers seem to lose interest after he answers a question that they ask early on: 'What was your last salary?'"
I never answer that question.
Almost always it's been recruiters asking that (and only some recruiters, the less reputable ones).
This is a seller's market for IT talent. You don't have to give in to bullying tactics to get a good job. I've had to walk away exactly once when a recruiter wouldn't accept that I wasn't going to tell him my previous salary and refused to work with me on that basis. The other recruiters who've asked accepted my refusal to reveal that information. They're generally more interested in getting paid for recruiting you than in finding out what you used to be paid.
I also never reveal the salary I'm looking for and insist on doing my own salary negotiations with the employer. I let the employer make an offer they think is reasonable and go from there.
You do have to be willing to walk away in the handful of times when this leads to an impasse. Fortunately, the way the IT job market is right now, there are plenty of other fish in the pond, and not showing your hand prematurely puts you in a much stronger negotiating position.
- joezydeco 11y agoBut it goes the other way, too. I've been contacted by many many recruiters offering interesting jobs but won't discuss the salary range targeted for that position. So how much time are you willing to spend on resume polishing, phone screens, on-site interviews, getting to an offer...just to find out that they can't even come close to your current salary? So now I just flat out say what my jump-number is. Any answer other than "yeah, we can work with that" is a reason to end the conversation and save everybody's time.
- jasonkostempski 11y agoWhat's a jump-number? Googling it came up with your comment as the top result and then skydiving :)
- coke12 11y agoThe salary number that would convince joezydeco to "jump ship".
- tunesmith 11y agojump ship to the new opportunity (meaning a high number), or jump ship on the conversation (meaning his bare minimum number)?
- joezydeco 11y agoJump to the new job. Doesn't necessarily have to be a high number, but if I'm not looking for a lateral (meaning, I like my current job), then it should be significantly larger than what I'm making in salary/benefits today.
- dceddia 11y agoI can see how that's ambiguous, and this is just an assumption, but I assumed he meant "jump ship to a new opportunity" because starting off with the lowest number you'd accept seems like a bad negotiation strategy :)
- deleted 11y ago[deleted]
- srpeck 11y agoMy standard response is "What is the pay range? Who is the client?" to the recruiter emails. The recruiters that get back to you generally mean business. Because of this, I have a huge amount of data on contract rates now. Also, a good side effect is that at least someone is telling them their rates are too low. Hope it helps another consultant down the line...
- kzhahou 11y agoYou should share that data, help your fellow job hunters. Last time I worked at a BigTechCo, salary ranges were $85-100K for juniors, 120-130 mid-level, and 150-165 for senior devs. Bonuses tend to hover around 30%. Of course, stock grants varied widely. The largest IC pay I saw was $2M/year for a someone who years ago was part of a famous project -- semi-known guy. More recently, I've seen (indirectly) BigTechCo's offering $300-350/year total comp to mid-levels, and 5-600K to seniors. Anyone else wanna share?
- merpnderp 11y ago300-350 for mid level developers and up to 600 for seniors? Where is this?
- kzhahou 11y agoBig tech companies in silicon valley.
- conanbatt 11y agoI want to believe the numbers you provide are right, but then I look at https://www.glassdoor.com/Salary/Facebook-Salaries-E40772.htm https://www.glassdoor.com/Salary/Facebook-Salaries-E40772.ht... and cant see where to get more reliable sources for thinking facebook or google pay that.
- kzhahou 11y agoThose salaries on Glassdoor pretty much match what I'm saying, with salaries running up to $165 for senior devs. Add 30% for bonus and $100-150K in stock and you're into the $300K+ range I'm describing. The $600K+ figure is for director level and above. The $2M/year individual contributor was an outlier.
- whoiskevin 11y agoSo now I just flat out say what my jump-number is. Any answer other than "yeah, we can work with that" is a reason to end the conversation and save everybody's time. Can't upvote that enough! I've been doing this for years. I don't have time to waste and if they won't talk the numbers there is no point in having the conversation. Statements like "we are competitive" or my other favorite "can you send us proof of your current salary" are hilarious. The proof is my favorite. What is the point of that? If I won't talk to you for less than x dollars there is no value in proving what I currently make.
- fleitz 11y agoYup on every call a sale is made, either you sell them on a reason they can pay you that much or they sell you on a reason they can't. Taking on a fuck you pay me attitude is the best thing that ever happened to my life.
- evo_9 11y agoAre you guys both over 45? Just curious.
- ldehaan 11y agoSeriously, this is good advice, if you're in the above average skill set range in an area that is in demand, such as senior sys admin/ senior programmer, and various other combos. Then you can name your price, the trick is finding a company that can afford you and isn't a total shit place to work for. I took a decent cut in pay just to be able to work for a company I actually really like. And while I can't afford to buy a new computer nearly as often I do get to work with really fun people and on projects that I really care about.
- tossaway1 11y agoAs someone who's regularly on the other side of the hiring (i.e. negotiating with candidates), I often prefer to have some insight into a candidate's rough salary requirements early in the process -- especially if it's someone that might demand more than I could offer. The hiring process is a huge time commitment for both me and the candidate -- I don't want all that time to be wasted if we could identify early on that it's not going to be a good fit. I wouldn't necessarily walk away from a candidate who wouldn't share approximate salary requirements early on in the process but it would probably be an added red flag if it was someone where I already had this concern.
- pmoriarty 11y agoSo just tell the candidate what the salary range for the position is. If that number's a dealbreaker for them, they'll let you know. Why does it always have to be the candidate who shows their cards first? Personally, for me there are no salary-based dealbreakers. There's always room for negotiation, after both sides determine there's a good fit.
- EvanPlaice 11y agoConsider that recruiters also have to justify their own existence. From a business perspective, their position is a sunk cost. If they can't signal to their employer that their work is gaining the business something above and beyond just doing their day-to-day job then there's no chance of advancement. They also dislike candidates that show proficiency in business for a few reasons. First, the candidate is more likely to move on for a better opportunity. Second, people with a business background like to 'shake things up' and head in new directions looking to maximize the potential of a company. Considering that HR's other primary responsibility is protecting the business from legal action, it's in their best interest to choose candidates who will stay on the straight and narrow and not shake things up. Third, business types ignore the 'gatekeepers' and take action on their own. They may make a groundbreaking decision that takes the business in a new and more profitable direction. Unfortunately for HR, it's hard to ride on the back of an accomplishment that they weren't aware of to begin with. Worse yet, that same type of personality may have the potential to climb up the chain to a level where they're the boss of the HR person one day. They aggressively select for 'code monkeys' because code monkeys do what their told, don't have enough soft skills to be a threat, suck at negotiation, and are too busy nerding out to look for something better.
- zippergz 11y agoI've found this to be an excellent way to waste a bunch of time by getting far along in the process, only to find out near the end that the company won't make an offer that's anywhere near my requirements. While I don't like being the first to name a number, I also haven't found putting the discussion off until the end of the process to be beneficial. I've been on the hiring side as a manager in a number of companies, and I've NEVER seen a situation where a candidate was so uniquely awesome that the company was willing to make an offer drastically larger than their normal range for that role. A bit more? Sure. Some more stock or something? Often. But not, say, 50% more salary than anyone else at that level is getting. After many years in this industry on both the candidate and hiring manager side, I believe that it's in everyone's best interest to make sure you can at least get in the right ballpark early in the process before you waste everyone time.
- fweespeech 11y ago> I've been on the hiring side as a manager in a number of companies, and I've NEVER seen a situation where a candidate was so uniquely awesome that the company was willing to make an offer drastically larger than their normal range for that role. A bit more? Sure. Some more stock or something? Often. But not, say, 50% more salary than anyone else at that level is getting. Fyi, at $DayJob we have one guy at my level who makes 50% more than anyone else at the level he is at. So it does happen but its unusual. [e.g. Developer A-Z get $60-80k, Developer Unicorn gets $120k]
- krschultz 11y agoHow are you defining 'level'? Two individual contributors are not at the same level just because they do relatively the same job. I'm sure some of the better IC engineers at my company make 2x or more what the new guys do, but there is 15 years of experience between them.
- fweespeech 11y agoSame job title. All relatively junior developers with less than 10 years of experience. Unicorn has 4.
- SwellJoe 11y agoHow old are you? I think something often unsaid in conversations about stuff like this is that ageism is rampant in the tech sector. I haven't experienced it first-hand (and I'm probably just now approaching the age where it might be a factor, and I haven't looked for a full-time job in a couple of decades), but I know several folks who have. Even when they've been willing to take lower salaries, when applying for startups, in particular, older folks often get passed over. It gets called things like "cultural fit", etc. But, the thing is, we're talking about a "low six-figure salary" here, which is not that high for engineering work. In fact, in many markets, it's the baseline for anyone with more than a couple of years experience. I can't believe salary is the primary motivating factor, if it is a reasonable salary, well within the bounds of expected pay for people with experience. I haven't been in the job market since I was quite young (I've run my own companies since my 20s, with some contract work along the way to make ends meet), but, I know my dad experienced this to some degree; and he was an engineer in an industry that was not nearly as ageist as high tech fields often are (he worked in the oil and gas industry). His salary climbed through his 30s and 40s, and then finding work became more difficult in his 50s, and he retired early partly due to health issues, but also because of difficulty finding good long-term work. I don't think salary is the only factor here, especially given that most of the folks I know who've experienced this aren't insisting on making more than their peers doing the same work. The people motivated by money tend to rise up to management roles. The engineers who are driven by the desire to build things just want to make a decent salary while being in an environment where they get to build things. The most productive software engineer I think I've ever worked with was in his late 50s, and was making less than a number of developers in the company (but he had a private office and a few other perks that no one else got, and got to work on stuff that excited him, so he seemed reasonably content).
- ChemicalWarfare 11y agoAs long as the recruiter (either a headhunter or a company recruiter) is up front with what they can offer compensation wise I don't have a problem telling them where I'm at and where I want to be salary-wise. If it's apparent that there's no match there - saves time to all the parties involved. Sure you don't want to be "pigeonholed" into an X..Y salary bucket forever but for the short term while looking for the next opportunity that's just the reality of the situation.
- EC1 11y agoMy mentality going in is "please give me a reason to walk away". The few that don't are always surprising offers and get me excited. I go in determined to find a reason to walk away.
- fecak 11y agoI own my recruiting agency, and I don't care what your last salary was. I do care about what you are looking for so I don't waste your time, my time, or the client's time. I also realize that any target range you give me before even meeting the client may increase or even decrease after you learn all about the company, team, benefits, etc. All that said, a candidate that knows their market value should never have to fear talking about salary history or expectations. If you know your market rate, and you stick to that as your expectation, you never have to worry about being underpaid. Market rate can be hard to define sometimes, and there are clearly companies that are willing to pay above market rate in certain scenarios, but candidates who do their research (or trust the knowledge of others) never have to worry about talking compensation.
- vacri 11y ago> All that said, a candidate that knows their market value should never have to fear talking about salary history or expectations. The main article starts with an anecdote about how talking about salary history prevents a guy from getting work.
- curun1r 11y agoThis is the case whenever your expected salary gets higher than younger, cheaper replacements are willing to accept. This isn't a problem for people that have made more of their younger years, since the positions they're applying for are high enough leverage positions to justify the higher salary ask and younger workers are simply not qualified to apply. I see this all the time in applicants. They've spent 15-20 years on the job and have less than 5 years of useful experience. The rest is stagnation where they haven't grown their skills. And yet they expect to be paid as if they've got 15-20 years of useful experience. That's why answering the salary question derails the negotiation. There may be an odd recruiter that is willing to accept the premise that an older worker is able to complete the job's tasks at enough above the acceptable level to justify the increase in cost. But most will opt for a younger worker willing to do an acceptable job.
- Bahamut 11y agoI actually am happy to reveal the salary, mainly because I find myself on the higher end of the compensation scale for my experience. When you're on the higher end, it can help on the candidate side to avoid wasting time with prospective employers who want to lowball. It also doesn't stop me from negotiating hard, since I have turned down drastically higher numbers than most companies are willing to pay, so they know I easily have options. I'm more than willing to walk away from recruiters (and employers) who want to coerce me into accepting bad deals. Setting number expectations upfront with knowledge of the market saves me time, and tends to be enough to weed out the crap.
- vinceguidry 11y agoI would not tell recruiters my current salary, ($75K) but I did tell him my target salary, which was market rate for a mid-level Ruby dev in my city. ($115K) He wanted to go in at $110K. I kept telling him how odd it was to be negotiating salary upfront, and he told me "that's just how recruiting works." I just shrugged and let him do his job. If I'd wanted to negotiate my salary myself, I wouldn't be using a recruiter. Truth be told, I'd take $95K. I learned from the art world, a lot of times "market value" is a fiction created by people whose job it is to manage expectations on all sides. It's in everybody's best interest to simply accept the status quo. Sure, you can buck the system and gain an additional $10-20K, but that takes a lot of effort and I'd rather put that effort elsewhere. People buy into the cult of individualism too much. There was an article a month or so back about the maple syrup cartel. People here were applauding the renegades bucking the cartel. Not me. I'd get on very good terms with my cartel rep, get him a very good gift basket for Christmas, jump through every hoop they want me to jump through. The cartel takes a nasty, volatile market and smooths it out and makes it into a nice, reliable engine. That's what I want to be a part of. Not a damn free-for-all. Any other career field, it would be 10+ years before I can make $100K. Here I managed to do it in 3 years. Be a team player. Climb the ladder, pay your dues. It doesn't take as long as you think.
- pmoriarty 11y ago"If I'd wanted to negotiate my salary myself, I wouldn't be using a recruiter." For me, recruiters are useful for two reasons: to find me interesting opportunities and to help me get an interview. When they've served those two functions, I'd prefer them to just get out of my way. From that point on, I feel my own interests are best served by me representing myself. The recruiter's real customer is not really any one particular candidate, who they might see just once in their whole career, but the employer, who will likely be a repeat customer if the recruiter satisfies their needs. Looked upon from that perspective, it's not always in the recruiter's interest to land the candidate the highest salary possible. That might get the recruiter a higher cut that one time, but their real customer might not be too pleased if the recruiter keeps sending them expensive candidates. They'd be far happier if the recruiter managed to get them a sweet deal on a good worker. So I'll just keep doing my own negotiations, thank you very much.
- mrfusion 11y agoYou're not worried about wasting your time on salary mismatches?
- Consultant32452 11y agoI'm the exact opposite. I'm at a rate that's above the local market, so I mostly have to work remotely for firms in areas with higher cost of living. Any recruiter is going to find my salary range within the first 90 seconds of talking to me. This allows me to filter out 90% of calls because the salary range they're offering isn't even close.
- LargeCompanies 11y agoIf recruiters are chasing me while I'm gainfully employed... I, jack up the rate Im currently making, which has worked once; got a better paying gig. If recruiters are chasing me while I'm looking for my next gig... I make up a fair livable wage salary that won't push me out of consideration
- deleted 11y ago[deleted]