Getting an Interview
Getting an Interview
Interviews for Top Jobs at Google
- Software Engineer (1442)
- Product Manager (176)
- Intern (147)
- Software Engineer Intern (84)
- Software Developer (83)
- Associate Account Strategist (80)
- Senior Software Engineer (69)
- Account Strategist (62)
- Software Development Engineer (56)
- Site Reliability Engineer (54)
- Software Engineering (52)
- Software Engineer In Test (51)
- Associate Product Manager (51)
- Account Manager (50)
- Software Engineering Intern (37)
- Administrative Assistant (35)
- Technical Program Manager (34)
- Program Manager (33)
- Engineering (32)
- Adwords Associate (31)
- Quantitative Analyst (31)
- Engineer (23)
- Interaction Designer (23)
- Analyst (23)
- Business Analyst (22)
- Product Quality Analyst (22)
- Technical Account Manager (21)
- Senior Product Manager (21)
- Financial Analyst (19)
- Test Engineer (19)
Software Engineer Interview
I applied through an employee referral. The process took 4 weeks. I interviewed at Google (Mountain View, CA) in April 2014.
Direct onsite because I interviewed in the past and did well that time. From the time I sent my resume to interview day: 2 weeks. From interview day to offer over the phone: 2 weeks. The syllabus for the interviews is very clear and simple: 1) Dynamic Programming 2) Super recursion (permutation, combination,...2^n, m^n, n!...etc. type of program. (NP hard, NP programs) 3) Probability related programs 4) Graphs: BFS/DFS are usually enough 5) All basic data structures from Arrays/Lists to circular queues, BSTs, Hash tables, B-Trees, and Red-Black trees, and all basic algorithms like sorting, binary search, median,... 6) Problem solving ability at a level similar to TopCoder Division 1, 250 points. If you can consistently solve these, then you are almost sure to get in with 2-weeks brush up. 7) Review all old interview questions in Glassdoor to get a feel. If you can solve 95% of them at home (including coding them up quickly and testing them out in a debugger + editor setup), you are in good shape. 8) Practice coding--write often and write a lot. If you can think of a solution, you should be able to code it easily...without much thought. 9) Very good to have for design interview: distributed systems knowledge and practical experience. 10) Good understanding of basic discrete math, computer architecture, basic math. 11) Coursera courses and assignments give a lot of what you need to know. 12) Note that all the above except the first 2 are useful in "real life" programming too! Interview 1: Graph related question and super recursion Interview 2: Design discussion involving a distributed system with writes/reads going on at different sites in parallel. Interview 3: Array and Tree related questions Interview 4: Designing a simple class to do something. Not hard, but not easy either. You need to know basic data structures very well to consider different designs and trade-offs. Interview 5: Dynamic programming, Computer architecture and low level perf. enhancement question which requires knowledge of Trees, binary search, etc. At the end, I wasn't tired and rather enjoyed the discussions. I think the key was long term preparation and time spent doing topcoder for several years (on and off as I enjoy solving the problems). Conclusion: "It's not the best who win the race; it's the best prepared who win it."
- None. 3 Answers
You can and should negotiate politely. You are in a stronger position if you have another offer, but even otherwise, you should ask for more of every type of payment!
Other Interview Reviews for Google
Software Engineer InterviewAccepted OfferPositive ExperienceDifficult Interview
I applied online. I interviewed at Google.
I first had a phone screen interview. After this, I was asked to come onsite for further interviews. I had 4 whiteboard and 1 lunch interview with the Youtube team. After this, I was told that my application is going through the Hiring Committee. Hiring committee asked my HR to find a team for me before giving any decision. I then had two phone interviews with different teams in Android. I informed my HR that I am interested in the first team. Next day, HR emailed me and said that this team no longer has an open position. I again went through the same process. This time, platform team was interested in talking to me. I gave 2 phone interviews wherein they made me write code. After their feedback, I was put through the Hiring committee again and this time I got a thumbs up from them. 1 week after that I was put through executive committee and got my offer. I had 7 other offers and my HR asked me about all of them before putting me through executive review. They gave me more than any other company I had offer from.
Software Engineer InterviewNo OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 4+ weeks. I interviewed at Google (Mountain View, CA) in July 2015.
The interview went seemingly smoothly, except for a couple quirks in the code on the whiteboard. The questions were way easier than I expected. The interviewers were not intimidating at all and did not try to make the process stressful. I felt like I passed and according to HR, the overall feedback was positive. My application went to the hiring committee which, in turn, rejected the offer.
Software Engineer InterviewNo OfferPositive ExperienceEasy Interview
I applied online. The process took 4+ weeks. I interviewed at Google (Mountain View, CA) in September 2015.
Awesome process. Very simple questions. Keep your nerves cool. Don't worry about very complex questions on the Internet. Do basics and you should be good. I screwed up two simple questions and not expecting offer. I will apply again next year .
Software Engineer InterviewNo OfferNeutral ExperienceAverage Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Google.
I was contacted by a recruiter who set up a technical phone interview for me. The interview question was average in difficulty, I didn't cover a corner case and when I asked the interviewer to add code to cover a specific corner case, he said I was out of time. I didn't get to move on to a second interview. I feel my answer was good enough for screening purpose (you'd assume first phone interview is the screening interview). Anyway, I would say as humans, talking over the phone while coding, we might not be in the best state to cover all the cases especially if it's just the screening call.
Software Engineer InterviewAccepted OfferPositive ExperienceAverage Interview
I applied through college or university. The process took 2+ months. I interviewed at Google (New York, NY).
about 2 months long telephone interview and then 2 onsite interviews the telephone interviewer asked basic questions and assessed your personality the onsite interview was more technical and asked questions that were more difficult
- p, np hard, np complete questions couple of data structures questions Answer Question
Software Engineer InterviewDeclined OfferNeutral ExperienceDifficult Interview
I applied through a recruiter. The process took 3 weeks. I interviewed at Google (Mountain View, CA) in September 2015.
I got asked through for two rounds of back to back phone 45 minute interviews, followed by one other phone interview. During these interviews, the interviewer called and we went through a Google doc. Usually, there was one or two programs I had to write with an after-discussion on time complexity, etc. I also had time to ask questions. They didn't ask about things on my resume/ projects, everything was coding.
Software Engineer InterviewNo OfferNeutral ExperienceDifficult Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Google (Mountain View, CA) in September 2015.
Onsite consisted of 4, 45min interviews in which interviewers asked questions about graphs and string manipulation. Lunch is with another engineer and a chance to ask questions and learn about campus. The interviewers did not ask about background or past experience and went straight into the interview question. Also, there is not much time at the end to ask them questions about Google.
- Given an array of integers, find the length of the shortest subsequence that sums up to over a certain threshold. 4 Answers
Software Engineer InterviewDeclined OfferPositive Experience
The process took 2 weeks. I interviewed at Google (Mountain View, CA).
A Google recruiter emailed me out of the blue. After three times of declining (1 month) since I wasn't that interested, I was contacted again so I thought "heck, sure, I'll take an interview". One week later the flew me to Mountain View for the on site. (Gotta admit Google is very generous about the whole travel arrangements! Free hotels, flights, meals, car rentals, etc) The whole experience was very pleasant for the most part. Got the offer 1 week later. The entire process, from initial phone screen to when the offer was made, took two weeks. One thing I'd like to call out and hopefully someone from Google recruiting/interviewing committee would take note is that they perhaps could do a better job at training their interviewers, not just from a technical standpoint but also from other nom-technical ones, especially on "normal" common sense and human interactions. I know we here are all nerds and as such could be a little awkward, which I totally understand. But one particular interviewer made me extremely uncomfortable during the interview since he kept staring at me like there had been something weird on my face and made excessively long eyes contact. I had to look away multiple times. Even when I was explaining my solution which is ON THE WHITE BOARD, he still stared at my face. The person's questions were good and had indept follow-up. So while I'd say he is a good technical interviewer, I still couldn't get over the awkwardness. This is no doubt thr weirdest interview I've ever had. Another minor thing I forgot to mention is that Google make you stay with your host at ALL TIMES. Even when you need to go to the bathroom which could be right next door, the host would follow you and stand at the door waiting for you, which is a bit awkward when you're a woman and your host is not.
- Signed NDA so no details here. But I can tell you if you review fundamental CS concepts(sorting,graphs, trees,etc) you should be fine. Just make sure you really understand what you are doing. I don't think they would ask you crazy questions on obscure data structures. Just basics problem solving skills. Also try to be original and honest when it comes to nom-technical questions, such as "why Google?". Don't try to be unique and make up some weird reason. Just tell the truth. Answer Question
Reasons for Declining
Wasn't sure I want to make a switch yet still love my current job
Software Engineering InterviewNo OfferNeutral ExperienceAverage Interview
I applied through a recruiter. The process took 4+ weeks. I interviewed at Google.
Screening was simple and much more like a conversation with just anybody. Phone interview was bad. The engineer never provided hints or clues and the libe was dead on his side. The question was simple, but since he was late, he didnt even provide the time promised.
- Matrix - given a nxn matrix, print the matrix in diagonal from left to right. 2 Answers
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review