The interview process was quick, both before and afterwards. I applied online and was recommended by a friend.
However, the experience was a very sad one. While I was describing the first solution that came to mind, I admitted that it was not the optimal one. The interviewer asked me to write it anyway. I started to write the code, and after three to four minutes, I realized what the optimal way to do it was. I asked twice if I should write the optimal solution, but the interviewer insisted I write the first one. After finishing the first solution in about 20 minutes, he thanked me and left the interview.
(P.S. I copied my C# code into Visual Studio and it executed perfectly fine, with not even a single error. It was just not the optimal solution, but again, he insisted that I should write this one.)
While writing the code, the interviewer seemed busy with other things and didn't even hear some of my explanations. The most weird moment was when he was interrupted by someone else in the office, who asked how much time it would take us to finish. He answered, "About five minutes," but they were talking for less than 15 minutes.
I received a rejection email by the end of the same day with the classic "You are good and experienced, and bla bla bla, but you are not a fit for the moment."
Anyway, I was expecting a professional interview at Google, but it was not, not even close.
Display all the numbers from 0 to 1000000.
All the digits of a displayed number should be different.
The following metrics were computed from 80 interview experiences for the Google Software Engineer role in London, England.
Google's interview process for their Software Engineer roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in London, England.