Interviewed at Google
Interview Details – applied thru website and got a phone interview set up. not much difficult questions but got a reject email a week later.
Interview Question – do u know sql? Answer Question
I applied through an employee referral and the process took 1+ week - interviewed at Google in January 2014.
Interview Details – This was a referral and I quickly got contacted by HR via email. Very professional process with lots of explanations and tips to best prepare for the interviews.
There was then an initial screening by HR. Ensuring that I had the background to move forward and also give me some good insight into the prosition and process.
Next was a phone interview with a PM who showed up 20 minutes late and started to ask questions anout the market and challenges in wearable devices. At this point this was a complete disconnect as I'm an enterprise software professional and honestly was not even interested having that discussion.
As a follow up I was explained that Google wants their PMs to be able to tackle any topic. Obviously they are a successful company and their screening process works. Good for them, I reserve the right to think different, C-level IT executives have different expectations and constraints than me using Gmail at home.
Interview Question – Design a system to serve streaming video to google glass users. Answer Question
I applied through a recruiter and the process took 4 weeks - interviewed at Google.
Interview Details – One phone interview followed by Onsite
Interview Question – Machine Learning and Search DB failure Answer Question
I applied through other source and the process took 2 months - interviewed at Google.
Interview Details – Round I Interviews include 2 interviews with current PM's.
1. Tell me about a product you like
a. Why do you like it?
b. how would you improve it?
c. how would you monetize it?
2. Now let's imagine you are PM of that product. And you launch a new feature (of the feature sets suggested above). Day after launch usage drop dramatically. How do you go about inquiring what happened?
3. What do you think about the Android vs. iOs ?
1. So, tell me what you would improve about Toothpaste
2. Tell me about a competitive move by a company in the past 6 months and what you think about it.
Google PM position is highly technical and interviewers look to see if interviewee has the technical background and understand coupled with the product ingenuity and innovative thought and creative approach needed to innovative new and existing product at Google.
Interview Question – Android vs. iOs. Answer Question
Negotiation Details – I got round II
I applied through a recruiter and the process took 3 weeks - interviewed at Google in February 2014.
Interview Details – Contacted by recruiter in Jan and started to schedule my phone interview.
1st one cancelled on me like 30 mins before the call, 2nd one even didn't bother to call me - it turns out to be her last day at Google (and i was told by recruiter the 2 days after that fact...)
3rd one - late to the call like 8 mins - which made me almost think that I wouldn't get the phone interview call again.
It was the most awkward phone interview process I'd even experienced. This wasted 2+ weeks.
Interview Question – - What's your most visited websites, what's good/bad, how to improve.
- What's a good design you've seen, how to improve View Answer
I applied through a recruiter and the process took 2 months - interviewed at Google in September 2013.
Interview Details – Standard Process. A phone screen by recruiter followed by phone screen with a couple of product managers. After that got an invite to come onsite. Had 5 gruelling interviews ( 3 PMs, 1 behavioral with a Director of PM, 1 engineer ). They get you to lunch with one of the PMs and the lunch is fairly casual which gives you a glimpse of the famous 'free google food' Those candidates will succeed who practice and stick to an enterpreneurial mindset day in and day out. Its not something that you practice, prepare and acquire overnight or even in a few months. This was my second shot, I felt optimistic but unfortunately i did not make it.
1) concept to design - how would you build X for Y kind of people?
2) Strategic - what would you do if u were the CEO of X?What is the next big thing that you would design for XYZ company?
3) Sizing/estimation/consulting case type questions - if you build xyz product what is the market size like and how much? key here is to make assumptions, think details and incorporate them..
4) Puzzles - i got a couple of them....imagine u are on an island and....or u hav a billion numbers and...
5) behavioral - i did not encounter them when i interviewed at google a few years back...seems like Google is changing its approach towards a more rounded up interview process
6) engineering/CS - this does require a solid CS Foundation...didn't help that it came towards the end of a long and tiring day...last time around i also got Big( O ) estimation problems thrown at me..
1. Use the whiteboard to articulate and frame your thoughts and go through the problem solving process...what you should be thinking of is to come up with a framework for the answer instead of jumping rightaway to a nice well rounded andswer..google wants to see your framework not your final answer....
also my big takeaway from the interview (even though i didnt get the job) was this framework building process could be used beyond this interview even in my day to day work with great results
2. Have a 'recursive approach' - which means when given a problem with which you are absolutely stumped, try to think of the simplest 'base' case...scale it slightly...observe the pattern and come up with an insight...if you have 7 bullets in a gun kinda problem try to think of it in terms of 1-2 bullets in a gun scale...figure out the pattern for the smaller problem and that is the key to the larger problem as well...
3. be creative, think about the status qou and whats wrong and what you would like to change..whether its google's products or a competitors...
4. Keep your calm...this is the most most important of all...remember to simply slow down since your heart rate will be 2x the normal...
At all times, Google's followup was very professional...u will learn of how you fared in 1 or 2 weeks and the recruiter was exceptionally considerate in reaching out to me at intervals and letting me know where the process was...a far cry from some of the other behemoths in the valley who do not even bother to acknowledge your onsite visit to them....
Very Easy Interview
I applied online and the process took 2 weeks - interviewed at Google in January 2014.
Interview Details – Planning was done over phone and email. The recruiting team was courteous and efficient.
Interview: 45 min phone interview with another product manager. The interviewer was multitasking and I was on the speakerphone. Not a lot of cross-questioning happened. I thought the interviewer was taking voracious notes, but now I think otherwise. Questions were easy and generic. Nothing related to my past or related to the position was discussed.
I applied through a recruiter and the process took 3 weeks - interviewed at Google in October 2013.
Interview Details – I was contacted by a recruiter on Linked In. Phone interview 2 weeks later. Phone interviewer was clearly reading from a script and not very interested in genuine communication. Felt like I was talking to a robot. Interviewer acted very uninterested and self-important. More interested in asserting dominance than in exploring mutual opportunity.
Interview Question – Interviewer asked question, "How would you 'write a program' to do [X]?" (a very vague question), and become dissatisfied when I answered from an architecture standpoint. What he really wanted to ask was "How would you design an ALGORITHM to do [X]"? Answer Question
Very Easy Interview
I applied through a recruiter and the process took 1+ week - interviewed at Google in December 2013.
Interview Details – Recruiter contacted me via LinkedIn. After a quick phone chat, she setup a phone interview with a Product Manager. I work at a direct competitor with solid experience - so I wasn't too worried. I thought the phone interview went great, but was disappointed to hear that they are not moving forward with the process. As per Google policy, no feedback was provided.
I was surprised by the result of the interview since I thought it went great. It was casual, low key. We discussed my resume with details on instances at my job where I had demonstrated specific skills. We also discussed my favorite google product and two features that I would add to it if I were the Product Manager.
Interview Question – None. Everything was straightforward and non technical. Answer Question
I applied through a recruiter and the process took 2 months - interviewed at Google in August 2013.
Interview Details – A recruiter reached out to me for the Product Manager role. The interview process includes a HR phone interview, 1st round phone interview with a current Product Manager, and final round includes an onsite 5/6 back-to-back interviews with a combination of Product Managers and Directors. The onsite interview also includes a free lunch at Google offices, where you can ask informal questions to a current Product Manager.
Interview Question – The questions are used to test your thinking. I don't remember the exact questions, but be prepared to justify your logic very thoroughly. The questions are actually fun and stretch your brain and can steer your conversation with the interviewer. Answer Question
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –