Candidates applying for Developer roles take an average of 21 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 38 days.
Common stages of the interview process at Google as a Developer according to 1 Glassdoor interviews include:
One on one interview: 33%
Skills test: 33%
Phone interview: 33%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 5 months. I interviewed at Google (London, England) in Jan 2014
Interview
*I am not english native speaker.
I applied online and get first non-technical call in a month. Then was 3 technical calls. I think I failed 2th. After each call I got feedback in a week.
After third call, I was invited to onside interview in London.
It took 2 months after last call to onside interview.
**I am not from GB. I had to get a visa to come to onside interview.
There was 5 interview + dinner. Dinner was with the man that was not only from my own city and speak my native language, but he also worked in the same company as me before relocate. It was really nice surprise.
Interview questions [1]
Question 1
All questions I already saw in Internet: leetcode, careercup. 4 was about algorithms, 1 for design. No more details - NDA.
I applied through a recruiter. The process took 4 weeks. I interviewed at Google (Mountain View, CA)
Interview
First phone interview was short and very easy -- basic questions about data types, complexity, concurrency. Second phone interview did not happen: interviewer got sick and did not warn the recruiter. After struggling to reschedule for about a week they decided to skip that phase and do an on-site interview.
Onsite interview consisted of five rounds 45 minutes each. Most of the interviewers gave one large problem and kept me polishing the solution until the time ran out. I did not really get a chance to ask a lot of questions about the company (just asked two and answers did not really amuse me).
I don't remember the most difficult problem, but two largest ones were: write `Game Of Life' (not in pseudocode, in Java!) and write a procedure that draws a line in a bitmapped array (again, in a real programming language). That had to be done on a whiteboard (side note: while I has writing interviewers were copying my solutions into their notebooks by hand). All problems throughout my interview included questions about complexity and some included questions about optimization and testing.
I got a feeling that the work is challenging from technical point of view, but the interview process seems quite ridiculous (especially writing substantially large programs on the board) and most interviewers' attitude can be described as `quite arrogant.' I did not get any background on the company and its nature of work I throughout the interview process and did not feel frustrated when they did not proceed with an offer.
P.S. One tiny upside, their recruiters are the best: prompt, good at personal communication and very organized.
Interview questions [1]
Question 1
I don't remember the most difficult question, it was something along the lines of computational complexity, but I got two really long problems (see review).