100M daily UPI transactions is the implicit baseline. Every answer should explicitly address throughput, p99 latency, and cost at India scale. 'It depends' is the right default starting position. PhonePe processes 1B+ transactions per month and their system design questions are grounded in that reality: UPI flows, reconciliation pipelines, and high-availability for India's payment infrastructure. The interview loop runs 4 rounds after an online assessment. PhonePe values a 'builder mindset': candidates who bring examples of initiative, shipping fast, and owning failures end-to-end score significantly higher on the behavioral round than those with only polished STAR stories.
Recruitment process
- Online Assessment: 2 DSA problems (medium-hard, 60 minutes)
- Technical round 1: DSA + architecture discussion with time/space complexity follow-ups
- Technical round 2 / System design: Payment system, notification engine, or settlement pipeline
- Behavioral round: Builder mindset and ownership stories (45 min)
Interview rounds
- Online Assessment (60 min): 2 DSA problems: typically medium-hard. Arrays, graphs, or DP
- Technical Round 1 (60 min): DSA + architecture discussion. Expect follow-up on time/space complexity
- Technical Round 2 / System Design (60 min): Design a payment system, notification engine, or settlement pipeline
- Behavioral Round (45 min): Values + ownership stories. PhonePe values 'builder mindset': prepare examples of initiative
Scale-first design framework
- QPS at peak
- storage growth
- consistency model
- caching tiers
- cost per million.
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
