What Is the Swiggy Interview Process Like? (Round by Round)

Candidates report four to six rounds at Swiggy, over about two to six weeks. The process starts with an online coding assessment, which candidates report on HackerRank for some roles and on HackerEarth for others.

Experienced candidates then report a machine coding round of about 120 minutes. After that come a problem solving round on data structures and algorithms, a design round, and a hiring manager round. Some reports add a short HR round of 20 to 30 minutes, although the exact set varies by level and by team.

Quick Overview

Stage 1: The Online Assessment

Candidates report 75 to 90 minutes on an assessment platform. One reported set had three coding questions at easy, medium, and hard difficulty, while another reported one database question in SQL plus three coding questions.

Reports name both HackerRank and HackerEarth, so confirm the platform with your recruiter. If this format is new to you, read what an online technical assessment is before you take it.

Stage 2: The Machine Coding Round

A machine coding round is a timed session where you build a small working program from a written requirement, and candidates report about 120 minutes for it at Swiggy. Reported problems include a Snake and Ladder game, a parking lot ticketing system, an expense splitting application, and CRUD APIs for a small service.

Candidates also report that internet access and outside code are not allowed. The grading covers three things: whether the program runs, how the classes are organized, and whether a new requirement can be added without a rewrite.

Stage 3: The Problem Solving Round

This round runs about 60 minutes of live coding. Reported questions include the count of binary search trees for a given number of nodes, the lowest common ancestor in a binary tree, and the gas station problem. Others report the intersection point of two linked lists, the longest palindromic substring, and searching a matrix sorted by row and by column.

One report describes a stack design question and two questions on balanced parentheses. A senior report lists finding a number in an infinite sorted stream, plus expanding a string written with repeat counts. Interviewers ask for the running time and the memory cost of your solution.

Stage 4: The Design Round

For senior roles this round is a system design discussion. For SDE-1 and SDE-2 candidates report low level design, which means classes, interfaces, and their relationships. One reported question asks for a catalog system with restaurants, items, categories, variant groups such as size, variants such as small and medium and large, and add-on groups.

Another reports an object oriented design for hotel room booking. Several candidates report a rejection at this round after clearing the coding rounds. The topics are covered in the Swiggy system design interview.

Stage 5: The Hiring Manager Round

This round covers your projects, the decisions you owned, and your reasons for applying. Prepare that second part with how to answer why Swiggy. One senior report also lists fundamentals questions. They include the difference between concurrent and parallel programming, the two-phase commit protocol, signal handling in operating systems, and when to use asynchronous rather than synchronous calls between services.

How the Campus Path Differs

On-campus reports describe a shorter loop than the off-campus one. One describes a 90 minute assessment with one database question and three coding questions, then a one hour technical interview with four data structure questions, and finally a managerial round of about 30 minutes.

No machine coding round appears in those campus reports, so freshers should expect the DSA rounds to decide the result.

Timeline and Decision

One candidate reports about a week between the online assessment and the recruiter call. Waits between the later rounds are shorter in the reports, from the same day to about two days. Reported end to end times run from about two to six weeks.

The written offer can arrive well after the verbal confirmation. The reported numbers are collected in how long it takes to hear back.

Questions to Ask Them

Every round ends with time for your questions. Useful ones here: which surface the team owns, whether that is food delivery, quick commerce, or restaurant tools. Ask how on-call works during peak lunch and dinner load, and how the team measures delivery time and order failure. A specific question also proves that you studied the product.

How to Prepare

• Build one program under a timer. Practice a parking lot or expense splitting program in 90 minutes, with classes you can extend.
• Drill the patterns, not the problems. Grokking the Coding Interview covers the tree, array, and string patterns these rounds use.
• Prepare the design round separately. Grokking the System Design Interview covers queues, caches, and geo lookups, which the Swiggy questions use.
• Write down three ownership stories. The hiring manager round asks what you decided, not what your team delivered.