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.
Recruitment process
- Recruiter screen and technical pre-screen
- SQL and data-manipulation round
- Streaming pipeline and experimentation design round
- Hiring-manager and behavioural round, then offer
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
Join and experiment framework
- 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
Practice questions
- 01Practise
Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.
Standard - 02Practise
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. - 03Practise
Write a SQL query to find the second-highest salary in a department.
Warm-up - 04Practise
What is normalisation in databases? When would you de-normalise?
Warm-up - 05Practise
What's the difference between a stack and a queue? Give a real-world use case for each.
Warm-up - 06Practise
Given a stream of integers, design a data structure that returns the median in O(log n).
Intense - 07Practise
You have a service that's slow only on Tuesdays. Walk me through how you'd debug.
StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first. - 08Practise
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. - 09Practise
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. - 10Practise
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.
