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 -
The process took 1 day. I interviewed at Google in Aug 2010
Interview
I had my first call today. The questions were fair, no golf balls in buses stuff. The interview lasted 45 minutes. Quite a few questions on how to improve a product or system. I would recommend anyone applying to really know the products of the company and the job description in detail. The organization seems to like to brainstorm and then refine to workable ideas. I like a bias towards action and look forward to the next step.
Interview questions [1]
Question 1
How would you compress a string of characters by hand, not using zip. To reduce size.
I applied through an employee referral. The process took 1 day. I interviewed at Google (Mountain View, CA) in Jul 2010
Interview
I was referred to Google by a current Google employee. The phone interview was arranged after the reference was input into the Google hiring system in about a week. The interviewer was an existing Google Product Manager and interview last for about an hour.
I applied online. The process took 1+ week. I interviewed at Google in May 2010
Interview
I was contacted by the recruiter and went through the initial screening process. After which I completed two telephonic interviews with existing Product Managers at Google. The interviewers were polite and ultimately felt that I was over qualified for the role I was looking for. Questions were mostly subjective in nature and were less technical. They were trying to get a feel of my understanding of Google's business and whether I could analyze situations and come up with strategic suggestions on the problem presented.
Interview questions [2]
Question 1
Where do you see Google in the mobile space with Android