3 ms·
Google’s interview process puts immense emphasis on doing thorough system design. Additionally, in contrast with companies who do ask hacker rank questions, Go
by VirusNewbie 3y ago
Google’s interview process puts immense emphasis on doing thorough system design.
Additionally, in contrast with companies who do ask hacker rank questions, Google only asks novel, unique questions that are not on leetcode or hackkerrank, prizing creativity in problem solving over memorizing.
Finally, since everything is reviewed by a hiring committee, there’s almost no chance of nepotism or someone playing favorites for whatever reason.
When I interviewed at Microsoft, I was asked to implement numerous classic CS algorithms, not disguised even remotely. With google, none of the coding questions were anywhere to be found on the internet.
Big organizations tend to follow regression of the mean, but at FAANG i’ve yet to see see the absolute bottom of the barrel that
have often snuck in at the various small companies i’ve worked for.
Certainly small companies have top tier talent as well as google and other FAANGs, but there’s remarkably little bureaucracy at FAANGs as well. It sounds like you’ve developed your opinion from a vocal minority that have left in anger rather than first hand experience.
- marcus_holmes 3y agoSo the article that the article mentions [0] has the bureaucracy as a problem - risk minimisation is the main organisational criteria, so any change is overwhelmed with bureaucratic processes to ensure it doesn't cause risk (my paraphrase). Is this true in your experience? How much bureaucracy is "remarkable little"? [0] https://medium.com/@pravse/the-maze-is-in-the-mouse-980c57cfd61a https://medium.com/@pravse/the-maze-is-in-the-mouse-980c57cf...
- VirusNewbie 3y agoThe changes they are talking about are consumer visible changes to the large money makers. I'm in infrastructure so I don't have first hand knowledge of the former, but that tracks from what I've heard. Making large changes to search or ads sounds like a bureaucratic nightmare. However, making changes to infrastructure, to technical products, to workspaces, to cloud products, and to APIs seem to strike a nice balance between quality and velocity. You need code reviews, there are tests and static analysis and all that jazz but otherwise ship it. There are very few MBAs around to stall things or create unnecessary process.