Hi, Im Michael Kehoe and this repository is a collection of Site Reliability Engineer (SRE) interview questions and answers. Please feel free to share or send me PRs with answers or new questions
How to Prepare for Site Reliability Engineer ( SRE ) Interviews | SRE Interview Questions
Interviews for Top Jobs at Microsoft
Site Reliability Engineer Interview
I applied through a recruiter. The process took 1 day. I interviewed at Microsoft
Interview
It was a very good experience. Interviewers were encouraging and kind. I had 4 technical questions, mostly LC easy or medium. It was my first technical interview and a smooth experience overall.
- What would you do if you saw error message X and you’d never seen it before?
Site Reliability Engineer Interview
I applied through a recruiter. The process took 2 months. I interviewed at Microsoft (Noida) in Jul 2021
Interview
First round was codility Test with two questions ranging from medium to high coding skills.After clearing codility test 2 coding interviews were taken virtually through MS teams. Then 4 technical screening and culture fitment round help with other SREs, Hiring Manager and Leadership team,After clearing them, recruiter reached out for salary discussion and offer is made.
- 2 hacker rank coding problems.2 coding interviews4 technical and cultural fitment interview
Site Reliability Engineer Interview
I applied through a recruiter. The process took 4 weeks. I interviewed at Microsoft (Hyderābād) in Apr 2019
Interview
1)Technical round – -> In person interview2)Technical round – Depth -> In person interview3)Another technical – Done by hiring manager -> telephonic4)Again Technical – telephonic5)Techno managerial – telephonicMicrosoft tests a person in various levels and in multiple rounds.They try to analyse especially if you are good at doing the below1)In depth understanding of the system architechure2)360 degree knowledge on domain/tools3)Very good at data structures4)Ability to write any programming (Java/.net/Python/Perl) with oops concepts 5)strong understanding with Cloud concepts providing End to end solutionsMy interview experience with Microsft was very good and the recruiter responses were always prompt.All the interviewers are very much friendly and the experience is worth learning.If they believe that you can make a change with your work you will be in. Since they have such a long hiring process involving so many people,I felt the decision making should not be based on one “single round”. If a member who is highly influential in a team flags a “no hire” you are done. Interviewers everytime may not be free enough to assess your skills in a right way.I was interviewed in a hurry by a very good techie (since my interviewer is fully occupied with meetings,he didnot show interest to listen my answers)who passed a -ve feedback. So please make sure of the interview timings as well.
- High availability,Containerization,CI/CD
– Is there a typical loop rounds for SREs in Microsoft? – What to expect in the coding rounds? Is it more of leetcode problems? – Hows the SRE culture, is it a mere support role? – Finally, what the salary range and level can be expected? JD says Sr. SRE. I can tackle linux internals, system design, kubernetes, infra/network and other DevOps/Security verticals. But not a leetcoder, can write scripts/tools, but more of practical problems (ex: custom prometheus exporter, file parser, infra management etc.,) but would flunk the leetcode type of questions. So, please help with the interview process or type of questions to prepare. Location: Hyd, India YOE: 10 TC: 75L (cash:60, esop:15) Note: To avoid doxing, cannot reveal the current company name, its a startup.#Microsoft
Hi, Im Michael Kehoe and this repository is a collection of Site Reliability Engineer (SRE) interview questions and answers. Please feel free to share or send me PRs with answers or new questions
Scenario 1: Removing toil through automation
Site reliability engineers and others who use SRE practices attempt wherever possible to remove toil. “Toil” means a specific thing in SRE. Toil refers to operations work being done by a human that has certain characteristics. Toil has no long term redeeming value. It doesnt move the service forward in any meaningful way. It is often repetitive and largely manual (even though it could be automated). As the service or systems gets bigger over time, the number of requests for that system will also probably increase in quantity at a proportional rate and require even more manual labor.
For example, if a service requires the SRE team to reset something every week, or to provision new accounts and disk space by hand, or repeatedly restart it by hand–this is operational load that is toil. Completing those actions hasnât made the service better in any long-term, persistent way. These actions will likely have to be repeated over and over.
SREs hate toil. They work to eliminate it whenever possible and appropriate. This is one of the places automation comes into play in SRE. If these requests can be handled automatically, that frees up the team to work on more rewarding and impactful things.
Coding expertise: automation requires some coding expertise, but it does not have to require full software engineering skills. If you can write small scripts (perhaps in PowerShell or Bourne shell) or even if you create an Azure logic app with barely any code, this app can still help eliminate toil.
FAQ
How do you prepare for a SRE interview?
- Test your technology. You’re in a technical field, so you know the basics, but it never hurts to do a test run. …
- Create the best environment. …
- Look your best. …
- Be ready to answer hard questions. …
- Make your own list of questions.
What type of questions are asked in SRE interviews?
- How can an organization improve its observability? …
- Can you explain what SLO means and why it’s important? …
- What is cloud computing? …
- How can you improve the relationship between operations and IT teams?
What is SRE Microsoft?
What are SRE interviews like?
