The Definitive Guide To Google Interview
For years people have been fascinated by the Google interview process.
They wanted to find out the secret of getting hired by Google.
There is no secret to Google interviews...
There is no short cut to Google interviews...
There is no luck involved in Google interviews...
There is only one way to get hired by Google and this guide is all about it.
And surprisingly its not that difficult once you know it.
So if you’re looking to up your interview game you’ll love this guide.
Let’s dive right in.
We live in a standardized world filled with people who are trained to be carbon copies of each other.
We go to the same schools, have, for the most part, the same sorts of dreams, compete for the same jobs.
And even worst use the same tactics for almost everything in life.
This is not necessarily a bad thing. But the only down side is. You will end up getting the same results as everyone else.
Which sadly is getting rejected by Google. .........
While knowing that there will be hundred’s of other candidates competing to get a job at Google.
The biggest mistake we make is, we think that all the others will fail before us.
We think that we will be the chosen one's. Failure seems a long way off. We feel confident and somewhat arrogant in our skills, experiences and fancy degrees.
We undermine the amount of effort, hard work and energy it takes to compete with equally skilled and arrogant candidates.
We undermine all the aspects of effort that are needed to get us prepared, to defend ourselves in one of the most insanely competitive and difficult interview processes on earth.
Remember you are your own worst enemy. You waste precious time in preparing yourself only for the few aspects of the interview.
You forget to understand that success in Google interviews is not only a technical but a much tougher emotional, mental and personal endeavor.
The only way to increase your chances of success is to know more about this process and then strategically prepare yourself for each aspect of the interview.
This guide will serve as a foundation for you to base your preparation for interviews at Google.
Whenever you find yourself on the side of the majority,it is time to pause and reflect. Mark Twain
99.99% of candidates fail in Google interviews
Failure is the worst thing possible.
You feel sick.
You feel like your career is over.
There is absolutely nothing good about failure.
And there is nothing you can do about it.
You can learn a lot from failures of others then your own.
In this way you can avoid those mistakes and will ditch the same fate as others.
This chapter will teach you about why 99.99% candidates fail at Google interviews.
Why Do 99.99% People Fail At Google Interviews?
After working for five years as contract programmer for Google, Michael Geary simply did not applied for a full-time job at Google. Just because he was afraid of the notorious interview process.
Alex Bowe had a Ph.D. in Algorithms and Data Structures but he failed three times at Google interviews. Because Google thinks he had some gap in his knowledge.
These are not just few cases in fact there is a huge No. of engineers working at Google. Who succeeded only after one, two, three or even fourth attempt.
Here are the top six reasons people fail at Google interviews.
1. No knowledge about Google interview process
Most of the people who are rejected by Google, are not fully aware of the Google interview process. They lack an oversight about how many interview rounds they have to go through.
They lack knowledge about what are the expectations and criteria for each interview phase.
You must realize that, in order to increase your chances of success. You need to fully understand the complete interview process.
You need to know precisely what is expected from you in each round. And What kind of questions you will be asked
2. Lack of preparation
Appearing in any Google interviews is a no joke. You will be tested ruthlessly about your knowledge, your experiences, your views and about your problem solving skills.
Most of the people who fail at Google, undermines the amount of effort required to get themselves prepared.
On average a successful candidate has spent around 2,5 months to prepare for their interview.
3. Taking too long to solve interview questions
Many people do arrive at correct, optimal solutions during an interview. But it takes them too long and they need too much help.
A better candidate would have gotten through the problems faster and with less help. This is also one of the main reasons most of the people are filtered out in the earlier rounds.
4. Shallow solution
The people interviewing you at Google are smart people, and most of them have been interviewing candidates for some time. They have seen solutions to same questions over and over again.
It is no surprise that they can clearly see the depth and scope of candidate's solution. Most of the candidates will be able to solve the questions, but the only problem is that they are not able to solve it well and well enough to impress the interviewer.
5. Not knowing the Big 'O' of an algorithm
Almost 90% of all the questions will revolves around data structures , algorithms and their big 'O' values.
It is a no surprise that most of the candidates fail, because they are either not able to implement an algorithm , or are unable to answer questions about its performance and optimization.
6. Poor communication skills
Google is interested in hiring smart people. People who can spread their ideas, people who can communicate well within teams and across the units.
There are a lot of smart candidates who do really well technically but lack social and communication skills. Google does not take any risks or make exceptions but simply reject these candidates.
Case study I
Failing at Google interviews
How many times you have appeared in Google interviews ?I’ve participated and failed in about four sets of Google interviews (3 interviews each time) for various positions.
What you have to say about the whole experience ?
The people you will talk to are smart, and it’s a fun experience to be able to solve problems with smart and passionate people.
All the intriguing questions back-and-forth made me feel like I was being taught by modern Socrates
In the end all these interviews have given me a great chance to realize some gaps in my knowledge and refine my approach to solve algorithms.
What advice you have for someone preparing for Google interview?
Here is the breakdown and advice i would suggest for anyone who is preparing for google interview.
How To Prepare for technical Interview:
First of all, you are going to want to practice. Even if you have been coding every day for years, you might not be used to solving algorithms on white board.
The best advice i can give is to Practice solving algorithms every day until your interview.
How To Prepare for Non-Technical Interview:
There will also be a few non-technical questions. When I did my first one, a friend recommended that I have answers ready for cookie-cutter questions like
“Where do you see yourself in ten years?”
Don’t bother with that!
They will ask you about your previous work and education, though, and pretty much always ask about a technical challenge you overcame.
If you have a tech blog, refer to it. I’ve had interviewers discuss my posts with me (which they found from my resume). Blogs aren’t hard to write, and even a few posts on an otherwise barren blog will make you look more thoughtful.
Finally, the absolute best way to prepare for a Google interview is to do more Google interviews, so if you fail, good for you! 😉
What are your reflections?
There are lots of smart Googlers who didn’t get in until their third attempt (I still haven’t gotten in after my fourth, and I don’t think I’m stupid).
But I found the process of doing a Google interview at all to be very rewarding.
It is important to reflect afterwards in order to reap the full benefits of interviewing at Google.
If you did well, why? But more importantly, if you feel you did poorly, why? Google won’t give feedback, which can be a bit depressing at times.
Remember in Google interviews everything is a question of preparation.
Learning and understanding the interview success factors is one of the most important aspects.
In this chapter you will learn the characteristics of the candidates selected by Google.
Characteristics Of Candidates Hired By Google
Although each engineer is individual and has his own set of skills and experiences. In general Google hires software engineers based on following criteria.
1. Coding Ability
Since you will be paid well and really well at Google for doing coding. So its no surprise that Google hires people with strongest coding abilities.
2. General Cognitive Ability
Google looks for smart people with problem solving ability, curiosity, and ability to learn.
GPA (grade point average) is not necessarily a good indicator. At Google, GPA is only used with newly-graduated students.
3. Emergent Leadership Ability
Google thinks about leadership in terms of people who are willing to step into a difficult problem and step out when their expertise is not needed.
Google breaks all the work down into small family size teams (4-6 people) and different skill sets (diverse backgrounds).
4. Cultural Fit With Google
Google look for people who are comfortable with ambiguity, humility, and possess consciousness (thinking of others).
5. Relevant Expertise
For technical roles in the company you have to be great in your field. For the other roles, Google takes a portfolio approach.
In those roles, you don’t have to have deep expertise, but you want to have a spark of creativity.
6. Communication skills
Google values people who can communicate and can spread their ideas. Who have the ability to listen to other people as well.
No matter how talented and skilled you are. If you lack communication skills there is no way to get hired at Google.
Case study ll
Getting Hired By Google
How did you prepared for your interview?
With over ten years of programming experience and a CS degree. It took me about a month and a half of daily practice to get ready for the interview.
The following is based upon what I did to prepare
your mileage may vary.
1) Learn as much as you can about the Google interview process
Just like an incomplete understanding of a technical question will ruin you in the actual interview, misinformation will derail your preparation.
2) Benchmark yourself
Now that you know how prepared you need to be, figure out where you are right now. Use Cracking the coding interview for this.
Take a couple of questions from each section and solve them. Keep track of how long it takes you to reach an optimal solution for each problem you solve.
3) Make a study list
- Memorizing two good sorting algorithms and their Big-O
- Memorizing binary search
- Memorizing how to implement basic data structures
- Memorizing graph traversal algorithms (BFS, DFS, and a shortest path algorithm like Dijkstra's)
- Practice bit manipulation exercises
- Object-Oriented Programming terminology (abstraction, inheritance, cohesion, coupling)
- Recursion and backtracking
- Review principles of basic discrete mathematics and statistics
What advice you have for others candidates going for google interview?
Having interviewed, coached, and sat on hiring committees with many candidates during my three year tenure at Google. I’ve learned a lot about what works and what doesn't.
So, I'm going to share six tips I believe you absolutely need to nail your interview.
1. Repeat the question in your own words
As soon as you hear it, repeat it out loud. Do this preferably in your own words to demonstrate your comprehension.
2. Check assumptions
Many candidates start writing code almost immediately after hearing the question. This is a big mistake.
3. Use real examples
You've got a whiteboard—use it! Draw out an example array, a binary tree, a linked list, etc. Give it real data and write out the expected output of a working solution
4. Brainstorm solutions and their time/space complexity
Stop and think about various approaches. Think about trade offs using Big-O analysis and think out loud. Don't stop with the first solution that comes to mind.
5. Write working code (no pseudo-code please!)
Choose your strongest language and turn your thoughts into working code as quickly as possible
6. Test your code, always
Now turn your brain into a compiler and execute each line of code to ensure you don't have any logical bugs
What is google hiring process?
How Does Google Hire Software Engineers?
Each year, Google receives more than two million job applications from around the world and hires several thousand of those candidates.
It takes an average of six weeks to secure a hire, and every candidate needs to go through on average 3 rounds of phone interviews and 6-7 rounds of onsite interviews by their potential boss, potential colleagues, and a hiring committee.
Here is a quick overview of Google Hiring Process
How To Search And Apply For Jobs At Google?
There are four ways to apply for a job at Google
1- Search and look for jobs on Google careers site: Google careers
2- A Google recruiter found you on LinkedIn (or similar) site and contacted you.
3- You know someone working at Google and he/she referred you for a job
4- You can use this powerful job hunt method to contact someone at Google and apply for jobs.
How To Get Noticed By Google Recruiter
Get an internal referral. One of the best ways to get Google recruiter’s attention is to get an internal reference.
Internal referrals get more attention. Do you have any Google connections in your extended network?
E.g. friends of friends? Professors who have had students that went to Google? If so ask them to submit your resume.
On-campus events. Google often has on-campus recruiting events. Having a face-to-face with a real recruiter may help them remember you.
You may even be given the opportunity to interview on campus.
Contact a Recruiter via Linkedin . One of the easiest ways is to search for Google recruiters on Linkedin.
Try to follow them for some time and send them a private message with details about you along with your CV.
Recruiters at Googles does not mind being contacted by good candidates.
Show off your work. This is one of the most important tactic to get immediate attention from Google recruiters. But unfortunately it is not for everyone.
Have you contributed to some well known open source project? Or are you a creator of some fancy framework, library or even an extension etc. Then this is the best strategy for you.
All you have to do is to contact a Google recruiter by using one of the above methods and show them your work. If it is important enough, you will get interview invitation.
Your chances for invitation are higher if
- You have a suitable degree *(e.g. BS in CS, EE, math or physics)
- Few years of relevant work experience.
- Or you are a contributor to some well-known open source project
- If you have studied Phd or have a degree from Ivy league university
*If you have no degree then its still ok, You can still be considered, if you can show some relevant work experience etc.
Tips For Google CV
Google receives 20,000 resumes a week, or two every minute. Google even once received 70,000 resumes in a week.
So as a candidate first thing you need is to prepare a very good CV. Most of the CV’s are rejected by the automated systems which scans your CV.
Make your CV short and sweet. Not only recruiters but the Google engineers going to interview you will also look at it. Only if it is short max 2 pages.
-Put your skills on your CV. Interviewers will ask you what you are best at. If you list what you are best at, they will ask you about that.
If your CV says “master of algorithms”, expect algorithms questions.
-Do not put your high school, marching band, or girl scout experience on your CV.
-Be careful for what skills you put on your CV, If you say expert, or experienced in something then be ready to answer a lot of tough and deep questions about them.
-Use a professional and latest picture
-Use a professional email id
-Never write about your political and religious views
-Never complain about your previous jobs, managers, projects, Companies
-Look for grammatical and spelling mistakes
-Keep your CV short maximum 2 pages
- Never lie or exaggerate things on your CV
- Use simple and plain english
Google's application tracking system automatically rejects most of the Cv’s for common mistakes
-Typos - grammer and spelling mistakes
-Sharing confidential information about previous work/employeer
-length (no more then 2 pages unless you are )
-No relevant education
-No relevant work experience
-No knowledge about programming or CS subjects (Only for software engineers)
-Listing irrelevant or unimpressive certifications
-Resume matching” Google does not like resumes tailored for a specific job
Google internship process
For internship you will go through the same process of phone interviews and onsite interviews.
But sometimes there is a slight difference. You can be asked to solve an assignment before interview. Here are the differences
- Apply for internship
- Phone Interviews
- Assignment submission
- First Hangout Interview (Normally with 2 engineers)
- Second Hangout interview (normally with 2 different engineers)
- Final Interview (With the hiring team/manager)
- Hiring committee submission
- Final decision
A great career at Google is not secured by revolution but with evolution.
Phone interviews are the corner stones of this evolution.
What you do in your first interviews is far more important then the later interviews
A momentum is built based on each round of interviews you do. Where one will server as the step stone for the next one.
Every Google engineers Job journey started with a phone interview. And yours will too
In this chapter you will learn all about the Google phone interviews
First telephonic interview will be with a recruiter, who has reviewed your CV. He will ask you a few simple questions.
Things such as "what's faster, quicksort or bubblesort". If you answer enough of these correctly, you get to the next round.
If you fail here. stop moaning, go away and go improve yourself, there is no way you would have passed the later stages anyway.
No. of Candidates Rejected in Phone interviews
If you have passed the first round with the recruiter. Then for the second round an engineer will call yo.
This interview usually lasts for 45 minutes.
This is one of the toughest part and only the "best" Google interviewers will do the screening of candidates.
Remember this is the part where most people get kicked out.
The following process is not the same for everyone.
Because different people have different styles, but it boils down to two main approaches:
- The “Get the overview” approach. The interviewer will ask you 5-10 different questions spread out across your areas of expertise.
- The “one hard problem” approach. You will be asked to write code. Usually this is split into two questions: an easy “warmup” followed by a “real” question.
Warm up Questions:
A warm up question might be something like “reverse a string in place” or “implement atoi” or something like that.
A good and capable engineer should be able to solve this in about 5 minutes. Sadly, only a minority of the people ever get past this warmup question in the allotted 45 minutes.
If you are stuck the interviewer will try to help you to make you feel good. But if you fail to answer this warm up questions you will sure be rejected.
They won’t hire you if you can’t reverse a linked list, or do a case-insensitive string comparison.
Now assuming that you made it past the warm up question.You are now part of the elite.
Who know how to write a recursive function, or how to split a string by commas. Now the Google engineer will ask you a “real” question.
This include questions like this:
- Remove duplicates from a list of strings which is larger than the available memory (i.e. with reloads from disk)
- Count the number of disjoint objects in a bitmap
- Implement a program which plays tic-tac-toe
- Or anything in the same difficulty level
These are all pretty hard to do in 35 minutes. Most people can't, and it's not necessarily a failure if you don't get 100% there.
What most important is how you attack and reach your solutions and are able to answer the questions interviewer will be asking you for clarifications.
This is exactly the same as round 2, but with a different engineer. Google want to hear the opinions of two different engineer before inviting someone for a full day interview.
From the interviewer's perspective, second phone screens are infinitely better than first phone screens, because the totally incompetent have been weeded out already.
If you pass Round 3, Congratulations you will be selected for onsite interviews!
Google onsite interviews
One of the things you must do is that you must be involved and working on achieving mastery over onsite interviews.
And the best way to do it is by learning in details about
What is Google onsite interview process?
What they expect from you?
How you should approach each round?
What are some tricks?
Understand as you invest the effort and time on learning the full onsite interview process. You will exponentially increase your odds of success in them.
And the best thing about this chapter is that you will learn exactly about all of these.
Google Onsite Interviews Process:
Onsite interviews are divided into 5 rounds, 45 minutes for each. Other than the lunch interview, all of these interviews will be technical.
You will be asked a mix of coding and algorithm questions. These might somewhat related to your background, but they usually aren't.
Normally interviewers would decide individually about which questions they would use, and they typically wouldn't coordinate in advance.
What You Should Expect In Google Onsite Interviews ?
The onsite interview at Google depends on various factors e.g. responsibility, project type, years of experience and the mindset of each interviewer.
It also depends on what skills candidate has listed on his CV.
Last but not least, the way the candidate carried the technical and non-technical discussion and many more.
All of the above factors may steer the direction of each individual interview. Furthermore each interviewer can asks whatever he wants.
Usually, the interviewers have a way of tracking which questions were asked to a candidate to ensure a good diversity of questions.
But in general in every round you should be prepared to write alot of code
-That demonstrates that you can apply algorithmic knowledge to solve problems that may or may not be well-defined
-Google cares about how to design a scalable system. So, make sure you prepare for questions from “System Design and Memory Limits”
-Most questions are basic data structures, algorithms, coding your solution, discussion about complexities (time, memory) and basic computer fundamentals.
-Interviewers often ask open ended questions and expect you to ask clarifying questions so, they can clarify what they are really looking for.
-In General no puzzles will be asked. So don't waste time on those.
-In addition, especially if you're more senior, you should expect to be asked some high-level design questions.
-For software test positions, questions will be based from testing too
-You should also expect questions that are meant to demonstrate your deep knowledge of programming or technologies.
What Does Interviewers Expect From The Candidates?
In each onsite technical interviews you will be asked tons of programming related questions.
For each question asked, the interviewer will have some expectations based on which they will evaluate you.
In general interviewer's expect from candidates.
-As most of the questions are technical and it will be the obvious expectation that you know algorithms and their implementation.
-They expect you to know the core CS subjects like Operating System, Computer Network, Distributed systems (overall basic ideas).
-They expect you to ask questions. They will give you vague questions and that's intentional.
-You should always ask relevant questions to make it more clear without making assumptions on your own. Make the problem clear before directly going to solve it.
-They expect you to think out loud. It will make them at ease as they can really hear how you are approaching the problem
-They do not expect the perfect solution in first attempt. You should come to a working solution and iterate it, rather than taking much time and coming with perfect thing.
Top 7 Mistakes In Google Interview?
Here are top 10 mistakes candidates make in Google onsite interviews.
You should avoid making these mistakes to increase your chances of success.
1- Practicing on a Computer
During Google onsite interviews you will be asked to solve the problems on the white board and not on the computer.
It is a totally different experience of solving the problems on the white board.
If you have never practiced to solve algorithms on the paper or white board. You will have a tough time in actual interview.
As a best practice try to solve one or two algorithm problems on the paper every day before your interview.
2- Non Technical Interview Questions
Remember in Google interviews you will be judged for every aspect of your personality.
It will be your coding skills, team collaboration skills, communication and leadership skills.
You will be asked many tough questions. The purpose of these questions will be to get a glimpse of your personality.
You should spend some time to go through all of these non technical and behavioral questions.
3- Not Practicing In Real Interview Circumstances
It does not matter how much prepared you are. On the actual interview day you brain will have a tough time to hold everything together.
The best way to avoid Google interview day panic is by doing practice , practice and more practice.
You should aim to practice as real interview. Try to ask one of your friend and ask him to do a mock interview with you.
You can use some online services for mock interviews.
4- Trying to Memorize Solutions
Never ever try to memorize a solution of some algorithms. Because in real interviews you will always be asked some twisted version of the problems.
5- Not Listening To The Feedback from interviewers
6- Not Testing Your Solution
Once you have finished your code. You should literally turn your mind into a testing machine. Try to locate all the scenarios
7- Bad Coding
Writing bad code during interview is worst for you. When you write code, imagine you’re writing for real-world maintainability.
Break code into sub-routines, and design data structures to link appropriate data.
How To Approach Google Onsite Interviews?
As candidates you will be judged and marked for your behavior, approach communication and eventually every move you will make during the interview.
The Google engineers conducting the interview are usually experienced, and thus can see very clearly how you are performing in relation to other candidates they have interviewed.
It is then very important for you to know how to behave and approach the interview to have maximum positive impact and chances of success.
Following points will provide you a baseline to further think and reflect on your own strategy.
1) How to code and approach the solution
- Use your strongest programming language with no pseudocode
- Think out loud. Show your interviewer how you're thinking about the problem.
- Ask your interviewer questions to resolve ambiguity.
- Design an Algorithm
- Write as close as possible to fully complete and correct code
- Pick good variable names. Run through the code yourself and clean up bugs right away. Ensure it works by using examples. Try to find edge cases. Watch for off-by-one errors
- Most questions should be answered in fewer than 20 lines of code, almost always fewer than 30.
- Questions will be progressive for instance, how does your solution scale to an input of a size of several billion?
- Don't be afraid to throw out a brute force solution in the beginning, but you should try to improve your solution as well. Think about the time and space complexity and see if you can improve those.
- Though you likely won’t have to prove your solution’s order of complexity, you must be able to know or approximate it well. Avoid exponential time and space. Try to solve the problems in linear or log time.
- Write your code at moderate pace, not too slow and not too fast.
- Once you're done writing code in your interview, test it.
2) How to communicate in interview
The main concept for the interview is to keep the interview active and this requires some action from your side.
Such as the following
- You need to talk.
- You need to explain.
- You need to discuss.
- You need to express your views.
- It’s okay and encouraged to question your interviewer. Ask for help when you need it. If you need to assume something, verbally check with your interviewer that it is a correct assumption
- Google is interested in your problem-solving approach. This means talking and asking questions.
- The interview questions will be in-depth, and Google wants to see how you think about complicated problems. Correct answers are often not necessary if you’ve shown a mature thought process.
- Communication throughout the interview is key. Not only will you improve your chance of solving the problem and show the interviewer your thoughts, but the interviewer will also judge the teamwork by which you both get to the solution.
- Interviewers will ask you questions about your skills, interests, education, career, and projects. Remember to be genuine and interesting.
3) Know when to stop
One afternoon in ancient china, Chao the King of Han from 333 to 358 B.C., got drunk and fell asleep on the palace gardens.
The court’s crown-keeper. Who’s sole purpose was to look after for the king’s head apparel.
Passed through the gardens and saw his master sleeping without a coat. Since it was getting cold. The crown-keeper put his own coat over the king, and left.
When Chao the king, woke up and saw the coat. He asked his attendants, Who put the coat over me ? The crown-keeper, they replied.
The King immediately called his official coat-keeper and had him punished for neglecting his duties. King then called for the crown- keeper whom he then get punished ruthlessly.
REMEMBER Never shoot at your own feet
It is quite often that candidates are stuck in one question or after solving the solution they go too far to the point where things get so complicated that they cannot handle.
Do not overstep your bounds. Do what you are asked to do, to the best of your abilities, and never do more.
To think by doing more you are doing better is a common blunder.
Just overstep and you will get caught in something, and fell in a trap you digged for yourself. And result, Just like crown-keeper you will be punished ruthlessly.
Remember if you are a crown- keeper then be a crown-keeper. Save your excess energy and time for other questions.
Google selection criteria
Google Selection Criteria
How Does Interviewers Rate Candidates?Each Google interviewer will rate the candidates based on various parameters. These ratings are usually on a scale from 1 to 4.
What Google engineers are interested to know in candidates can be broken down to following points
If candidate is quick to comprehend and solve problems. Does he enjoys finding multiple solutions before choosing the best one.
Does he seeks out new ideas and methods of tackling a problem or not. Is he inventive and flexible in solutions and open to new ideas. Can he move up to more complex problem solving.
If a candidate can code, If yes how well, Does he knows the deep stuff or just surface knowledge
Candidates approach to Understand, analyze and then break down a complex problem.
How well a candidate can communicate, how he asks questions, answers , general ability to explain and clarify problems, social communication skills etc
How does each interviewer feels about working with a candidate. From (No go, maybe, perhaps and definitely) Note: Only definitely counts positive
How Does Google Decides Which Candidates To Hire?
The interviewers do not make the hiring decision. Instead after the interview, each interviewer write a report after the interview, called
An interviewer had to fill out extensive feedback, including a transcript of any code the candidate wrote.
This Feedback is typically broken down into four categories (Analytical Ability, Coding, Experience and Communication).
And the candidate is given an overall score from 1.0 to 4.0. Where 3.0 is the threshold of hire vs. no-hire.
This feedback is then submitted to the hiring committee of engineers. Hiring committee makes a hire/no-hire recommendation based on these scores from each engineer.
They look at the feedback and score for 3-5 minutes and decide whether a candidate is hired or not.
In exceptional cases, hiring committee can decide that they don’t have enough information, and ask the interviewers to do more interviews..
If hiring committee decide to hire a candidate, the recruiter will call the chosen one and will make an offer.
How to prepare for onsite interviews?
You should prepare yourself mentally, emotionally, and technically to align yourself with your dream of
Getting hired by google
You should be willing to do whatever it takes to pursue your dream.
Get yourself ready to go to extreme lengths to ensure its fulfillment.
The stronger the emotional connection the greater the chances of your success will be.
It’s horrible to have no dream.
It’s horrible to have a dream and then not pursuing it.
It’s even more horrible to pursue your dreams half heartedly and then failing to achieve it.
Then it was all for nothing.
You either need to go all in or just kill your dream.
In this chapter you will learn how to prepare yourself for Google interviews Emotionally, Mentally and Technically.
1. How to Prepare Emotionally
2. How To Prepare Mentally
We act, and feel, not according to what things are really like, but according to the image our mind holds of what they are like.
You have certain mental images of yourself, your world, and the challenges facing you, and you behave as though these images were the truth, the reality, rather than the things they represent.
Realizing that our actions, feelings and behaviors are the result of our own imagination and beliefs gives us incredible powers.
We can use these powers to prepare us for the unforeseen and tough situations.
Mental pictures offer us an opportunity to "practice" our interview everyday with very minute details.
We can practice it unlimited times until our actions and responses takes a natural form.
This is possible because your nervous system cannot tell the difference between an actual experience and one that is vividly imagined.
So our imagined interview actually is treated as a reality by our own mind.
You need to plan for the interview in advance. Go over in your mind, all the various questions that you are likely to be asked.
Think about the answers you are going to give. Then "rehearse" the interview in your mind.
Even if none of the questions you have rehearsed come up in actual interview, the rehearsal practice will still work wonders.
It gives you confidence, because you have practiced reacting spontaneously.
“There are no limitations to the mind except those we acknowledge”
3. How to Prepare Technically For The Interview
4. How to Develop Interview Intelligence
5. How To Separate Yourself From the Crowd
Google interview questions
There is no way to succeed in Google interviews without consulting the right resources.
When i first started my journey, I was bad at interviewing.
I did not knew how to learn from the online and offline resources.
I did not knew how and where to look for help.
But all of that changed, Once i figured out how to get help from the right books, right resources, right mentors
So i guess that's the key, and now i can introduce you to the best resources for Google interview.
Books to help you get ready for Google interview
Cracking the coding interviewLink: Cracking the coding interview
This book should be your no. 1 resource in preparing for Google interview. This is a deeply technical book and focuses on the software engineering skills to ace your interview.
The book includes 150 programming interview questions and answers, as well as other advice. You should try to solve all the exercises in this book without looking at the solution first. Once you have your solution you can compare it with the book's solution. also try to come up with alternative implementations for each exercise in this book.
2. Introduction to AlgorithmsLink: Introduction to algorithms
By now you should have realized that,you cannot succeed in Google interview without knowing the in's and out's of algorithms. Some books on algorithms are rigorous but incomplete, others cover masses of material but lack rigor.
Introduction to Algorithms uniquely combines rigor and comprehensiveness. The book covers a broad range of algorithms in depth, yet makes their design and analysis accessible to all levels of readers. Each chapter is relatively self-contained and can be used as a unit of study. The algorithms are described in English and in a pseudocode designed to be readable by anyone who has done a little programming.
3.The Algorithm Design Manual
Link: Algorithms design manual
This is another excellent book to learn about algorithms. This book takes the "mystery" out of designing algorithms, and analyzing their efficacy and efficiency.
The reader-friendly Algorithm Design Manual provides straightforward access to combinatorial algorithms technology, stressing design over analysis
Web resources to learn and practice about Google interview questions?
- Introduction to algorithms
What would you do when you are not the only one dreaming to become a Googler?
I wish i could tell you 80% will be enough.
But it's not
I wish i could tell you 90% will be enough
But it's not
I wish i could tell you 100% will be enough
The truth is.
You have to put in 120% of your efforts, focus and energies to prepare for Google interviews.
You have to outwork everyone else.
Remember: The Harder You Work Luckier You Get
About The Author
If you have any questions or need some help with your upcoming interview, feel free to contact me. I will make sure to help you in the best possible way.
All the materials and services on this site are 100% free. Just to help someone who might be stuck as I once was.
- http://cslibrary.stanford.edu/103/LinkedListBasics.pdfhttps://docs.oracle.com/javase/7/docs/api/java/util/HashMap.html https://www.linkedin.com/pulse/10-things-java-developer-should-know-hashmap-chinmay-parekh