Live data from Hacker News

Base salaries offered to software engineers in SF, NYC, and Seattle

triplebyte.com

91–100 of 301 posts

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#91

I'm in Boston & went through an intensive FT job search here about 18 months ago. I'm a mobile developer with 20+ years total experience in desktop, backend, web+mobile, product management, started my own company, etc. Worked with lots of recruiters, personal network etc., felt like I really got a sense of what the salary landscape is here. Some facts: - I was leaving a job at a hot unicorn startup that paid $125K ba…

Purely based on my 'gut' (though I've been around):

1) SF/NY/Seattle salaries are skewed by really rich companies 2) Yes, there a big uptick as it's more competitive, FYI cost of living is much more. 3) The salary I think has a selection/sample problem that probably over estimates.

My bet is $150K for an experienced dev at a normal company in Boston is probably somewhere in the league of normal.

Consider that salaries are not as an efficient a market as we might imagine. If Boston area companies can get away with paying $140 instead of $180 they will! Most people don't move across the country for a pay raise. Worker mobility in the US is down over the last 30 year (weirdly).

SF has a lot of people moving there which creates a different kind of frothy market.

Boston is established and so everything gets established, including salaries.

Consider the situation: imagine if you had a company making ok profit, with 50 Engineers in Beantown. Do you think you could all of a sudden get your Eng. to the 'next level' by paying SF rates?

So you're staffing costs are way up, but is productivity? Surely, you might be able to bring on the best hires, but will that make all the difference?

It's such a big bet, and the inclination is always to make (or save) money 'now'.

It's a little bit like the 'open vs. closed office' calculation. The CFO can make a direct and measurable compelling case for open office: it's 20% cheaper. Those in favour of a nicer office can't provide the hard numbers on how much the company would increase productivity.

I think salary differentials are a crazy interesting subject and suspect there are a lot of weird and interesting things going on.

I'm from Canada, where any good developer can double their salary by moving to a choice job in the US. Why the hell would young talent stay? Which implies, how the hell can Canadian companies even remotely compete on building great companies of the top tier talent leaves?

Obviously this depends a lot on a companies specific need for hyper-top tier talent, those that don't would maybe be better off out of the Valley.

I also wonder a lot on what would happen if a well funded Canadian startup actually started paying super great salaries. Sure, they'd be able to get the best talent that comes through the door ... but then there's the other paradox: most Canadian cities are not destinations! Toronto, Montreal, Vancouver are regular cities, if you start a company there, most of your applicants will be local. It stands that local talent may not be all that spectacular (good but not great) thereby not justifying really big salaries. And can you really have 'regular salary' for the 'regular, local talent' and then inflated salaries for the international hot talent? That might be hard!

So SF, NY and Seattle have the advantage of being destinations, i.e. cities where people are willing to move, meaning that their quest for talent is really a not a function of the locals, but the top tier of a much broader pool of talent.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#92
post #85

Years of experience tops out at "8+"? An engineer that started working at 22 is barely 30 by the time they reach that experience level. Is 8 years really the point where additional experience ceases to have a meaningful effect on salary? Or do these three cities (SF/NYC/Seattle) just do a pretty good job of expelling software engineers after they attain their first gray hair?

I think in terms of strictly engineering after 8 years you start seeing diminishing rates of improvement.

I would imagine a lot of people in this group start transitioning into other roles in management

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#93
post #85

Years of experience tops out at "8+"? An engineer that started working at 22 is barely 30 by the time they reach that experience level. Is 8 years really the point where additional experience ceases to have a meaningful effect on salary? Or do these three cities (SF/NYC/Seattle) just do a pretty good job of expelling software engineers after they attain their first gray hair?

It may be the case that for a variety of reasons, salaries don't creep up that much past 8 years as it's just more difficult to either signal or create value then.

Despite the fact that a polygot dev. with tons of experience is always good to have around, and you need some weighing in on big decisions ... most dev is just dev - and a competent mid-tier developer with good habits can do the job in most cases.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#94

Earlier quoted context omitted.

What’s the difference between any of these roles? Full-stack versus generalist?

