Google Interview Questions & Reviews
Getting an Interview
- Popular Job Titles:
- Software Engineer (852)
- Product Manager (129)
- Intern (86)
- Software Engineer Intern (84)
- Software Developer (65)
- Senior Software Engineer (47)
- Software Development Engineer (43)
- Account Strategist (40)
- Associate Product Manager (39)
- Software Engineering Intern (38)
- Account Manager (36)
- Associate Account Strategist (35)
- Administrative Assistant (31)
- Software Engineer In Test (31)
- Site Reliability Engineer (31)
- Engineering (31)
- Adwords Associate (29)
- Program Manager (24)
- Engineer (22)
- Analyst (20)
- Software Engineering (18)
- Technical Account Manager (18)
- Product Quality Analyst (18)
- Technical Program Manager (17)
- Business Analyst (17)
- AdWords Representative (17)
- Systems Engineer (17)
- Financial Analyst (17)
- Senior Product Manager (16)
- Test Engineer (13)
Software Engineer Interview (Negative Experience; Difficult Interview)
I applied through an employee referral and the process took 4 weeks - interviewed at Google in May 2014.
Interview Details – 1. HR Recruiter: standard chat
2. Technical Recruiter: scheduled the interview
3. On site Interview
- 5 rounds of technical interviews
- system design questions
- recursive questions
- some java language questions
Three out of five engineers doing the interviews were not very friendly. One was very abrupt. One behaved like a police officer who pulled me over. One was late and kept interrupt me while I was writing code
Interview Question – The java language questions Answer Question
Software Engineer Interview (Positive Experience; Average Interview)
I applied online and the process took 4+ weeks - interviewed at Google in July 2014.
Interview Details – Contact by recruiters a couple days after submitting my application online. The interviewers are very nice and gave me hints when I were stuck. We had a very friendly conversation.
Interview Question – Questions about data structure, algorithm. Also object oriented design Answer Question
Administrative Assistant Interview (Positive Experience; Average Interview)
I applied online and the process took 3 weeks - interviewed at Google.
Interview Details – People are told up front that Google's hiring process is long. It takes a determined and committed person to subject themselves to the torture of waiting for an answer and next steps. However, once you get past the initial interview with the recruiter and the critical thinking test you are added as a viable candidate for consideration on future opportunities. The recruiters do a great job of keeping you informed regarding expectations and process. They also make an effort to give you the proper information to make sure you have a good experience and advice on how to market yourself.
Interview Question – There were no really difficult questions. If you are a truly qualified candidate it becomes more about finding a good personality fit for the team. Answer Question
Software Engineer Interview (Neutral Experience; Average Interview)
I interviewed at Google in May 2014.
Interview Details – Recruiter contacted me via email or linkedin, can't remember exactly. Asking if I would be interested in Google. I have a long resume and somewhat specialized set of skills in embedded systems so I said ok I will give it a go, but that I am not quite sure how my skills would be useful at Google. They waived the phone screen and moved me directly to an onsite interview. They send you a list of things to go over to prepare for the interview that looks like something out of college computer science course. I was really busy at my current job so I had little time to go over it, but it was fun revisiting the basic algorithms and data structures.
Onsite was 3x45 miutes 1on1 interviews, lunch and 2 more 45 mins sessions. All back to back, no breaks other than lunch.
1st session: Interviewer introduced himself gave me time to introduce myself for the 1st 10 mins. Then asked 2 questions. 1st was arrays didnt require to writ code, 2nd was dynamic programming asked to wrote code. I did well on both so we had 10 more mins to spare where I asked him questions.
2nd session: Introduction took a really long time, interviewer talked at great length about himself and his work. Asked me if I am interviewing for real or just there to get some interview experience, because apparently thats what he did initially himself. When we got to the question there was only about 15 mins left. Tree related question, that in my opinion wasn't really presented very well. Code was required. I started solving it but he was basically walking me through every step. Not sure if he just wanted to pass me or realized that he already spent too much time talking. Got the correct solution, but I felt like I was being lead to it.
3rd session: Embedded systems engineer, asked me a lot about my actual resume. In the end asked me a pretty basic question embedded system specific, asked to write code. Was really easy for me, did really well. Probably the most enjoyable session.
Lunch: The weirdest part of the day. Interviewer only got notified the night before, didnt look like wanted to be there. Didn't even know where the closest cafeteria was. Ended up walking for about 15 mins around the campus. Dropped the tray when getting food and spilled lunch over clothes, got really upset. Then suggested we sit outside because its quieter there. But the day was hot and it was really uncomfortable, I was glad to get back inside.
4th session: Usual introductions. General distributed systems question. Went pretty well in my opinion, but then I am not a distributed systems specialist, so cant really judge.
5th session: The worst one ofthe day. Usual introductions. 2 Questions. 1st question supposed to be a warmup, really simple bit manipulation, but for some reason my brain just went into a feeze, not sure if it was the stress or the sun from the lunch. Anyway I worked manually through some samples and did come up with an algorithm and a correct solution. In fact the interviewer corrected something in my solution, but when I started running it through a test case it turned out my initial code was in fact correct, so we reverted it. Because 1st question took so much time, we only had about 10 mins for the 2nd one which was supposed to be the main question. So we didn't really finish it.
Recruiter called me a week later saying that they decided not to go forward with my candidacy at this time. I am not really too bothered since I am pretty happy at my current job and this was more of a learning experience, but I admit that if they did make me a good offer, I would've seriously considered it.
While driving home I did come up with a really good solution to that unfinished question from the 5th session. And then also found every single question that I got asked in my interview on programming websites. So looks like if I wasn't so busy and just spent more time preparing, the interview would've gone much smoother. I thought just experience would be enough to pull me through.
Other than the lunch person and the 2nd session interviewer, everybody else was very pleasant and enjoyable to talk to.
Interview Question – All were unexpected. I didnt prepare for any, but was able to work through most of them. None really difficult under normal circumstances. Answer Question
Product Quality Analyst Interview (Neutral Experience; Average Interview)
I applied through a recruiter and the process took 3 weeks - interviewed at Google in June 2014.
Interview Details – A recruiter contacted me and conducted a phone screen. He couldn't tell me much about the position. Two Hangouts followed. They were long on analytical, "let's see how you think" questions and short on details about the position.
Preparation should include a thorough understanding of how Google makes money and how scammers abuse its products.
Interview Question – How would you mitigate fraud on Google Wallet? Answer Question
Strategic Partner Manager Interview (Neutral Experience)
Interviewed at Google
Interview Details – Like most people the hiring process is a little long however they were very accommodating with my schedule and were always open with what has happening in the interview process. The recruiters are the best I've even had to deal with. Super nice and upfront.
Interview Question – Pretty straight forward questions. Just tried to pressure me into answering questions that I didn't know. Answer Question
Very Difficult Interview
ITRP Interview (Positive Experience; Very Difficult Interview)
I applied through a recruiter and the process took 3 months - interviewed at Google in May 2014.
Interview Details – The communications from the recruiter were very fast initially, within two weeks I had the phone screen which seemed more like a conversation with a friend than a grilling interview, two weeks later I was offered the opportunity for an onsite interview. I heard the onsite interview process was grueling and difficult, and it was just that. My brain hurt from all the questions but after the interviews were over we had lunch and toured the facility. Unfortunately I wasn't chosen for the position but nevertheless it was still an amazing chance to get and was really once in a lifetime.
Interview Question – Just probed into my deepest IT knowledge Answer Question
Program Manager Interview (Neutral Experience; Average Interview)
I applied through an employee referral and the process took 5 days - interviewed at Google in May 2014.
Interview Details – Do phone screening. Didn't get to the next step. Recruiter said that team didn't want to pursue any further. Didn't say why. The process was fast although if I got further in the process, it could take two months to complete.
Interview Question – Question around whether I have own product roadmap decisions. Answer Question
ASIC Design Interview (Neutral Experience; Average Interview)
I interviewed at Google in June 2014.
Interview Details – A very slow process. My resume was submitted through a friend's friend working in google.
Then after couple weeks I got email from staffing department saying they are looking at my resume.
After couple weeks, I got a email about phone interview.
Interview Question – online coding through phone interview Answer Question
Software Engineer Interview (Neutral Experience; Difficult Interview)
I applied through an employee referral and the process took 4+ weeks - interviewed at Google in July 2014.
Interview Details – Generally are two coding questions and mostly didn't ask the resume. One is about array and another is tree question. The questions are kind of hard and good coding preparition are needed.
Interview Question – The difficulty of questions is expected but is harder than average coding questions I have seen. Answer Question
Interviews for Top Jobs at Google