Google Interview Questions & Reviews

Interview Details – Was referred by a Google employee through the internal system and recevied an email right away saying I would hear back within a week. Four weeks later I get a phone call from a recruiter asking about my interest in the position, if I was authorized to work in the US, and about setting up a phone interview with someone from the team. After submitting an updated resume + unofficial transcript I set up an interview via phone. The interview was 30 minutes with one person. I tried to prepare for how I was qualified for the position but you know Google, it's never a straightforward interview and I was totally thrown off. Not really questions you can prep for but if you find yourself in a similar situation just don't be set on prepared answers and just expect the unexpected. I didn't do a very good job relating the obscure questions to the job and my qualifications and I was not surprised not to make it any further. Hopefully just reading this you can get yourself in the mindset of thinking on your toes and not making the same mistakes! GL

Interview Details – Fairly well known interview process. Applicants should know about Google products and be ready to talk about what they want to build. Basic analytical questions and design questions are also standard. Applicants who are able to create a framework on the fly, and really focus on the process of designing a product are likely to have the best outcomes.

Interview Details – I had previously interviewed with Google during my final year as a Computer Science Engineering undergraduate student. I didn't get an offer, but the recruiter said that it was a close call and that she would follow up with me after two years once I had more experience. I joined Microsoft right out of college instead.

Exactly two years later (literally same day/month), a new recruiter followed up and I began the interview process again. A week later, I had a phone screen. After 4 days, the recruiter informed me that I passed and could move on to the on-campus interviews. I was assigned a new recruiter. Two weeks later, I flew out and had a total of 5 interviews at Google's headquarters in Mountain View, CA. Two weeks later, the recruiter informed me that I passed the hiring committee. One week after that, the recruiter informed me that I had passed the final executive review and I was provided offer details. In general, the recruiter was polite and knowledgeable, though late to call me on a few occasions when we had chats scheduled. Also, the recruiter began discussing relocation and job perks, as if I had the job, before an offer had been extended (after approval by the hiring committee, but before executive review). It sounds as though a fair number of candidates are rejected at this stage, and as such I feel this was somewhat inappropriate.

I found the on-campus interviews to be very academic-slanted. Though I had only been working in industry for one year, I expected more focus on what I had learned and accomplished there, rather than my knowledge of algorithms and data structures (most of which I hadn't touched since graduating from college). I don't know whether I will use these algorithms much in my day-to-day work, but I feel as though I am qualified for the job because of how I approach real-world software engineering problems, not my knowledge of algorithms and data structures.

My first on-campus interviewer was about 15 minutes late, but he had a sufficiently geeky excuse and I wasn't annoyed. Although some may find this lack of "professionalism" frustrating, I didn't mind, and he turned out to be my favorite interviewer.

A couple of the interviewers asked me to implement (in full or in part) algorithms to solve board games/strategy games. Think of the category of games that use a board with a grid of values, where solving the game consists of putting the right values onto the grid, or extracting knowledge from the existing grid arrangement -- this is what I'm talking about. Per my NDA I won't get into specifics. These questions were very in-depth and it took the majority of the time for me to come up with solution (or a sufficiently-developed line of thinking that would lead to a solution). In each case, my solution was incomplete or had minor errors/inefficiencies that the interviewers called me out for. I then used the interviewers' hints to refine the solution.

Another interviewer proposed a hypothetical product (a web application, with some sort of user interface, some amount of business logic, and a database backend, with a set of interesting scalability features) and asked me to talk through the process of testing it. This was an open-ended question which I enjoyed very much -- I felt like I was able to demonstrate my breadth of testing knowledge by touching on a number of potential test angles, and I went into detail on the ones that the interviewer found interesting.

Another interviewer asked me to design and implement a data structure that had constant-time performance for two specific operations. The constraints weren't satisfiable by any single simple data structure -- the solution involved a hybrid of two different ones. I believe this type of question is common at Google -- I had a very similar question (though with different data structures) two years earlier. I talked through the problem with the interviewer and, with a few hints, arrived at the correct solution and implemented it.

I didn't deliver perfect answers to any of the problems. I think I received an offer because I was able to talk through what I was thinking and doing as I was doing it. This allowed the interviewers to follow along, ask clarifying questions, and get me back on the right track when I made a mistake. I was able to demonstrate that I'm a competent programmer and pleasant to work with, even though I'm not an algorithm or data structure rockstar. I believe that better programmers than me get rejected because the interviewers are only able to evaluate their raw technical competency, rather than their people skills or problem solving process. If you are able to converse freely with them, as if you were tackling the problem with coworkers, they will feel much more comfortable overlooking minor technical flaws in your answer.

Best of luck, and hopefully I'll see you inside! :)

Negotiation Details – I didn't negotiate. With only one year of industry experience, the offer provided was slightly higher than a new college graduate offer, which is acceptable since I'll be learning an entirely new technology stack after working at Microsoft for a year, and therefore I consider myself to be a "new college graduate"-caliber hire.

Interview Details – I applied through a friend and was contacted by HR almost immediately. They scheduled me for on-site interviews at the Mountain View office without a technical phone screen.

I arrived early at Google's West Campus and found parking easily. It took a while to find a non-employee entrance to the building I was supposed to go to but I found it and signed in on a computer. The HR person then met me and took me to a conference room where I had two technical interviews, took a lunch break with an engineer who was not interviewing me, and had three additional technical interviews.

I can't discuss the specific questions but they were rather easy except one which was moderate. Four involved programming on the whiteboard and the last one covered system design. All of the interviewers were courteous and polite but two of the interviewers and the guy I had lunch with were especially warm and friendly.

The questions already posted on Glassdoor under Google are a bit harder than the questions I was asked but they are good preparation. I got one question which was listed here so I admitted that I knew it and gave the answer right away. I didn't get a follow-up question so that one was probably a free pass.

Most people asked questions in three phases. The first part is trivial. The second part is moderate and the third part is moderate or hard depending on your familiarity with the subject area (dynamic programming, recursion, hashtables, etc.)

I don't know whether I'll get an offer or not yet but since that's not an option on this form, I'll say that I did and accepted it.

Interview Details – contacted me 2 days after filling out the online application

Interview Details – Submitted an application in December, heard back a few months later. Had two phone interviews and a rejection. Even if you're not applying for an engineering job they really want people who are super connected to the internet and social media. It is almost as if they are trying to prove a point so it would help to become more active on social media in the months leading up to the application.

Interview Details – Fairly quick, since it was a contract position, had a VC with a recruiter, lasted about 20 minutes. Set up an 2nd interview for the following week.

It was a group interview, 10 other people and 2 managers...lasted 3 hours

Interview Details – Was contacted by HR from LinkedIn. Then I was connected later to interivew over the phone with a technical recruiter. The recruiter called on time and I was asked to type in code via Google docs. I was asked to write code to invert a Map. I had listed JAVA as my proficiency and this question tested it. It wasn't very hard but felt I needed more time...

Interview Details – Interviewed with Google for PM just a few minutes ago. The interview was supposed to be 45 min long, but lasted less than 30 min. The interviewer gave me a feel that she had already made up her mind what the outcome would be even before the interview even began.