ws with engineers; both of them consisted of one soft question and one programming problem. I wrote code in a Google Docs document that was shared between me and the interviewer. Before the interviews, the recruiter provided a wealth of preparation materials. The final stage was an onsite interview at a Google office. Google paid for travel and lodging, and was very flexible in scheduling the flight. There were four 1-hour interviews, each with a different programming problem and a few follow-up questions, with a lunch break in the middle. To write the code, I could use a whiteboard or a Chromebook that was provided. When I forgot a detail about a method of an STL container, I was allowed to pull up a reference page. There was a focus on doing things in an algorithmically efficient way; I was usually asked to estimate the complexity of my code, and come up with improvements if my initial solution was not optimal. Open source experience proved very useful, as I was able to provide in-depth answers to soft questions. After

Informal. Telephone interview followed by in person interviews with management/peers. This process took about 30 days, so don't be in a hurry. The interview process itself is relaxed, but serious. Don't be surprised if people "drop in" during the interview and ask a few questions…or if new names are added to the interview panel at the last minute.