PhonePe | Software Engineer | Dec 2024
Question Details
Experience: 3+ Years Company: PhonePe Role: Software Engineer (3-5 yoe) Location: Bangalore Applied through referral __
Round 1 Machine Coding | 1.5 hr Activity tag logging system. Functionalities to build: 1. user should be able to add tags to...
Full Details
Experience: 3+ Years
Company: PhonePe
Role: Software Engineer (3-5 yoe)
Location: Bangalore
Applied through referral
**
Round 1 Machine Coding | 1.5 hr**
Activity tag logging system.
Functionalities to build:
1. user should be able to add tags to activity in hierarchical order.
2. user should be able to retrive count of how many times tag is used accross all entity
Focused Skills: Design Patterns, Time complexity, Code quality
After few days code evaluation round was schedule where you have to explain your approach and tradeoffs if any to the interviewer
Verdict Strong Hire
**
Round 2 DSA and Problem Solving | 1 hr**
1. https://leetcode.com/problems/matchsticks-to-square/description/
2. https://leetcode.com/problems/kth-smallest-element-in-a-sorted-matrix/description/
Focused Skills: Problem Solving approach, Time/Space complexity
Verdict Lean Hire
**
Round 3 Design | 1 hr**
Design Twitter
Functionalities:
1. Post Tweet
2. follow-following
3. user timeline
4. user profile
Focused Skills: LLD, HLD
Verdict Strong Hire
**
Round 4 Hiring Manager | 1hr**
Questions from resume and previous projects/features I worked on.
Focused Skills: Deep understanding of the work you have done previously and design decisions
Verdict Strong Hire
Final
Verdict Hire
About This Question
This is a reported interview question from a twitter/x interview for a swe role during the phone screen round reported in 2025.
About Twitter/X Interview Reports
This question was reported by a candidate who interviewed at Twitter/X. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Twitter/X are the higher-signal extractions to take from this report.
For broader preparation context, the Twitter/X interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Twitter/X reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Twitter/X Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Twitter/X reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.