[ablatt89]

Why is the defensiveness "unpleasant" when you're the one calling engineers incompetent because they work for FAANG? I quote you:

> In fact, most Google engineers taken out of Google are fucking useless, because they've developed a body of knowledge built entirely on systems that do not exist on the outside, many of which were developed many years ago to make hard problems simpler. >

Who is making this unpleasant? You critique a body of engineers, using biased personal anecdotes and no hard metrics, and think I am the one being negative and unpleasant? Insane.

[dijit]

Ok, let's break it down because if you're working for FAANG (and this is why you're defensive) then I think you're making your own case here, by not understanding what people are saying.

1) I said that hiring has less to do about intelligence than compliance (which is what the parent was saying).

Do intelligent people work there? absolutely.

Does working for FAANG mean you are intelligent? No.

This is the distinction in which you seem to be confused. The interview process does not mean that everyone working in Google is smarter than anyone else, it just means (and in no uncertain terms) that you were willing to jump through hoops.

2) I stated that there are skills you learn inside google which are not relevant outside.

Google themselves know this, it's part of why their literature is littered with "in a google context" or "a problem exclusive to google's way of working".

For example: Piper, a centralised source code storage system is not available outside Google. Everyone uses Git, or, in the games industry they use Perforce (and you will quickly learn if you work in this context that the lush SCM tools that you're used to don't exist, there might be 1 person looking after perforce for an entire studio of 1,500 people -- if you are extremely lucky).

Blaze, the build tool which was open sourced as Bazel: Does not make sense to most engineering orgs and has very low penetration in the real world.

Monarch (and its query language) are exclusive to google.

Borg, has no corollary, Kubernetes is both completely different (borrowing a few ideas) and less mature at running most kinds of workloads. You would have to re-learn this.

The statement: "knowledge of these tools is not helpful outside" is absolutely correct.

Maybe there are some ideas that if you had 5 years to redesign you could build something. Similarly though, if you took a person from today and sent them 100 years into the past and they described a smart-phone.... well, you're no closer to actually having a smart phone.

I'm simply saying that most ex-Google employees will have to learn the tools used on the outside. In some cases they're going to be annoyed at not having certain conveniences.