← Interview experiences
Got the offer

Software Engineer at PhonePe

Difficulty
Process took
2-3 Weeks
Rounds
4
Format
Remote
Applied via
Company Website

How it went

  • PhonePe’s process is structured and strongly backend/product-focused. Expect practical real-world systems and questions tied to domain understanding.
  • Keep communication crisp. Ask clarifying questions and explain choices confidently, even partial solutions can be appreciated if they show depth.

What they would tell you

  • PhonePe’s process is structured and strongly backend/product-focused. Expect practical real-world systems and questions tied to domain understanding.
  • Keep communication crisp. Ask clarifying questions and explain choices confidently, even partial solutions can be appreciated if they show depth.

How to prepare

  • For machine coding, focus on design patterns, code extensibility, and clean interface separation.
  • Prepare for Hiring Manager rounds that reflect ownership, problem-solving under constraints, and end-to-end delivery.

Round by round

  1. 1

    Machine Coding60 min

    I was asked to build a Dispute Management System where users could raise disputes like GOLD, MUTUAL FUND, or PAYMENT related issues. The goal was to make sure each dispute got assigned to an agent who really knew their stuff for that specific dispute type. What made it interesting was figuring out how to always send the dispute to the least busy agent with the right expertise, so the workload was balanced fairly. Plus, the system needed to be flexible enough so that later on, they could easily add new ways to assign disputes if needed. I enjoyed working on a design that was not just functional but also clean and easy to extend, which I think is important for any system that might grow or change over time.

  2. 2

    DSA60 min

    One of the questions was a grid-based problem where I had to find the nearest 1 for each 0 using the minimum number of steps. It was a classic multi-source BFS problem and followed a standard pattern. The second question was based on Binary Search. I don’t remember the exact details, but it needed a strong understanding of edge cases and fine-tuning of conditions to get it right.

  3. 3

    System Design60 min

    I was asked to design WhatsApp, covering both 1:1 and group chats. The discussion included features like message delivery, read receipts, and how to model data for users, messages, and groups. We also talked about how to handle scalability, ensure real-time message delivery, and what kind of database structure would support such a system efficiently. It was a deep dive into both system design and data modeling.

  4. 4

    Hiring Manager60 min

    This round was more about understanding me as a professional. We had a deep dive into my past projects, where I shared examples of ownership and how I made key decisions. We also discussed how I handle ambiguous requirements, and my experience working with cross-functional teams. Toward the end, the conversation shifted to my career goals and whether I’d be a good fit for the team and company culture.

What came up

HardRemote3 4 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources