Expect a pipeline round on near-real-time per-city delivery-partner utilisation metrics from order and location events that survives dinner-time bursts, a SQL round on ranking restaurants by repeat-order rate within each city (self-joins and window functions), and a modelling round on a warehouse that serves operational dashboards and ad-hoc analyst queries without resource contention. Interviewers reward reasoning about autoscaling, back-pressure, event-time windowing, and workload isolation over generic batch ETL. Ground answers in real delivery-operations analytics.
Recruitment process
- Recruiter screen and technical pre-screen
- SQL and data-manipulation round
- Streaming pipeline and warehouse-design round
- Hiring-manager and behavioural round, then offer
Interview rounds
- Round 1 (45-60 min): SQL round on cohort metrics and self-joins
- Round 2 (60 min): streaming pipeline round under bursty load
- Round 3 (45-60 min): warehouse-modelling and workload-isolation round
- Round 4 (45 min): behavioural and hiring-manager round
Burst and isolate framework
- Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads
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.