Great question - these roles correspond to our notion of engineering archetypes ( https://triplebyte.com/archetypes ), which define what concentration of skills a company is looking for for a particular role. In this case, full-stack indicates a web focus, while a generalist engineer is a more, well, general programming role - often one that requires less specific web knowledge.

You list six broad categories on the archetypes page, but only five made it onto the salary page. The "Low-Level Systems Engineer" got lost. That is the only one I care about. That's me, all three sub-categories, and also what I posted about today on the "Who Is Hiring?" article.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#95

Ben from Triplebyte here, I'm the engineer who built this tool from our offer data. The finding that most surprised me was that the mean salary for an engineer without a college degree is only $3k (~2%) less than for those with one; this gap is much smaller than in the labor market as a whole. One explanation is that CS really is a field where educational signaling doesn't (or at least needn't) matter as much as in o…

I do not have a college degree or bootcamp experience, do not put an "education" section on my resume, and only asked about it ~1/4 times in interviews/contacts. I am paid well at my "lead engineer" role at a fortune 100.

My open source/side project experience has opened doors though I'm sure.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#96

Earlier quoted context omitted.

What’s the difference between any of these roles? Full-stack versus generalist?

Great question - these roles correspond to our notion of engineering archetypes ( https://triplebyte.com/archetypes ), which define what concentration of skills a company is looking for for a particular role. In this case, full-stack indicates a web focus, while a generalist engineer is a more, well, general programming role - often one that requires less specific web knowledge.

These archetypes are great. Any info on what the compensation rank is among these?

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#97
post #85

Years of experience tops out at "8+"? An engineer that started working at 22 is barely 30 by the time they reach that experience level. Is 8 years really the point where additional experience ceases to have a meaningful effect on salary? Or do these three cities (SF/NYC/Seattle) just do a pretty good job of expelling software engineers after they attain their first gray hair?

It's the latter.

It's not the latter. Additional years don't matter as much past 10 or so... you're kind of doing the same types of things over and over as history repeats itself.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#98
post #85

Years of experience tops out at "8+"? An engineer that started working at 22 is barely 30 by the time they reach that experience level. Is 8 years really the point where additional experience ceases to have a meaningful effect on salary? Or do these three cities (SF/NYC/Seattle) just do a pretty good job of expelling software engineers after they attain their first gray hair?

It may be the case that for a variety of reasons, salaries don't creep up that much past 8 years as it's just more difficult to either signal or create value then. Despite the fact that a polygot dev. with tons of experience is always good to have around, and you need some weighing in on big decisions ... most dev is just dev - and a competent mid-tier developer with good habits can do the job in most cases.

In most careers, you top out around 8 years of experience for individual contributor. After that, you add value through scale of managing direct reports.

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#99

Ben from Triplebyte here, I'm the engineer who built this tool from our offer data. The finding that most surprised me was that the mean salary for an engineer without a college degree is only $3k (~2%) less than for those with one; this gap is much smaller than in the labor market as a whole. One explanation is that CS really is a field where educational signaling doesn't (or at least needn't) matter as much as in o…

Hey Ben! (Also) Ben here.

I work in New Jersey, as an Enterprise App Full-stack dev with 0 college experience.

I started as a developer 4 years ago @15/hr, and I recently breached the 6 figure mark. I've told my coworkers that I have a fire lit by a sense of inadequacy. I've always been behind classically trained developers, that is what keeps me pushing forward. Always playing 'catch-up'.

Now that I'm involved in my company's interview process, a few thoughts on what having a college degree does for our offers;

1. Because we hire through an agency, we already have a single layer of vetting that helps remove unqualified persons (both college-level and not), which ensure we have a decent, homogeneous pool to conduct face to face interviews with.

2. Whether we hire a candidate with or without a college background, our the offer range isn't enormous. If we have an offer in mind, (say 75k), having a college degree doesn't automatically grant you the high end of our scale. I can't think of a single instance where we cared about their degree once they were in the Face-to-face. Their performance in the interview dictates their offer, and we aren't asking questions like 'How do you implement bubble sort'. We ask some hard skill questions, sure, but we also ask just as many communication and general problem solving ones as well.

3. The range of starting pay is really small for us (think 75k mid, 70k min, 80k max). So that 3% gap makes a lot of sense.

To summarize, a degree may put you in a position to interview, but the range you get paid is largely depending on a wide array of skills, some of which are unrelated to development. Missing some of the hard-skills won't disqualify you for a position as much as missing the communication skills will (for us).

Re: Base salaries offered to software engineers in SF, NYC, and Seattle

#100
post #35

Earlier quoted context omitted.

Did you ever need to provide a resume/CV? If so were you honest about your education? Did you just omit it?

Not the above poster, but for me - I omit my degree from my resume, because in my mind it was so long ago as to be irrelevant. It's also a bit odd - I have a degree in "Letters, Arts, and Science" - a make-your-own major from Penn State. My last two jobs the recruiters asked me if I had a degree - this came up AFTER they had decided to interview me and when they were entering me in to the system - the degree was just…

Even better... My wife has a Master of Science, but not an undergraduate degree. That literally makes recruiters and hiring managers do double-takes.
Post reply on HN