Live data from Hacker News

Ask HN: Negotiating Salary

news.ycombinator.com

121–130 of 172 posts

Re: Ask HN: Negotiating Salary

#121

Disclaimer, I'm a CTO. Here's how I evaluate this if I was evaluating you: 1. I already have a salary budget already allocated for this role based on industry average for position and location (but location _could_ be irrelevant depending on skill mostly). 2. I look at your skillset and put you at the bucket for the position where you are at: low-med-high 3. I make my offer based on my evaluation. 4. If you are "wort…

I'm curious, what industry is offering roughly minimum wage (30k) to programmers in the US?

$30k is far beyond minimum wage in most of the world.

Re: Ask HN: Negotiating Salary

#122

Earlier quoted context omitted.

Yea! The best way to negotiate is to have leverage. You can fake leverage, of course, but that's where the risk of losing the deal materializes. So rather than fake leverage, create it. Get other job offers.

To expand on that, there are two obvious forms of leverage: - have another offer - have a job that’s better the offer you get In my experience, having the job is easier timing wise. When Company A wants to extend you an offer, you can’t really get Company B to accelerate their hiring most of the time (and pushing them might just make them say you should take the other offer).

It's much more relaxing to be in a situation you're perfectly comfortable with and basically be in a position to tell someone "Make me an offer I can't refuse." Vs. being in a lousy situation, getting a very fair offer from someplace you want to work, and not wanting to risk extending/messing up things. (I've been in both. In the last case of the latter, I really wanted to just close things now and relax--and I'm pretty sure that was the right decision.)

Re: Ask HN: Negotiating Salary

#123
post #95

Earlier quoted context omitted.

I'm not the person you're asking, but I tried a question very similar to that once. It -- the question -- did not have the intended effect. The negotiation itself left all parties happy though, so what do I know?

It seems most think it would be awkward, so it probably would be. I'd like to hear more about how it went for you. It seems like one of the ultra logical views which people find weird (or offensive) when spoken out loud. I mean, the principle here is clearly true, both the employee and employer must profit, if this condition doesn't exist the company soon dies.

It wasn't that it was awkward, it was just very hard to reason from the number that corresponds to future profits in a complicated way down to current compensation in a principled way.

Re: Ask HN: Negotiating Salary

#124

Earlier quoted context omitted.

I'm curious, what industry is offering roughly minimum wage (30k) to programmers in the US?

FWIW, that's double the federal minimum wage. I'm mostly pointing out how absolutely absurd our minimum wage is.

California minimum wage.

https://www.dir.ca.gov/dlse/faq_minimumwage.htm

Re: Ask HN: Negotiating Salary

#125

It’s all about who has the better 2nd option. How long will it take them to find someone else like you at the rate they want to pay? How long will it take you to find the pay you want somewhere else? The best thing you can do is find another alternative at the rate you want. Then you can say, “I want to work for you. You are my first choice. Just please match my other offer.” The other offer shows you are coming from…

> It’s all about who has the better 2nd option

Bingo. Know your BATNA:

https://en.wikipedia.org/wiki/Best_alternative_to_a_negotiat...

Re: Ask HN: Negotiating Salary

#126
post #121

Earlier quoted context omitted.

I'm curious, what industry is offering roughly minimum wage (30k) to programmers in the US?

$30k is far beyond minimum wage in most of the world.

30k Euros is what I got with 5 years experience as a developer in Italy, and it's quite normal here.

Re: Ask HN: Negotiating Salary

#127

I normally go with a range, not a specific number. I would be happy if I made between x and y. This allows you to set the actual minimum and give a higher max than you expect. Normally, they will pick a number in between.

I'm confused. Why wouldn't they pay you the minimum you requested. Why would you put an upper limit to your salary? Is this some strange game people play?

The minimum you request should be a number that would actually make you happy and content to accept the job. The upper number should be a high ball that you yourself don't actually expect to get. It shouldn't be some outlandish number way outside of what someone in your field can attain. This gives the company room to bid for your expertise with other companies without having to worry too much about putting yourself in a position like the original poster. And yes, I kind of think of it as a game, but an important, open and transparent one. The range you put forth leaves room for interpretation and makes the company uncertain. If you say one minimum number and they want you, they will pay you that minimum number. If you give a range, it opens the door to the possibility that they will pay you more. The more that they like you and the more that they are worried you might accept a competing job offer the more likely they are to bid more.

