4 ms·
I was of similar mindset until I worked with some. Not to say a 200k dev couldn’t do it, but especially at big tech or rapidly growing large scale startups, the
by celim307 5y ago
I was of similar mindset until I worked with some. Not to say a 200k dev couldn’t do it, but especially at big tech or rapidly growing large scale startups, the price difference is worth it from experience alone.
Not only are the technical challenges different at large scale, the product and human challenges are different. The 750 principle is basically leading a 500+ engineer org’s technical vision and steering the ship. Not only is it crazy difficult to get 500 people align on a vision, but the mechanics of organizing and leading that large number of people are unique too.
Plus product wise a 750k engineer can save the company multiples of that just by advocating on what not to do, and avoid expensive mistakes.
I’ve learned more in 2 years at big tech than I have in 7 in local companies or smaller startups.
- baron816 5y agoThis. A principle engineer probably wouldn’t be expected to write that much code in most cases. They’d be leading other senior/staff engineers. They’re spending a lot of time doing research, reviewing design docs, mentoring, and contributing their technical knowledge to high level planning meetings with directors and VPs. I’d also agree with others that something like a “10x engineer” does exist, it just doesn’t look like the legend might have you believe. They’re not fast typing antisocial weirdos. They just understand the technical and business problems more deeply and have the breadth and depth of knowledge to come up with really good solutions. So in that regard, the value of their output is at least 10x that of their more junior peers.
- riskneutral 5y ago> The 750 principle is basically leading a 500+ engineer org So not that different from senior management pay grades in other industries.