Swiggy - interview guide

Swiggy interview questions - a complete guide

Both machine coding and DSA are reported to matter at Swiggy. Here are design questions tied to food delivery too.

Language:EnglishHinglish

About Swiggy

Swiggy is an Indian platform for food delivery and quick commerce (Instamart). Its engineering deals with problems such as real-time orders, delivery partners and ETAs.

This guide covers 12 Swiggy interview questions with answers - what each question checks and how to answer it - plus the Swiggy interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

Swiggy hiring process

  1. Step 1: Online assessment

    Medium-level coding, sometimes one SQL question.

  2. Step 2: Machine coding

    Working code in about 2 hours - class design and extensibility.

  3. Step 3: DSA and design

    Live coding, and low-level design (system design for senior roles).

  4. Step 4: Hiring manager

    Projects and fit.

Swiggy does not publish its interview process for India freshers in detail (as of our check). This information is based on candidate reports and varies by role, level and team.

Sources (checked 15 October 2026): Swiggy Careers. Hiring processes change - read the official notice before you apply.

Swiggy interview questions and answers

Machine coding and design

  1. 1.Machine coding: build a digital wallet.

    What they're checking
    Working, extensible code.
    How to answer
    Classes: User, Wallet, Transaction. Add money, transfer, history. The balance must never go negative. Core first, then extras such as offers.

  2. 2.Low-level design for assigning an order to a delivery partner.

    What they're checking
    Design tied to the domain.
    How to answer
    Order, Restaurant, DeliveryPartner. Keep the assignment strategy in its own class (nearest, least busy) so it can change.

  3. 3.Build a pub-sub system.

    What they're checking
    Design patterns.
    How to answer
    Topic, Publisher, Subscriber. Subscribe/unsubscribe, and deliver each published message to all subscribers.

DSA

  1. 4.Koko eating bananas: find the minimum speed.

    What they're checking
    Binary search on the answer.
    How to answer
    Speed from 1 to the largest pile; for each speed count the hours; binary search for the lowest speed that finishes in h hours.

  2. 5.Vertical order traversal of a binary tree.

    What they're checking
    Trees + hashing.
    How to answer
    Track each node's column during BFS; collect nodes column by column in a map.

  3. 6.Why Swiggy?

    What they're checking
    Motivation.
    How to answer
    Real-time logistics and large-scale problems - whatever genuinely appeals to you.

More questions

  1. 7.Task scheduler: the minimum time for tasks with a cooldown.

    What they're checking
    Greedy + heap.
    How to answer
    A formula from the count of the most frequent task, or run tasks each cycle from a max-heap.

  2. 8.How would you estimate a delivery ETA at a high level?

    What they're checking
    Domain thinking.
    How to answer
    The restaurant's preparation time + the partner's time to the restaurant + to the customer (distance, traffic, past data).

  3. 9.SQL: the average delivery time in each city.

    What they're checking
    Understanding of data.
    How to answer
    GROUP BY city, AVG(delivered_at - picked_at) - using the right time-difference function.

  4. 10.Machine coding: a snake and ladder game.

    What they're checking
    A clean design for a simple game.
    How to answer
    Board, Snake, Ladder, Player, Dice; a turn-by-turn loop; the winning condition.

  5. 11.Why do we use a queue (like Kafka)?

    What they're checking
    Understanding of systems.
    How to answer
    To keep services separate - an order goes into a queue and other services process it at their own pace; it helps with load spikes.

One more question

  1. 12.A restaurant isn't accepting orders at peak time - what would you do in the app?

    What they're checking
    Product and system thinking.
    How to answer
    Show the restaurant as temporarily 'busy', raise the ETA, and suggest other options to the customer.

7-day preparation plan for the Swiggy interview

  1. Day 1: Machine coding - a wallet in 2 hours.
  2. Day 2: Binary search on the answer.
  3. Day 3: Trees and hashing.
  4. Day 4: LLD - order assignment, pub-sub.
  5. Day 5: A second machine coding problem.
  6. Day 6: SQL and hiring manager stories.
  7. Day 7: A mock round.

Preparation tips

  • Practise machine coding with a 2-hour timer.
  • Understand the 'binary search on the answer' pattern well.
  • Show approaches like the strategy pattern in design so the code is easy to change.

Mistakes to avoid

  • Ignoring extensibility in machine coding.
  • Not recognising binary search patterns.
  • Never having thought about the domain (delivery, ETA).

Frequently asked questions

How long is the Swiggy machine coding round?

It is commonly reported as about 2 hours.

How many rounds are there in the Swiggy interview?

Commonly 4-6: OA, machine coding, DSA, design and hiring manager.

Does the Swiggy test have SQL?

One SQL question has been reported in some online assessments.

Similar companies - Product and internet companies

More company guides

Read next

On a live call, Cuelyte AI hears questions like these and has an answer ready in about a second, built from your resume and notes. Coding interviews: how Cuelyte AI helps

Ready for your Swiggy interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.

Start free - no card neededSee pricing