PhonePe interview rounds
Pick your level above: the list shows only your rounds, with what interviewers score at that level.
-
Phone / recruiter screen · 20 min
An HR call on experience and expectations.
At : Usually one medium problem. Explain your idea before coding and test by hand at the end.
At : One or two problems, a little faster. Some companies mix in a design question.
At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.
At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.
-
Online assessment · 90 min
Campus hiring uses a coding test; lateral loops usually start straight with machine coding.
At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.
At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.
At : Rare. Most companies replace it with a live screen for senior candidates.
At : Almost never used.
-
Low-level design / machine coding · 90 min
Machine coding: about 90 minutes to build a working in-memory app, then a 30-minute debrief full of 'why' questions.
At : Object-oriented design with clear classes and responsibilities. Working code matters more than patterns.
At : The core round at many product companies: working, modular, extensible code with validation, error handling and tests, finished on time.
At : Same as SDE 2 plus concurrency (two users booking the same seat) and a clean extension story.
At : Rare as a standalone round; folded into design discussions.
-
Coding (DSA) · 60 min
PSDS: two problems candidates often rate hard; a well-explained approach can earn partial credit.
At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.
At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.
At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.
At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.
-
System design (HLD) · 60 min
Database choice, auth at the gateway, token propagation between services, and scaling.
At : Usually absent, or light design questions inside a coding round.
At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.
At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.
At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.
-
Hiring manager · 55 min
Your current project's architecture in depth (sharding, replication, APIs), sometimes with a design problem.
At : Motivation, learning, a project walk-through and sometimes CS fundamentals.
At : Ownership of features, handling production issues, working with product and other teams.
At : Technical leadership, mentoring, and how you choose what to work on.
At : Strategy, influence without authority and the biggest bets you have made.
What interviewers look for
- A working, modular machine-coding submission with validations and error handling
- Thread safety in the machine-coding code
- Justifying data structures and design patterns
- Optimal DSA under pressure
- Depth on your own system's architecture
Worth knowing
- The customer issue resolution machine-coding problem appears in both 2024 and 2025 reports.
- An August 2025 SDE-2 loop: machine coding (90 + 30), PSDS (60), design (60) and manager (55).
- Machine coding is graded on structure, validation, error handling and concurrency, not just whether it works.
Sources
Written in our own words from public candidate reports and PhonePe's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with PhonePe.
- techprep.app/blog/phonepe-interview-process
- roundz.substack.com/p/interview-experience-174-phonepe-sde2
- glassdoor.com/Interview/PhonePe-Interview-E2289138-RVW103053712.htm
- leetcode.com/discuss/post/7539137/phonepe-backend-software-engineer-3-5-ye-n5mi/
- leetcode.com/discuss/interview-experience/7087077
- leetcode.com/discuss/post/7770543/phonepe-software-engineer-5-7-years-bang-tppy/
- jointaro.com/interviews/companies/phonepe/experiences/software-development-engineer-sde-be
- lets-code.co.in/interview-experience/phonepe-sde-(android)/6917137c1bde4aa8817070c3/
- placementpreparation.io/blog/phonepe-interview-questions-and-experience/
- raw.githubusercontent.com/liquidslr/leetcode-company-wise-problems/main/PhonePe/5.%20All.c
- raw.githubusercontent.com/snehasishroy/leetcode-companywise-interview-questions/master/pho
Questions people ask
How many interview rounds does PhonePe have for SDE 1 (Software Engineer 1)?
About 3 interviews after the screening: phone / recruiter screen, online assessment, low-level design / machine coding, coding (dsa), hiring manager. Design is part of the loop at this level.
How many interview rounds does PhonePe have for SDE 2 (Software Engineer 2)?
About 4 interviews after the screening: phone / recruiter screen, low-level design / machine coding, coding (dsa), system design (hld), hiring manager. Design is part of the loop at this level.
How many interview rounds does PhonePe have for SDE 3 (Senior Software Engineer)?
About 4 interviews after the screening: phone / recruiter screen, low-level design / machine coding, coding (dsa), system design (hld), hiring manager. Design is part of the loop at this level.
What coding questions does PhonePe ask?
The most reported are Distribute Coins in Binary Tree, Word Search, Word Search II, LRU Cache, Subarray Sum Equals K, Water and Jug Problem. Candidates say PhonePe focuses on trees, prefix sums, sliding window, graphs, dynamic programming.