I was contacted by a recruiter asking if I was interested in working at Google and scheduled a phone interview.
The first round was a recruiter screen with basic Unix/Linux commands, which went well.
The second interview was more technical. It included topics from networking, TCP/IP protocols, RAID, etc. They would dig a little deeper as you kept answering. It ended with writing a program in a language of your choice. I chose Perl.
The third phone screen was mostly focused on data structures and algorithms, which required coding in C or Java. It included the implementation of hash tables and binary trees, and more open-ended questions. The third interviewer seemed to be hurrying and did not give much time to think, perhaps because I failed to answer the first question correctly.
Overall, it was a good experience.
Implement a hash table.
The following metrics were computed from 1 interview experience for the Google Site Reliability Engineer role in Dublin, California.
Google's interview process for their Site Reliability Engineer roles in Dublin, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Site Reliability Engineer interview process in Dublin, California.