Senior Software 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 56% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 31 days to get hired, when considering 250 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 38 days.
Common stages of the interview process at Google as a Senior Software Engineer according to 250 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 24%
Skills test: 17%
Presentation: 7%
Group panel interview: 7%
Personality test: 6%
Background check: 4%
IQ intelligence test: 3%
Other: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied in-person. The process took 5 weeks. I interviewed at Google
Interview
Recruiter was very compassionate and professional through the overall process all the way until conveying that reject decision.(Got some specific feedback on nitpicked issues on mistakes made and some complements). Overall the experience feels like a big machinery(It is GOOGLE come on! ) churning through the huge number of candidates to prove themselves they believe they can hire only who are star software engineers (who can code like a machine as if coding is the singular aspect of software engineering and makes no mistakes in the first attempt). A mix of some friendly and some intimidating jerkish engineers. One interviewer used some intimidating words ('Be careful') whenever he thought there was a mistake in an interface I was asked to define, a guy who said 'we have already done this', pulled of shaking hands with me in a rude way (I accidentally had done the gesture apparently already once), couple of cases the English language of the engineers who interviewed were bad enough that I could not understand their question or not sure if they understood my analysis when he/she gave feedback. Overall, the process felt the engineers want to prove why those engineers are in Google( and why they are convinced that these interviews ) and why most others coming into interview should not be. In one case, another employee was annoyed that my interviewer was staying in the conference room too long when he was banging the door. So, when we came out of the interview the other guy started yelling that he had to wait so long and could not get into his meeting. At the end of the interview came out with the feeling this place has more baggage of bad personalities and churn of the mill imperfect humans instead of 'I want to work at the places where all modern complex distributed systems problems where solved impacting average person in the world.'
The process consisted of four technical problem-solving interviews and one "Googleness" and leadership round. The first technical interview started off relatively easy but quickly dove deeper into complex edge cases. The second interview increased in difficulty.
Interview questions [1]
Question 1
it was 4 problem solving interview and one googleness
Initial intro call, prep time , prep material provisions,
1 Phone Screening by HR, 3 DSA, 1 HLD and 1 Googliness, Team matching and offer negotiation and offer discussion , offer acceptance
After clearing all the interviews in 2 months, here comes the team match. Where no one ever knows when they gonna get a team match call. Even if you get the TM call next comes the HC again no one knows why they reject.
Interview questions [1]
Question 1
Coding questions from Leetcode google tagged but deep dived into it based on the level.