Swiggy Software Engineer interview typically runs 3-4 rounds: OA, DSA, LLD, and HM/system design. The process usually takes about 3 weeks and is structured but can vary by candidate.
$1942K
Avg. Base Comp
$2206K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
We’ve seen Swiggy consistently favor candidates who can move beyond textbook answers and reason like someone shipping production systems. Across experiences, the strongest signal wasn’t just solving medium DSA problems; it was whether candidates could stay composed while the interviewer kept the pace brisk and then pivot into clean, implementation-ready design thinking. One candidate noted that the coding round felt more about reasoning under time pressure than writing something huge, and another described the machine coding exercise as a search engine problem that rewarded building something workable end to end.
A recurring theme is that Swiggy seems to care a lot about how well you connect code to real product constraints. Multiple candidates were pushed on Java or Go specifics, Spring basics, REST APIs, error handling, and even automation-framework thinking, which tells us the bar is stack-aware rather than language-agnostic. The low-level design rounds also weren’t abstract whiteboard exercises: candidates were asked to design a wallet or pub-sub system and explain responsibilities, components, and tradeoffs clearly. That means working code plus crisp design rationale matters more here than polished diagrams alone.
We also see a practical, resume-driven final conversation style. Candidates reported being asked to walk through what they actually built, then extend that into system design or database discussion tied to real work. The non-obvious make-or-break factor is communication under pressure: not just knowing the answer, but explaining why your approach is safe, maintainable, and aligned with the problem. In our view, Swiggy is screening for engineers who can handle ambiguity without losing structure.
Synthetized from 3 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Swiggy process.
The toughest part for me was the DSA round, because it came right after the OA and the interviewer kept the pace pretty brisk. I had solved the online assessment and then about a week later HR called me for the next round. That first technical round mixed coding with a few basic CS and language questions. I was asked a couple of array-style problems, including finding a target in an unsorted array, and then a median-of-every-subarray-of-size-k type question. After that, they moved into some Spring and Java questions, so it wasn’t just pure algorithms. The coding part felt more about how cleanly I could reason under time pressure than about writing something huge.
The next round was LLD, and that was the one that felt most different from a typical DSA interview. I was asked to design a wallet, and the interviewer expected working code, not just a high-level diagram. They also pushed on error handling, SOLID principles, and REST API-related questions, so I had to explain design choices as I went. The final round with the hiring manager was more conversational but still technical in a practical way. We talked through my resume, what I actually worked on, and then a system design-style discussion around something similar to Instamart. The whole process took around three weeks and had three rounds in total, with the technical rounds lasting about 45 minutes each. I felt the interviews were smooth and professional, but I was ultimately rejected and didn’t get any feedback mail. If I were preparing again, I’d focus on being able to code through array/median problems quickly, and I’d practice explaining a wallet design with error handling and REST endpoints clearly, since that came up directly.
Prep tip from this candidate
Be ready for an OA followed by a fast-paced DSA round with array problems like target search in an unsorted array and median of every subarray of size k. Also practice a wallet LLD design where you can write working code, discuss error handling, SOLID principles, and REST API choices.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Swiggy
Write a function can_shift to return whether or not A can be shifted some number of places to get B
| Question | |
|---|---|
| Size of Joins | |
| Order Assignment and Delivery Time | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Delivery Estimate Model | |
| Over-Budget Projects | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Top 3 Users | |
| Scrambled Tickets | |
| Recurring Character | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Address Schema | |
| Download Facts | |
| SELECTive Wine Connoisseur | |
| Permutation Palindrome | |
| Average Quantity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates first go through resume shortlisting, followed by a recruiter or HR call to line up the next step. In some cases, the recruiter shares the process one round at a time rather than all at once.
The OA typically includes 2 coding questions and MCQs, or a couple of coding problems plus basic screening questions. It serves as the first technical filter before the live interviews.
This round focuses on medium-level coding problems, often in arrays, intervals, DP, or binary search. Interviewers also ask basic CS and language-specific questions, such as Java, Spring, or Go, and expect clean, efficient solutions under time pressure.
Candidates are asked to build a practical system or feature, such as a search engine, wallet, or pub-sub system. The interviewer looks for working code, architecture, error handling, SOLID principles, and API design rather than just a high-level diagram.
This round covers higher-level design discussions, sometimes tied to Swiggy products like Instamart. Candidates are expected to explain design choices clearly and discuss how components would scale and interact.
The final conversation is with the hiring manager and is a mix of resume deep-dive, past project discussion, and practical technical questions. It can also include system design-style discussion or basic database and behavioral questions.