I applied through an employee referral. I interviewed at Google (New York, NY) in Aug 2016
Interview
I was brought into the New York City office for five forty-five minute problem sessions, one with two interviewers, and the other four with only a single interview. In each, I was asked to solve a technical problem, writing my software solution onto a whiteboard, this program complete enough to actually run. I was not able to complete solve all five of the technical problems I was given.
I applied online. The process took 2 months. I interviewed at Google (Mountain View, CA) in Jul 2016
Interview
One phone interview, about 45 minutes. My recruiting contact sent me preparatory materials and explained the process beforehand. Interviewer opened by asking about a project on my resume; rest of the time was on a couple technical problems. I wrote code in a shared Google Doc while talking on the phone. Questions required writing algorithms involving bit manipulation.
Google flew me to Mountain View for on-site interviews after I passed the phone screen.
Four one-on-one on-site interviews, each ~45 minutes. Coding was done on a whiteboard. Three interviews were primarily on algorithms/data structures; the other involved OOP. Each interviewer had his/her own style, but overall atmosphere was informal and collaborative.
Interviews were back-to-back. After the first two, a different employee accompanied me for lunch and to answer my questions.
Interview questions [1]
Question 1
NDA on interview questions, but you are provided with lots of information about the types of questions you'll receive and how to prepare.
I applied through an employee referral. The process took 4 weeks. I interviewed at Google (New York, NY)
Interview
I interviewed in NYC. No phone screen because of my previous experience. Besides the convenience of the location, I did not enjoy the hotel I was put in. Ask for The Maritime if you get the chance. Interview day was very good overall. The system design question was about a field that did not match my background at all at I was a bit disappointed about that. Between review committees, team selection, and other stuff it took over a month to discuss the offer details. When it came to that phone call my recruiter refused to give me any details if I didn’t tell him my other offers first. I didn’t. This introduced other delays and put me in a very weird position with other companies that I was still interviewing with. I believe that Google prepared a 'low ball' but then refused to pitch it once I told them that some other players were in the game. The offer finally arrived while I was flying to California for another interview (I can’t just sit and wait after all). It sounded in the middle of the range that I asked for but when I received it in writings I realized that it was just below the lower range that we discussed. Let’s blame that on miscommunication or great presentation skills on their side. Google refused to negotiate those numbers at all in two different occasions and went in ‘radio silence’. By the time they got back to me checking if I wanted to continue the conversation I had already accepted another offer, quit my job, and took a flight to the other side of the world to enjoy my time off. I cannot believe that this did not work out. Google was my #1 pick at the time. No regrets.
Interview questions [1]
Question 1
You have a bunch of light bulbs. Store them as you wish. Implement a function that tells you if the light is on or off given its index and another one that toggles the state of the light bulbs given a start and end index. Good. Now, how about you have a gazillioon of those?