Getting an Interview
Getting an Interview
Interviews for Top Jobs at Google
- Software Engineer (1443)
- 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)
- Recruiting Coordinator (19)
- Financial Analyst (19)
Helpful (634)Accepted OfferPositive ExperienceDifficult 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!
Helpful (258)No OfferPositive ExperienceEasy Interview
I applied through college or university. The process took 2 weeks. I interviewed at Google in April 2015.
Phone interview: The Interviewer was late for 20 mins... Ask nothing on my resume. Tow questions: 1) A string consists of ‘0’, ‘1’ and '?'. The question mark can be either '0' or '1'. Find all possible combinations for a string. 2) Give you a text file, remove duplicated lines. Follow up: If the file is very large, general hash map takes too much spaces, come up with a better solution.
Helpful (174)Accepted 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.
Helpful (196)Declined OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 3+ months. I interviewed at Google.
I had a recruiter contact so applied directly. The entire process took 3 months. Round1: HR Questions: Why Google, what do you bring to the table etc. Most people clear this. Honestly if you did not or cannot then consider another career Round2: Phone screen with a Senior Product Manager Very professional, punctual and courteous Questions: Resume review, projects, product I like and what I will change about it Round3: Onsite Interviewer 1 (I-1): Seasoned PM Questions: Took one project on my resume and discussed it for 45 minutes. Standard PM framework approach to answering questions I-2: Seasoned GPM from YouTube Questions: Market sizing, opportunity assessment, why Google, how will you improve product X I-3 Junior PM in Search and was previously at Microsoft Questions: Annoying as hell and the only value add was he/she corrected me that it's Orange is the new black. I said Orange is the new Red. Mid 20's, annoying and arrogant as hell. We discussed about Netflix model and what can be improved. He/She just kept on saying.. What else.. what else.. what else... I think he/she said that at least 30 times. I-4: Seasoned GPM Questions: None as it was lunch interview. General talk about soccer world cup, etc. Guy was jaded and I think waiting for his stocks to vest. Overall nothing much to report here I-5: HR I thought I was done but she asked me to stay back. Hopes up... LOL I-6: Seasoned PM from Identity Management team Questions: SSO, OAuth, improving checkout etc. Nothing crazy I-7: Engineer from YouTube Questions: Professional and very very nice. Asked me to design a load balancer using data structures. I told him I can write in VB or SQL. He said does not care about language. Wants to see how I use data structures I-8: Junior PM from Google+ Questions: Mostly around improve X, improve Y. What non tech product I like? I told I love my Canon Mark III. Discussed it to death and since I know it in an out it was easy to talk about what I would love to change in it Overall, if you know frameworks you are good to go. They don't asking anything earth shattering. HR called in a week and said team loved you.. no questions there but felt that you would be a better fit elsewhere. I was offered a position in Google Tech Services as a Senior Manager. I am a Senior PM in a top company in the Bay area. It did not make sense for me to move into a Tech role. I declined and moved on. In hindsight I thank Google for saying no to me. I'm nearing 40. It does not make sense for me to hang out with 20 year olds PM's. There is only so much I have in common with them. I'm more of a PBS kind of guy. Orange could be the new Blue for all I care.
- I have been a PM for over 5 years and in marketing and management consulting all my career. Nothing was unexpected. Irksome? yes. But then again I said to myself, a decade ago I was as arrogant as that 20+ kid. Answer Question
Reasons for Declining
Not a PM position but a position in Google Tech Services
Helpful (53)No 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.
Helpful (23)No 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 .
Helpful (40)No OfferPositive ExperienceDifficult Interview
I applied through a recruiter. The process took 3+ months. I interviewed at Google (Mountain View, CA).
They warn you ahead of time that the interview process will take months but it was surprising nonetheless. The interviews were fun, I went through a pretty light phone screen with a recruiter, a more rigorous screening with an existing PM, and then three rounds of onsite interviews for one day. After about a week, I heard back from the company saying they would pass on me for now and re-apply, but they refused to give any feedback, which would have been helpful for upcoming interviews and to understand what I could work on if I should re-apply.
- The NBA championships are about to happen and you produce merchandise showcasing the winning team--but, you don't know which team that will be. What do you produce and how much do you produce to dress the stadium visitors with merchandise? 1 Answer
Helpful (11)No OfferNegative ExperienceDifficult Interview
I applied through an employee referral. I interviewed at Google.
First round interview. Interviewer coasted through questions, I ultimately ended the conversation. As excited as I was about working for google the questions made me rethink that decision in the moment.
- They asked those common "googly" questions like "why are manhole covers round" and "if you and a friend were on the same flight what are the odds you'd be sitting next to each other?" which aren't even really good logic questions and have nothing to do with the position. Answer Question
Helpful (27)No 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.
Helpful (2)No OfferPositive ExperienceDifficult Interview
I applied online. The process took 2 weeks. I interviewed at Google.
I applied thru their website. It took a ay or two for recuiters to contact me. First phase was a 15 min screening. Basic questions like why google, why HR. Second phase was an hour long phone interview with more situational questions like what would you do if you had to present a google product to the team or to the public. How would you coordinate, organize rotation within the company. What system would you create to faciliate recruiting/rotations in the company. Overall the recruiting team was really nice and organized. The thrid phase would have consited of a google hangout and then fourth phase in person interview.
- Tell me about a time when you had to work in a group? Any challenges? How did you face those challenges? Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review