Live data from Hacker News

High Salaries Haunt Some Job Hunters

wsj.com

171–180 of 236 posts

Re: High Salaries Haunt Some Job Hunters

#173

Earlier quoted context omitted.

Why the hostility? I'm not making any of this up. That bonus is typical of multiple places I've been, usually comprising 15% individual performance bonus and 15% company performance. And of course 150 sal != 300 sal. 300+ is total comp, as I already said.

Software Engineer 5 at Facebook is total comp $268k on glassdoor. Your estimates are way too high.

If I look at the Glassdoor salaries for places I've worked the numbers (total comp especially, but also base salary) are sometimes quite low.

They get less accurate the higher up you go (where you also have less data points), I think mainly it's a combination of sparse data + older data points being way out of whack with recent increases due to the competitive market.

I've personally seen numbers at several places that some people on HN vehemently tell me I shouldn't believe... and sometimes, even Glassdoor seems to give numbers that a lot of commenters here don't always seem to believe (like that $268k number).

Re: High Salaries Haunt Some Job Hunters

#174
post #136

Earlier quoted context omitted.

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. 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…

Yup 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.

Are you guys both over 45? Just curious.

Re: High Salaries Haunt Some Job Hunters

#175
post #136

Earlier quoted context omitted.

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. 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…

Yup 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.

Seriously, 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.

Re: High Salaries Haunt Some Job Hunters

#176
post #92

Earlier quoted context omitted.

My 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...

You 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 o…

>Anyone else wanna share?

Yes please do (everyone). The reason is to drive wages up. Hiding this knowledge doesn't protect YOU, it raises the bar for your next job. They're going to outsource and insource you anyway so that's nothing to fear.

Looking for an entry level Django gig and have always wondered what it should be (of course market matters). Generally stated, finding -any- developer under 85K is a bargain IMO and you pretty much confirmed that. I know many make less than 85 (like me), but I've had it with being taken advantage of as well. Only have so many healthy years to provide, next job is going to be the right deal to take care of my family.

Re: High Salaries Haunt Some Job Hunters

#177
post #174
post #136

Earlier quoted context omitted.

Yup 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.

Are you guys both over 45? Just curious.

I'm 32 and I've been setting my price for the past 4 years. I also didn't get out much for 6 years :D but it was worth it.

Re: High Salaries Haunt Some Job Hunters

#178

Earlier quoted context omitted.

Big tech companies in silicon valley.

I want to believe the numbers you provide are right, but then I look at 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.

Google and Facebook don't let it be easily known who their highest paid employees are, or even that they exist. They'd get poached.

Re: High Salaries Haunt Some Job Hunters

#180
post #130

Earlier quoted context omitted.

I share if the candidate asks. In the end the candidates requirements come out though. If I say X, they'll often say, oh I really need Y. I can work with that. If they just walk away when I say X, that's fine too -- it wasn't a good fit.

That's not a fit issue. They just don't want to work for that wage. Find someone who will. Why do they have to ask? If you're really interested in efficiency, state it upfront, atleast the lower and upper bounds.

It doesn't matter to me who asks first, just the the discussion is had to avoid wasting time if it's likely to be a problem. Sometimes they ask about salary range, sometimes I ask about salary requirements.

Debating whether a disconnect on $$ is a "fit" issue seems kind of silly. If it's not a job they would take because of pay, it's not a good fit for them.

Post reply on HN