alt Hacker NewsAs someone who has worked at big tech (and interviewed fellow big tech workers), I can confirm this is pretty typical.
People from Google, Meta, Microsoft, Apple, etc...it's all the same. Given the size of these organizations (anywhere from 100K-300K employees if you include contractors), there's a vanishingly small chance the individual you're interviewing had influence or responsibility over any important thing specifically. And if they were high enough on the org chart to be responsible for something real, they weren't ever hands on and just played politics all day in meetings.
Everyone will claim otherwise of course, but its all layers and layers of diffusion of responsibility.
The pace of work inside these orgs is, meet for months about a narrowly scoped new feature (eg. "add a 5th confusing toolbar to Gmail to market Google's 7th video call tool"), take months to build it and run it up the organizational gauntlet for approval, launch it and then chill for 3 months because nobody does anything big in Q4.
For many people at these orgs this is what an entire year of "work" can look like, for which they will be paid roughly $400k.
Replies
> People from Google, Meta, Microsoft, Apple, etc...it's all the same.
Hmm...it's been a while, but when I was at Apple one of the reasons given internally for why products were so much better than the competition (and they were) was that Apple typically had 1/10th the number of people working on a particular product or feature.
I wonder if that's still the case.
I've also worked (and currently work) at a big tech company and personally this has not been my experience. I'm sure it happens but it's not typical.
Who is more impactful, the startup engineer who singlehandedly ships a feature that increases a startup revenue by 25% off a base $5M/yr ($1M extra rev), or a Meta/Google team of 5 engineers who ship a .01% revenue improve off a base of 150B/yr (15M/5 = $3M/engineer).
As an engineer you are thinking about impact as 'scope' or 'features'. Leadership will be thinking marginally on what adding a net new engineer will provide to the business.
“Marginalism is the economic doctrine that we can best understand value by considering the question of how many units of a good or service an individual has, and using that starting point to ask how much an additional – or marginal – unit would be worth in terms of other goods and services.”
Given how inefficient Meta et al are, why do the pay so much more than the nimbler smaller companies? (Rhetorical question, I already know the answer: monopoly and regulatory capture)
Of course those engineers would rather have more meaningful work if it came with similar compensation and work life balance.
Yeah. This is part of why I wasn't excited to work at G after my first time there. It was very boring
You’re painting with a pretty broad brush there.
“…for which they were paid roughly $400k.”
If I had to guess, the main reason you don’t hire big tech employees is because you can’t afford to. Everything else is extremely subjective depending on what area said engineer worked.
While at G I was one of three engineers working on a mid-sized iOS app. We shared ownership of the entirety of the codebase. It wasn't dissimilar to some of the other teams I've worked on at orgs of differing sizes.
> The pace of work inside these orgs is, meet for months about a narrowly scoped new feature, take months to build it and run it up the organizational ladder for approval, launch it and then chill for 3 months because nobody does anything big in Q4.
This sounds wonderful, it certainly wasn't the case for us.