Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · PhonePe

PhonePe Technical Interview 2026: UPI & DSA

PhonePe's coding rounds tie classic data-structures and algorithms to payments reality: sliding-window top-K over a UPI transaction stream, rate limiting per merchant at thousands of requests per second, and dynamic-programming counting problems framed as cashback denominations.

By the HireStepX editorial team · How we source and label this

Questions7
Rounds3
Intense4 of 7
FrameworkReason-Aloud DSA
Try it · PhonePe question 1 of 7
Standard

On-call has gotten miserable, engineers paged 3-4 times/night, half false alarms. Walk me through the redesign you'd lead.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect medium-to-hard problems where the interviewer wants your optimal-substructure reasoning stated aloud, an honest complexity analysis, and a note on idempotency or concurrency because the code would sit in a real payments backend. Puzzles for their own sake are rare; in-domain framing is the norm.

Practice questions

  1. 01

    On-call has gotten miserable, engineers paged 3-4 times/night, half false alarms. Walk me through the redesign you'd lead.

    StandardTech-leadership operational craft. Wants: alert-tier discipline (paging vs warning), runbook hygiene, blameless postmortem culture, on-call-load metric tracked weekly. 'We'd just fix the alerts' fails, wants the system change.
    Practise
  2. 02

    Given a stream of UPI transactions, find the top-K merchants by volume in the last 10 minutes with a sliding window. Walk me through your data structure choice.

    IntensePhonePe technical rounds tie DSA to payments reality: expect stream-processing, idempotency, and concurrency framed around real UPI scale rather than abstract puzzles.
    Practise
  3. 03

    Implement a rate limiter for an API that must allow 5000 requests per second per merchant. Which algorithm, and how does it behave at the boundary?

    Intense
    Practise
  4. 04

    Find the number of ways to make a payment of amount N using given UPI cashback denominations. Then optimise the space complexity of your DP.

    StandardClassic coin-change framed in-domain. PhonePe wants the optimal-substructure reasoning stated aloud and the 2D→1D DP space optimisation.
    Practise
  5. 05

    Design a pipeline that computes daily per-merchant settlement summaries from a high-volume UPI transaction stream. How do you guarantee no transaction is double-counted?

    IntensePhonePe data-engineer rounds probe exactly-once aggregation over payment streams: idempotency keys, dedup windows, and reconciliation against ledger.
    Practise
  6. 06

    Write SQL to detect merchants whose daily transaction success rate dropped below 90% on any day in the last week, across all states.

    StandardPhonePe tests analytical SQL with conditional aggregation and partitioned thresholds for payment-health monitoring.
    Practise
  7. 07

    How would you build a fraud-signal feature pipeline that computes rolling per-user aggregates (velocity, distinct devices) with low latency for scoring?

    IntensePhonePe probes real-time feature engineering: rolling windows, stateful stream processing, and latency budgets for fraud scoring.
    Practise
Prep notes

How to walk in ready.

The typical PhonePe recruitment process has 4 stages: Online coding assessment on a DSA platform → Technical coding round one on data structures and algorithms → Technical coding round two on harder problems and complexity → Hiring-manager or bar-raiser round, then offer.

PhonePe typically conducts 3 interview rounds: Round 1 (60-90 min): online assessment with two to three DSA problems; Round 2 (60 min): live coding on arrays, strings, and sliding-window or heap problems; Round 3 (60 min): harder coding round with dynamic programming and complexity discussion.

HireStepX recommends the Reason-Aloud DSA framework for this type of interview: State the brute force, name the pattern (sliding window, DP, heap), optimise with the invariant spoken out loud, then analyse time and space and mention the production edge case.

Tech-leadership operational craft. Wants: alert-tier discipline (paging vs warning), runbook hygiene, blameless postmortem culture, on-call-load metric tracked weekly. 'We'd just fix the alerts' fails, wants the system change.

PhonePe technical rounds tie DSA to payments reality: expect stream-processing, idempotency, and concurrency framed around real UPI scale rather than abstract puzzles.

Classic coin-change framed in-domain. PhonePe wants the optimal-substructure reasoning stated aloud and the 2D→1D DP space optimisation.

PhonePe data-engineer rounds probe exactly-once aggregation over payment streams: idempotency keys, dedup windows, and reconciliation against ledger.

PhonePe tests analytical SQL with conditional aggregation and partitioned thresholds for payment-health monitoring.

Practice

Rehearse the room before you enter it.

Run a mock PhonePe interview and get scored feedback on every answer.