News for hackers. Stuff that matters.
Re:Ask HN: How much do you make at Amazon? Here is how much ... by enraged_camel on Friday March 18, 2016 @09:13PM (#11316670)
I interview techies, and I always make a point to ask them to give me their expected salary range. The purpose behind this isn't to one-up them and pay them as little as possible. It's just in both parties' best interest to avoid wasting time if the expected pay is too high. Neither we nor the candidate want to go through several rounds of interviews for something that ultimately won't work out.

And at the opposite end of the spectrum, if a candidate gives a number that's too low, we ignore that and offer them what we think they are worth (which is a higher number). Our reasoning is simple: if we treat people fairly, they will be more loyal and less likely to jump ship at the earliest opportunity that pays more.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by p4wnc6 on Friday March 18, 2016 @10:05PM (#11316862)
A lot of recruiters say that it's not about ensuring the candidate gets the lower end of their expected range, but that's just what they say.

I actually have a friend who worked at one of the aggressive boutique recruiting firms who mostly focus on the New York investment banking jobs.

He told me that almost always, their client companies would tell them that if they were able to get a candidate to come in with a salary below X, the recruiting firm would get an extra bonus on top of their commission, and the bonus was priced to make sure it was more lucrative to try to suppress candidate wages than to adequately represent the candidate's higher-end expectation.

Whenever I hear a recruiter say anything like, "Look, I don't get paid unless you do so clearly I'm trying to get you the most that I can..." it's an immediate dealbreaker. They are probably being paid a bonus precisely to ensure I come in at a lower salary than what I could otherwise command.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by mdpopescu on Saturday March 19, 2016 @01:49AM (#11317502)
Agreed. I had two different recruiters offer to increase my contract rate when I told them I had accepted another offer. That suggests to me that they're paid amount $X and were offering me $Y < $X, with their commission being the difference.
Re:Ask HN: How much do you make at Amazon? Here is how much ... by bboreham on Saturday March 19, 2016 @04:51AM (#11317823)
I hired developers into investment banking for 18 years. If we gave somebody a low number, the next bank would poach them in 1-2 years, wasting all the time we spent training them. After I learned this the hard way, I always went as high as I felt able to on the initial salary, because raises were much harder later on.
Re:Ask HN: How much do you make at Amazon? Here is how much ... by timv on Saturday March 19, 2016 @08:17PM (#11321159)
That was my experience as well. If you want to pay your team well, the best option is to bring people in at the highest number you can justify.

Raises were always harder to arrange, but it was a lot easier when we had evidence that new hires were costing us 20% more than our existing high performers were paid

Re:Ask HN: How much do you make at Amazon? Here is how much ... by JoshDoody on Friday March 18, 2016 @10:49PM (#11317038)
This response makes me wonder why you don't just tell the candidate the range you're willing to pay and let them tell you if that works for them.

I definitely understand the need to be efficient with everyone's time, but "have the candidate share their desired salary" is only one way to do that.

I have heard this reasoning from recruiters many times, but haven't heard a good explanation as to why they don't just tell the candidate the range they're willing to pay.

(This is a genuine question) Why not just tell the candidate your range if your concern is to respect everyone's time?

Re:Ask HN: How much do you make at Amazon? Here is how much ... by enraged_camel on Saturday March 19, 2016 @12:01AM (#11317232)
We do that too. We don't have a preference either way, because for us it only serves one purpose, which is to determine if we should continue the interview process.

Surprisingly, very few candidates ask us upfront what the position pays. In fact, we've only had one candidate who tried to play the "salary game" (if you will) and turned the question back on us when we asked what their salary range was. Like I said though, we just reveal it. To us, it's not a game, but rather two parties exchanging information in a fair and transparent manner.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by vidarh on Saturday March 19, 2016 @05:44AM (#11317918)
You may think it is not a game, and I don't doubt your intentions, but it still is a game.

At the beginning you are not invested in the candidate. A candidate that wants to work for you, but wants to maximize salary would be foolish not to try to get you to invest more before starting to talk salary, as it's far harder for you to walk away over 5% or 10% or even 20% once you've decided you have a candidate you like and face the prospect of spending time on another candidate instead.

You have the power advantage that passing the candidate over has less impact for you than it has for many/most candidates, so to a candidate it is far more important to spend the effort of selling you on just them first before talking price.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by albinofrenchy on Saturday March 19, 2016 @12:07AM (#11317252)
The reason is because the first person to say a number is at a slight disadvantage, and recruiters and managers don't want it to be them.

It is true that making sure you are on the same page salary-wise is a good idea, but it doesn't always have to be the interviewee to establish that.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by enraged_camel on Saturday March 19, 2016 @12:40AM (#11317337)
See my response... this isn't the reason we do it. In fact we try to put the position's salary range on the job posting if we can come up with an agreement internally (our hiring is very informal). Or we put "market rate; negotiable" or something along those lines, and put the onus on the applicant to research what their market rate is.

Basically, I have a checklist for the first phone interview, and the relevant item on that checklist is "make sure pay range is agreeable". It doesn't say "get desired pay range from candidate" or "let the candidate know what the pay range is". We have no preference.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by vidarh on Saturday March 19, 2016 @05:29AM (#11317885)
This, to me, indicates that if I was interviewing with you my priority would be to not give a salary range, nor to agree that your salary range is acceptable.

Because when you say "if we can come up with an agreement internally (our hiring is very informal)", that to me means that if I get through interviews and you like what you see, I'll be able to work with you to get you to fight for a bigger budget if I expect more than what you had in mind.

It's easy to get people to push their numbers up once they know you and like you and believe they need just your skills, and it's easier to do that if you've not revealed that you'd be willing to settle on their range earlier in the conversation.

My best results in getting good offers have been when I've deferred all exchange of salary information until the very end: Get them to agree that they want me to join, and it's "just" the formality of getting me to agree to a salary. At that point the interview process has gone from me courting them, through a "it looks like we both like each other", to them courting me, and the power balance has shifted substantially because the hiring manager is invested, and everyone has spent lots of time getting to that point.

This doesn't necessarily work as well at low end position where you're just one of many cogs, but it makes a big difference when people are looking to slot in just that one important (to the hiring manager, you might still be inconsequential to the overall business, depending on size) position.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by albinofrenchy on Saturday March 19, 2016 @01:19AM (#11317440)
So in talking in generalizations, it might not apply to you specifically. But broadly, over the industry, I think its slanted this way for the reason I described.

Even here, you ask the candidate for their salary range, instead of just stating what yours is.

If the salary isn't posted, it's a negotiation. There isn't a hiring manager alive that will blow off a potential hire because they ask for 5-10% more than the initial offer. They might not give it to them, but they won't walk away because of the question. Naturally, as a hiring manager, you might very well offer 5-10% less than your maximum in order to either give you bargaining room, or come in under budget for the position.

It's lightly adversarial, sometimes unpleasant, often annoying, but a part of life unfortunately. Some places more than others for sure, but I think it'd be hard to escape it fully.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by vidarh on Saturday March 19, 2016 @05:38AM (#11317906)
Personally I have never taken only 10% more than the initial offer. I've also as a hiring manager never offered so much that I didn't have much more than 10% to give up in negotiations... Usually I'd have at least 20% wiggle room, and if I really like a candidate I'd fight to be able to offer more if necessary.

For my own part, usually I end up negotiating up at least 25%-30%. My "record" is 50% over the initial offer. Usually I also end up asking for more options etc.

The most unpleasant and adversarial negotiations have been ones where I had to give up salary information at the beginning or have the conversations cut short. They're the only negotiations I've entered into where I've sometimes ended up being lowballed, and the only ones that have failed over salary, and in one case led to me telling a recruiter to fuck off and never me call me again over it. As a result, these days I will tell them flat out that if they need my salary details up front, that indicates to me they are unlikely to be able to afford me, and to call back when they have more budget flexibility.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by p4wnc6 on Saturday March 19, 2016 @01:45AM (#11317495)
Candidates don't know this about you and have no a priori reason to trust you or believe it. Since most other corporate negotiators are far more predatory than you, it means candidates are better off adopting a unilateral strategy in which they just believe all negotiators are behaving badly.
Re:Ask HN: How much do you make at Amazon? Here is how much ... by tamana on Friday March 18, 2016 @09:36PM (#11316746)
Why don't you just tell the candidate your offer range and let them decide if they are interested?

Because you aren't honest at all, to system is trying to get rmpoyees for less.

Re:Ask HN: How much do you make at Amazon? Here is how much ... by mdpopescu on Saturday March 19, 2016 @01:46AM (#11317498)
On my phone interview with an US company in 1999, they asked me what salary I wanted. I told them "in my previous remote job, I was making $3.25 an hour; I would like $4". They replied "we'll give you $6". (Romania, Eastern Europe - this was about 8 times the average salary.)

This was the only time someone offered me more than I was asking :)

Re:Ask HN: How much do you make at Amazon? Here is how much ... by vidarh on Saturday March 19, 2016 @05:57AM (#11317940)
I've been on the hiring end of similar conversations. Often the thought process is that you're dealing with salaries so small compared to what they're used to that it's worth quite a bit extra to get someone who is so happy with what they're paid that you increase retention and don't have to spend time hiring replacements as often.

It can be one of the great parts of negotiating with someone located in a much higher paid location.