I was contacted by a Google recruiter. After a brief behavioral phone screen, in which she asked about my background and interests, she invited me to apply to the Software Engineering Internship once the job was posted. She also provided me with resources on how to prepare beforehand.
A time to take the Online Assessment (OA) was quickly set up. As it was my first real interview, I pushed back the date further than necessary and overprepared. The questions were very easy (two questions in 90 minutes) and seemed like a way to weed out applicants with no coding knowledge, rather than a real test of coding aptitude.
Soon after, I was asked to schedule two phone interviews back to back. The first one went really well, but the second one was significantly more difficult, and I was not able to solve the problem in time. Luckily, I was asked to give a third and final phone interview roughly a week after the first two. I scheduled this one for two weeks from when I was contacted. Two weeks later, I received a call from my recruiter saying that unfortunately, they would not be moving on with my application and suggested I apply again next year.
Throughout the process, the interviewers and recruiters were very helpful and friendly. Recruiters never took longer than two business days to respond to any email.
Given a list of lists as input, return every unique combination that can be made by taking one element from each list.
The following metrics were computed from 482 interview experiences for the Google Software Engineer (Internship) role in United States.
Google's interview process for their Software Engineer (Internship) roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer (Internship) interview process in United States.