Expect game-theory problems with optimal play (the coins-from-either-end game solved with dynamic programming), geometric and combinatorial probability (the broken-stick triangle problem), and expected-value games with optimal-stopping rules (a die game with a re-roll). Interviewers reward candidates who set up the recurrence or region argument cleanly, state their strategy explicitly, and compute a fair price with confidence. For quant-developer roles, strong coding and algorithms are tested alongside. Practise optimal-play reasoning, geometric probability, and stating decision rules precisely under questioning.
Recruitment process
- Apply or get sourced; online assessment or recruiter screen
- Probability and game-theory round
- Technical and algorithms rounds (for quant-developer roles)
- Final rounds with the desk, then offer
Interview rounds
- Round 1 (45-60 min): probability and expected-value round with games
- Round 2 (45-60 min): game-theory and optimal-play problems
- Round 3 (45-60 min): algorithms and data-structures round for quant-developer roles, or deeper quant for research roles
Optimal play and price framework
- Set up recurrences or region arguments cleanly, state your optimal strategy explicitly, and price games with confidence under a demanding interviewer
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.
