Swiggy

Swiggy's process is virtual for most rounds and usually takes two to four weeks. Engineering roles start with a coding test; business and operations roles start with a case or guesstimate discussion.

1. Application and recruiter screen

Apply on the Swiggy careers page, through campus placement or via a portal such as Jobaaj. A recruiter reviews your profile and, for lateral roles, holds a short call on experience, expectations and notice period.

2. Online assessment or take-home task

Engineers take a timed coding test with two or three problems. Product, analytics and business candidates may receive a short case study or data exercise to complete at home within a few days.

3. Technical or functional interviews

Two rounds with team members. For engineers these cover data structures, algorithms and a machine coding or design exercise; for business roles they cover cases about launching a city, improving delivery times or growing a category.

4. Hiring manager interview

The manager of the team explores how you have handled ownership, speed and conflict, and whether your motivations match a fast-changing consumer business.

5. Leadership or bar-raiser round

For senior roles, a director or head of function conducts a final round on judgement and culture fit. For freshers this is usually skipped.

6. HR discussion and offer

HR discusses compensation, including stock components where applicable, joining date and location, and releases the offer letter.

Engineering candidates usually face four rounds; business and operations candidates three or four. Interviews last 45 to 60 minutes.

Round 1: Online coding assessment

A proctored test with two or three problems of medium difficulty. Partial credit is given for passing some test cases, but optimal solutions matter for shortlisting.

• Arrays, hashing and prefix sums
• Graph traversal such as shortest path between locations
• Greedy scheduling and interval problems

Round 2: Data structures and algorithms interview

A live coding interview with an engineer. You are expected to write working code and discuss complexity and edge cases.

• Trees, heaps and priority queues
• Dynamic programming on strings or grids
• Designing a rate limiter or an LRU cache

Round 3: Machine coding or system design

Freshers and junior engineers get a machine coding round where you build a small working application in about 90 minutes. Experienced engineers get a system design round on a delivery-scale problem.

• Designing an order assignment or delivery tracking service
• Handling surge traffic during a cricket match or festival
• Clean code structure, extensibility and tests

Round 4: Business case round for non-engineering roles

Operations, sales and category candidates solve a case with the interviewer, often using real-world numbers.

• Estimating daily orders in a mid-sized city
• Reducing delivery time in a dense area
• Onboarding restaurants or dark-store partners in a new locality

Round 5: Hiring manager and culture round

A behavioural interview on ownership, speed and working with cross-functional teams.

• A time you delivered with incomplete information
• A metric you moved and how you measured it
• Why Swiggy and what you would improve in the app