The Swiggy Engineering Interview Guide
Swiggy handles millions of concurrent, hyper-local transactions daily. Their engineering team is heavily focused on Golang and Java for the backend, and React/React Native for the frontend.
The Interview DNA
Swiggy favors practical coding ability and system design over pure algorithmic puzzles (though DSA is still tested).
Round 1: Machine Coding
This is the famous Indian startup filter.
- Scenario: “Build an in-memory Food Delivery application. Classes required: User, Restaurant, DeliveryPartner, Order. Implement a function to assign a delivery partner based on proximity.”
- The Rules: You have 2 hours. The code must be highly modular, follow Object-Oriented principles (SOLID), and be fully runnable.
Round 2: Data Structures & Algorithms
- Usually LeetCode Medium. Heavy focus on HashMaps, Heaps (e.g., finding the top 5 nearest restaurants), and array manipulation.
Round 3: System Design
Food delivery is a complex distributed system.
- Scenario: “Design the Swiggy delivery-partner tracking system.”
- The Approach:
- How do you ingest GPS coordinates from 100,000 riders every 5 seconds? (Discuss Kafka).
- How do you store it? (Discuss Cassandra or a Time-Series database).
- How do you push live updates to the React frontend? (Discuss WebSockets).
Round 4: Hiring Manager (Culture)
- Startups value extreme ownership. “Tell me about a time production went down because of your code. What did you do?”
- Swiggy wants engineers who can debug live issues, write post-mortems, and not point fingers.