Braintree India Site Reliability Engineer Interview: Rounds, Questions and Preparation

What the job involves

Site Reliability Engineers (SREs) at global tech companies like Braintree India ensure that payment systems and other critical services are highly available, scalable, and performant. They combine software engineering and systems engineering to automate operations, monitor production, and respond to incidents. Day to day, they write code to improve reliability, analyze system metrics, and collaborate with development teams to design resilient architectures.

Role and Technical Knowledge

1. 1

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

   Highlight that SRE focuses on reliability through engineering, with error budgets and SLIs/SLOs, while DevOps is a broader cultural and automation movement. Mention that SRE is a specific implementation of DevOps principles.

2. 2

   Explain the concept of SLI, SLO, and SLA. How would you define them for a payment processing service?

   Define SLI as a metric (e.g., latency), SLO as a target (e.g., 99.9% availability), and SLA as a contract with consequences. For payments, emphasize low latency and high success rate.

3. 3

   What is an error budget and how does it influence decision-making?

   Explain that error budget is 1 minus SLO, allowing a certain amount of failure. It helps balance innovation and reliability; if exhausted, focus shifts to stability.

4. 4

   How does Linux memory management work? What is the difference between virtual memory and physical memory?

   Cover paging, swapping, and how the kernel maps virtual to physical addresses. Mention OOM killer and how to monitor memory usage.

Practical Scenarios

1. 5

   A service is experiencing high latency. How would you troubleshoot and resolve the issue?

   Outline a systematic approach: check metrics (CPU, memory, network), logs, and traces. Use tools like top, netstat, and distributed tracing. Identify bottlenecks and mitigate, then prevent recurrence.

2. 6

   You need to automate the deployment of a microservice to Kubernetes. Describe the steps and tools you would use.

   Mention writing Dockerfile, Kubernetes manifests (Deployment, Service), using Helm or Kustomize, and CI/CD pipelines (Jenkins, GitLab CI). Emphasize rollback and health checks.

3. 7

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

   Discuss metrics collection (Prometheus), visualization (Grafana), logging (ELK), and alerting (Alertmanager). Define meaningful alerts based on SLOs to reduce noise.

4. 8

   What steps would you take to secure a production environment?

   Cover least privilege, network segmentation, regular patching, secrets management, and audit logging. Mention tools like IAM, Vault, and security groups.

Technical Deep Dive

1. 9

   Explain how TCP three-way handshake works and what happens during a DDoS attack.

   Describe SYN, SYN-ACK, ACK. For DDoS, mention SYN flood and mitigation like SYN cookies, rate limiting, and scrubbing centers.

2. 10

   What is the difference between a process and a thread? How does context switching work?

   Processes have separate memory, threads share memory. Context switching saves and restores state; explain overhead and how it affects performance.

3. 11

   How does DNS resolution work? What are common DNS issues in production?

   Cover recursive and iterative queries, caching, TTL. Common issues: misconfigured records, propagation delays, and DNS poisoning.

4. 12

   What is Infrastructure as Code? Compare Terraform and Ansible.

   IaC manages infrastructure through code. Terraform is declarative for provisioning, Ansible is procedural for configuration management. Mention idempotency and state.

Behavioral and HR

1. 13

   Tell me about a time you faced a critical production issue. How did you handle it?

   Use STAR method: describe the situation, your actions (troubleshooting, communication), and the resolution. Highlight learning and preventive measures.

2. 14

   How do you prioritize tasks when multiple incidents occur simultaneously?

   Explain triage based on impact and urgency. Mention communication with stakeholders and using runbooks. Show ability to stay calm and delegate.

3. 15

   Why do you want to work as an SRE, and why at a company like Braintree India?

   Express passion for reliability and automation. Research the company's tech stack and culture; align your skills with their needs and mention interest in payments.

4. 16

   Describe a time you automated a repetitive task. What was the outcome?

   Highlight the problem, the script or tool you wrote, and the time saved or errors reduced. Emphasize proactive improvement.