PhonePE

1. Application or referral

Roles are posted on the PhonePe careers site and LinkedIn. Employee referrals are common and are the fastest route for experienced candidates. Freshers mostly come through campus placements at engineering colleges and business schools.

2. Recruiter screening

A short call to confirm your experience, current role, notice period and expectations, and to explain the interview loop for the specific team. Recruiters also check that you have used the app and understand the business you are applying to.

3. Online assessment or machine coding

Engineering candidates typically get a coding test or a take-home or live machine-coding exercise where a small working application has to be built with clean design. Analytics roles get SQL and case-based questions; product roles may get a written product exercise.

4. Technical or functional interviews

Two to three rounds with engineers, analysts or product managers from the hiring team. Depth of understanding matters more than breadth; interviewers keep probing until they find the edge of what you know.

5. Hiring manager and leadership round

A conversation with the hiring manager and often a senior leader on ownership, decision making, collaboration and cultural fit.

6. HR round and offer

Compensation structure including ESOPs, location and joining dates are finalised. Most loops close within three weeks of the first interview.

PhonePe's engineering loop is considered one of the tougher ones among Indian fintechs; business roles are more case-driven.

Round 1: Machine coding or online test

For engineers this is a 90 to 120 minute exercise to build a small system, such as a parking lot, a splitwise-style ledger or a rate limiter, followed by a discussion of your design choices. Freshers may get a standard coding test instead.

• Clean object-oriented design and separation of concerns
• Handling edge cases and extensibility
• Unit-testable code structure

Round 2: Data structures and algorithms

A 60 minute interview with one or two medium to hard problems solved live. The interviewer expects optimal complexity and will ask follow-ups that change constraints.

• Graphs, heaps and dynamic programming
• Sliding window and binary search variants
• Concurrency basics for backend candidates

Round 3: System design

For candidates with roughly two or more years of experience. Expect payment-domain problems and questions on consistency, idempotency, retries and observability.

• Design UPI transaction processing with bank timeouts
• Design a notification service at hundreds of millions of users
• Database sharding and hot-key handling

Round 4: Product or analytics case

Product managers and analysts get a 45 to 60 minute case built around a real PhonePe surface, such as improving merchant retention or diagnosing a metric drop, and are expected to structure the problem and quantify trade-offs.

• Sizing the addressable market for a new feature
• Choosing metrics for a merchant lending product
• SQL on transaction tables for analysts

Round 5: Hiring manager and culture fit

Behavioural questions on ownership, disagreement with stakeholders and learning from failure, plus a discussion of what you would do in the first 90 days.