Project Manager applicants have rated the interview process at Google with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 66.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Project Manager roles take an average of 21 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 39 days.
Common stages of the interview process at Google as a Project Manager according to 6 Glassdoor interviews include:
Phone interview: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. I interviewed at Google
Interview
Throughout the pre-screening and interview process, I heard again and again that my potential is how I would be judged, and that my experience was not a factor. The only feedback after my interview was that I didn't have the specific experience required for the position. Remain realistic despite the stated idealism.
Interview questions [1]
Question 1
How would you design a product that increases the consumption of fruit in the US?
I applied online. The process took 1 week. I interviewed at Google (Mountain View, CA) in Feb 2015
Interview
I break down to 4 parts . 1. Car , 2 . Household , 3. Transportation , 4 others.
Interviewer replied me to focus on Car only.
I use USA population to answer this questions.
Divided into Commercial car and non-Commercial car, then calculate the number.
Finally, Interview ask me how do I think my estimation , is that too high or too low.
I replied too low , because car sometime also needs to do maintenance and etc.
He said ok .
I applied through other source. The process took 4 weeks. I interviewed at Google
Interview
A friend of mine submitted my resume through some contacts of his; I'm not sure about the exact details here. I got an email from a recruiter who asked if I would like to apply for the Product Manager position. I said yes, I would love to.
Another recruiter then contacted me to set up a phone interview with a Product Manager for around two weeks later. This interview had a few basic questions, then centered around a theoretical problem: imagine that you are the manager of [one of Google's largest products], and that you're thinking about doing [major change to the business model of the product]. How would you think about that? What would you do? (I'm omitting the details of the question in order to respect the confidentiality of their interview process. The very same day the original recruiter told me I passed and asked for my availability over the next three weeks to come in for a full day of on-site interviews.
The next day I received an email from yet another recruiter confirming that I would have my interviews on one of the days I had sent, with detailed instructions on time, location, etc. This had NDAs and a formal job application to fill out. As it turned out the interview process required only 4.5 hours on site, including lunch, but I kept the whole day blocked off as I had heard rumors (here?) that some people were asked to stay later than their scheduled end time in order to have additional interviews, if the feedback was ambiguous.
On the day of the interviews, my train in was delayed and I was ~10 minutes late for my first one. I'm not sure if that was counted against me, but it did throw me off a bit. I believe that over the course of the day I interviewed with four product managers and one software engineer, in addition to a "non-evaluatory" lunch with another product manager in one of the cafes. I thought I had good rapport with two of the product managers, although it was hard to tell, as they were trying hard to push me with their questions.
The big questions I got were:
First interview: Product Manager
What are all the products you used since you got up this morning?
Pick one you like and describe why.
Pick one you don't like, describe why, and how would you improve it.
Second Interview: Product Manager
Tell me about yourself.
How big is the [xyz] market?
What are some technology trends you are following?
Third Interview: Product Manager
How would you improve [Google product]?
Is [Google product] important (to Google)? Why? How from a product perspective, would you get more people to use it? What features would you add?
Fourth Interview: Product Manager
Tell me about yourself.
What is a product manager?
How would you handle a situation in which someone senior to you disagrees with your product decision? (came out of something I said about how sometimes you mold user research into a product, and sometimes you're not able to)
Tell me about a product that you created that you're proud of.
Imagine that you are a PM at a big software company, and you are assigned to build [a business process] software for [a small business vertical]. How would you measure success?
How would you build the product? What would you say to the engineering team? How would you iterate?
Fifth Interview: Software Engineer
Some technical questions about web-based collaboration software.
A simple code sample that I had to read and then say what it did.
What's wrong with the code sample?
Assume that you put the [code sample app] up on the web, and it became really popular. What are some optimizations you could do to speed up response times under load?
Interview questions [1]
Question 1
Imagine that you are a PM at [big software company], and you are assigned to build [business process] software for [small business vertical]. How would you measure success?