There is lots of advice that says to avoid giving any number. Sure, you can try to do that, but in my experience it comes off as a more aggressive tactic that may leave a bad taste in their mouth. I'm not sure if anyone else recommends this strategy, but anecdotally it has worked well for me. You still need to do research on what your field pays and you need to understand how well you do whatever it is that you do.

edit: Over time, being assertive but not overly aggressive in salary negotiations will pay huge dividends. I've heard of far too many stories of timid engineers that accept 5% raises or salaries for new positions year after year. Each one of those small increases in salary puts you further and further behind the curve. Companies don't ask what the history of your pay raises are, just what you are currently paid. Getting more now, means getting a lot more later. Early in your career if you are good at what you do, you can be more aggressive than later because it does not impact the balance sheet of bidding companies much. I had a good 4 to 5 year stretch early in my career where I was making >50% more than I was the previous year. Switching companies usually meant bigger increases in pay, but not in all cases if you prove yourself to be a valuable asset. Doing what you do well is still extremely important and if you do it well enough, the ROI of hiring you far outpaces your salary and companies will gladly make that investment to hire you and to retain you by keeping you happy and productive.

Re: Ask HN: Negotiating Salary

#128
1. Try to get them to throw out the first number. You never know, they might offer more than you would have asked for. (This isn’t always possible, especially for entry-level jobs.)

2. Always politely reject the first offer.

Then make a specific counteroffer, don’t just say “More money, please.” Give a specific, reasonable-sounding justification. It doesn’t even have to be that great.

“I am excited by the opportunity to join $COMPANY as a $ROLE. It is directly in-line with my career path, and I’m confident that I will bring my skills and enthusiasm to this role. However, based on my research into prevailing industry wages/salaries in our region, I believe $X is more appropriate for someone with my educational background and level of experience.”

3. Ask to see the entire compensation package, not just the wage/salary.

Stock options/RSUs? Employee stock purchase plan? What kind of health insurance do they have? How many paid holidays? Vacation policy?

Re: Ask HN: Negotiating Salary

#129
The key to all negotiations is to avoid "you vs them". Don't engage in an arguement over money, ask "what would it take for you to justify paying me the extra"?

Your partner in the negotiation (note, partner not adversery) has a whole bunch of worries NOT connected to the dollar amount: will you fit in (will he look bad if you don't), will you leave too soon, will you phone it in, will you be reliable, will you refuse $X/hr (will he look bad if you don't AND will he look bad if he pays you more than that).

You're job is to find out what he is concerned about and then deal with those concerns. That allows him to pay you extra. You're working together on this.

In my second job in tech I had two issues: I wanted about 10% more cash and I wanted more time off.

I knew they had had issues with staff turnover. So I suggested delaying the higher pay and split it in two raises: one wasn't until I'd been there 6 months and the rest at 12 months. So I got a 20% raise, more than I actually wanted, just by dealing with their bigger concern.

I got the raises in writing of course.

For your case, what do you need to do to be worth the extra $/h? Presumably the CTO wants you to reach certain milestones so ask them to be specific, and tie things to that. Maybe if you had qualification Y he would feel happier justifying the higher rate. So if the company pays half you could do that in your spare time right?

The added advantage of this is that it makes it really hard to say no. He sees you as a reasonable person, willing to work with him, able to give as well as take etc. He doesn't want to look petty or uncooperative in front of whoever else is involved. So he will also make offers.

Don't expect to get everything you want or to get it immediately. You won't. But also remember you will regret not at least asking.

There are a bunch of "tricks" (really just tips eg "don't name a number first") you should Google but the overall mindset is much more important.

Re: Ask HN: Negotiating Salary

#130
Just because $30/h is a lot in your country it doesn't mean you should get yourself exploited. If you really have the skill, then you have very very valuable asset and you would want to sell it at appropriate price.
Post reply on HN