Junior Software 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 63% positive. To compare, the company-average is 74.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Junior Software Engineer roles take an average of 1 day to get hired, when considering 8 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 Junior Software Engineer according to 8 Glassdoor interviews include:
Phone interview: 17%
Drug test: 17%
Presentation: 17%
One on one interview: 8%
Group panel interview: 8%
IQ intelligence test: 8%
Other: 8%
Background check: 8%
Personality test: 8%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. I interviewed at Google (Hyderābād)
Interview
The Google job interview process typically begins with an online application, followed by an initial screening that may involve a phone call or online assessment. Successful candidates proceed to technical phone interviews, on-site interviews covering technical and behavioral aspects, and a team-matching phase. Reference checks and a background check are conducted before extending a job offer. Throughout, Google emphasizes technical skills, problem-solving abilities, and alignment with the company's culture and values.
it was very smooth and good mostly behavioral then went into deep technical skills mostly from leet code and hardest and very hard but as long as your prepared uou should be good
During my Google interview for the junior role, the focus was on practical problem-solving and foundational knowledge. I was asked to debug a REST API endpoint with authentication issues, implement an in-place linked list reversal, and discuss how I’d design a small but scalable feature for Google Maps. The interviewers emphasized clean code, efficiency, and clear communication of my thought process. While challenging, it was a great learning experience that highlighted the importance of both technical skills and collaborative problem-solving.
Interview questions [1]
Question 1
Debug a function, Reverse a String, Explain how I’d store user passwords
Good it went well good questions were asked but i haven't said anything as the level of questions were hard for me so prepare carefully and all the best NA NA NA.