Swiggy DevOps/SRE Roadmap
Targeted preparation for Swiggy DevOps, SRE, and Cloud Infrastructure roles. Covers Swiggy's food-tech scale, real-time delivery infrastructure, AWS expertise, and interview format.
Swiggy's Tech Stack & Scale
Know the platform before walking in
What to learn
- Swiggy runs entirely on AWS — EKS, EC2, RDS, S3
- Real-time order routing — millions of delivery decisions per minute
- Golang is the primary backend language at Swiggy
- Kafka for real-time event streaming across services
- Primary cloud stack — EKS, MSK (Kafka), RDS Aurora, ElastiCache
- Engineering blog: engblog.swiggy.com — read before interview
Key tools
AWS Deep Dive
Swiggy is all-in on AWS — you must be an expert
What to learn
- EKS — cluster setup, managed node groups, IRSA, add-ons
- VPC — multi-AZ setup, private subnets, NAT gateway, VPC peering
- RDS Aurora — multi-AZ, read replicas, failover
- ElastiCache Redis — clustering mode, eviction policies
- MSK (Kafka) — broker sizing, replication factor, consumer groups
- IAM — IRSA for pod-level AWS permissions (Swiggy uses this heavily)
- CloudWatch + X-Ray — Swiggy's primary observability stack
Key tools
Kubernetes Operations at Scale
Swiggy runs large EKS clusters — own K8s
What to learn
- EKS node groups — managed, self-managed, Fargate tradeoffs
- IRSA (IAM Roles for Service Accounts) — Swiggy uses this everywhere
- Karpenter for dynamic node provisioning — cost efficiency
- Horizontal and Vertical Pod Autoscaler — handle lunch rush spikes
- PodDisruptionBudgets for zero-downtime rolling deploys
- Kubernetes networking — Calico/Cilium CNI, CoreDNS tuning
- Debugging production — kubectl exec, logs, events, describe
Key tools
CI/CD & GitOps
Swiggy deploys multiple times per day safely
What to learn
- GitHub Actions for build and test pipelines
- ArgoCD for GitOps-based deployments on EKS
- Canary deployments — Argo Rollouts with automatic rollback on error rate
- Helm charts — Swiggy teams own their service Helm charts
- Image scanning in pipeline — Trivy for CVE detection
- Secret management — AWS Secrets Manager + External Secrets Operator
Key tools
Observability & SREs at Swiggy
Real-time visibility for real-time delivery
What to learn
- Prometheus + Grafana — Swiggy's core metrics stack
- SLOs for order success rate, delivery ETA accuracy
- Kafka consumer lag monitoring — key SRE signal at Swiggy
- Distributed tracing — finding latency in order dispatch flow
- On-call runbooks — Swiggy SREs own lunch and dinner peak hours
- Alert tuning — reduce noise, actionable alerts only
Key tools
System Design for Food Delivery
Design systems that survive the dinner rush
What to learn
- Design real-time delivery partner assignment at scale
- Design restaurant availability with read-heavy geo queries
- Payment retry and idempotency — duplicate order prevention
- Rate limiting during peak hours — protect downstream services
- Design live order tracking with sub-second updates (WebSockets)
- Kafka consumer architecture for order state machine
Key tools
Interview Format & Prep
Swiggy-specific interview loop breakdown
What to learn
- Round 1: Coding — Go/Python scripting + easy-medium DSA
- Round 2: Linux + AWS deep dive (SRE fundamentals)
- Round 3: Kubernetes + CI/CD technical round
- Round 4: System design (food-tech scale, 45–60 min)
- Round 5: Hiring manager — ownership and impact stories
- Tip: Swiggy values engineers who think about peak traffic proactively
- Read Swiggy Engineering Blog before each round
Key tools
Interview Prep
DevOps Interview Prep Bundle — 1000+ Q&A
Every topic on this roadmap has interview questions in the bundle — Docker, Kubernetes, AWS, CI/CD, Linux, SRE, FinOps, System Design. Grab it before your next interview.