Intuit Site Reliability Engineer Interview: Rounds, Questions and Preparation

What the job involves

Site Reliability Engineers (SREs) at global tech companies ensure that large-scale, customer-facing systems are reliable, scalable, and efficient. They blend software engineering with systems engineering to build automation, monitor services, and respond to incidents. Day to day, they write code to improve reliability, set SLOs, and collaborate with development teams to design resilient architectures.

Role and Technical Knowledge

1. 1

   What is the difference between SLI, SLO, and SLA?

   Define each term clearly: SLI is a metric, SLO is a target for that metric, SLA is a contract with consequences. Give an example like request latency or availability.

2. 2

   Explain the concept of error budgets and how they influence decision-making.

   Describe error budget as 1 minus SLO. Explain how it balances innovation and reliability, and when to halt releases.

3. 3

   How does Kubernetes help in achieving high availability?

   Cover self-healing, rolling updates, replica sets, and multi-zone deployments. Mention liveness and readiness probes.

4. 4

   What are the key differences between vertical and horizontal scaling?

   Contrast adding resources to a single machine vs adding more machines. Discuss trade-offs in cost, complexity, and fault tolerance.

Practical Scenarios

1. 5

   A service's latency spikes every day at 2 PM. How would you debug this?

   Outline a systematic approach: check monitoring dashboards, correlate with traffic patterns, inspect logs, and look for scheduled jobs or cron tasks.

2. 6

   You need to reduce cloud costs without impacting reliability. What steps would you take?

   Suggest rightsizing instances, using auto-scaling, spot instances for non-critical workloads, and reviewing storage lifecycle policies.

3. 7

   How would you design a monitoring and alerting system for a microservices application?

   Mention metrics (RED/USE), distributed tracing, centralized logging, and alerting on symptoms like SLO violations rather than causes.

4. 8

   Describe how you would handle a production incident where a database is overloaded.

   Focus on immediate mitigation (e.g., rate limiting, read replicas), communication, and then root cause analysis with a postmortem.

Behavioural and HR

1. 9

   Tell me about a time you had to troubleshoot a technical problem under pressure.

   Use the STAR method. Highlight your structured approach, communication, and what you learned.

2. 10

   Why do you want to work as a Site Reliability Engineer?

   Show passion for reliability, automation, and large-scale systems. Connect to your skills and desire to prevent outages.

3. 11

   Describe a situation where you disagreed with a teammate. How did you resolve it?

   Emphasize listening, data-driven discussion, and focusing on the best outcome for the team.

4. 12

   How do you prioritize tasks when everything seems urgent?

   Mention impact-based prioritization, using frameworks like Eisenhower matrix, and communicating with stakeholders.

Coding and Automation

1. 13

   Write a function to parse a log file and count the number of errors per hour.

   Demonstrate clean code, use of regex or string splitting, and handling of large files efficiently.

2. 14

   How would you automate the deployment of a service to a Kubernetes cluster?

   Describe CI/CD pipeline, using Helm charts or Kustomize, and GitOps principles with tools like ArgoCD.

3. 15

   Given a list of server response times, write code to calculate the 95th percentile.

   Show understanding of sorting and percentile calculation. Discuss why percentiles matter in SRE.

4. 16

   Explain how you would use infrastructure as code to manage cloud resources.

   Mention tools like Terraform or CloudFormation, version control, and idempotency.