Swiggy Data Analyst Interview Process

The Swiggy Data Analyst Interview Guide

Swiggy (headquartered in Bangalore) is not just a food delivery company; it is an incredibly complex logistics and quick-commerce (Instamart) engine. A Data Analyst here solves real-time routing problems, predicts inventory demand, and optimizes dynamic pricing (surge pricing).

The Interview Stages

Swiggy’s process is highly analytical and heavily focused on product metrics and logistics unit economics.

1. Aptitude & SQL Assessment (HackerRank): Filtering round.
2. Technical SQL / Coding Round: Live querying.
3. Business & Product Case Study: Solving a core Swiggy problem.
4. Hiring Manager / Bar Raiser Round: Behavioral and strategic fit.

Round 1: Advanced SQL & Data Manipulation

Swiggy expects top-tier SQL skills.

• Question: "Given a table of customer sessions and order timestamps, write a query to find the average time it takes for a user to place an order after opening the app, grouped by city."
• Focus: LAG/LEAD functions, date-time manipulation, and query optimization. They will check if your query scales well.

Round 2: The Instamart / Quick Commerce Case Study

Quick commerce is Swiggy's fastest-growing segment, so expect questions on it.

• The Scenario: "Instamart delivery times in Indiranagar have increased from 15 minutes to 22 minutes over the last month. How do you find the root cause?"
• The Approach: Break it down into the delivery funnel:
  1. Time to allocate a rider.
  2. Time for the rider to reach the dark store.
  3. Time to pack the items (picker efficiency).
  4. Time to travel to the customer (traffic/weather data).

Round 3: Product Analytics & Dynamic Pricing

• Question: "How would you measure the impact of implementing 'Surge Pricing' (Rain Fee) on customer retention?"
• Focus: You must balance short-term revenue gains against long-term customer churn. Discuss cohort analysis (do users who pay surge pricing once never return?).

Round 4: Behavioral & Stakeholder Management

Data Analysts at Swiggy work closely with Product Managers and City Operations Heads.

• "Describe a time when the data showed one thing, but the City Operations Manager strongly disagreed based on their gut feeling. How did you handle it?"
• "What do you do when a dataset you need for an urgent analysis is completely corrupted?"

Final Advice: Swiggy loves candidates who understand the physical constraints of their business. It's not just software; there are actual riders on bikes dealing with traffic and rain. Factoring these real-world constraints into your data models during the interview will make you stand out.