The sample set of people using TripleByte is not going to be remotely representative of the market for developers as a whole. Candidates with stronger resumes are not going to be using third party recruiters to spray their resume around; they are going to be applying directly to the companies they want to work at or getting headhunted by the companies themselves.
- TripleByte imposes a cost (having to go through their process) in exchange for getting to signal programming ability, a prerequisite to getting in the door (getting an interview)
- People with strong credentials don't need to incur that cost, so they probably won't do so.
This means TripleByte's pool probably doesn't have any Stanford CS grads who are looking to leave their Google job. But these are also the people who command the highest salaries. Let's say it chops off the top x-percentile of the market, for some reasonable definition of x (10? 15?)
Then, TripleByte's screening process probably also chops off the bottom y-percentile, because those are people who can't actually pass the screening.
Once you restrict the range like that, and also make paper credentials less relevant because there's an alternate signal available, of course the rates are going to be compressed.
I wouldn't say Triplebyte imposes a significant cost on the candidate. They only have two rounds: one is a quiz that's quite straightforward to complete (about a half hour of multiple choice, if I recall correctly), and a single 1-2 hour video interview. If nothing else, it's good practice for the candidate.
Plus, they dangle some brand names as partners that would attract any candidate, including the cream of the crop. Stripe, Palantir, etc. So top tier candidates are certainly likely to be convinced to give Triplebyte's process a shot.
I'm not sure how often candidates get matched with those top tier companies on Triplebyte -- I didn't get matched in my recent job search, and ended up applying and receiving offers from several of them independently of Triplebyte -- but it's certainly plausible that Triplebyte has many top candidates at least giving the platform a try.
Regardless of which candidates are using Triplebyte, the only relevant data is which candidates are _getting offers via Triplebyte_. In my experience, I received several offers, only one of them via Triplebyte (I only accepted one onsite there) - Triplebyte has no insight into my other offers.
That one offer via Triplebyte was significantly lower - at least on base - than all of the other offers I received. It would've put me in the 50ish percentile on this post's plots. The other offers put me in ~60-97 percentile. Very anecdotal, but I wouldn't be surprised if the majority of companies giving offers via Triplebyte are generally paying less than top companies who are less likely to use Triplebyte despite having a presence on the platform.
“How much software engineers on Triplebyte received in base salary offers in SF, NYC, and Seattle”
Yes, I know HTML titles cannot do any emphasis.
EDIT: HN title has now been improved by dang.
To be more accurate about “SEO/targeting”, I meant the title on the blog hosted by Triplebyte: “How much money do Software Engineers actually make?”
Edit: I took a shot. "Triplebyte" doesn't fit, but probably shouldn't be in there anyway; it's already next to the title.
You have 15 more chars to work with.
Why are those mutually exclusive? I like to think I have a decent resume and would apply to companies directly but if I can get more offers using Triplebyte why wouldnt I? Isn't their draw that you don't have to interview at individual companies but can use a streamlined application?
If you’re sincerely highly talented, you’re not going to advertise yourself as a commodity on a platform. Your increased skill may not have a chance to be displayed because the platform uses foolish things like coding trivia or a black box proprietary method for recommending salary ranges for candidates like you, or offers automatic ways to find similar candidates so that if employers don’t like your salary demands, they can use your characteristics to tailor a search for a cheaper version of you.
Putting yourself on a platform like TripleByte essentially instantly signals that you’re on the cheap, commodity end of the spectrum (and yes employers think of $130k as cheap salary for this type of position).
Using TripleByte is like cheapening your personal brand. In fact it’s even worse because you’re voluntarily doing it and voluntarily centralizing all of this interview performance data and profile data for them.
I'm confused about why you think this is irrational. If I find some startup through Triplebyte, and then apply to them, it doesn't seem like a substantially different process than if I applied directly. Once I'm talking to someone at the company, any signal based on how the recruiter found me seems like it should immediately be swamped by concrete observations about me.
If you know a better strategy for next time to find the kind of companies that Triplebyte will connect me with, I'm all ears.
If you’re OK with that, then by all means use that commodity portal to seek jobs. I mean that sincerely. If you prefer to trade possibly tens of thousands of dollars of salary, bonuses, equity or other compensation for some vague ease of access “value-add” of a platform that makes your resume function like Tinder for jobs, then you would not be irrational to search via TripleByte.
For me, for example, the fact that those positions can be matched up to me on TripleByte would literally make me reject those jobs. No thanks. I’ll either pay for a private recruiter that essentially functions like a personal talent agent, or I’ll find networking events or other boutique application portals to use that keep me exclusively looking at jobs that pay competitive rates. Hell, I’d sooner just send cold application emails through regular company HR websites than agree to be the commodity product of TripleByte.
That seems shortsighted.
If I was running a startup again and looking to grow my team after exhausting my personal network, triplebyte would be a good value proposition: reduce the time it takes me to hire by pre screening candidates and presenting me with a curated set of people to interview.
So it follows that if I wanted to join a startup I’d consider triplebyte for the same reason —- I can see busy ceos of small companies using it.
You seem to be focused on compensation not finding interesting offers though. To that I’d say two things:
1) If you want to purely optimize for compensation, work at FAANG. I don’t think they source via triplebyte so the point is moot.
2) In my experience, offer size is not related to where the candidate was sourced.
How does this follow? Obviously the buyer (busy CEOs of start-ups looking to pay below market) wants a commodity platform to buy.
That does not mean the seller (job candidates) wants to sell on that platform, especially if the platform cheapens their product (such as reducing developers to a commodity interview process that fails to capture their value additive skills).
I don’t see how customers of TripleByte are looking to pay less any more than any other ceo that’s trying to maximize profits while minimizing costs.
If Indeed is like Wal-Mart, TripleByte is like Sam’s Club. A different branding of a cheap, commodity store.
If you’re truly willing to pay a high price for something, you don’t even walk in the door at Sam’s Club. You research a boutique seller that’s harder to find.
Start-up pay is so universally bad compared even to low or mid tier public companies. I’m not sure it could be possible to use start-ups as any kind of counter argument to a question of low pay.
Are you saying it's impossible to negotiate a fair compensation package with an employer you found through TripleByte? You don't seem to be telling us why we should believe that.
After comparing to a much smaller set of broad-market resumes, it was clear that you’re right: people using online job finding tools are actually shut out, for some reason, from conventional job channels where the intuitive rules apply.
But yes, obviously there’s something wrong with the data if the salary gap observed was so small. I generally like TripleByte and its writing, but it seems like they really got something 200% wrong here.
We are a small team of 5 expecting to double in 2019, all from experienced folks extracted from big companies. We budgeted $260 each and our investors didn't bat an eye.
Let's take a $150k base salary as a specific example, as a nice round-ish number. The numbers from Triplebyte don't include bonuses and equity; I suspect that 20% combined is a reasonable assumption. That puts us at 180k.
Now we have employer costs that the employee never sees (this all assumes the US):
* Social security: $8.2k (6.2% of $132,900 in 2019). * Medicare: $2.6k (1.45% of 180000) * State payroll taxes (for things like unemployment insurance): ~$1.5k in California, say, mostly for State Disability Insurance bits.
We're up to $193k.
Health insurance for employees, if you provide it, is probably $10k-$30k depending on the health plan and whether the employees have families. So $203k-$223k. Equipment is a few thousand per year. Office space (if local) or possibly travel (if remote, though maybe you could try to do everything async or over videoconference), really depends on the geography.
At that size, I don't know whether you have 401(k) matching or safe harbor contributions, but if you do that's presumably another $5k-$15k depending on how generous the match is.
So a base salary of $150k means a budget of at least $205k and more likely closer to $230k or $240k.
We expect most of the hires to have tuition payments to make...not that we will pay younger hires less. But we have specific people with specific experience in mind. These folks are getting that kind of money at FAAxG today.
This is an interest statement.
It is interesting, because the data I am seeing is that apparently Triple Byte is able to give people quite successful results. (Yes, 150k base salary is pretty good).
But your statement seems to imply that candidates that use them are apparently below average or something. And yet even though they arent as good candidates, they are apparently able to give people really good results, despite that.
Is my barometer for tech salaries so off, that apparently people believe that 150k base isn't something that a "stronger" candidate might receive? Yes, I've heard of some high salaries, but I still wouldn't call this something to scoff at
(I tried Triplebyte's process this job hunt but ended up getting my current job through a personal connection instead)
Maybe if you work at google. But you have an extremely skewed view of job salaries, if you describe 150k as "terrible".
Yes, FAANGs pay a lot. But the vast majority of developers, even in san francisco, do not work at FAANGs. 150k, is just around the average salary, for a senior engineer, actually.
Non faang pay for principal engineers in Mountain View could be estimated roughly by using stack overflow’s salary calculator. Mountain View, react, typescript, aws, postgres, linux, 20 years experience, no degree lists $187,000 for the 50th percentile.
I think the discussion gets confusing because as an industry we suck at describing levels of the technical track in a portable way.
I do know senior engineers making 150k in the Bay Area. I also know some making 750k.
But in the context of this conversation, IE people who use triple byte, we are likely talking about engineers with a couple years experience. (Yes, a couple years experience gets you the title of "senior" these days).
And within this context of engineers with a couple years experience who are using triple byte, I'd say that 150k is pretty alright.
You can see this data from the graphs that they posted, about how this is referring to people with a couple years exp.
I'm a high school drop out with no diploma. It's never come up during any hiring process in the 17 years I've been doing this.
That said, I've only had two long term jobs. I spent years doing contract work, and I mostly got contracts by word of mouth.
I've been on a number of hiring teams, mostly at Puppet. I was also a hiring manager at Puppet for a while. Education never came up once — I don't remember even talking about it in interview training.
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 a field to fill in.
I can't say what impact having a degree has had on my salary, and I can't say how hard it would be to get those first couple of years of work experience without a degree (it didn't matter for my first job, but that was 19 years ago), but in terms of applying for jobs once you have experience, I've not seen it matter outside of a few jobs that inexplicably require "a" degree (of any kind).
Several of my friends in the field don't have a college degree, and they appear to be functioning well, but they are also painfully aware of the lack, which tells me it's a source of some stress, be that actual or just hypothetical.
Oxford M.Sc. Computer Science https://www.ox.ac.uk/admissions/graduate/courses/msc-softwar...
SOAS Finance https://www.ox.ac.uk/admissions/graduate/courses/msc-softwar...
London School of Tropical Medicine, Clinical Trials https://london.ac.uk/courses/clinical-trials#entry-requireme...
Queen Mary University of London, MBA https://london.ac.uk/courses/global-mba
It took her a while to find the program. Most wanted an BA/BS first.
MS is the exception to that rule.
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).
Total Comp figures are important, and differences in effective take home pay will be hidden if you only list salaries.
and yes, it is underwhelming that we still don't know "how much software engineers actually make"
Thanks for letting me know the data is present. :)
The only thing I feel like I missed out on compared to a CS grad is a better intuition for big O. I just don't have any use for it in real life, so it never really clicked. Good benchmarking tools are all I've ever needed. But it would be nice for my own intellectual gratification.
I have found the biggest discriminator on hiring salary and hiring generally is due to approach to problem. If you are limited to a single convention, such as OOP, or are limited to certain tools/frameworks businesses are less eager to hire you. In theory that makes sense in that you are more valuable if you can provide an original direct solution to a problem with greater ease. In practice it doesn’t make sense because those limitations tat prove to be a negative bias during hiring tend to be the reality internally.
Care to share the city? Or region?
I've also seen people graduate who couldn't do anything, so a CS degree is not proof that someone can do the job, and not having it is not proof that someone can't. I think university education is still extremely valuable, and I'm glad I've had it, but more for what I learned than for the piece of paper.
That said, salaries in Amsterdam, with or without degree, are far lower than the $130k to $150k described here.
I wouldn't expect Triplebyte to be able to observe this, because it only works with candidates who are US citizens, permanent residents, residents of Canada, Mexico, Singapore, Chile, Australia, or, have an existing H-1B visa (per the Candidate FAQ: https://triplebyte.com/candidate_faq).
Are these base salaries or total compensation?
Can you share what the distribution of companies you source to is? Ie are they mostly early stage startups or do they include many large post ipo tech companies?
Triplebyte works with over 400 companies, including Apple, Dropbox, Instacart, and numerous early stage companies (including many YC companies). The Open Positions section on the salary tool page should give a pretty good feel for the kinds of specific roles and companies that work with us
Since total compensation tends to vary more significantly than base salary, I would continue showing the salary-only graph by default, with an option to toggle total compensation as a second series.
It's definitely not unheard of for bonuses of top engineers to reach multiples of their base salary. I'm not aware of compensation being that lopsided where I work, but it purportedly happens at places like Two Sigma.
I think I may have found a tiny bug: the “all Triplebyte” dropdown seems to always reset the previous dropdown to “all company sizes” and visa versa so it’s impossible to have both selected to something other than the first options. Perhaps this is because data doesn’t exist for both? Maybe it’s just a slightly confusing UX.
It’s such a thoughtfully considered tool that I thought you’d appreciate my considered feedback.
Thanks!
Why are you mistakenly confusing education for education signalling?
There are many types of skills required to be an effective software engineer. Most of them have nothing to do with mastery of a programming language or technical tool, and have zero connection to solving coding puzzles in a short timeframe or memorizing answers to classic systems design questions.
You need to be a skilled writer and researcher to deduce business use cases and write effective summaries, presentations or user documentation.
You need appreciation for potentially many other knowledge domains, from legal topics & security to applied sciences. Having basic coursework in calculus, chemistry, physics, rhetoric, history & civics, etc., are crucially important in business settings.
It seems so tone deaf to me to baldly state that education signalling is a factor here, as if signalling was the phenomenon (it’s not).
Education (as opposed to education signalling) is a very valuable thing, and certainly fosters more effective engineers by a landslide.
The popularity of hiring from bootcamps or non-traditional engineering backgrounds is a commoditization issue, meant to suppress wages from growing as labor productivity creates dramatically greater returns.
There’s no shortage of engineers... there’s a shortage of “cheap” engineers (and yes, $130k is a cheap price for these types of hires).
My open source/side project experience has opened doors though I'm sure.
If you take their numbers that works out to $350-$400k.
A director at Google wouldn't be making much more than $200k in base salary, but their total comp can easily exceed $1M if you count stocks.
Yes. Most boot camps are outright scams and I know that I (along with everyone I know) has never hired a bootcamp grad. They usually cannot write fizzbuzz.
Some anecdata on the college grad note: most of the best engineers I've worked with did not study CS in college, though they all did graduate from college.
I'm a little suspicious because the median and mean are equal for several of the larger subsets (years of experience). I clicked several combinations to filter by and the difference between the median and mean was always low-mid single digits.
Would you mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the spirit of this site more to heart? It would be great if you'd contribute just out of curiosity and avoid poisoning the well. Maybe you don't owe better to companies that annoy you, but you owe better to the community here.
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 other industries - we recently discussed this with Bryan Caplan over on our blog (https://triplebyte.com/blog/bryan-caplan-interview). I'm self-taught and don't have a CS degree, but I do have a college degree which still opens doors. I'd be curious to hear from other developers without a formal background on this.
Boot-camp grads average $19k less - but $130k is still quite a bit higher than I've seen bootcamps advertising. Could this be indicating that they're at a disadvantage in the normal hiring process just for signaling reasons?