by bhaile on 9/3/15, 5:15 PM
by exstudent2 on 9/3/15, 5:14 PM
As stated in the article, it's best to ask them for
their budget. If I have any interest at all I clearly state these two things on first contact with a recruiter:
1. I don't discuss my current or past compensation.
2. Before I engage at all, I need to know what the baseline salary and compensation package is for the role in question.
If they're coming to you, you have 100% of the negotiation leverage.
by abannin on 9/3/15, 5:11 PM
Recruiters are often paid x% of one year's base salary. In this case, your interests are aligned with the interest of the recruiter.
In my experience, recruiters are 'box checkers'. They have little to no knowledge of your skill set or the skills required for the job outside of buzz words that can be printed on a resume. The reason recruiters ask for your salary is not to engage in price fixing but to ensure that they pursue a placement where 1) the candidate is getting a pay bump and 2) the candidate is priced competitively.
by qudat on 9/3/15, 5:11 PM
Ignoring the recruiter problem for a second, should I ever feel obligated to disclose salary information? I have had potential employers straight up ask me what my current salary is, should I just tell them I'm not going to answer that question?
by halite on 9/3/15, 5:23 PM
This is useful advice. I'm in Canada and thinking (and trying!) about moving to states in very near future. honestly it's been challenging dealing with this.
Here are few conversations (from what I remember):
Amazon Recruiter: So how much are you making right now?
Me: I'm in Canada and I'm interviewing for a position in NYC, how's that relevant. In my Province, we've a central database with salary stats. If you've something similar, I can use that to come up with a number backed by data.
Amazon Recruiter: I'll get back with that info (he never did!)
Generic Recruiter: How much in CAD dollars you make right now?
(Me thinking: Do you've any idea about conversion rate? If so, you'd not be asking this)
Me: Sorry I can't provide that information.
Recruiter: Just so you know when you work with US recruiters, this is a standard requirement that you must provide your current salary for us to be able to proceed.
Me: Thanks, I think I'll have to find someone else (and we ended there).
Based on news articles it seems it is difficult for tech companies to find good people but it is equally difficult for individuals to weed out these recruiters trickery from my experience.
Glad to see that asking for salary is not 'standard' requirement!
by antjanus on 9/3/15, 5:16 PM
This is definitely a hard lesson to learn for many. Recruiters often cite that it's a routine question. But just because it is, doesn't mean you should answer it.
I've seen some recruiters straight up refuse to work with me when I wouldn't disclose my current salary. Very glad they did.
by totalrobe on 9/3/15, 5:24 PM
Did this thread get flagged or something? It was just on the homepage and now don't see it.
by tomjen3 on 9/3/15, 5:13 PM
Ask yourself how much of a salary increase would I like to see, then add that to your current salary and say that sum when asked. The recruiter knows you are not going to take a salary that is below what you currently make, so they will have to offer you a good salary or give the job to somebody else.
Also go read "A Strategy of Conflict", which will enable you to understand and analyze all sorts of negotiations.
by myblake on 9/3/15, 5:09 PM
Seriously, read this post, listen to this post. I am a terrible negotiator (as in I have taken pay cuts because jobs seemed interesting and paid sticker price for cars) and hate it like 95% of the rest of software engineers but it's how the game is played and we're both ourselves individually and ourselves as a group a disservice by not protecting this information.
by abofh on 9/3/15, 5:13 PM
When you know you're above market, it's not unreasonable to disclose, knowing they'll go to your old employer and verify you are the "real" deal.
There's little that's a more powerful statement of your value to your prior employer as the salary you'd previously negotiated.
by patorjk on 9/3/15, 5:39 PM
This is a tough one, because you don't want to waste your time on jobs that wont pay you what you're worth, so stating that you make X and need X + .2X is a good way of weeding out the crap. The author does sort of advise this with the notion of giving a salary requirement, but I've had friends who've used this term and companies have ignored it, thinking they are bluffing. Also, I do see how you could short change yourself if their actual budget was higher when you state your salary or salary requirement. I've found the best thing to do is to apply to multiple places and see what kind of offers you get (and then to pit those offers against each other).
by ojgeojgaew on 9/3/15, 5:19 PM
The ideal is not to say nothing, but to know what you're worth and state that politely.
Most candidates who say nothing are either underpaid or overpaid and are trying to dance around that, instead of simply reframing the conversation to be about your market value.
by MisterBastahrd on 9/3/15, 5:19 PM
Sure, don't tell them what you're earning. Tell them what it would take to get you to leave... plus 15% for the inevitable downward negotiation with the manager. If your current employer is unwilling to pay you what you think you're worth, you have an obligation to yourself to go into the market and find compensation that matches your expectations. With few exceptions, compensation discussions with your current employer should be mutually exclusive from compensation discussions with other firms. Businessmen don't want to get into bidding wars when they can avoid it.
by russelluresti on 9/3/15, 7:39 PM
The frustrating thing about this is that the entire concept of salary negotiations is one of the prime causes of unequal pay between genders.
The entire culture of a company trying to offer you less than you're worth so that they can save a few pennies is disgusting.
There shouldn't be salary negotiations - people who do the same job should be paid the same salary. If you want to negotiate for extra vacation days or a signing bonus or whatever, fine, but not salary. Just pay people a fair salary and pay them the same.
The current salary negotiation setup is extremely detrimental to people and should be eliminated, not encouraged.
by oskarth on 9/3/15, 5:18 PM
Is there a crowdsourced list of startups that use shady recruiting practices somewhere? Not too long ago I was approached by a recruiter for a Unicorn company that repeatedly refused to move forward in the process before I disclosed my "accepted salary range" (asking for their budget, as people have suggested, gave me no response either). This was before I had even met a single person employed at the company. Normally I would have gone around the person in question, but this experience left a really bad impression of the company to me.
by meatysnapper on 9/3/15, 5:17 PM
It depends. If this a decent headhunter, and not just some chump recruiter trying to find lukewarm bodies, then they are trying to answer the question:
"What will it take for you to switch jobs?"
No problem with telling them your current salary- their goal is to offer you something better, and you can straight up say I'd need 30% more to switch. Remember, they get paid a % of your salary to get you!
by Quiark on 9/3/15, 5:15 PM
Eh, obviously. Now imagine my surprise when I came to Hong Kong and started to see candidates' current salary on their CVs without even being asked for it.
Not to mention that many companies do 'require' it. Next time I should claim it's confidential. Just to see how they react to a novel situation.
by xacaxulu on 9/3/15, 5:14 PM
Never never. The market is competitive. Just tell them "I'd be interested to hear how your company/client values my experience" or "I'm open to competitive offers". I've received crazy good job offers by simply never revealing salary.
by paulhauggis on 9/3/15, 5:10 PM
Wait, what happened to freely disclosing your salary to everyone? Remember the hashtag movement??
You mean to tell me that this is actually a bad idea?
by davidgrenier on 9/3/15, 5:14 PM