The loop starts with an online assessment (2-3 DSA problems, 90 minutes), a machine coding round where you build a working system from scratch in 90 minutes, two problem-solving whiteboard rounds, a system design round for SDE-2+ roles, and a hiring manager behavioral round. Their system design questions are rooted in India-specific constraints: tier-3 pincode delivery, kirana last-mile logistics, monsoon season traffic spikes: and you'll be asked to design at 10x scale and defend trade-offs explicitly. DSA topics that consistently appear: trees and graphs with BFS/DFS variations, medium-hard dynamic programming, hashmaps and two-pointer techniques, and matrix or grid problems.
Recruitment process
- Resume screen: competitive; referrals increase visibility significantly
- Online Assessment: 2-3 DSA problems (medium-hard difficulty), 90 minutes
- Machine Coding Round: build a working system from scratch in 90 minutes with clean OOP design
- Problem Solving x2: whiteboard-style DSA with follow-up complexity questions
- System Design Round: architecture, trade-offs, and 10x scale thinking (SDE-2+ roles primarily)
- Hiring Manager Round: ownership stories, communication clarity, cultural fit
Interview rounds
- Online Assessment (90 min): 2–3 medium-hard DSA problems: the primary filter. Most candidates don't clear this stage
- Machine Coding (90 min): Build a full working application (parking lot, ride-sharing, inventory system). OOP design, edge-case handling, and extensibility matter
- Problem Solving x2 (45 min each): Whiteboard DSA with follow-up complexity questions. Trees, graphs, and DP appear most often
- System Design (60 min, SDE-2+): Design at 10x scale with India-specific constraints. Start with QPS and storage estimates before solution
- Hiring Manager (45 min): Ownership stories, communication clarity, and 'would this person raise the bar on our team?'
Capacity-first design framework
- Start with QPS + storage estimates
- reads/writes ratio
- bottlenecks
- solution
- cost.
Practice questions
- 01Practise
Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.
IntenseFlipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships. - 02Practise
We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?
IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific. - 03Practise
Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?
Intense - 04Practise
Design Swiggy Genie's matching algorithm. How does it differ from food-order matching?
Intense - 05Practise
Walk me through how you'd architect transaction-level fraud detection for 100M daily UPI transactions.
IntensePhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale. - 06Practise
How would you build a recommendation engine that suggests bills the user is about to forget?
Standard - 07Practise
Design a cashback-allocation system that prevents abuse without alienating genuine users.
Standard - 08Practise
Design a system to detect duplicate documents at web scale. What's your approximation strategy?
IntenseGoogle SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating. - 09Practise
Design Amazon Prime's recommendation engine. How would you handle the cold-start for a new Prime member?
Intense - 10Practise
Design a URL shortener like bit.ly. Walk me through database choice and scaling.
Standard
