0-2 years experience ~3 hours 8 Topics
Checklist covers Reliability concepts, Monitoring and alerting, Incidents and on-call, Linux and networking, Kubernetes and delivery, Databases, caching and queues
This pack is for candidates going for a Junior or Associate SRE role. Interviewers at this level do not expect years of production scars.
You should be able to answer each item in one or two sentences. If you cannot, mark it and study it before the interview.
Q1. What does an SRE do day to day? An SRE keeps services reliable by combining operations work with engineering.
Q11. A Pod is in CrashLoopBackOff. How do you investigate? CrashLoopBackOff means the container keeps starting and crashing. Find out why it exits.
Q21. What is a database connection pool, and how can it cause an outage?
Scenario 1: Latency Doubled After a Release The Prompt At 14:05 your team deploys a new version of the product API.
Interviewers want real, short stories using the STAR pattern: situation, task, action, result.
These figures are indicative annual ranges in lakhs, and they vary a lot by company, city and market. Use them as a rough guide, not an offer.
This pack is for candidates going for a Junior or Associate SRE role.
You should be able to answer each item in one or two sentences.
Q1. What does an SRE do day to day? An SRE keeps services reliable by combining operations work with engineering.
Q11. A Pod is in CrashLoopBackOff. How do you investigate?
Q21. What is a database connection pool, and how can it cause an outage?
Scenario 1: Latency Doubled After a Release The Prompt At 14:05 your team deploys a new version of the product API.
Interviewers want real, short stories using the STAR pattern: situation, task, action, result.
These figures are indicative annual ranges in lakhs, and they vary a lot by company, city and market.
Roles this pack prepares you to interview for.
Site Reliability Engineer (SRE)
Rs 6L - Rs 14L a year
Not a software engineer sheet. Every problem comes from real DevOps, SRE, Platform and Cloud interviews, from your first script to a system you build yourself.
Open the Coding SheetIt is for candidates with up to about two years of experience, or those moving into SRE from support, system administration or development. It assumes basic Linux, networking and one cloud or Kubernetes exposure.
The question bank groups concept questions by difficulty. This pack follows a full interview loop with a fundamentals checklist, real questions, scenarios, behavioral questions and salary notes.
Plan on about two hours: read the checklist, work through the questions, and talk through each scenario out loud before reading the ideal solution.
Move on to the Mid-Level SRE pack once you can answer the scenarios without notes, then the Senior SRE pack for design and leadership questions.