course prep arena ask shorts stories you ?

0 / 100 xp → junior

~course prep arena ask shorts stories you

Loading page…

~/himanshutty1

~/himanshu$cd ~/next-page

[ok]resolve route

[..]stream page

Loading page…

~/sdmtty1

~/sdm$cd ~/next-page

[ok]resolve route

[..]stream page

Prep/Companies/PhonePe

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

Machine codingAbout 90 minutes to build a working module, then a separate evaluation call to explain approach and trade-offs.source ↗
DSA and problem solvingOne hour of data-structure problems.source ↗
DesignOne hour of HLD and LLD for a product.source ↗
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.

Design a Distributed Job SchedulerSystem design
IP-17 · Design a Distributed Job Scheduler →W02 · DAY 05 · Distributed Cron & Job Scheduling →reported in:LeetCode Discuss · PhonePe Software Engineer (3-5 years) interview (2026) ↗
Design a subscription management systemSystem design
SQ-18 · Razorpay Payment Gateway →IP-17 · Design a Distributed Job Scheduler →reported in:LeetCode Discuss · PhonePe SDE-2 interview experience (2024) ↗LeetCode Discuss · PhonePe SDE-2 machine coding and design rounds (2024) ↗
Design a News FeedSystem design
IP-07 · Design a News Feed →SQ-10 · Twitter/X →W04 · DAY 04 · Feed Caching →reported in:LeetCode Discuss · PhonePe Software Engineer, Dec 2024 (Design Twitter) ↗
Design InstagramSystem design
SQ-21 · Instagram Feed and Stories →IP-07 · Design a News Feed →reported in:LeetCode Discuss · PhonePe backend SDE, 3 YOE (2025) ↗
Design a song recognition service like ShazamSystem design
no lesson for this one yetreported in:LeetCode Discuss · PhonePe SDE-2 backend interview experience, 4 rounds (2026) ↗
Design SplitwiseLow-level design
LLD-06 · Design a Bill-Splitting App (Splitwise) →reported in:LeetCode Discuss · PhonePe Software Engineer, Nov 2024 offer ↗
Design a prepaid mini walletLow-level design
IP-20 · Design a Payment System →W02 · DAY 02 · Idempotency in Practice →reported in:LeetCode Discuss · PhonePe machine coding, mini wallet (2024) ↗
Design a payment gateway (machine coding)Low-level design
SQ-18 · Razorpay Payment Gateway →IP-20 · Design a Payment System →reported in:LeetCode Discuss · PhonePe machine coding, payment gateway (2023) ↗
Design an app version management systemLow-level design
W10 · DAY 03 · Deployment Strategies →reported in:LeetCode Discuss · PhonePe machine coding round, app version management (2025) ↗LeetCode Discuss · PhonePe machine coding round LLD (2025) ↗
Design a hackathon platform with scoring and recommendationsLow-level design
IP-14 · Design a Real-Time Leaderboard →reported in:LeetCode Discuss · PhonePe Software Engineer machine coding round (2025) ↗LeetCode Discuss · PhonePe machine coding question (2025) ↗
Design a task tracker with an activity logLow-level design
W03 · DAY 05 · Audit Log System →reported in:LeetCode Discuss · PhonePe Software Engineer, Nov 2024 offer ↗
Design a pendency system that counts in-flight entitiesLow-level design
no lesson for this one yetreported in:LeetCode Discuss · PhonePe LLD question, pendency system (2022) ↗
Design a malicious URL detection serviceSystem design
IP-11 · Design a Distributed Cache →W04 · DAY 01 · Caching Patterns →reported in:LeetCode Discuss · PhonePe system design, malicious URL detection (2023) ↗

Likely, from what they build

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

Design a Payment SystemSystem design
SQ-01 · India's UPI →IP-20 · Design a Payment System →W02 · DAY 02 · Idempotency in Practice →

Study path

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

01SQ-01India's UPIthe UPI flow, PSPs and NPCI
02W02 · DAY 02Idempotency in Practiceexactly-once debits
03W01 · DAY 04Hot Keys and Skewone hot merchant or account
04W01 · DAY 01Partitioning Deep-Divesharding payment data
05W01 · DAY 02Replication Trade-offsreplicas, lag and what to read from where
06SQ-04Visa/Mastercard Global Payment Networkhow card networks compare to UPI
07W10 · DAY 02Observabilityseeing a failing bank before users do
08W10 · DAY 01SLIs, SLOs and SLAsSLOs for payment success
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.

← all companies Sit the Bill payments and AutoPay mock →