First, a remote coding exercise in Google Docs. It presented one problem, followed by a second, more involved one. The code written was supposed to compile without errors.
Second, an on-site coding session on a whiteboard. This again involved writing real code, followed by a discussion about improvements, complexity, and so on.
Some optimization, analytical geometry-based.
The following metrics were computed from 5 interview experiences for the Google Software Engineer role in London, undefined.
Google's interview process for their Software Engineer roles in London, undefined is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in London, undefined.