~learn.
Fintech · Bengaluru

PhonePe.

UPI payments app, wallet, merchant payments, bill payments and financial services at India's largest UPI volume.

its questions lean on
  • machine coding with clean data and service layers
  • payments and wallets
  • subscriptions and scheduling
  • feeds at scale
  • caching

The rounds, as candidates describe them

  1. Machine codingAbout 90 minutes to build a working module, then a separate evaluation call to explain approach and trade-offs.source ↗
  2. DSA and problem solvingOne hour of data-structure problems.source ↗
  3. DesignOne hour of HLD and LLD for a product.source ↗
  4. Hiring managerDeep dive into past work and the design decisions behind it.source ↗

Reported by candidates

From public interview write-ups; each links its source.

Likely, from what they build

Our pick, not a report: questions that fit PhonePe's products.

Study path

An ordered path through the course for PhonePe, and why each step is there.

  1. 01SQ-01India's UPIthe UPI flow, PSPs and NPCI
  2. 02W02 · DAY 02Idempotency in Practiceexactly-once debits
  3. 03W01 · DAY 04Hot Keys and Skewone hot merchant or account
  4. 04W01 · DAY 01Partitioning Deep-Divesharding payment data
  5. 05W01 · DAY 02Replication Trade-offsreplicas, lag and what to read from where
  6. 06SQ-04Visa/Mastercard Global Payment Networkhow card networks compare to UPI
  7. 07W10 · DAY 02Observabilityseeing a failing bank before users do
  8. 08W10 · DAY 01SLIs, SLOs and SLAsSLOs for payment success
  9. 09IP-20Design a Payment Systemthe classic payment-system interview question

Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.