Engineer applicants have rated the interview process at Google with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 92% positive. To compare, the company-average is 74.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Engineer roles take an average of 23 days to get hired, when considering 13 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 30 days.
Common stages of the interview process at Google as a Engineer according to 13 Glassdoor interviews include:
Background check: 17%
Other: 13%
Skills test: 13%
IQ intelligence test: 10%
Phone interview: 10%
One on one interview: 10%
Presentation: 10%
Group panel interview: 7%
Personality test: 7%
Drug test: 3%
Here are the most commonly searched roles for interview reports -
There were 4 rounds, the first round was easy and i cleared it but the second and third round were coding and system design rounds which were a little hard to clear. The coding problems I was able to finish on time but the system design interview didn't go very well
Interview questions [1]
Question 1
Where and what do you see yourself contributing here
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?