Expect prompts on a payment-processing system that transfers money reliably and never loses or double-sends it, a real-time fraud-detection pipeline that scores and flags transactions, and a restartable batch job that reconciles a day's transactions against clearing-house files. Interviewers reward idempotency, a state machine per transfer, reconciliation for every failure mode, and checkpointed restartable batch processing. Because the domain is money movement, hand-waving on failure handling does not survive; the interview rewards precise reasoning about exactly-once semantics and recovery.
Recruitment process
- Online coding and aptitude assessment
- Technical coding round on DSA
- System-design round on a payments or reconciliation service
- Hiring-manager round, then offer
Interview rounds
- Round 1 (60-90 min): online coding and aptitude assessment
- Round 2 (45-60 min): coding round on data structures and algorithms
- Round 3 (45-60 min): system-design round on payments, fraud, or reconciliation
- Round 4 (45 min): behavioral and hiring-manager round
Idempotent and restartable framework
- Model each transfer as an idempotent state machine, reconcile every failure mode, and make batch jobs checkpointed and restartable so no money is lost or double-sent
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
