Google Interview Questions & Reviews

Interview Details Got contacted by a recruiter, who set up a phone interview a week later. The phone interview was very technical, just a couple of questions about my University projects and the rest of the time was focused on solving an algorithm task, the interview was about 50 minutes long. The next day my recruiter told me that he got positive feedback and they would like to set up an on-site interview in London. There were 5 head to head interviews, 4 of which where very similar to the phone interview and one was focused on systems design. A week after the on-site interviews I was informed that they were going through to the offer process, and a week after that I got the offer.

Interview Details Contacted by a google recruiter. Arranged a short telephone interview, and two weeks later an onsite in the london office.

The onsite consisted of five interviews, with lunch in between. Most interviews were coding interviews, the last one was system design. I found it the hardest, but couldn't say whether that's because I was already tired, or if it was actually hard.

I had to follow up the recruiter after 10 days, and then learned that I will not be offered the position. No other feedback was provided.

Interview Details 45 min Phone screen - I was asked to implement a stack in a language of my choice - I chose C++. I was then asked about how to make it more efficient - until there were no more improvements. I was asked specific questions about my CV - such as how did I implement such and such. then I was asked to visit the office - I had 5 interviews. The first interview, I was asked how to implement a drawLine() function. And also asked how I would create test cases ( TDD ). Second interview I was asked how to find a particular record with a given date out of a set of records. Third interview I was asked a really obscure problem which I can't remember. Fourth interview was about how to implement queue behaviour with 2 stacks. Fifth interview was an algorithm for string operations. Remember to work on your HR type answers, not just technical questions.

Interview Details I applied online where I submitted my CV and was contacted after a day. I was working during that time, so my two phone interviews were scheduled on the same day and the recruiter was really helpful in making sure I can make the time. The phone interviews were 15 minutes apart and the first one had a lot of small questions that required no coding, but rather collaboration on how I might do things as well as questions about data structures. On one of the questions I did not entirely understand what I was asked and the interviewer explained what was expected. The second interview was a single coding exercise. I had to write a solution to a given problem and after I wrote it, I had to explain the complexity of my solution. After that I was asked to improve my algorithm so that it runs faster. The interviewer did not require the code to be compilable, but to show knowledge of the language and the solution. Off the top of my head I did not remember the exact way of doing I/O with files in Java, but that was not a problem. After the interviews I was contacted the following day and the recruiter informed me that I am continuing to the next stage where they search for a project for me. The project was found in a couple of days and I had a phone conversation with the team manager who asked me about my previous experience with some technologies and my availability for the needed dates. After that I was given my offer in another couple of days. Through all the experience the recruiter made sure I was informed of what is coming next and what I need to expect.

Interview Details I've got an email from HR to make an appointment for a phone interview.

Interview Details very very difficult and full use of technology

Interview Details First contact takes a long time but will be from HR through email. A phone interview is setup with two hiring managers, 30 minutes each. Both managers will ask technical questions and you will be expected to code in a Google doc while they watch what you are typing. Once you finish these two interviews you will receive your results from the HR manager.

Interview Details I was contacted by a recruiting contact from HR. From there I was passed off to another contact who scheduled two back to back, 45 minute coding interviews. The first interviewer was very pleasant. After initially asking a question on which I fumbled, we spent the remaining time working on one question. The question itself wasn't terribly difficult, but it was intentionally ambiguous, to make sure I asked the right questions. After clearing up details we discussed optimizations, etc. This is probably the part of the interview that was most enjoyable as it didn't really feel like I was getting grilled. It felt as if we were discussing a problem and different approaches we could take. The second interviewer had a bit of an accent and seemed a bit less engaged/helpful. Also, the questions he asked were significantly tougher. All in all the process went very smoothly.

Interview Details After an interview workshop run by Google at my university I was contacted a few weeks later by a Google Recruiter. I initially had a 45 minutes phone interview with an engineer answering questions and writing code on a shared Google Doc. After that I was invited for on-site interviews. In total there were 5 interviews of 45 minutes each on that day. 4 of the interviews were mainly about problem solving and coding. The other one was more about system design (no coding, it was just a discussion). All interviews were with engineers. After the on-site interviews they asked for references from supervisors/managers etc.