Process
Phone screen followed by an onsite interview.
I was asked, "What is an RPC call?" I cited a form of IPC followed by a number of examples. I thought my answer was sufficient, but they were looking for something outside of the client/server model specific to Java RPC stub calls and such. I found this odd, given that Java development wasn't my forte.
Questions
There wasn't any question that was overly difficult. They were looking for a developer mostly, and I just wasn't at that level. It's not clear how they separate SRE from DevOps to Developer.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Google SRE role in New York, New York.
Success Rate
Google's interview process for their SRE roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Google's SRE interview process in New York, New York.
Google Work Experiences
- 5.0So far so good!SRE • Current EmployeeMay 29, 2025Pros: Good balance, perks, and pay.Cons: nothing to add here !
- 3.0Save up, burn out, move onSRE • Former EmployeeSeattle, Washington, United StatesFebruary 27, 2020Pros: You can learn how to do big IT things right by watching people do it wrong at scale.Cons: Too many strongly opinionated geniuses around.
- 5.0Experience at GoogleSRE • Former EmployeeMountain View, California, United StatesSeptember 19, 2016Pros: The extra perks, such as a gym and good food, are really good. The benefits and free transportation to work are a plus working for Google.Cons: Google is a very big company with really smart people in its teams. Improving the levels is really hard unless you are a pro.
Google Interview Questions
