Initially, I received an email to set up a time for a phone interview. This email contained about 10 questions that they said would be discussed.
The following week, I had the behavioral interview, and we discussed the questions that were emailed to me. At the end of the behavioral interview, the recruiter said he wanted to move forward and mentioned he would have the engineering department email me to set up a technical phone interview.
Within a few days, the engineering department emailed me to set up a time, and the interview was scheduled for the following week. The technical interview was conducted over the phone, and Google Docs was used to code answers. An actual engineer who works at Google would type out the questions, and I would type in my solution while attempting to talk them through it. They want you to explain your process and thinking as you are working on the solution.
The interview lasted approximately 45 minutes.
A few days after the technical phone interview, the recruiter called me and informed me about my performance during the technical interview and the reason they were not moving forward, which I respected and felt okay about.
Overall, the recruiter was very nice and transparent throughout the process, so you should feel comfortable asking them any questions you may have.
Code: Convert the given numbers in hex to the equivalent integer number.
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.