Board International India Site Reliability Engineer Interview: Rounds, Questions and Preparation

What the job involves

Site Reliability Engineers (SREs) at global tech companies like Board International India ensure that large-scale, distributed systems remain highly available, performant, and scalable. Day to day, they combine software engineering with systems administration to build automation, monitor production environments, respond to incidents, and improve reliability through metrics and SLOs. Freshers in this role often start by writing scripts, fixing bugs in infrastructure code, and participating in on-call rotations under mentorship.

Role and Technical Knowledge

1. 1

   What is the difference between a Site Reliability Engineer and a traditional DevOps engineer?

   Highlight that SRE applies software engineering to operations, focuses on SLOs and error budgets, and often has a stronger emphasis on reliability and automation. DevOps is a broader cultural movement; SRE is a specific implementation.

2. 2

   Explain the concept of an error budget and how it influences release velocity.

   Define error budget as 1 minus SLO (e.g., 99.9% availability gives 0.1% downtime). When exhausted, teams slow down releases to focus on reliability. Mention that it balances innovation and stability.

3. 3

   What are SLIs, SLOs, and SLAs? Give an example for a web service.

   SLI is a measured metric (e.g., request latency), SLO is a target for that metric (e.g., 95% of requests under 200ms), SLA is a contract with consequences. Use a concrete service like an API endpoint.

4. 4

   How would you monitor a microservices-based application? Which tools would you use?

   Mention metrics (Prometheus), logging (ELK or Loki), tracing (Jaeger), and dashboards (Grafana). Emphasize the need for distributed tracing and health checks per service.

Practical Scenarios and Troubleshooting

1. 5

   A website is suddenly returning 502 errors. Walk me through your troubleshooting steps.

   Start by checking load balancer logs, then backend service health, database connectivity, and resource utilization. Use a systematic approach: identify scope, check recent changes, and isolate the failing component.

2. 6

   How would you handle a disk space alert on a production server at 2 AM?

   First, assess impact and whether it can wait. If critical, log in, identify large files or logs, clean safely, and consider temporary measures like log rotation. Then follow up with a permanent fix and post-mortem.

3. 7

   You need to deploy a new version of a service with zero downtime. What strategy would you use?

   Discuss blue-green deployment or canary releases. Mention health checks, rolling updates, and the ability to roll back quickly. Emphasize testing in staging first.

4. 8

   A critical service is down, and you are the only one on call. What do you do first?

   Acknowledge the incident, check monitoring dashboards, and try to restore service (e.g., restart, failover). Communicate status to stakeholders. Escalate if needed, and document everything for later analysis.

Automation and System Design

1. 9

   How would you automate the provisioning of a new Linux server in the cloud?

   Use infrastructure as code (Terraform, CloudFormation) and configuration management (Ansible, Chef). Mention idempotency, version control, and integration with CI/CD.

2. 10

   Design a simple CI/CD pipeline for a containerized application.

   Outline stages: code commit, build (Docker image), test, push to registry, deploy to Kubernetes (e.g., via Helm). Include automated testing, security scans, and rollback strategy.

3. 11

   What is the role of Kubernetes in an SRE environment? How does it help with reliability?

   Kubernetes provides self-healing, scaling, and rolling updates. Mention liveness/readiness probes, replica sets, and how it abstracts infrastructure. SREs use it to manage microservices consistently.

4. 12

   How would you reduce toil in your daily operations? Give an example.

   Define toil as manual, repetitive work. Example: automating log rotation or alert remediation. Mention writing scripts, using runbooks, and measuring time saved.

Behavioural and HR Questions

1. 13

   Tell me about a time you had to learn a new technology quickly for a project.

   Use STAR method: describe the situation, the technology, your learning approach (docs, tutorials, hands-on), and the outcome. Show enthusiasm for continuous learning.

2. 14

   Describe a situation where you had to work under pressure or with a tight deadline.

   Focus on prioritization, communication, and staying calm. Highlight the result and what you learned about time management.

3. 15

   Why do you want to work as a Site Reliability Engineer, especially at a company like Board International India?

   Connect your interest in reliability, automation, and large-scale systems to the company's focus on business intelligence and analytics. Mention the opportunity to learn and grow in a fast-growing environment.

4. 16

   How do you handle disagreements with a team member about a technical decision?

   Emphasize listening, data-driven discussion, and focusing on the best outcome for the project. Mention that you are open to being wrong and value team harmony.