Candidates applying for Sr Developer roles take an average of 30 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 39 days.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Google (Newport Beach, CA) in Dec 2008
Interview
After a phone interview and an engineering interview in which I wrote code in a Google doc while talking with the interviewer, I was invited in for a face to face. I met with about twelve engineers and managers over eight hours with a break for lunch. They asked very tough questions and really dug in to see how you think.
Interview questions [1]
Question 1
They gave me printouts of a couple of classes that worked together but were badly designed. The goal was to talk about how to better design the classes so they had clearer roles and better implementation.
The process took 4 weeks. I interviewed at Google (Chicago, IL) in Dec 2011
Interview
The interview started with a non-technical phone interview with a recruiter -- easy, standard stuff. A week later was a technical phone screen. We had a shared Google Doc and I had to implement a HashMap. Up until now, things were ok.
I had some issues with how the in-person reviews were run. Most of the questions were reasonable, but the interviewers clearly lacked any sort of experience in running an interview.
I applied through a recruiter. The process took 3 months. I interviewed at Google in Dec 2011
Interview
There was an initial phone screen to cover fit and possible openings. This was cultural and focused on achievements as well as communication skills. Then there was a long gap to schedule an in person technical round. This consisted of a few engineers and was very technical. There was no strong communication of expectations of the role and the title and many groups spoke. Another round of interviews happened two months later and it was the same process with vague communication of possible roles.
Interview questions [1]
Question 1
How do you design a high-write, high-read database.