Autocoder

PhonePe Interview Questions and Answers

Last updated 2026-11-19

PhonePe sits on UPI rails and a large merchant network, so its interviews, as candidates describe them, lean on low-level design and on thinking about money moving reliably between parties. This page gives practice questions with worked answers on UPI basics, design patterns, scaling and behaviour.

They are practice questions on the topics the rounds are commonly reported to cover, not a record of what anyone was asked in a given year. The coding side is in PhonePe coding round questions, and the process in how to crack the PhonePe interview.

Typical roundsDSA screen, technical rounds with LLD, managerial (commonly reported)
RolesSDE-1

Rounds as commonly reported

Candidate reports for SDE-1 describe an online or DSA screen, then technical rounds covering DSA and low-level design, with system design for senior roles, and a managerial or HR round on behaviour and fit.

PhonePe does not publish its rounds; the structure varies by team and level.

Hiring status

A sourced fact from PhonePe's own press release: it plans to hire more than 20,000 on-roll frontline sales staff over the next year and deploy 50 lakh payment devices. These are sales roles, not engineering. See PhonePe hiring for more, and apply through the careers page at phonepe.com/careers.

Preparing for the design round

Know three or four patterns well: strategy, factory, observer and state. For each, have a payments example ready, such as strategy for payment instruments or state for a transaction lifecycle.

PhonePe Interview Questions and Answers: questions with worked answers

  1. 1

    Explain the steps of a UPI payment at a high level.

    medium

    The payer's app sends a pay request through the payer's PSP bank to the NPCI switch, which routes it to the payee's bank using the virtual payment address. The payer's bank is debited and the payee's bank credited through the switch, and each side receives a response. The app shows the status. Say that exact internals are not public, and focus on the parts you can reason about: authentication with the UPI PIN, timeouts, and status checks for pending transactions.

  2. 2

    A payment shows debited but the merchant shows failed. How do you design for this?

    hard

    Treat it as a pending state, not a failure. Persist the transaction before calling the bank, poll or receive the final status, and run a reconciliation job against bank statements. Auto-reverse debits that never complete, notify the user, and make every state transition idempotent so a late callback cannot flip a refunded transaction to success.

  3. 3

    Model transaction status with the State pattern.

    medium

    Create a Transaction with a state object: Initiated, Pending, Success, Failed, Reversed. Each state class defines which events it accepts, so Success rejects a later Failed event. This replaces a long if-else on status with small classes, makes illegal transitions explicit, and lets you add Refunded without editing existing states.

  4. 4

    Design a payment instrument system that supports UPI, card and wallet.

    medium

    Define a PaymentInstrument interface with validate() and pay(amount). UPI, Card and Wallet implement it, and a factory chooses the right class from the request. Orchestration code depends on the interface only, so adding net banking means one new class. Keep fees, limits and retries in separate strategies rather than inside the instruments.

  5. 5

    How would you design a distributed rate limiter for the payments API?

    hard

    Use a token bucket or sliding window counter in a shared store like Redis, keyed by client or merchant, with atomic increments through a script. Return 429 with Retry-After. For very high throughput, allow small local counters that sync periodically, and accept slight over-admission in exchange for fewer network calls. Choose a policy for when the store is down, which for payments is usually to fail open with a local limit.

  6. 6

    Difference between optimistic and pessimistic locking, and where each fits.

    medium

    Pessimistic locking takes a lock before changing data, which suits high contention such as a hot merchant balance, at a cost to throughput. Optimistic locking uses a version column, checks it at update time and retries on conflict, which suits low contention. Both need a retry or failure path in the caller.

  7. 7

    What is eventual consistency, and where is it acceptable in payments?

    medium

    Replicas converge over time instead of agreeing instantly. It is acceptable for the transaction history screen, analytics and notifications. It is not acceptable for the debit decision, which must read the latest balance or use a single source of truth with strong consistency. Say which data you would put in each category.

  8. 8

    How do you design a ledger?

    hard

    Use double-entry: every transaction writes at least two immutable rows, a debit and a credit, that sum to zero, in one database transaction. Balances are derived or cached from the entries. Never update or delete entries; correct mistakes with reversing entries. This gives an audit trail and makes reconciliation a sum check.

  9. 9

    Explain the SOLID principle you find most useful and show an example.

    easy

    Pick one and be concrete. Open-closed: a discount calculator takes a Discount interface, so adding festival offers adds a class rather than editing a switch statement. Name the cost, which is more small classes, and when it is not worth it, such as for a rule that will never change.

  10. 10

    Design a notification system for payment success and failure.

    medium

    Publish a payment event to a queue; a notification service reads it, picks channels from user preferences, renders a template, and sends through push, SMS or email providers. Deduplicate on event id, retry with backoff, and keep a delivery log. Critical messages such as failed debits must not be dropped, so use a durable queue and alerts on lag.

  11. 11

    Tell me about a time you worked with an unclear requirement.

    easy

    Use STAR. Describe the situation, the questions you asked to narrow it, a short written assumptions list you shared, and a small first version that tested the riskiest assumption. End with how the requirement settled and what you would ask sooner next time.

  12. 12

    Why PhonePe and why engineering over other roles?

    easy

    Mention the scale and the reliability demands of payments as the draw, a related project or topic you have studied, and what you want to learn. Be honest about what you do not yet know and how you are closing the gap.

Frequently asked questions

Does PhonePe focus on low-level design?

Candidate reports for SDE-1 mention low-level design alongside DSA. Prepare patterns and clean class design.

Do I need to know UPI internals?

Not in detail. Know the flow at a high level and be able to reason about pending states, retries and reconciliation.

Is system design asked to freshers?

It is more often reported for senior roles. Freshers should still understand caching, queues and databases.

Where can I find PhonePe openings?

On the company's careers page, and in PhonePe hiring for sourced news.

Sources

Related guides

More in Company Interview Questions

See all in this section