Swiggy Interview Questions and Answers
Last updated 2026-11-19
Swiggy runs a three-sided marketplace of customers, restaurants and delivery partners, and its engineering questions tend to come from that shape: assigning a rider, estimating arrival time, keeping a menu fresh and not charging twice. These practice questions follow those topics, with worked answers.
They are practice in the style of the topics the rounds are commonly reported to cover, not a record of what any candidate was asked in a given year. For code, see Swiggy coding round questions; for the process, read how to crack the Swiggy interview.
| Typical rounds | Online DSA test, machine coding, managerial (commonly reported) |
|---|---|
| Roles | SDE-1 |
Rounds as commonly reported
Candidate reports for SDE-1 describe an online test with about three DSA problems in roughly 90 minutes, a machine-coding or low-level design round of two to three hours on problems like Splitwise or a parking lot, and a managerial or HR round about past work. Senior roles add system design.
These are candidate-reported and not published by Swiggy, so formats differ by team and year.
Hiring status
We have no sourced hiring statements for Swiggy to quote, and there is no Swiggy page under /hiring on this site. Check current openings and any campus or hackathon notice on the company's own careers site at careers.swiggy.com, and treat any date quoted elsewhere as unconfirmed until it appears there.
How to practise
Pick one marketplace flow, such as order placement, and trace it end to end: what is stored, which service owns it, what happens on retry or timeout. Then do the same for dispatch. This builds the vocabulary the design questions need.
Swiggy Interview Questions and Answers: questions with worked answers
1 How would you assign a delivery partner to a new order?
hardStart by filtering riders who are free or nearly free and within a radius of the restaurant, using a geo index such as geohash or an H3 cell. Score the candidates on pickup distance, rider current load, restaurant preparation time (so the rider arrives when food is ready, not before) and fairness. Batch assignment in short windows, a few seconds, so you can solve a small matching problem globally rather than greedily per order. Lock the chosen rider with compare-and-set so no two orders claim one rider.
2 How would you estimate delivery time shown to the customer?
hardBreak it into parts: restaurant preparation time, rider assignment delay, travel time from restaurant to customer, and a buffer. Prep time depends on the restaurant, item count and current load, and travel time on map routing and live traffic. Start with a rules model, then a regression or gradient-boosted model trained on past orders. Show a range, not a point, and track the error so the model is retrained when it drifts.
3 Why are menu and availability hard to keep consistent, and how do you handle it?
mediumRestaurants change items and run out of stock all day, while customers read menus from caches. Use a write path through a menu service that publishes change events to a queue; the search index and caches consume the events. Accept brief staleness for browsing but validate each item's availability and price again at cart and at payment, and show a clear message if it changed.
4 Explain idempotency for the payment callback.
mediumGateways may call your webhook more than once, and the customer's app may retry. Use the gateway transaction id as an idempotency key with a unique constraint, so processing the same event twice has no extra effect. Make the state update conditional (only move from PAYMENT_PENDING to CONFIRMED) and return success on duplicates so the gateway stops retrying.
5 How would you design a notification service for order updates?
mediumUse an event per order state change on a message queue; a notification service reads events, applies user preferences, renders a template and sends through push, SMS or WhatsApp providers behind one interface. Retry with backoff, add a dead-letter queue, de-duplicate on event id, and rate limit per user. Prefer push over SMS for cost and fall back when the push token is invalid.
6 How do you choose between SQL and NoSQL for orders?
mediumOrders need transactions and joins with payments and refunds, so a relational store is the safe default, partitioned by user or region as it grows. A document or wide-column store suits high-write, key-based data such as rider location pings or an order timeline. A common answer is both: relational for the source of truth, a key-value store for hot reads, and a search engine for restaurant discovery.
7 Describe how you would handle surge in orders at lunchtime.
mediumScale stateless services horizontally and keep hot reads in cache. Put a queue between order placement and slower steps like notifications and analytics. Protect dependencies with timeouts, circuit breakers and bulkheads so one slow service does not take down checkout. Use rate limiting, and degrade non-critical features first, such as recommendations.
8 What is the difference between a process and a thread, and when does it matter for a backend service?
easyA process has its own address space; threads share the process memory and are cheaper to create, but need synchronisation. For a backend it decides your concurrency model: thread-per-request is simple but limited by memory, while an event loop or a small thread pool with non-blocking I/O handles many idle connections. Shared mutable state between threads needs locks or immutable data.
9 Explain the CAP theorem with an example from food ordering.
easyDuring a network partition you must choose between consistency and availability. The inventory count for a limited item favours consistency, because overselling is costly; a restaurant list favours availability, because showing a slightly old list is harmless. Say that CAP applies during partitions only, and that most systems tune consistency per feature.
10 Tell me about a time you had to deliver under a tight deadline.
easyGive a short STAR story: the date and constraint, how you cut scope to what was essential, what you communicated and to whom, and what you deferred knowingly. Close with the outcome and a follow-up you made to pay back the shortcut. Interviewers listen for judgement about trade-offs, not heroics.
11 Why Swiggy?
easyLink your answer to something concrete: a logistics, search or pricing problem you find interesting, a feature you have used and could improve, or a project of yours with similar constraints. Avoid repeating the company tagline. Say what you want to own in the first year.
12 How do you debug a latency spike reported in production?
mediumStart from the symptom and the time it began: check dashboards for which endpoint and percentile moved, then correlate with deployments, traffic and dependency latency. Use traces to find the slow span. Mitigate first (roll back, scale, disable a flag), then find the root cause and add an alert so you see it sooner next time.
Frequently asked questions
How long is the Swiggy machine-coding round?
Candidate reports describe two to three hours, but Swiggy does not publish it, so check the time on your own invite.
Which topics matter most for Swiggy SDE-1?
DSA on arrays, graphs and heaps, plus object-oriented design for the machine-coding round. Know basic system design and databases as well.
Do freshers face system design?
Rarely reported. Still, be ready to discuss caching, queues and a simple schema for projects you list.
Where do I see Swiggy openings?
On the company's own careers page. This site has no sourced Swiggy hiring statements to quote.
Sources
Related guides
More in Company Interview Questions
- Synopsys Coding Round Questions with Solutions
- Synopsys Interview Questions and Answers for India R&D Software Roles
- Target Coding Round Questions
- Target Interview Questions with Answers
- TCS Coding Round Questions with Solutions
- TCS Interview Questions for Freshers
- Tech Mahindra Coding Round Questions with Solutions
- Tech Mahindra Interview Questions for Freshers
- Texas Instruments Coding Round Questions with Solutions
- Texas Instruments Interview Questions and Answers for India Embedded Roles
- Thoughtworks Coding Round Questions
- Thoughtworks Interview Questions with Answers