phonepe logo
PhonePe· Backend Engineering, SDE-III

Phonepe Interview Experience | 6 YOE | SDE-III

Experience
6 years
Posted
17 Mar 2026
517 reads

Summary

I cleared two technical rounds (Machine Coding and Data Structures & Algorithms) for a Backend Engineering, SDE-III role at Phonepe but was ultimately rejected in the System Design round, which felt complex and lacked clear communication from the interviewer.

How it went

Role - Backend Engineering (5-7 YOE).

Round 1: It was a Machine Coding round, where there were multiple candidates on call, interviewer came and gave the problem and then asked candidates to solve them on thier own, once done we were supposed to share the code in a zip file to the recruiter. There was a time limit of around 1.5 hour to solve that.

After submission there was a evaluation call where the interviewer came and discussed about the implementation and it was for around 30 mins.
Problem Stamement: : HackAthon Platform

Verdict: Pass

Round 2: It was DSA Round, there were two hard levels problems asked
Problem 1: Sliding Window Maximum I was not able to give the most optimal solution it was roughly O(nlog(n))
Problem 2: Burst Ballon I was able to solve this

Verdict Pass

Round 3: System Design round
Problem: Design a order feed system for a food ordering app where users can see the real time updates to their orders.
Requirements:
1.⁠ ⁠Different category services involved in order path publish realtime context data into feed service under
a global orderId during the order life cycle. Expected Latency: < 50ms
2.⁠ ⁠Client apps can poll feed service for a consumer in real time(<10 ms).
3.⁠ ⁠It should give search/filtering option to user based on orderId, restaurantId, order status, time-window etc.(<150 ms)
4.⁠ ⁠It should allow user to download summary of past orders with a relaxed SLA(<2 sec) with time window constraints for eg. Last 6 months.

Number of users: 500m
Number of daily active users: 100m
Number of orders: 80m
Number Restaurants: 50m
Read qps: 5000
Write qps: 1500


This was not a good round as interviewer made the problem complex even after asking questions was not giving proper answers. Did not went through the process just asked directly to give the design. Overall this round was not good.

Verdict Rejected.

Questions asked (4)

  1. 01

    HackAthon Platform Machine Coding

    Data Structures & Algorithms

    The problem statement was to build a HackAthon Platform. The candidates were asked to solve it on their own within 1.5 hours, then share the code in a zip file to the recruiter. An evaluation call followed for about 30 minutes to discuss the implementation.

    Open the problem
  2. 02

    Sliding Window Maximum

    Data Structures & Algorithms · Hard

    I was asked to solve the Sliding Window Maximum problem.

    Open the problem
  3. 03

    Burst Balloons

    Data Structures & Algorithms · Hard

    I was asked to solve the Burst Balloons problem.

    Open the problem
  4. 04

    Design Order Feed System

    System Design

    Design an order feed system for a food ordering app where users can see real-time updates to their orders.
    Requirements:

    1. Different category services involved in order path publish real-time context data into feed service under a global orderId during the order life cycle. Expected Latency: < 50ms
    2. Client apps can poll feed service for a consumer in real time(<10 ms).
    3. It should give search/filtering option to user based on orderId, restaurantId, order status, time-window etc.(<150 ms)
    4. It should allow user to download summary of past orders with a relaxed SLA(<2 sec) with time window constraints for eg. Last 6 months.
    Number of users: 500m
    Number of daily active users: 100m
    Number of orders: 80m
    Number Restaurants: 50m
    Read qps: 5000
    Write qps: 1500

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at PhonePe recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!