Swiggy Software Engineer candidates describe an online assessment, medium-level DSA, low-level design or machine coding, and a hiring manager conversation. Reports vary by level and campus, so prepare for both coding and design.
$85K
Avg. Base Comp
$110K
Avg. Total Comp
3-4 rounds
Typical Rounds
1-13 weeks
Process Length
Candidates describe a Swiggy Software Engineer interview that goes well beyond a single DSA screen. Most accounts start with an online assessment, usually on HackerRank, with coding questions. Some add MCQs, SQL, or an API question. Several describe medium-level DSA rounds, with problems such as array search, median of subarrays, edit distance, graph search and tree questions like LCA or diameter.
The round that comes up most often after DSA is low-level design or machine coding. Reported prompts include a wallet, a pub-sub system, a rate limiter, Snake and Ladder, and a search-engine-style feature. In one report, the interviewer wanted the Snake and Ladder design as modular as possible. Another candidate was expected to write working wallet code and discuss error handling, SOLID principles and REST choices. Practice writing runnable, cleanly separated code, not only drawing boxes.
The hiring manager round is typically a discussion of your current or past work. Candidates report questions about resume projects, design choices, failover and system growth. One candidate was asked about a challenging task, the move from competitive programming to corporate work, and leadership. Bring specific stories with outcomes.
Fundamentals also appear. Reports mention OS concepts such as deadlocks and threads, OOP, Java and Spring, SQL, and a verbal explanation of how a HashMap works. One candidate said nearly half of a first-round problem-solving session was CS fundamentals. Outcomes were mixed, so treat these accounts as a range of experiences and not one fixed loop. Check language requirements early, because one candidate was told to code in Go or Java.
Synthesized from 18 candidate 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 HackerRank screen was the part that worried me most. It was three questions in 90 minutes, and the difficulty was high enough that I didn't have much time to polish anything. I made it through, and the next two rounds were less about speed and more about how I think through code and design.
The first interview was 60 minutes. It started with a quick intro and then moved into technical questions based on my own work, which for me meant Java and Spring. The main coding task was designing Snake and Ladder. The interviewer wanted the code to be as modular as possible, so the design mattered as much as getting the game to run. Keeping responsibilities separate so that pieces could change independently was the thing to focus on.
The second round was also 60 minutes, and this one required writing code and running it locally. The problems were N-Queens and subset sum. The rest of the round covered OOP concepts, questions about my work experience, and a verbal explanation of how a HashMap is implemented. That last part had no code, just a spoken walkthrough, so I'd make sure you can explain the internals clearly without a whiteboard.
The third round was with the hiring manager and was mostly a discussion of my current job. The behavioral questions were specific: a time I faced a challenging task and how I completed it, what I had learned moving from competitive programming in college to corporate work, and an example of leadership I had shown in my role. Come with concrete stories with real outcomes rather than general summaries.
I accepted the offer. My takeaway is that the coding rounds are manageable if you're comfortable with the fundamentals, but the interviewers were pushing on how I structured my solutions and how I talked about my own experience. Be ready to defend your design choices and explain your past work clearly.
Prep tip from this candidate
Be ready to build a modular object-oriented design for a board game like Snake and Ladder, since the interviewer emphasized modularity, and to explain HashMap internals verbally without writing code. Prepare concrete behavioral stories about challenges, learning from competitive programming to corporate work, and leadership, because the hiring manager round was largely discussion of your current job.
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 | |
| Unified Event Pipeline | |
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Longest Streak Users | |
| Random SQL Sample | |
| Merge Sorted Lists | |
| Upsell Transactions | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Scrambled Tickets | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Duplicate Rows | |
| Flight Records | |
| Prime to N | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Paired Products | |
| Month Over Month | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates report a recruiter or HR call before or between technical stages, and one mentioned a notice-period limit of 30 days. Recruiters may schedule rounds one at a time, so the full loop is not always visible up front. Confirm the round list and any language requirements early.
Candidates report a timed online test, often with two to three coding questions. Reported extras include MCQs, SQL, a REST API question, and, for frontend roles, React problems. One candidate had a three-question, 90-minute HackerRank screen. Check any language rules before starting.
Candidates typically describe one or more rounds of medium-level DSA in about 45-60 minutes. Reported topics include arrays, trees, graphs, DP and linked lists, and interviewers appeared to care about explaining the approach. One candidate was told to code in Go or Java. Some rounds also mix in Java, Spring, OOP or CS fundamentals, so do not prepare algorithms alone.
Many candidates report a low-level design or machine coding round. Reported prompts include Snake and Ladder, a wallet, a rate limiter, a pub-sub system and a search-style feature. Some interviewers expected runnable code and discussion of modularity, error handling and REST choices. Practice structuring classes with clear responsibilities.
Candidates report a conversation centered on their resume and previous projects, sometimes with behavioral questions and a system design discussion. Reported topics include challenges, leadership, failover, resiliency and API security. Prepare concrete stories with outcomes and be ready to defend your design decisions.
