This is clearly both necessary if they want to retain their "all our people are among the best (and therefore have lots of options if they want to leave)" workforce and harmful to their projects. There's plain flakiness to their approach to things that's at this point a distinguishing characteristic of Google products. Even things that stick around long-term and don't get cancelled outright show heavy signs of no-one wanting to do the boring work, and no-one making them do it. Or of half-assing the boring work and then never fixing it.
I've seen many great projects sink over time because management over-indexes on easily understood, time consuming efforts, with only marginal customer impact. These efforts are easy to justify quarter on quarter - but are incredibly generic.
Great big products tend to emerge from driving repeatable improvements in something everyone needs e.g. search, content, recommendations, servers, networks, data etc. and solving the hard problems that no one else has the dedication to solve.
It is incredibly ancient. It's possible to use Babel w/ it though, and write reasonably modern JS. There's a CLI tool out there to upload something into an Apps Script … app? too; at one point, I had a project w/ a Makefile that would run the project through Babel and then upload it to Google.
I didn't try all the features (and I didn't have any npm/package management), but things like format strings, for(… of …) loops, let/const, new Map() all worked. Babel is a wonderful, wonderful thing.
I built my babel config to balance clean, new syntax with the least intrusive transforms possible. e.g. I have loose template literals on, since `\`hello ${world}!\`` is an easy transform (and still readable in the final source) as `'hello ' + world + '!'`. Generators, for .. of, and object rest/spread, are okay, but babel puts a ridiculous amount of helper functions at the top to support this. I suppose I could always configure each project with a shim file, but that's extra overhead I really could do without.
block-scoping, arrow-functions, function-name, shorthand-properties, spread (for arrays and arguments), template-literals (loose, so `+` not `String#concat`), and exponentiation-operator I found give the most bang for your buck. `for .. of` is nice but if I can pass arrow functions into my `forEach` callbacks that's pretty clean too. Pretty great being able to say
``` rows.forEach(row => { const payload = row.map(([name, rank, serialNo]) => ({ name, rank, serialNo })); SomeApi.doThing({ onComplete() { foo(); }, payload, }); }); ```
in gapps. That said, it took a while to even figure out how much was possible, but yeah it's a big step up.
So, it may be easy to move, but only in certain directions where management wants people to move.
(Or see if you can make a case for increased headcount somehow. Being good at persuasion or having a manager who trusts you can work.)
I've heard that you'll get raises for working on new things. That's why Google launches so many new projects (and closes so many of those projects) and that's why old projects are constantly rewritten/redesigned instead of just imprpoving and bugfixing. I don't like it as a user, I want to use the same interface for 50 years and I want all bugs to be removed, rather than learning new interface and new bugs every few years.
I think that the OP's referring to a phenomena at different big companies where certain divisions get paid more because management deems that division more important. That creates a dynamic where everybody tries to get into that division, and the ones that can't end up bitter, demoralized, and resentful (and hence unproductive). Connecting pay to tangible accomplishments rather than where you are in the company avoids that dynamic, though it does create the one you've observed where everyone is hunting for tangible accomplishments.
I spent 5 years at Google hoping the intrapreneurship thing would work. AFAICT it doesn't, and eventually I came to accept Paul Graham's conclusion that big companies are constitutionally incapable of innovating and that's why he makes lots of money funding startups. In my observations the biggest problem isn't even compensation: it's that there are too many roadblocks to launching things and trying things out in a big company, too much incentive to be risk-averse, and too little feedback from the market itself with too much feedback from irrelevant decision-makers within the organization. The flip side of fixing those is that it radically increases both the failure rate and the rate at which the company pisses off outside people, both of which would be fatal at Google's scale.
IMHO the way Google does compensation is the best I've seen, it's just that "the best" will still result in good companies getting crushed by upstarts. So just accept that and try to create a good working environment while the company continues to print cash.
It is true that people are rewarded for impact, which usually means new systems. But this does not necessarily mean new products from an external perspective. I know a lot of people who have been promoted really high based on stuff that they have led that has zero visibility to external users but ends up being worth oodles of money (or whatever metric you are trying to impact).
Zillions of product launches seems to arise from a combination of a largely bottom-up company with a ton of employees and a culture of building things themselves rather than using existing solutions.
I’d phrase this a little differently: the people there can be relied upon to at least have some “baseline” technical ability. Having worked at both FAANG and more mediocre companies, one thing that stands out is that while not everyone at FAANG are super-wizards, you’ll never have to sit there and explain things like “what is a stack trace” and “what happens when you write past the end of an array” and “what is the difference between O(n log n) and O(log n)”. You’ll never have to argue whether using source control is a good idea. You’ll never have people who spend weeks just trying to get Hello Project” to compile. All of which I’ve seen in other companies.
The big guys hiring processes might not be great but unlike most companies they seem to be able to filter out the complete know-nothings, and that alone is probably what raises the average.
TLDR: it’s not that they hire smarter people—they just avoid hiring way-below-average people.
Ed.: also appear to be very often very insecure about it.
I'd love to read the back story on this. Was it really a "hello world" project?
I've learned that once you're in a large and complex corporate structure, judging your value becomes difficult. In every job I've been I've found professional slackers who truly optimize to do the minimum. They can send all the right value signals while they keep their true lack of value hidden behind a complex maze.
The only way I can think of to minimize them is to set up high barriers of entry that require on the spot proof of ability: coding tests and programming problems. Everything else can be and has been bulshitted through.
I've read and heard many accounts of college admission officers and hiring managers who say that among the top 30%, it is essentially random. They don't know how or even need to differentiate between the 30%, 20%, and 10%.
So what it comes down to is selecting a random differentiator that can stand up against nepotism (objective and measurable), legal scrutiny (fair), audits (easy to comply with) and so on.
Essentially everyone who answers those questions reasonably well passes. But the one who answered best gets hired because at that point we don't even have a good differentiating signal.
Many companies hire people before they decide their position. So your job tasks might wildly different.
Spill. The. Tea.
Spill. The. Tea.
Spill. The. Tea.
To what extends does this work? Let's say I want to work on Chrome's WebGL implementation, but I've no prior professional experience with neither C++ nor 3D graphics - would they still take me as a noob that will take a couple years to ramp up? I suspect not. So, you're probably most likely just stuck with your current niche and can only move within it - which, to be fair, is still much better than in most other companies where you're just stuck with your current project.
I’ll bite. Which other companies are like this would you claim?
In which way is Google innovative? They have good products for sure, but I haven't seen much innovation at Google since a while. If anything the past few years have been mostly disappointing (Loon, Calico, Fiber, etc)
https://www.bcg.com/en-ch/publications/2019/most-innovative-...
I would argue that the best innovations tend to also be "soul-consuming". If it were easy, someone else would have innovated in that area earlier, right?
Point being, crappy work is hard to staff, and some work is just always going to be crappy. Nobody wants to maintain a hideous collection of accumulated bad decisions workarounds that exist for historical reasons but which have no value other than allowing lazy customers to avoid upgrading their 1970s client code. At IBM we maintained it anyway and hated it. At Google that sort of thing can't keep a team together.
There is, in my experience, plenty of appetite for hard, risky, complex, grinding, ambitious problems, and very little tolerance for boring, unimpactful or evil projects, since everyone at Google can already feed themselves and is more towards the self actualization end of the hierarchy of needs, and has no strong incentive to not roll off onto something more interesting or fulfilling.
1: The people are smarter. It's sort of cheating I suppose; better inputs make better outputs. Google doesn't have all the smartest people, but it's one of the few companies that get top-tier talent in a way that is meaningful. Everything else hinges on this.
2: Your manager (and their manager) cares a lot about you. That's a pretty broad statement and definitely not universal, but it's more often true than not. Managers are explicitly trained to focus on the needs of their employees, and the ones who don't are largely viewed as failures. No other success compensates for poor treatment of your reports. Again, there are plenty of bad managers, but they're widely seen as bad managers; justification like "demanding but fair" or "knows how to get results" or "evil genius" have little effect.
3: It's easy to move. There is no pay difference no matter what project you work on and internal mobility is encouraged and supported. People do what they want to do, and they tend to be extremely motivated as a result. It also helps remove bad managers: sinking ships get abandoned really, really fast. This is arguably the company's greatest weakness as well as it's hard to get people to work on something soul-consuming. But it's great for the employees and it's great for innovation.