Expect prompts on real-time position and risk aggregation across trading desks, an order-management system that routes trades and handles partial fills and cancellations, and tick-level market-data storage optimised for backtesting reads. Interviewers probe consistency of aggregated state under high message rates, event ordering, and time-series read optimisation. Generic web-scale answers miss the mark; the bar is precise reasoning about correctness, latency, and the write-versus-read trade-off in a trading context. Grounding your design in real financial workflows is what separates strong candidates.
Recruitment process
- Online coding assessment (HackerRank)
- Technical coding round on DSA
- System-design round on a trading or risk service
- Hiring-manager and Superday rounds, then offer
Interview rounds
- Round 1 (60-90 min): online coding assessment
- Round 2 (45-60 min): coding round on data structures and algorithms
- Round 3 (45-60 min): system-design round on trading, risk, or market data
- Round 4 (45 min): behavioral and hiring-manager round
Consistent and ordered framework
- Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path
Practice questions
- 01Practise
Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.
IntenseFlipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships. - 02Practise
We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?
IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific. - 03Practise
Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?
Intense - 04Practise
Design Swiggy Genie's matching algorithm. How does it differ from food-order matching?
Intense - 05Practise
Walk me through how you'd architect transaction-level fraud detection for 100M daily UPI transactions.
IntensePhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale. - 06Practise
How would you build a recommendation engine that suggests bills the user is about to forget?
Standard - 07Practise
Design a cashback-allocation system that prevents abuse without alienating genuine users.
Standard - 08Practise
Design a system to detect duplicate documents at web scale. What's your approximation strategy?
IntenseGoogle SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating. - 09Practise
Design Amazon Prime's recommendation engine. How would you handle the cold-start for a new Prime member?
Intense - 10Practise
Design a URL shortener like bit.ly. Walk me through database choice and scaling.
Standard
