Customer Engineer applicants have rated the interview process at Google with 3.5 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 66.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Customer Engineer roles take an average of 49 days to get hired, when considering 2 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 Customer Engineer according to 2 Glassdoor interviews include:
Group panel interview: 50%
Presentation: 50%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. I interviewed at Google (Sydney)
Interview
Went through 4 types of interview: Technical phone screening, Role Related Knowledge (RRK), Googliness, Manager interview. If you have experience in the area, You should be able to pass the technical screening and RRK.
Interview questions [1]
Question 1
Mostly technical and cusomer facing experience questions
I applied through a recruiter. I interviewed at Google (New York, NY) in Dec 2021
Interview
after hr screeing then you will go through 4steps of checking how does your mind works, leadership style, technical knowledge, organization culture, presentation . each session was around one hour and more
I applied through an employee referral. The process took 4 weeks. I interviewed at Google in Oct 2021
Interview
3 interviews and recruiter chat:
Recruiter chat - overall discussion about interest in the role and experience
General Cognitive Ability - go over mainly hypothetical questions, and how you would tackle them
Googleyness and Leadership - mainly focused on behavioral situations in the past
RRK - more technical interview, meant to gauge your fit for the role
The GCA and G/L interviews were fair and pleasant, yet challenging. The interviewers were based in France, and they did a very good job of being collaborative and engaging, but also questioned you on points to test the strength of your answer. I left the interviews feeling like they were people I would enjoy working with.
The RRK interview was very different. It was with 2 customer engineers from the Madrid team, and it felt like I was interviewing with a completely different company. The tone of the call was dry, and it felt like an interviewee vs. interviewer environment. The only feedback provided from this interview was regarding two questions on data engineering concepts and their definitions, which can be googled in 10 minutes, so it's difficult to imagine how these types of questions can help gauge someone's future success in the role. I finished the interview with the impression that, culturally, the Madrid office was quite different (if not inferior) from the rest of the Google offices in Europe.
Interview questions [1]
Question 1
For the GCA and G/L, they were mainly hypothetical and real-life scenarios, and how you would handle them.
RRK - starts with sales-related questions, like how you would handle working with a prospect to migrate technology to the cloud; moves on to technical questions, mainly terminology and definitions; and finally an architecture diagram question based on Google Cloud.
Note: it didn’t seem like there was very good coordination between the recruiting and interviewing teams on how to handle the architecture diagram remotely. The recruiting team provides a Google Drawings doc with instructions, yet in the interview, it didn’t seem that they were not aware of this option and even suggested approaching it with pen and paper.