Expect problems framed around product data: single-pass per-account aggregation over a large stream with bounded memory, prefix-based autocomplete or ticket search, and traversal of nested comment threads with cycle detection. Interviewers want correct code, sensible data-structure choices (hashing, tries, BFS or DFS), and a clear complexity analysis. Cleanliness and clarity matter as much as raw cleverness.
Recruitment process
- Online coding assessment
- Technical coding round one on DSA
- Technical coding round two plus low-level design
- Hiring-manager round, then offer
Interview rounds
- Round 1 (60-90 min): online assessment with DSA problems
- Round 2 (60 min): live coding on hashing, tries, or traversal problems
- Round 3 (60 min): harder coding plus low-level design with complexity discussion
Practical DSA framework
- Pick the simplest data structure that fits (hash map, trie, queue), implement it cleanly, and defend the time and space complexity out loud
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.
