Site Reliability Engineer Interview Experience - Mountain View, California
Process
The interview process was really smooth. After a couple of phone interviews with HR and engineers, I was invited to the HQ in Mountain View.
An onsite interview and a lunch with a Google engineer (I was told he is not going to submit a review).
It started out in the morning; I was greeted by the HR employee, and he took me to the building where I would be the rest of the day. Then, one by one, interviewers came and asked me questions. Most of them quickly jumped on technical questions rather than my previous experience. So, expect to spend most of your time on coding questions rather than talking about your resume.
Questions
I signed an NDA, so I can't say anything about that.
The only thing I can tell you is to prepare on Data Structures and HashMap/Hashtable questions. It is really helpful.
Was this helpful?
Interview Statistics
The following metrics were computed from 25 interview experiences for the Google Site Reliability Engineer role in Mountain View, California.
Success Rate
Google's interview process for their Site Reliability Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Site Reliability Engineer interview process in Mountain View, California.
Google Work Experiences
- 5.0Lots of interesting problems and chances to grow if you work at itSite Reliability Engineer • Current EmployeeMountain View, California, United StatesJune 17, 2008Pros: You get to work on some of the biggest clusters in the world on some very hard and interesting problems. The people are generally above average, and you always have to work to make sure you're doing better. For the most part, it's a very strong meritocracy.Cons: You might not get assigned to the groups doing the really cool things. It must be very frustrating to want to do, e.g., large-scale graph algorithms (think maps) and be stuck doing HR programming or JavaScript. Though, after 18 months, you can move to any team you want if they need engineers (and you're performing). The infrastructure is getting complex enough that there is a huge ramp-up time. While that means that it takes a while to launch a project for the first time, if you know what you're doing, you can launch a very scalable project quickly.
- 5.0Great Balance, Slow DevelopmentSite Reliability Engineer • Current EmployeeMountain View, California, United StatesOctober 31, 2024Pros: Good work-life balance provided.Cons: Slow development process because it’s a big company.
- 4.0One of the best places in the world to workSite Reliability Engineer • Former EmployeeMountain View, California, United StatesMay 1, 2009Pros: It's a company with a conscience, and the Dilbert-esque moments are rarer than at other companies. Plus, the food is *amazing* (at least in the larger offices).Cons: Long hours, high stress. Depending on which part of the organization you are in, expectations can be wildly different for the same job level. Promotion is a very tricky path and is done by committee. Decisions from them seem arbitrary and hard to justify. It seems to have become an unwritten rule that not seeking promotion over a 2-3 year period is unacceptable.
Google Interview Questions
