A recruiter contacted me to interview with Google again, and we set up a phone screen approximately a month after the initial call. During that initial call, I was asked simple questions about my current job, what I do, what I'm interested in doing at Google, and so on.
On interview day, an engineer from Seattle called me pretty much on time. He introduced himself and told me what he did there. Afterwards, we went straight to the question, and I spent some time working on it. When I finished, he asked if I had any questions for him, and then that was it!
I felt like I did okay, but then realized I made a lot of mistakes as I thought about it more. So, I expected a "no" when I got a callback. The major problem I was having with the whole process was the wait for the callback. I interviewed at the beginning of June and didn't get a call back until July. What made this crazier was that my roommate interviewed with them as well and got a call in two days! To get this call, I needed to contact my Google friend and ask if this was normal, which it was not. He pulled some strings, and then I finally got the call with my expected result.
Overall, the process was okay. The wait for results was a little absurd, though.
John Conway's Game of Life
Implement a method that updates the game board to its next state.
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.