Google Site Reliability Engineer interview questions

Google has a long process. I've interviewed with them several times before, the occasionally refresh their past candidates and call them back. The last time i spoke to them was about 3 years ago. The recruiter emailed me and asked to chat with me again, thru this process they explained the phone interviews that would be done, the skills assessment/packet preparation, then the onsite panel interview. Then the panel participants submit written feedback to a committee who makes the decision. You never speak to the people making the decision, sometimes this causes a loss of fidelity between who is being spoken to and who is making the decision. I don't care for the in-personal approach of never talking to the decision maker, but google is reported to be a good employer.

Was contacted by recruiter on Linked In. Scheduled a phone call with the recruiter who asked me basic programming questions. I was then passed on to another recruiter who scheduled a technical phone interview. There are two tracks in SRE, programming and system administration. I interviewed through the programming side. During the technical interview I had to answer specific questions about queues, graphs, and distributed architecture. I have 12 years experience programming, managing people, products, and projects. They do not care about any of that stuff. At the phone stage of the interview, they are screening folks for technical knowledge and ability. All they care about is whether you know the methods and tricks to solve technical programming problems. Know your data structures. The interview process builds from simple to complex, based on your previous answers. If you really want to work at Google as an SRE, study algorithms, algorithm analysis, and memorize as many methods and tricks to solving programming problems as you can. Bonne chance!