Expect prompts on processing millions of card transactions a day with fraud checks in the authorisation path, a retail-bank ledger that must always balance, and near-real-time multi-channel customer notifications. Interviewers reward separating the low-latency authorisation path from asynchronous fraud scoring, using an append-only double-entry ledger with careful concurrency control, and guaranteeing at-least-once delivery with deduplication. The domain is unforgiving: money must never be lost or double-counted, so precise reasoning about consistency, idempotency, and failure handling is what distinguishes strong answers.
Recruitment process
- Online coding assessment
- Technical coding and OOP round
- System-design round on a banking-scale service
- Hiring-manager and fit round, then offer
Interview rounds
- Round 1 (60-90 min): online coding assessment
- Round 2 (60 min): coding and object-oriented design round
- Round 3 (60 min): system-design round on transactions, ledgers, or notifications
- Round 4 (45 min): behavioral round with a finance-domain framing
Fast path slow path framework
- Keep the authorisation path low-latency, push fraud and heavy work to an async slow path, and back money movement with a balancing ledger and idempotent delivery
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
