Cashback systems, fraud detection, and merchant payouts all involve adversarial users who actively probe your system for arbitrage. Be ready for 'how do you prevent X' questions where X is explicitly a fraud pattern: double-spending on wallets, referral abuse, QR code replay attacks. The system design bar reflects Paytm's position as India's original payments super-app: their infrastructure handles hundreds of millions of UPI transactions monthly across a fragmented user base with feature phones and poor connectivity. Engineers are expected to reason about idempotency in payment flows, eventual consistency trade-offs in ledger systems, and rate limiting under burst demand. The technical interview also probes deep CS fundamentals: Paytm hires for systems that must not fail under adversarial conditions.
Recruitment process
- Online coding assessment: 2–3 DSA problems, medium difficulty
- Technical round 1: DSA with follow-up questions on edge cases and optimisation
- Technical round 2 / System design: fraud detection, merchant payout, or cashback system design
- Behavioral round: ownership, speed, and adversarial-user mindset
Interview rounds
- Online Coding Assessment (60 min): 2–3 medium-difficulty DSA problems. Standard first filter
- Technical Round 1: DSA (60 min): One problem with follow-up questions on edge cases and optimisation. Paytm specifically tests idempotency reasoning: what happens if a payment request is processed twice?
- Technical Round 2 / System Design (60 min): Fraud detection system, merchant payout pipeline, or cashback arbitrage prevention. Adversarial user modelling (double-spending on wallets, QR code replay attacks, referral abuse) is a Paytm-specific differentiator
- Behavioral Round (30 min): Ownership, shipping speed, and adversarial-user mindset. Stories about owning a production incident end-to-end or catching a fraud pattern score well
Adversarial design framework
- Threat model
- detection signals
- mitigation tiers
- false-positive cost.
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
