I asked a friend for a referral, and HR was persistent in helping me with the interview. That was the only best part.
I felt like I was in school. HR didn't ask me once what projects I was into. Instead, they asked me to pick a coding language, algorithms, data structures, more algorithms, and Linux internals.
I was told the job demands 80% coding work every day, which is fine. But the interview process felt like a grilling session focused only on algorithms and data structures.
In the end, after asking questions (she conducted an assessment), HR said she was just a messenger.
Honestly, Google, one can just take off, prepare only for data structures and algorithms for three months non-stop, give your interview, and crack it.
I'm sorry, I'm not just a day-to-day LeetCoder.
Is this the expectation?
Disappointed.
DS algo complexities and Linux internals (deep dive into file, process handling, and memory management)
The following metrics were computed from 1 interview experience for the Google SRE - Site Reliability Engineer role in New York, New York.
Google's interview process for their SRE - Site Reliability Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Google's SRE - Site Reliability Engineer interview process in New York, New York.