Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · Swiggy

Swiggy Data Engineer Interview Questions India 2026

Swiggy's data-engineering rounds mix stream processing, analytical SQL, and experimentation pipelines, reflecting a food-delivery business run on real-time signals.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds4
Intense3 of 12
FrameworkJoin and experiment
Try it · Swiggy question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect a streaming round on producing per-restaurant delivery-time analytics from order and GPS event streams (joining streams with different arrival rates, event-time processing), a SQL round on week-over-week order-volume drops using window functions with LAG, and an experimentation round on building reliable A/B metric pipelines that guard against sample-ratio mismatch and peeking. Swiggy is experimentation-heavy, so interviewers reward statistically sound aggregation and correct stream-stream joins over generic batch ETL. Ground answers in real delivery workflows.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The typical Swiggy recruitment process has 4 stages: Recruiter screen and technical pre-screen → SQL and data-manipulation round → Streaming pipeline and experimentation design round → Hiring-manager and behavioural round, then offer.

Swiggy typically conducts 4 interview rounds: Round 1 (45-60 min): SQL round on window functions and trend detection; Round 2 (60 min): streaming pipeline design round with stream-stream joins; Round 3 (45-60 min): experimentation and A/B metric pipeline round; Round 4 (45 min): behavioural and hiring-manager round.

HireStepX recommends the Join and experiment framework for this type of interview: Handle stream-stream joins and event-time processing for delivery analytics, write window-function SQL for trend detection, and build statistically sound A/B pipelines.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

Designing pipelines for per-restaurant delivery-time analytics from order and GPS event streams, including stream-stream joins with different arrival rates and event-time processing.

Window functions with LAG for week-over-week comparisons, such as finding restaurants whose weekly order volume dropped beyond a threshold, partitioned by restaurant and city.

Practice

Rehearse the room before you enter it.

Run a mock Swiggy interview and get scored feedback on every answer.