Chef De Projet 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.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Chef De Projet 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 Chef De Projet 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 a recruiter. The process took 6 weeks. I interviewed at Google (Mountain View, CA) in Sep 2012
Interview
Summary: You had better know the technology inside & out - at a much greater level of detail than a Project Manager would ever need. Basically they are looking for Engineers who want to give Project Management a shot.
Details: I was contacted by a recruiter at Google about an opportunity with the company. Went through a couple phone screen type calls with him before moving onto the next step which was a phone interview with another Project Manager. This phone interview lasted 45 mins & did not discuss anything about project management, it was only technical questions. I passed that interview (but was skeptical about the job really being "Project Management") and was asked to fly out to Mountain View for 5 hours of face to face interviews.
The vast majority of the questions through the face to face interviews were technical just like the original phone interview- not really concerned about Project Management skillsets. Again, very bizarre considering that the title of the position was Project Manager (albeit a Technical Project Manager but still). I would say that 95% of all questions I received were technical with the other 5% being general management type questions (not a single question that was pure project management).
Google really does only care about your technical skill sets even for project managers - but who am I to argue with them, they are taking over the world. :) That being said I made it perfectly clear in my phone interview that my technical skill sets are my weakest, yet they moved forward with the interview. If technical skills were 95% of the job requirements they should have been able to weed me out a lot earlier in the process (before having to travel for face to face interviews).
After 1.5 weeks I received a "Dear John" call from the recruiter saying that there just wasn't a fit. I was completely fine with this because there was very little they could have done to convince me to take the job after the interview questioning I went through. I knew it wasn't a fit for either of us.
Interview questions [1]
Question 1
Basically explaining how the technology works down to a really detailed level.
I applied through an employee referral. The process took 2 months. I interviewed at Google (Mountain View, CA) in Jun 2011
Interview
I was recommended by a friend. There was a long lag (~3 weeks) and then I got a call from a recruiter out of the blue. She brought me in for 3 interviews. Each interview focused on differnet things: Domain expertise, analytical abilities, etc. The interviews went well and the hiring manager wanted me to come back for additional interviews. Then a long silence and finally was told that the position was filled by an internal candidate. Big waste of time in the end.
Interview questions [1]
Question 1
Let's say we wanted to build a service to index all the images in the world. How would you think about the cost to do that?