Engineer applicants have rated the interview process at Google with 3.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 44% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Engineer roles take an average of 30 days to get hired, when considering 9 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 Engineer according to 9 Glassdoor interviews include:
Phone interview: 50%
Group panel interview: 13%
Skills test: 13%
Background check: 13%
Personality test: 13%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 days. I interviewed at Google (Detroit, MI) in Jan 2021
Interview
Easy but challenging. Need to understand a lot of stuff on the science side. Make sure you have a degree. Don’t think you can just go in there and talk about math and think you can get a job it is going to be tough
Five rounds of interviews from which first two rounds are based on coding and that too based on DSA. Must practice string related questions from leetcode or any other websites
I applied through other source. I interviewed at Google (London, England)
Interview
The interview process was structured and professional, with clear communication at each stage. The assignment was relevant and fairly scoped, and feedback/updates were timely. However, the evaluation timeline after submission felt somewhat unclear, and more transparency on expected review duration would improve the candidate experience
Interview questions [1]
Question 1
One question that stood out during the interview was about how I would design a system to handle concurrent requests safely while maintaining performance under high load. They were particularly interested in how I would approach thread safety, resource sharing, and avoiding race conditions in a real-world backend service.
Good, in depth technical questions and detailed analysis. Attention to detail to the problems given. technical knowledge needed spans several technologies and use cases. Ample time was given and felt very comfortable.
Interview questions [1]
Question 1
What are you long term goals and how are you pursing them?