Live data from Hacker News

My somewhat complete salary history as a software engineer

humanwhocodes.com

31–40 of 691 posts

Re: My somewhat complete salary history as a software engineer

#31

What kind of work is being performed by those at the 200k level? machine learning or just like react, etc?

I'd look at it from a different perspective. A low-level SWE salary might be $120k, and the all-in cost of employment might be $160k (benefits, taxes, office space, lunches, etc.). For a senior person, the base salary might be $200k, and the all-in cost might be $260k. So how does the senior person justify that extra $100k?

Well, they just have to output about 2x more impact. In my experience, it is not very hard to be 2x more impactful than a junior engineer. This is not meant to be arrogant, just that it's very easy for a junior engineer to waste time on useless stuff. In some cases junior (or bad) engineers will be 10x or 50x slower than they should be. I've seen some really bad examples in my 10 year career.

For example at my last job, a team of 2 engineers was using the wrong tool for a task, and this resulted in them taking 5x longer to deliver a worse product than alternates. I was able to do the same thing as them, but deliver much faster and at lower cost.

In other cases, junior engineers will make poor decisions, or write bad code that needs to be refactored later. This can be simple things like thinking on the wrong layer of abstraction. Refactoring the bad code is effectively 10x slower than doing it right the first time.

In all, I think paying an extra $100k for a good engineer is a real bargain for companies, because the impact can be so huge. The real challenge is figuring out who is a legit senior engineer.

Re: My somewhat complete salary history as a software engineer

#32

I'm actually surprised that as a 'Principal Architect' he was only making $208,000 a year. Considering that entry-level positions at large companies which can have cash compensation of around $150,000+, it seems he may have been 'underpaid'. Of course $208,000 is nothing to scoff at, and money is hardly the most important thing when it comes to life. Just interesting to see that a reasonably large Bay-area company wo…

As I noted in another comment he’s for whatever reason only counting cash salary.

I agree with your point though, no matter how bad it makes me feel :(

Re: My somewhat complete salary history as a software engineer

#34

I'm actually surprised that as a 'Principal Architect' he was only making $208,000 a year. Considering that entry-level positions at large companies which can have cash compensation of around $150,000+, it seems he may have been 'underpaid'. Of course $208,000 is nothing to scoff at, and money is hardly the most important thing when it comes to life. Just interesting to see that a reasonably large Bay-area company wo…

[deleted]

Re: My somewhat complete salary history as a software engineer

#35
The salaries are somewhat reflective of where you work and how good was your interview. And of course you have to love what you do. 2010 . 72 . (East Coast) 2011 . 78 . (East Coast) 2012 . 84 (East Coast) 2013 . 88 . (East Coast) 2014 . 96 . (East Coast) 2014 . 135 . CA 2017 . 210 + 20 CA 2018 . 185 + 30 + 60 CA 2018 . 195 +25 + ? CA

I try not to work more than 40 hrs a week. Ironically people are more happy when I am working lesser cause it seems to ease everyone. I have been able to get offers as high as 350K for base salary but honestly they scare me.

Re: My somewhat complete salary history as a software engineer

#36

Nice money at those big American companies. In Australia, you have to become a plumber to get to those levels :-)

The pay rates for tradies in Australia is phenomenal. If I had kids, I'd be encouraging them to become electricians, not software engineers.

Even a lot of unskilled jobs pay really well in Australia. I have a friend who works for Aldi in their distribution centre as a general worker, and he's on $35 per hour (only 6 hour shifts though, I think), plus when he's rostered on Sunday he goes up to $70 an hour.

Anecdotally, as a software developer in Melbourne for a small company, with 2 years experience, I'm on AU$75k + super, which is a pretty comfortable wage. Coming from NZ$42k (and only 3% super) back in New Zealand, it was certainly a nice payrise.

Re: My somewhat complete salary history as a software engineer

#38

What kind of work is being performed by those at the 200k level? machine learning or just like react, etc?

My friend is making about that as a new grad at a trading company.

He writes performant React code for high-speed table rendering. I know another guy making about that much at FB as a new grad. He works on Messenger games.

Re: My somewhat complete salary history as a software engineer

#39
I can’t help but be alarmed by the fact that his health has been on the decline for the last five years due to contracting Lyme disease.

I know of one person who was fine after like a month (detected early) and someone who spent the better part of a year recovering, but nothing like this!

Hope the blog writer gets better soon.

Re: My somewhat complete salary history as a software engineer

#40
I worked briefly with Nicholas at Box though we never met. I recall him being one of a handful of Principal engineers at the company when I joined and aspiring to reach that position myself. I commend Nicholas for sharing this data and for the thoughtful way in which he laid out why he felt compelled to do so.

I wish Nicholas health and happiness.

Post reply on HN