17 ms·
Google Interview University – Plan for studying to become a Google engineer
- guru110 10y agoLooks great even for just refreshing the basics again. Great work. Thanks.
- astrange 10y agoIf you like, I can forward you my emails from their recruiters too. They're starting to get a little passive-aggressive since I never reply to them.
- toast0 10y agoThey stopped emailing me when I told them they were mailing the wrong person with my name. It helped that they were actually trying to reach someone else, they referenced "my" experience at a company I've never worked for, and I found a blog post for that company by another person with my name.
- UweSchmidt 10y agoGreat ressource! Thanks for making this public. "If you like this project, please give me a star. " So it's "like, comment, subscribe", and now "give me a star"? It's the first time I've seen this and I hope this doesn't catch on. The current system of aggregation/curation/voting works fine imo.
- wodenokoto 10y agoA github like is a star. Or is there something I've misunderstood?
- mixedCase 10y agoThe system is not the problem. It's the solicitation.
- andrewSC 10y agoI agree, if you agree with me can you upvote my comment? Thanks.
- solutionyogi 10y agoI don't get it. Why is the solicitation a problem? It's a different thing if he says that you must STAR before you can access the repo.
- whorleater 10y agoI think it's a merit thing. If your content is truly worthwhile, is there a need to solicit/ask for stars? Researchers don't beg people to "like/comment/subscribe/star/tweet/etc" in their abstract, it feels odd to ask for a star in this manner.
- wodenokoto 10y agoThe way I understood parent was that liking, commenting and subscribing was okay to ask for, but asking for stars was too much. Re-reading it now, I'm actually not so sure what parent was complaining about.
- earlyriser 10y agoIt's not the same for me. Stars have a long history of been used as "Favorites", so it's more than a simple "like" in FB terms.
- sotojuan 10y agoA lot of people will get turned off by the idea of having to or wanting to study so much just for a job at a company. The way I see it though, this is a great list of resources to learn about a lot of programming-related things.
- samfisher83 10y agoGoogle pays pretty well. You have to spend so much time in school getting a degree and if you spend some extra time getting this job well as incremental cost it isn't too bad.
- martiuk 10y agoWhile joining Google is probably the last thing I want to do, this is a perfect resource for someone who hasn't had a formal education in computer science.
- guessmyname 10y agoIndeed, I have no degree but have been working for +7 years in the field. Recently I decided to start searching for new challenges but thanks to ATS [1] my resume has been rejected 90% of the time, the other 10% has been invested in interviews in fairly popular companies including Amazon and Booking.com. After having studied CtCI [2] and practiced on LeetCode [3] for two weeks (yes, just two weeks) I was able to pass most of the technical interviews, so I can testify that using this repository as a way to improve your skills actually works. PS: Just to clarify, I haven't been hired by any of the "Big 4" yet, but that is because — again — I have been studying for only two weeks, if I invest more time on this, maybe in 5-6 months I can guarantee an offer in one of those popular companies that appear featured on HN all the time. And as the parent comment says, even if you have no intention to work for Google or any other of the big corporations, this still is a good list of resources to improve your skillset. [1] https://en.wikipedia.org/wiki/Applicant_tracking_system https://en.wikipedia.org/wiki/Applicant_tracking_system [2] https://www.amazon.com/a/dp/0984782850 https://www.amazon.com/a/dp/0984782850 [3] https://leetcode.com/ https://leetcode.com/
- allenleein 10y agoAgree. IMO, if you master all the resources above then you probably can get into any software company you like to go. Google should not be the only option.
- exabrial 10y agoI once really wanted to work for Google, but after my in person interviews I realized I would never fit in. I was instantly judged for my soft Midwestern accent and dress shirts, while the guy in skinny jeans and explained to me that Java's HashMap.get() was not 0(1) and asked if I was taught that in my non-Stanford education. (It is btw, feel free to analyze the implementation) For a place that claims to be culturally diverse, I realized there was a hidden list of acceptable cultures, and mine was not one of them. I politely declined the offer and decided to stay a bit closer to home.
- whack 10y agoI live in NYC and most of the Googlers I meet are from the Midwest or East Coast. It sounds to me like you happened to end up with an idiotic interviewer. I would personally chalk that up to bad luck more so than company culture.
- ianlevesque 10y agoYeah, I'm not a Googler but the only one I know had no formal CS education and wore a full suit to his interview. Just study algorithms like mad and go for it if it's what you want. Technical merit will get you in.
- justinhj 10y agoWhen a company selects someone to interview a candidate they're also choosing that person to represent and sell the company. If that person turns out to be rude and condescending then I chalk that up to more than bad luck.
- walshemj 10y agoDoesn't Google train its interviewers I worked for a large company and before you could interview anyone there was a 2/3day course you had to pass.
- kmicklas 10y agoIn my experience Google NYC attracts a lot of people who are very cynical about the stereotypical bay area tech culture. I get the impression there is a lot less cool-aid being drunk here but then again I've never lived in the bay so I can't really compare.
- OJFord 10y agoThis seems like a great set of resources, but getting as keen as [0,1] just seems like the author setting himself up for disappointment. [0]: https://github.com/jwasham/google-interview-university#get-in-a-googley-mood https://github.com/jwasham/google-interview-university#get-i... [1]: https://github.com/jwasham/google-interview-university#follow-me https://github.com/jwasham/google-interview-university#follo...
- bbctol 10y agoYeah, I had thought this was just a fun way to organize a set of CS learning materials, but this guy seems to both 1) be very certain this will work, which is no guarantee even if the learning program is perfect, as there's obviously more that goes into hiring decisions, and 2) be really quite focused on Google specifically, which may not make sense.
- adrianm 10y agoI also feel bad that he has seemingly tied up so much of himself into this. Although the technical interviews at Google kind of require this prep, at the end of the day interpersonal skills and other factors contribute to the final decision as well. It's possible someone interviewing him will find this distasteful. It's also possible someone might just not like him. It's impossible to know exactly what will happen, I just hope he's somewhat psychologically prepared to not be offered a job.
- lkmslkmdfsd 10y agoSaddest title I have read in a while. I don't think being a disposable screw in a corporation X is anything great.
- falcolas 10y agoThis is a bit meta, but it bothers me sometimes how much virtual ink is spilled on how to pass algorithmic interviews. Especially considering how little of your career will actually depend on the knowledge being presented. I'm slowly learning that despite how much more money I've earned by skipping between companies, skipping is not a path to knowledge. It provides better earning opportunities (to a point), it provides new challenges on a regular basis, but I've lost the ability to go deep into a topic. The depth that can't be achieved in two or three years. I guess I'd really like to see a bit more ink spilled on "congratulations, you got a job; now what?" What interpersonal skills are most important? What are good resources for continued learning? What do C level people actually do? How can I help the company succeed? What career opportunities are possible for me without having to skip jobs? What can I learn from this company before I go to create my own? That would be much more valuable, IMO, than a primer on how to pass an interview process.
- gravypod 10y agoI think the only way to really prepare for working in industry is to actually work in industry. Being able to parrot the crap you where taught in college is only useful for interviews, which is a sad reflection of what interviews actually test for. You are completely right about what you said but I'd like to add one thing is the most important for any software engineering roll at any company: your ability to learn as you continue practicing in our field. That should be the highest priority. How do I familiarize myself with all my tools and resources not so I can do my job really well but so I can move to any task and execute it well? That should be the focus of any practicing software engineer. To be able to learn and adapt as requirements and goals change.
- t4nkd 10y agoI have done maybe 20 or so interviews in the last 2 years and this is the #1 thing I look for. However, I have still hired people who do not display a talent for continuous rapid learning, that is to say, they will only learn on company time and they take a long time (reasonably) to learn anything new. The flip side is that these people "work with what they know" and you can rely on them for a steady work pace and consistent quality. Much like so many development tools, people come in lots of shapes and sizes that benefit your organization differently.
- fgblanch 10y agoMore than a Google interview university this is the curriculum for an online degree in computer science. Thanks for sharing.
- ipsin 10y agoI used the same approach last time I was interviewing -- keeping a wiki of "everything I knew or sort-of-knew about computer science" and then trying to fill in the gaps. At a glance, a few things I would throw in are: * UTF-8 (a basic understanding of how wide characters are encoded) * streaming algorithms * lock-free data structures (what they are and why you probably shouldn't implement one) In some sense it's like trying to hold the entirety of CS in your head for one day. You might spend 30 minutes learning about something so you can mention it as an aside. But... I think it's worth it, more for the knowledge. Knowing that something is possible (e.g. encrypted search) opens doors in the same way that working cross-discipline can.
- rz2k 10y agoI like the idea of using a wiki to track a lot of concepts you've learned. How do you keep track of everything that is in the wiki? Do you have a front page that is organized like an outline, or maybe a long list of concepts?
- ipsin 10y agoI went with the "long list" approach -- it was just a single page.
- arez 10y agoWould be nice to have such a list more data science, database orientated, maybe someone knows of a similar list.
- paulgb 10y agoI think this is what you're looking for https://github.com/datasciencemasters/go https://github.com/datasciencemasters/go
- kornakiewicz 10y agoGood list of resources, but motivation to have a job in certain company seems, for me, like wrong approach. What if Google won't be the place you would like to work after two years (because something happens in your life, or at Google.) Or after few months of employment you got feeling it's not place for you? This motivation also won't make you a better person.
- deleted 10y ago[deleted]
- jimbokun 10y agoInterviewing at Google gives him a specific target to motivate his efforts, but the material he is learning will be very useful to interviewing at other places as well.
- deleted 10y ago[deleted]
- sulam 10y agoGoogle people regularly tell me that qualified candidates have a 50/50 chance to make it through the interview process successfully. I'm sure they're working on that, but I would be thinking about it in those terms.
- samfisher83 10y agoIf you don't prepare the probability is much less than 50/50. I would rather have prepared and failed then just go it there and bomb it. You are going to have waste a day going to interview might as well be prepared.
- sulam 10y agoI didn't say not to prepare. :) Just defining the terms. Ie, a "good" chance is 50/50. I think knowing that might influence how you prepare, how you go into it mentally -- and most importantly how you process a rejection if that's the outcome you get.
- pjlegato 10y agoThat's kind of the point -- even if you prepare well, your chances are only 50/50, so don't be too disappointed if you don't make it.
- gnator 10y agoThese interviews are no different than a lottery where you hope and prey they choose an algorithm question you studied and learned well
- babygoat 10y agoA recruiter at Google literally told me which algorithms to know study and learn well, and only one of them came up in interviews (DFS).
- sunilkumarc 10y agoThis list is really huge! Do we really need to learn all of this?
- pjlegato 10y agoGoogle's sort of "computer science trivia" style interview is the bane of software engineering. "CS trivia" 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. In the real world, you use a well-tested premade off the shelf library to traverse a DAG or implement a red/black tree. Just because someone can recite algorithms and data structures in their sleep doesn'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. This mode of interviewing is like interviewing the contractor you'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. So why do they do this? Lack of any better option. Their previous "brainteaser" style interview didn't work at all, and this is probably marginally better than that at finding good engineers. But more importantly, it'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.
- walshemj 10y agoThat is is a good analogy.
- chii 10y agoHow does one hire a contractor for other industries? I'd garner that word of mouth is the way. The alternative is an association and certification body (not too disimilar to the medical association or the bar for lawyers), and gating the access to this certificate.
- EduardoBautista 10y agoWell they are pretty successful, so they must be doing something right.
- mattnewton 10y agoWho writes those premade robust libraries? Who improves them, when a few percentages of improvement will be multiplied by enough machines to come out to millions of dollars saved? If you have a pile of raw iron and you're currently running your own smelt for cost savings over the other remodelers, maybe even though you are in the remodeling business you could use those skills. I agree though that contracting is by far the best way to grade performance. But the Google style interview is the only reasonable alternative I know of to filter out people who don't actually know the technologies they are talking about and can fake it with other people's code for months.
- pjlegato 10y agohttps://en.wikipedia.org/wiki/Correlation_does_not_imply_causation https://en.wikipedia.org/wiki/Correlation_does_not_imply_cau...
- oneloop 10y agoSo tell us. What DOES imply causation? All you ever have in life are correlations. Can you ever conclude any causation at all? Do you see how easy it is to throw a wrench into your brain's cogs if all you know is repeating catch phrases that you don't understand?
- pjlegato 10y agoI have a philosophy degree, and I can say with some confidence that I understand that particular catchphrase pretty profoundly. Not everyone who happens to disagree with you is merely an ignorant barbarian in need of enlightenment. See Karl Popper's theory of critical rationalism to answer your questions about causation.
- Accacin 10y agoI notice you never actually answered his question.
- pjlegato 10y agoHis snotty attitude made me disinclined to engage further and answer directly, though I did provide a general reference to where to find the answer.
- oneloop 10y agoI noticed the same thing. I couldn't help but read his response in Trump's voice. "I'm very very smart, believe me. I went to a tremendous school and learned yuge words. No one knows causation better than me let me tell you."
- 10y ago
- sagivo 10y agonice info. i built something similar in ruby for my interview, focusing more on the coding part - https://github.com/sagivo/algorithms https://github.com/sagivo/algorithms
- kp25 10y agoI would start doing this from today, Not for getting a Job in Google, but to become a better software engineer. - Thanks for the Amazing List of Resources
- iskonkul 10y agoWhile we could debate on the meaningfulness of his goal, I find the person admirable. We could perhaps award more credit to the fact that this is a 44 year old person who is taking the difficult course of going through the material of CS on his own and then setting a clear goal to aim for. And of course not forgetting to celebrate his virtue of learning for life.
- almata 10y agoTotally. Being 38 myself this is one of the things I've liked the most from this case.
- yodsanklai 10y agoPeople complain about Google style of interviewing but I like the idea that you can at least prepare for them. I'm sure there are many companies that wouldn't even consider because you're too old or because you don't have the right background.
- stale2002 10y agoYeah, I have a suspicion that this is the only reason why people still use it. The signal that it is measuring is "How much did you prepare to get this job." Which isn't that bad of a signal.
- deleted 10y ago[deleted]
- edgyswingset 10y agoThis guy's website is weird. Feels like he's fetishizing Google the company. Not that there aren't people who do that, but still.
- partycoder 10y agoIt is fine to create a training program targetting top tier technology companies. No problem with that so far. But he specifically mentions Google. That I have a problem with: you cannot advertise a program as an being effective approach to the Google interview, if you have not been an interviewer, or you have not received an offer as a result of the interview process.
- hal9000xp 10y agoThere is a flaw in this program and in many coursera courses about algorithms and data structures. Although, you can relatively quickly grasp all basic algorithms and data structures, you most definitely can not quickly build up skills of recognizing these algorithms in problems (which is most valuable skill and most overlooked). Another problem is that you also forget these algorithms pretty quickly and can't implement them after a few months. I was on and off in algorithms since 2014 and already experienced these problems during last two years. Now, I took another route which is much slower but now, I can remember, recognize and implement some algorithms after a few months. I started to participate in algorithm contests, mainly on CodeForces, sometimes on HackerRank. Often these problems cover pretty narrow topics and what you can learn in two months on Coursera, on CodeForces you can learn in one year or even more. Why algorithm competitions is useful? When you stuck on the problem for a while, then you read solution and you see that this problem is solved [for example] by Dijkstra algorithm, you remember this algorithm for a while. If you stuck on another problem, and then after reading solution you discover Dijkstra algorithm again. You remember this algorithm for very long time (provided you put significant effort to solve the problem). That's because your brain connects Dijkstra algorithm with some important problem because you are frustrated solving this problem during contest. So frustration is actually good for memorization! (if used correctly). So there are 3 aspects which you should develop together in order to achieve really good results: 1. Implementation skills; 2. Problem solving skills (i.e. how you recognize algorithm in the problem); 3. Knowledge of algorithms, data structures, paradigms (like dynamic programming, greedy etc); Often courses covers only third aspect. Here is my description of CodeForces problems difficulty and relevant skills they develop: Div2 A - trivial implementation problem, train accuracy; Div2 B - little tricky but still trivial problem, find little things to solve the problem; Div2 C - sometimes easy, but sometimes really hard to solve, covers topics: combinatorics, dynamic programming, greedy, elementary graph algorithms etc; Div2 D - usually hard to solve, but can cover classical algorithms like Dijkstra, Kruskal's, binary indexed trees etc; Div2 E - very hard to solve, way above my current level (the same applied to Div1 problems); If you can solve Div2 C problems consistently within 15 minutes and sometimes solve D problem within 30-45 minutes, you will crush Google interview (at least their algorithms + data structures part, which is where most people stuck!).
- 10y ago
- yborg 10y agoWhere is the university for engineers that want to replace Google, not work for Google? Because working for Google is basically like working for IBM back in the 1970s.
- TheDrizzle43 10y agoSpend your time building shit instead of reading Cracking the Coding Interview and wasting time on Hacker Rank / Leetcode. There's the university.
- Yhippa 10y agoThis is a very ambitious list. It basically describes what you would end up going through in a CS undergrad curriculum (as others have pointed out). Personally it takes me a while to initially learn something and keep probing my understanding until I feel I have a solid understanding. There is so much to learn in this list I'm not sure how someone could reasonably understand most of these things without it taking quite a bit of time. I know for me if I tried to go through this list from top to bottom that the stuff I learned first would start to fade from memory as I kept adding more stuff at a rapid clip.
- ksk 10y agoIsn't it kind of perverse in a way that all this CS talent is going towards supporting a company whose primary purpose is to mine your data and create profiles about your habits and needs?
- omarforgotpwd 10y agoalso check out interviewcake.com
- desireco42 10y agoI don't think any corporation deserves this kind of attention. I did notice that Indian and Pakistani engineers like to do those kinds of preparations, and reasons are mostly cultural. You should always come prepared on the interview, but the better engineer you are, more companies and options you will have.
- supervillain 10y agoYou'll get into Google if you have a CS degree plus good in memorization. memorization != understanding, I hope Google should give chance to the latter being the "time-tested proven" engineers which some can't answer "computer science trivia" because most of them don't spend time memorizing theories, they spend their time building and applying what they learned.
- CrypticSplicer 10y agoI like your list! I'm going to give it to my little brother before he applies to work for Google. One thing I'd recommend looking into is deep search with pruning. It's nothing terribly clever- just boxing up something you've probably done before and giving it a name. It's a problem solving technique that often has tremendous real world benefits. Essentially- if you can take a problem and define it like a tree with potential solutions on the leaf nodes, can you define a search on that tree that gets you to the right solution as fast as possible? Often simple tricks can help you chop off entire branches of the tree so you never having to waste computation exploring them. It's nothing revolutionary, but its good practice to be mindful of when you can chop pieces off of your search space. Interviewers always love hearing something like "and if we organize the problem this way, we can always stop searching here because we know we can't get a better result". P.S.- If you know python I'd recommend interviewing in that. You won't be able to implement anything with nodes very well, but you can write most code on the whiteboard very succinctly. They WILL want to see actual code.
- crispyambulance 10y agoMaybe its just me, but it sounds like the OP is setting himself up for profound disappointment even (and perhaps especially) if successful. All that time and energy focused on becoming an employee of that one company, Google, will create enormous expectations which are likely to be crushed by reality when the OP comes to the realization that, yes, even Google is just another place to work for a living. Does anyone who actually work there think otherwise?
- morgante 10y agoHow is this not an indictment of Google's interview process? I have a CS degree and many successful software projects under my belt. Plenty of employers have happily paid me to ship software for them and I have repeated referral customers. I have no doubt that if given my computer and access to the internet, I can easily implement any algorithm in this list. Yet I also have no doubt that I'd have to prep for at least a dozen hours before a Google interview if I wanted a chance to succeed. Why on earth should going through a software engineering interview require pulling out your old textbooks and running through problems? Since this is really just a glorified IQ test, I'd much rather they just handed my an IQ test (or asked for my SAT).
- iblaine 10y agoThis is a great list of fundamentals for CS. This is also very creepy.
- jamisteven 10y agoFML I could not imagine prepping for something like this.
- geebee 10y agoI don't really object to content of these exams any more than I'd object to taking the math and linear algebra exam if I were an actuary, or the bar exam if I were a lawyer. I certainly don't think this is all trivia. It's foundational, but not the sort of thing developers walk around ready to be tested on in their day to day lives. If you suddenly plunked a vector calc or numerical analysis exam in front of a senior actuary, many of them would probably fail, even though they all passed the test at some point. If you suddenly forced experienced lawyers to re-take the bar exam, many would fail, including those who did very well on the bar. Trees, graphs, mathematics, binary? Sure. It's foundational. What I dislike about these "interviews", so much that I have contemplated leaving the field, is that we, as developers, have to take them over and over again, under capricious and arbitrary circumstances. Think about all the exams I mentioned above. They have a proper study path, they are administered consistently, they are graded and evaluated by respected and vetted professionals who will at least attempt to apply similar standards. You get information about what will be tested, you get feedback on how you did. You don't spend studying and preparing only to hear "we've decided not to pursue your (actuarial candidacy/bar candidacy/nursing boards) at this time". That's what makes this all so awful. I feel, after 15+ years, that I've re-taken my fundamentals exam enough times. If it were trivial, that'd be fine, but it takes time and focus to get ready for it, time I'm less and less inclined to spend on it. I think that there is an informal set of rights and responsibilities that evolved over time between exam-based professions and students. I believe that the "tech interview", which is really an exam, has almost all the downsides and none of the positives, none of the protections that evolved in the other fields. The only positive thing I can say is that at least tech doesn't require a very specific degree, unnecessarily long, that can only be obtained by going through certain accredited programs that cost $40k+ a year in tuition (the 3 year law degree at sky high tuition that can only be obtained through certain programs is cartel-like, professional regulatory capture at its very worst). But you know, actuarial exams are rigorous, don't require a specific degree, you can prepare how you like. I'd say that's probably the best model for software. I don't mind studying for this, but I don't want to have to do it over and over, and I'd like some assurances that it will administered properly.
- sp527 10y agoIf you're already a successful entrepreneur, the only reason you'd want to be a Google software engineer is if you have no idea what you're signing up for. There's absolutely nothing magical about working at Google and the learning curve plateaus fast, at which point you're likely a salaried code monkey. If that's more money than you anticipate making on your own, then I guess go for it. Otherwise you're making a serious mistake.
- potbelly83 10y agoWhy are people so obsessed at working for Google? Granted, I'm sure there are a few niche groups which are probably really cool to work in, but the others probably involve their fair share of CRUD work, like any other typical large corporation.