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