I applied online and had a brief chat with a recruiter going over my background. A technical phone interview was arranged for about a month after this initial call. Ten minutes before the call was scheduled, I was notified that it would not be proceeding and would have to be rearranged. The rearranged call took place the next day.
The caller had a very poor phone connection with lots of echo, presumably they had put me on speakerphone in a meeting room. I mentioned this but was told there was no time, and we had to get straight into the coding (the interviewer phoned five minutes late, so there was not any time for introductions, etc.). The questions are purposely open-ended, allowing you to ask clarifying questions. This was difficult as we could not hear each other properly. Sometimes I would ask a question and get no answer; other times, I would have to ask the interviewer to repeat themselves due to the line dropping. If I spoke for too long at a time, there was too much echo, and I would have to stop. The questions themselves weren't too difficult, but we ran out of time.
Overall, it was quite a negative experience, considering I had to take an extra day off due to the cancelled call, only to then receive the call late and in an unprofessional environment.
Find the last digit of the nth Fibonacci number.
The following metrics were computed from 47 interview experiences for the Google Software Engineer role in London, United Kingdom.
Google's interview process for their Software Engineer roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in London, United Kingdom.