Guide To Preparing for the Google Technical Interview

With more than ten years of programming experience and a CS degree, it took me about a month and a portion of every day practice to prepare for the meeting. "Prepared," for my purposes, is yearningly characterized as the capacity to handle practically any specialized inquiry question quickly or less and arrive at an ideal arrangement. Coming up next depends on how I dealt with set up—your situation will be unique. 

Fixings: 

Around two years of strong coding experience 

Pencil and paper 

Breaking the Coding Interview (CTCI) 

Your #1 calculations book—Introduction to Algorithms, The Algorithm Design Manual, and Programming Pearls are a couple of good decisions. Might I propose you go low tech and purchase actual duplicates? 

A few hours every day 

Energetically suggested: Whiteboard 

Energetically suggested: CS degree 

Discretionary: MIT OpenCourseware or another learning site 

Headings: 

1) Learn however much you can about the Google screening (days 1–2) 

Very much like a fragmented comprehension of a specialized inquiry will destroy you in the genuine meeting, falsehood will wreck your arrangement paving the way to it. I took in this the most difficult way possible when I fizzled at my first endeavor in the wake of underscoring mind mysteries over concentrating on calculations and information structures. 

Start with the source—look at google.com/vocations for data on how Google enlists. Then, at that point, watch this video from Google concerning what questioners search for in the meeting, lastly look at a model meeting including genuine Google engineers. 

When you have a strong establishment, I'd suggest following up by perusing CTCI. Especially center around parts 5 and 6 entitled Behavioral Questions and Technical Questions. 

When you at long last read my short article about the six things you totally need to do during the genuine meeting, you ought to have a decent handle of what a completely ready up-and-comer resembles. 

2) Benchmark yourself (days 3–5) 

Since you realize how pre-arranged you should be, sort out where you are at this moment. Use CTCI for this. Take several inquiries from each segment and settle them utilizing the six stages I referenced before. Monitor what amount of time it requires for you to arrive at an ideal answer for every issue you tackle. 

On the off chance that and provided that you've tackled the issue yourself, investigate the going with answer for evaluate how you did. Did you arrive at the ideal arrangement or if nothing else progress past the guileless/beast power reply? How since quite a while ago did it take you? Was your code written in the least lines conceivable? 

Do this for each segment. When done, you can focus on the areas that you didn't excel on forthcoming in your training routine and leave different segments for some other time. You should rehash this activity not long before your meeting so you realize your shaky areas going into the day of the meeting. 

3) Make a review list (days 3–5) 

Utilizing the information you procured from the past advance, make a focused on rundown of things you need to consider. This rundown ought to include: 

Remembering two great arranging calculations and their Big-O 

Remembering paired pursuit 

Remembering how to execute essential information constructions, for example, hashmap, connected rundown, stack, line, and trees (n-ary, trie, pile) and their Big-O intricacies 

Remembering diagram crossing calculations (BFS, DFS, and a most limited way calculation like Dijkstra's) 

Remembering forces of 2 

Practice bit control works out (working with bit maps, bit moving) 

Item Oriented Programming phrasing (reflection, legacy, union, coupling) 

Know the assortments and math APIs for your given programming language 

Recursion, backtracking, and memoization 

Audit standards of essential discrete arithmetic and measurements 

This is completely canvassed in CTCI and your number one calculations book. Note: the place of the remembrance is understanding! You will most likely never be approached to work out a calculation word for word. Maybe, you'll be relied upon to know each all around ok that you can utilize them innovatively to take care of an issue you've won't ever see. 

4) Practice calculations and information structures day by day (days 6–30) 

Pick a few things from your rundown and submit around a few hours every day dealing with these things (for example 1 hr before work, mid-day break, 1 hr after work). As you retain things, test yourself by working out a calculation or information structure on paper or on a whiteboard. Record the most pessimistic scenario Big-O existence intricacies for the calculation when you're set. Continuously take a look at your work, consistently! 

Presently duplicate what you've kept in touch with your #1 IDE and aggregate. Observe any aggregation blunders so you can stay away from them when you rehash the activity. You can and ought to likewise make unit tests to check the rightness of your code. 

Continue to do this until you can translate and incorporate your code without consistent or grammatical blunders. 

5) Tackle however many programming questions as you can (days 16–30) 

At this point, you ought to have a very decent handle on the abilities you need to prevail on an inquiry question. Beginning with CTCI, tackle each and every programming issue you can, again utilizing the six stages. Dedicate about a large portion of your review time to this while you spend the other half looking into things from your review list. 

In case you're progressing admirably, you'll most likely begin to run out of inquiries in the book. You can discover tons a greater amount of genuine examples online from locales like CareerCup or Interview Cake. Or on the other hand, simply utilize your number one web search tool. I realize a very decent one you can utilize ;). 

Practice a couple of times with someone else, both with somebody specialized and somebody non-specialized. Inquire as to whether: 

You looked and sounded loose 

You resembled a restrained issue solver 

You continued to verbally process all through the whole exercise 

6) Relax and get some great rest (day 30)