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 through a recruiter. The process took 3 weeks. I interviewed at Google
Interview
I was approached by Google through their foobar challenge. I thoroughly enjoyed working through the levels of the challenge (I got through level 4) and actually learned few things in the process. But everything after that was pretty terrible.
First, through all of the exercises in the challenge, I had already provided them several hundred lines of code that I had written specifically for Google. But then they still wanted me to do a phone interview with a virtual 'whiteboarding' session. Which basically amounts to writing code in a Google Doc. Which is something I have never done, and never will do ever in any real life situation.
I have written code almost every working day for the past 20 years, in a variety of different languages. I have designed and led teams building web applications with dozens of classes and thousands of lines of code. But I have never written code in a word processor program. So in the phone interview I was pretty slow, and due to that slowness the interviewer concluded that I did not know how to implement a fairly simple Java class. It was demeaning experience and a complete waste of my time.
Interview questions [1]
Question 1
Implement a Java class that read a log file from a web application. The log contained data about how users interacted with a specific feature in the application. The task was to build a method that collected some simple statistics on that data.
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.