About two weeks after I applied, a Google recruiter reached out to me requesting a time and date for two phone interviews with current Google engineers. I scheduled these interviews for about two weeks after the recruiter contacted me.
Each interview was one hour long and focused entirely on technical knowledge and problem-solving skills. The first interview included six questions of medium difficulty, with each problem building on the previous one. The second phone interview featured one long, very involved, and tricky question.
At the end of both interviews, there were about five minutes for questions. The questions you ask do not affect your interview performance, but Google engineers are very passionate and love to talk about their work.
Overall, the process was relatively short, and the interviewers were extremely nice and accommodating.
I can't go into specifics because I signed an NDA.
However, upon being requested for an interview, the Google recruiter will provide you with a bunch of resources to succeed.
Know your basic data structures and some common coding problems.
Read through "Cracking the Coding Interview" that corresponds to what the Google recruiter said to know.
Be sure to talk through all of your problems and solutions.
Ask the interviewer whether your assumptions are correct and ensure what the exact solution should look like by providing examples.
Do all of this, and you should do very well.
The following metrics were computed from 120 interview experiences for the Google Engineering Practicum role in United States.
Google's interview process for their Engineering Practicum roles in the United States is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Google's Engineering Practicum interview process in United States.