Anyone else reading this: I wouldn’t want you to feel anything like this amount of prep is necessary.

Of course, I totally get this because I have worked with Software developers and I can judge them by a piece of good code they’ve written and their learning ability when I tell them about F# or a new language and how it works, it’s compiler structure rather than asking how many different languages and how many different algorithms they know of. But a lot of others who are reading this might just feel that the dude has over killed it and that too with such an intense prep routine and yet Google hasn’t still hired him so that only means that their dream of getting in Google is unachievable ultimately.

For those of you reading my comment, I would like you to know that it is not true, rather than focusing on many different subjects and concepts and many different languages, focus on a particular set of algorithms and data structures and their implementation in a language or two alongside all the basic concepts of EECS, that will do just fine. The rest is just a yes or no for Google to decide on. Also I think some good projects will look more appealing than anything else on your resume if you have done them well.