| HN Mirror

> (Just to dispel the impression that you can join Google/FAANG by acing the interview, and then coast along. Fake work with zero impact is very obvious.)

Too bad all of those totally don't matter. What you're saying here comes down to doing what management wants. And management, above all else, DOES NOT WANT THE STATUS-QUO UPSET. The chairs in management are to be divided according to endless politicking and 5000 meetings for every line in the org chart, the only thing that matters. If any effort is actually successful beyond what was agreed beforehand ... that would undo the "work" of thousands, maybe tens of thousands of management meetings.

In other work drafting design documents, doing interviews, improving existing codebases, mentoring junior ICs (to do the same) ... it's not a design document to create a new successful product on the internet. It's a design document discussing whether component #1823871 of Google maps should be monitored by a Python, C++, Java or Go program, and whether it this monitoring server gets configured using json, yml, chubby, files with strings, protobuf, python (configuration in code, python to configure flags, python to configure startup files, python to change build files, or python read by the program upon startup), Go, Java or Go. Don't forget: 8 page minimum, and you can't have less than 40 reviewers.

This document is then followed by a manager from outside your org deciding that the whole monitoring is being shipped to India, and 3 months later you check on borg ... and surprise! There ISN'T anything monitoring it, as far as you can tell. Your manager assures you your work was not for nothing, but your design document curiously has never been accessed, and everybody you ask (btw: you're quickly told you're not supposed to do that) says management forbade them from looking at your design document.

Later you learn that there isn't a single team in India that actually has access to your document (if you're working long enough at Google and actually know how to check that, which used to be 99%, but now ... perhaps 20%).

A year later, the product takes down all of Google maps, your team's lack of monitoring gets blamed for the outage ... but 10 minutes after you go to your manager with this the postmortem, suddenly, gives you "access denied". Then, you get scheduled for a support checkin where the person doing the support checkin has no idea what it's about.

Of course, what it's really about is that your forced one of the managers in your org to explain to higher ups how your concern is being addressed while still meeting budget constraints ... Which could have upset the status quo (recognizable by "Moderate impact" on your GRAD review) or actually upset the status quo ("Not Enough Impact" on your review). Congratulations!