How to prepare for an SRE interview? Find all the answers in this guide curated by an expert SRE. Learn about the role, preparation strategy and skills needed.
Blog
Google is the mother of SRE as a concept and as a role. Not too long ago (in 2003), an engineer named Benjamin Sloss realised that Google’s reliability needs were larger than usual. To boost the company’s user experience, they needed minimal downtime and latency.
That’s when Sloss thought - “hey we need a specialised team for this!”💡
This is how the world’s first SRE team was created. Now every single tech company recruits for this role. And startups are no exception to this.
“SRE is what happens when you ask a software engineer to design an operations team.”
- Benjamin Treynor Sloss, Vice President, Engineering, Google
Working as an SRE at a hypergrowth startup or a ‘soonicorn’ can be absolutely life-changing and lucrative. As you might know, startups are full of new technical challenges. If you are a die-hard problem-solver like me, you’ll be happy that you chose a startup to work at in order to strengthen your skill sets.
In this guide, I am going to take you through an in-depth interview prep roadmap of the SRE role, that will give you valuable insights on:
By the way, I’m currently building interview preparation solutions for candidates such as yourself. If taking a mentorship-driven interview preparation approach sounds interesting to you, do look us up!
In the role of Site Reliability Engineer, the notion of reliability takes precedence. An SRE ensures that software, once deployed, is absolutely reliable. This person works on improving and automating the operations cycle.
SRE as a team defines operational processes.
And as rightly stated by Sloss,
“An SRE team must spend at least 50% of their time doing the actual development work.”
So, one would think, isn’t it just a fancier name for IT developers? No, it’s not. As an SRE, two things are the most crucial for you:
Here are the top 5 responsibilities of an SRE:
So, as you might have guessed by now, an SRE is someone who is in demand in every company that has or is planning to have a fully functional development team.
Now let’s get to know how SREs get hired.
Top-tier startups have now adopted an interview process for SRE that is similar to that of FAANGs or any other tier 1 and 2 tech companies. The newly budding and soon-to-approach hypergrowth startups, however, still seem to have a less streamlined approach to interview processes.
Here’s the step-by-step SRE interview process that is usually followed at top-tier startups such as Flipkart, MobiKwik, Nykaa.com, Swiggy, etc.:
Clearing all these rounds might take around 6 to 8 weeks.
Some minicorns and soonicorns follow this interview process for SRE roles:
These interview rounds may wind up sooner than the unicorn startups, approximately within 4 to 6 weeks.
No matter what startup you’re applying at, you might want to take prompt follow-ups and feedback with HR or your interviewer through LinkedIn and email (or call if needed). This conveys your genuine interest in a company and the role you’re applying for.
Here are the top 6 topics you should start brushing up on right away if you’re preparing for an SRE interview.
I've given a detailed topic chart below for your reference.
Now, to the most important part - the interview preparation strategy.
At Preplaced, a platform where we’ve helped 2,000+ candidates get placed in their dream companies, we follow a similar but personalised strategy for our SRE interview preparation program.
Let’s see what that winner strategy is.
Ideally, I would suggest giving your SRE interview preparation a 2-month timeline.
As the first and foremost step, I recommend that you get your basics right.
Speaking of boo-boos, here are some of the common mistakes I’ve seen a lot of candidates make. You definitely want to steer clear of those.
Not at all. DevOps teams focus on core development that supports speed, quality, and control. A DevOps engineer is constantly thinking of development, whereas, an SRE is busy working on improving the development cycle.
(Image source: https://nevkontakte.com/2020/wtf-is-sre/devops.jpg)
Not necessarily. Being a DSA expert is not mandatory. Having basic or moderate-level knowledge of DSA is enough.
Not true. In an SRE role, there are 50% of development and 50% of reliability functions involved. So, if you want to transition from DevOps to SRE, that’s the most ideal. However, if you’re currently working as a developer, you can still apply for an SRE role.
The role of an SRE combines architectural, development-related, and operational duties. It is never just operational. DevOps roles surely have more operational duties to fulfil than an SRE.
Interview preparation for this role is not paid much heed, but that’s where we’re going wrong. Being methodical in your approach and investing time in consistent efforts can actually get you placed in your dream company.
The role of SRE is an ever-evolving one. The way you, as a candidate are unique and come with your own distinct skill sets, every startup has its own different needs when it comes to hiring for an SRE role. So, try to understand the reliability needs of your target companies in detail.
Build rapport with the interviewers from day one. Connect with as many like-minded techies as you can. The power of networking and communication is potent.
And lastly, don’t shy away from asking for help when you’re preparing. If you’re feeling stuck in your interview preparation journey, you can always connect with our mentors and seek consultation. You can also connect with me on LinkedIn if you want. I’d be happy to help you out.
If you liked this interview preparation guide, I’m pretty sure you’ll like my YouTube video where I discuss this strategy and some SRE interview preparation tips in depth. Do check it out here.
Copyright ©2024 Preplaced.in
Preplaced Education Private Limited
Ibblur Village, Bangalore - 560103
GSTIN- 29AAKCP9555E1ZV