PhD applicants have rated the interview process at Google with 1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Candidates applying for PhD roles take an average of 30 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 42 days.
Common stages of the interview process at Google as a PhD according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at Google in Sept 2017
Interview
I was contacted by a Google recruiter around mid-August. The recruiter asked me if I was interested in applying in a PhD Internship at Google Research for next summer. I was unsure, the recruiter sent me some links about the research teams and areas. We then had first hangouts call and since I don't have much coding experience I have been suggested to spend this year preparing and then get into the interview process next year.
Interview questions [1]
Question 1
How many hours per week do you spend coding? When was the last time you did problem-solving? Why would you like to do an internship?
The process took 2 weeks. I interviewed at Google (New York, NY) in Feb 2017
Interview
Two screening interviews. They started with some simple knowledge question without coding something like bit manipulation or some network concept. And then coding of course. It was not that difficult, and I think I did well, but did not get the offer.
I applied through an employee referral. I interviewed at Google
Interview
I had two back-to-back interviews, each 45 mins long with a 15 minute break in between. The interviewrs called me over phone, while I had to write my solutions on a shared document. Two different people interviewed me.
Interview questions [1]
Question 1
Analytical questions, which I had to code afterwards.