E. Shaw's India quant and technical interviews blend rigorous probability, combinatorial logic, and clean derivations, reflecting a research-driven firm. Expect expected-value problems solved via recurrence relations (expected flips to see two consecutive heads), classic combinatorial puzzles (the 25-horses racing problem), and probability and estimation questions where the reasoning matters more than the memorised answer. For technical roles, algorithms and data-structures depth is also tested. Interviewers reward a minimal, rigorous argument and honest handling of what you are unsure about. Practise deriving expected values from first principles, structuring combinatorial arguments cleanly, and narrating your logic so a sceptical interviewer can follow every step.
Recruitment process
- Apply or get sourced; online assessment or recruiter screen
- Probability and quantitative-reasoning round
- Technical and algorithms rounds (for technical roles)
- Final rounds with the team, then offer
Interview rounds
- Round 1 (45-60 min): probability and combinatorial-reasoning round
- Round 2 (45-60 min): expected-value derivations and estimation questions
- Round 3 (45-60 min): algorithms and data-structures round for technical roles, or deeper quant for research roles
Derive from first principles framework
- Solve probability with clean recurrences, build minimal rigorous combinatorial arguments, and show every step so the reasoning, not the memorised answer, carries the round
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.
