The hiring process
| Round | Format | What's tested |
|---|---|---|
| Machine Coding | ~2 hours | Build clean OOP services in real time |
| Machine-Coding Walkthrough + DSA | ~60 min | Design defense + problem-solving |
| DSA + System Design | ~60-90 min | Hard problem + architecture |
| Hiring Manager | ~45 min | Ownership and culture |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Machine Coding
~2 hoursRoughly 15 minutes clarifying requirements, then the rest implementing a working, object-oriented service. This round eliminates the most candidates; grading centers on clean abstractions, SOLID, and extensibility.
- Design an extensible wallet/ledger service
- Model a splitwise-style expense manager
- Build a rate limiter or notification dispatcher
- Design a booking or inventory system
- Extend your design cleanly for a new requirement
- Build full OOP systems under a 2-hour timer
- Master SOLID and design patterns (strategy, factory, observer)
- Structure into modules with clear interfaces + tests
- Practice clarifying requirements in the first 15 min
- Not finishing a working solution
- Monolithic, non-extensible code
- Skipping requirement clarification
- Working, modular OOP solution
- Extensible, SOLID design
- Good clarifying questions
Machine-Coding Walkthrough + DSA
~60 minThe interviewer walks through your machine-coding submission, probing design decisions and trade-offs, then moves to one or two medium-hard DSA problems to test problem-solving breadth.
- Justify class boundaries and trade-offs in your design
- Medium-hard graph or tree problem
- Heap or stack based problem
- Sliding window / two pointers
- DP medium-hard
- Be ready to defend every design decision
- Drill medium-hard DSA across graphs/heaps/DP
- Rehearse complexity and edge-case discussion
- Practice explaining trade-offs concisely
- Can't justify your own design choices
- Weak on harder DSA
- No complexity analysis
- Confident design justification
- Strong DSA breadth
- Clear trade-off reasoning
DSA + System Design
~60-90 minOne hard DSA problem followed by system design. For SDE-1 the design portion is light; for SDE-2+ expect full HLD covering database choices, API contracts, scalability, and fault tolerance, often on payment-infra themes.
- A hard DSA problem (advanced graph/DP)
- Design a payment transaction system with retries
- Idempotency and exactly-once semantics
- Rate limiting at scale
- Event-driven architecture for payments
- Practice LC-hard on graphs and advanced DP
- Study idempotency, retries, and distributed transactions
- Learn rate limiting and event-driven design
- Do 2 payment-infra mock designs (SDE-2+)
- Freezing on the hard DSA problem
- No idempotency/retry plan in design
- Ignoring fault tolerance
- Handles hard DSA with structure
- Payment-domain design awareness
- Fault-tolerant, idempotent thinking
Hiring Manager
~45 minA behavioral and culture round assessing ownership mindset, handling ambiguity, and cross-team collaboration, with project deep-dives.
- A project you owned end-to-end
- Handling ambiguity or shifting requirements
- Cross-team collaboration or conflict
- A production incident and your response
- Why PhonePe
- Prepare 4-5 STAR stories emphasizing ownership
- Ready a strong project deep-dive
- Research PhonePe's payment scale
- Prepare questions for the manager
- Vague, low-ownership stories
- No specific motivation
- Overclaiming impact
- Strong ownership mindset
- Comfort with ambiguity
- Genuine interest
What to master
- Medium-hard DSA: graphs, heaps, DP
- OOP, SOLID, design patterns
- Machine coding under a 2-hour timer
- Idempotency, retries, exactly-once
- Rate limiting and event-driven design
- Distributed transactions and fault tolerance
- Payment-infra system design
- Ownership STAR stories
Eligibility
SDE-1 through SDE-3. Machine coding is central across levels; full HLD is added for SDE-2 and above.
PhonePe salary & compensation (2026)
Among the most aggressive payers in Indian fintech; large ESOP grants make senior packages equity-heavy.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE-1 | 0-2 yrs | ₹28-42 LPA | — | very strong fixed + ESOP; top campuses can hit ₹40L+ |
| SDE-2 | 2-5 yrs | ₹45-70 LPA | — | ESOP grant is substantial; market-leading fixed |
| SDE-3 | 5-8 yrs | ₹75-120 LPA | — | ESOP can be 30-40% of CTC |
| Staff / Architect | 8-12 yrs | ₹130-190 LPA | — | equity dominates; deep-scope ownership |
| Principal | 12+ yrs | ₹200-280 LPA | — | top of Indian fintech pay; large ESOP refreshers |
How the package is structured
- Known for high fixed AND high ESOP, so total CTC often tops peers.
- ESOPs vest 4 yrs with periodic buybacks providing liquidity.
- Joining bonus ₹3-6L to offset prior-employer clawbacks.
- Lever: PhonePe pays up to win competitive offers, so competing bids materially raise both fixed and ESOP.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1-4: Build OOP systems under a 2-hour timer repeatedly
- Days 5-7: Medium-hard DSA (graphs/heaps/DP)
- Days 8-10: Payment-infra system design (idempotency, retries, rate limiting)
- Days 11-12: LC-hard practice + design walkthroughs
- Day 13: Ownership STAR stories
- Day 14: Full mock loop
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Which round eliminates the most candidates?
The machine-coding round. Practice building complete, extensible OOP services under a 2-hour timer.
How hard is the DSA?
Medium to hard, including one hard problem in a later round. Focus on graphs, heaps, and advanced DP.
What design topics come from PhonePe's domain?
Payment-infra themes: transaction retries, idempotency and exactly-once semantics, rate limiting, and event-driven architectures.
How much design at SDE-1 vs SDE-2+?
SDE-1 gets a lighter design portion; SDE-2 and above face full HLD covering DB choices, API contracts, scalability, and fault tolerance.
How should I prepare for machine coding?
Repeatedly build working OOP systems under time, spend the first ~15 minutes clarifying requirements, and make your design extensible with tests.
How many rounds?
Typically 4-5 across DSA, machine coding, design, and a hiring-manager round.