Rapido.
A ride-hailing app for bike taxis, autos and cabs across 150+ Indian cities, matching riders with captains in real time.
its questions lean on
- geospatial matching
- real-time location
- microservices and data ownership
- SQL vs NoSQL and indexing
- mobile feed architecture
Reported by candidates
From public interview write-ups; each links its source.- Design an LRU CacheLow-level designLLD-02 · Design an LRU Cache →reported in:Learn with Rashika (blog) · Rapido Interview Experience, On Campus (2023) ↗
- Design a Server-Driven Video Feed for a Mobile AppSystem designSQ-19 · YouTube Video Platform →W04 · DAY 04 · Feed Caching →reported in:LeetCode Discuss · Rapido Android Developer (2022) ↗
- How do you send a push notification to one specific device?ConceptW06 · DAY 02 · Core Notification Flow →IP-06 · Design a Notification System →reported in:LeetCode Discuss · Rapido Android Developer (2022) ↗
- Monolith or microservices, and should each microservice own its database?ConceptW00 · PART 1 · System Design Fundamentals →W03 · DAY 02 · Transactional Outbox →reported in:GeeksforGeeks · Rapido Interview Experience for SDE-2, Off-Campus (2023) ↗
- What is horizontal versus vertical scaling?ConceptW00 · PART 1 · System Design Fundamentals →W10 · DAY 04 · Capacity Planning →reported in:GeeksforGeeks · Rapido Interview Experience for SDE-2, Off-Campus (2023) ↗
- SQL or NoSQL, and when does an index not help?ConceptW00 · PART 2 · Infrastructure Building Blocks →W00 · PART 6 · System Design Terminology & Theory →reported in:GeeksforGeeks · Rapido Interview Experience for SDE-2, Off-Campus (2023) ↗
Likely, from what they build
Our pick, not a report: questions that fit Rapido's products.- Design a Ride-Hailing ServiceSystem designSQ-09 · Uber →IP-13 · Design a Proximity Service →
- Design a Proximity ServiceSystem designIP-13 · Design a Proximity Service →W01 · DAY 04 · Hot Keys and Skew →
- Design Live Captain Location Tracking and ETASystem designSQ-09 · Uber →W08 · DAY 01 · Event Ingestion at Scale →W03 · DAY 03 · Backpressure and Flow Control →
- Design a Surge Pricing EngineSystem designW08 · DAY 02 · Streaming vs Batch Processing →SQ-09 · Uber →
- Design a Captain Wallet and Daily PayoutsSystem designIP-20 · Design a Payment System →W02 · DAY 02 · Idempotency in Practice →W03 · DAY 05 · Audit Log System →
- Design a Cab Booking App (LLD)Low-level designSQ-09 · Uber →
Study path
Every lesson the questions above point to, once, in order.
- 01LLD-02Design an LRU Cache
- 02SQ-19YouTube Video Platform
- 03W04 · DAY 04Feed Caching
- 04W06 · DAY 02Core Notification Flow
- 05IP-06Design a Notification System
- 06W00 · PART 1System Design Fundamentals
- 07W03 · DAY 02Transactional Outbox
- 08W10 · DAY 04Capacity Planning
- 09W00 · PART 2Infrastructure Building Blocks
- 10W00 · PART 6System Design Terminology & Theory
- 11SQ-09Uber
- 12IP-13Design a Proximity Service
- 13W01 · DAY 04Hot Keys and Skew
- 14W08 · DAY 01Event Ingestion at Scale
- 15W03 · DAY 03Backpressure and Flow Control
- 16W08 · DAY 02Streaming vs Batch Processing
- 17IP-20Design a Payment System
- 18W02 · DAY 02Idempotency in Practice
- 19W03 · DAY 05Audit Log System
Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.