Google Interview University – Plan for studying to become a Google engineer
Google&#x27;s sort of &quot;computer science trivia&quot; style interview is the bane of software engineering.<p>&quot;CS trivia&quot; interviews select for people who know the mathematics of computer science, not for people who know how to ship robust software systems on time and within budget. The two are only loosely related and mostly uncorrelated.<p>In the real world, you use a well-tested premade off the shelf library to traverse a DAG or implement a red&#x2F;black tree. Just because someone can recite algorithms and data structures in their sleep doesn&#x27;t mean they can effectively scope, plan, or execute a complex software dev project; and conversely many of the best engineers either never learned or long ago forgot the details of the CS.<p>This mode of interviewing is like interviewing the contractor you&#x27;re considering to remodel your bathroom by handing them a pile of iron ore and asking them to smelt high grade structural steel out of it.<p>So why do they do this? Lack of any better option. Their previous &quot;brainteaser&quot; style interview didn&#x27;t work at all, and this is probably marginally better than that at finding good engineers. But more importantly, it&#x27;s much cheaper and faster and less risky in terms of confidentiality than hiring candidates as temporary contractors for a real world test doing actual work, which is the only remotely effective way to tell who is actually a good engineer.