The name’s Divyendra Patil but everyone refers to me as “Div” (Like the HTML tag). I’m fine with that. There are very few people who can spell my name properly and I’m very happy if you can do it. It basically means you have a good sense of pronunciation.
I used to write a lot on quora but after gaining 4.5 million views and 3.5k+ followers in a year, I deleted my profile since I didn’t think it was worth writing anymore.
But hey, I can do tech writing.
So here are some key things I learned about bombing my final round at google for an SRE.
- You will be judged on your competitive programming skills than your knowledge of Linux and systems.
- You should be able to communicate the code you have written properly to the interviewer.
- The 5-hour interview is tiring, practice it with people.
- Practice whiteboarding.
- Be ready to accept failure.
- Your interviewer can be an asshole and will try to destroy your confidence, be calm AF.
- If you have to prepare for the interview, means you are not yet ready for google.
- I lost 6kgs of weight in 3 months in preparation, don’t do it.
- Try to interview in sunny vale, Philadelphia, etc Interviewing in 3 degrees Celcius in NYC is not fun at all.
- Don’t be depressed if the hiring committee does not go forward with an offer.
- The starting salary of an SRE (University Graduate) is $1,28,000 base salary. Don’t do it for the money. Do it for the learning and impact.
- SRE was invented at google and I would have killed to be one and grow over there.
- If you are experienced, you will have 5 rounds + lunch. 4 coding and 1 system design.
- Google is not the end of the world.
I am an SRE in the DevOps team @ CB Insights where I work with some very smart, young and talented people.
Welcome to Site Reliability Engineering where hope is not a strategy and accepting failure is not one of our traits.