System design interview guide
Rapido System Design Interview: Bike-Taxi Dispatch at Scale
Two courses by the author of this page:
770 lessons · 18 free to read
₹1,111 in India · $35 elsewhere, once
Get System DesignYou own this course
219 lessons · 10 free to read
₹1,333 in India · $35 elsewhere, once
Get Generative AI and Agentic AIYou own this course
Save your progress and get the interview checklist PDF
Rapido grew to nearly half of India's ride-hailing on the back of two-wheeler taxis, reaching about 50 million monthly active users and 2 million earning captains. It also flipped the money model: instead of taking a cut of every ride, it charges captains a flat subscription and lets them keep the whole fare, which brought in 275 crore rupees of subscription income in a year.
Designing Rapido is a ride-hailing problem with two things that make it distinct. First, the core vehicle is a two-wheeler, and Rapido has published how it matches riders to nearby bikes, moving from a simple radius-and-straight-line approach to hex-grid geography with learned driving times. Second, the money model is different: rather than taking a commission on each ride, Rapido charges captains a flat subscription and lets them keep the full fare, which changes the settlement path from a per-ride commission ledger to a subscription-entitlement check. This walkthrough covers the two-wheeler dispatch that Rapido has published, the subscription money model and its system implications, and the data platform behind it, and is honest about which parts are published versus reasoned.
Where it shows up
Commonly asked at Rapido, Ola, Uber, and mobility teams, and the general forms, meaning design a ride-hailing app, a real-time matching system, or a subscription-billing system, show up at most product companies for SDE2 and SDE3 rounds. Rapido is a good question because it foregrounds two-wheeler matching and a genuinely different money model, so it does not collapse into a generic ride-hailing answer.
Spec sheetRapido
- 01Monthly active users
- ~50M (2025)
- 02Active captains
- ~2M earners
- 03Rides per day
- ~1.5M/day (2022, published)
- 04Subscription income
- ~275 crore rupees/year (~14x YoY)
worked through below, with the maths
in this guide
Design Rapido, part by part
7 parts open to everyone · 3 with a free account · 3 with the course
You can read 7 of 13 parts. A free account opens the deep dive; the course opens all of it.
- Requirementsopen
- Scale estimatesopen
- High-level architectureopen
- Core componentsopen
- Data modelfree account
- Deep dives (5)free account
- Trade-offs to discussfree account
- What the interviewer asks nextwith the course
- The interview scorecardwith the course
- Mock interview on this questionwith the course
- How Rapido actually does itopen
- Frequently asked questionsopen
- Interview readiness checkopen
The hard parts of this design are taught step by step in the System Design course: Design Uber/Ride Sharing, Stream Processing and Geospatial Indexing.
Why this question is asked
Ride-hailing tests real-time geospatial matching, but Rapido adds two distinctive angles that interviewers like. The dispatch problem is one Rapido has actually written about, including why a straight-line distance is misleading and how it moved to hex-grid geography and learned driving times, which makes for a concrete matching discussion. And the money model is a real design difference: charging captains a subscription instead of a per-ride commission replaces the commission calculation and ledger with an entitlement check and full-fare settlement, which is a different billing and money-movement design. Interviewers use Rapido to see whether you can design the matching core, reason about why driving time beats straight-line distance, and think through what a subscription model changes in the settlement path, rather than reciting a generic dispatch diagram.
This page is the free part.
The course goes deeper on the Rapido design
₹1,111 in India$35 everywhere elseonce, for the whole course
The System Design course covers the Rapido design across a run of lessons, not one page. These 4 alone are about 83 minutes of step-by-step reading, every one with a quiz.
- Geospatial Indexing
How databases efficiently answer 'find everything near me'. R-trees, geohashes, and spatial queries.
- WebSockets
Full-duplex, persistent connections, how the real-time web actually works.
- Message Queues
Decouple producers from consumers with a buffer that holds messages until they're processed.
- Cache-Aside Pattern
Cache-aside is said to degrade gracefully when the cache fails. Measured, unwrapped it answered 0.0 percent of requests, and wrapped it answered 13.0, which is exactly the database's capacity.
all part of
System Design Masterclass
770 lessons · about 290 hours · 18 free to read
₹1,111in India, by UPI
$35everywhere else, by card or PayPal
You own this course
Continue with Geospatial Indexingpay once,
yours for life
Live from the course bench
Before you design Rapido, try the questions it rests on.
Real interview questions, live diagrams and measured lab results, pulled at random from the lessons. A new set every time you come back.
Requirements
Always clarify these in the first 5 minutes of the interview. Do not start drawing boxes until both lists are agreed.
Functional requirements
- Rider requests a ride and is matched to a nearby captain, primarily on a two-wheeler, and also auto or cab
- Rider tracks the assigned captain approaching, then tracks the trip to the destination
- Fare is shown up front and settled at the end, by UPI, wallet, or cash
- Captains can subscribe to a plan that lets them take rides without a per-ride commission and keep the full fare
- The system verifies a captain's subscription entitlement rather than computing a commission on each ride, where the subscription model applies
- Support multiple vehicle types (bike, auto, cab) and also delivery, on one platform
- Show estimated time of arrival and trip time, learned from real ride data
- Handle demand across large cities and smaller towns
Non-functional requirements
- Match a request to a captain within seconds, with nearby-captain queries answered in low tens of milliseconds
- Accurate estimated arrival and trip times based on real driving conditions, not straight-line distance
- Live tracking updated every few seconds during a trip
- Correct money settlement: full fare to the captain under the subscription model, or the right split under commission
- High availability on the request, tracking, and settlement paths
- Scale to millions of rides a day across 100-plus cities
- Cost efficiency, since a mass-market, low-fare model depends on low cost per ride
Back-of-envelope scale estimates
Show your math. Pulling numbers from thin air signals you have not thought about the load.
Monthly active users
~50M (2025)
Rapido reported about 50 million monthly active users in 2025, ahead of some rivals. This is the demand side of the matching problem.
Active captains
~2M earners
Rapido reported about 2 million active earning captains, with roughly 160,000 new drivers onboarded a month. Captains are the supply side, and the subscription model is aimed at them.
Rides per day
~1.5M/day (2022, published)
Rapido's own data-platform post cited about 1.5 million rides a day across 100-plus cities as of late 2022. It has grown since, but this is the strongest figure Rapido itself published; treat later, larger daily-ride numbers from secondary blogs as unverified.
Subscription income
~275 crore rupees/year (~14x YoY)
Rapido reported about 275 crore rupees of subscription income in FY25, roughly 14 times the year before. This is the clearest evidence that the subscription money model is real and material, not a pilot.
Market position
~50% ride-hailing, bike-taxi leader
Rapido reported about half of India's ride-hailing overall and leads bike taxis, having grown fast in autos and cabs too. Its two-wheeler core is what set it apart from cab-first rivals.
Data platform scale
15+ PB/month, ~1,000 pipelines
Rapido's data-platform post reported processing more than 15 petabytes a month across about 1,000 pipelines and 3,000 datasets, with 12,000 to 15,000 queries a day. This is the analytics backbone behind matching and pricing.
High-level architecture
Design Rapido around two-wheeler matching and a different money model. The dispatch evolution and the data platform are things Rapido has published, while the subscription entitlement system is reasoned from the publicly stated model, and the surge and live-location internals are the general ride-hailing pattern. The matching core answers which captain should take a request. When a rider requests a ride, the system finds nearby captains and picks a good one. Rapido has described how this evolved. The original approach was a simple radial system: draw a circle of a couple of kilometers around the rider, find the captains inside, and order them by straight-line distance. The problem it hit is that straight-line distance misleads, because a captain who is close as the crow flies may be far by road across a ring road or a railway crossing. So Rapido moved to partitioning geography with a hexagonal grid, using the H3 system at a fixed resolution, and to learning driving times from historical rides rather than trusting straight-line distance. It predicts two things: the time for a captain to reach the rider, and the time for the trip itself, both bucketed by time of day and day of week, so matching and estimates reflect how the city actually moves. A two-week A/B test in one city showed this cut the estimated arrival time meaningfully. Live captain positions are kept in an in-memory geo index so proximity queries are fast, which is the standard ride-hailing approach. The money model is where Rapido is distinctive. Ola and Uber take a commission on each ride, which means computing a split and keeping a commission ledger per trip. Rapido shifted much of its supply to a subscription model: a captain pays a flat subscription, and then keeps the full fare on rides, with no per-ride commission. Rapido has publicly framed this and reported large subscription income from it. The exact entitlement system is not published, so reasoning from the stated model, the settlement path changes shape: instead of calculating and recording a commission on every trip, the system checks whether the captain holds an active subscription and, if so, settles the whole fare to them, so the recurring subscription billing becomes the revenue event rather than the per-ride cut. This is a genuinely different billing and money-movement design, and it is worth being clear that the concept is well established while the internals are inferred. Behind both sits a data platform Rapido has published. Kafka ingests millions of events a day, feeding a layered lake, raw, then cleaned and enriched, then curated, queried through Trino across several clusters with Spark for processing, on Google Cloud using low-cost spot machines for efficiency. This platform is what powers the learned driving times, pricing, and analytics. In a real interview, sketch this on the whiteboard before diving into any single box.
In a real interview, sketch this on the whiteboard before diving into any single box.
Core components
Walk through each service. The interviewer wants to hear what each one owns, not just the names.
Ride request and matching service
Takes a rider's request and selects a good nearby captain, primarily a two-wheeler. Rapido has published how this moved from a simple radius-and-straight-line approach to hex-grid geography with learned driving times, so matching reflects real road travel rather than crow-flying distance.
Geospatial index and driving-time models
Partitions geography with the H3 hexagonal grid at a fixed resolution and keeps live captain positions in memory for fast proximity queries. Machine-learned models predict the captain-to-rider time and the trip time from historical rides, bucketed by time of day and day of week, replacing straight-line distance.
Trip service and tracking
Owns the trip lifecycle from request to assignment to completion, and streams the captain's live position to the rider every few seconds. The live-location streaming follows the general ride-hailing pattern rather than a Rapido-published internal.
Subscription and entitlement service
The distinctive money component. Captains buy a flat subscription, and the system checks that a captain holds an active subscription rather than computing a commission per ride. Rapido has publicly stated the model and reported large subscription income; the internal entitlement design is reasoned from that, not published in detail.
Fare and settlement
Prices the ride and settles money at trip end. Under the subscription model the full fare goes to the captain with no per-ride commission, so the recurring subscription is the revenue event; where commission still applies, a split is computed. Payments across UPI, wallet, and cash are handled idempotently.
Multi-modal platform
One platform serving bike, auto, and cab rides, plus delivery, which grew into Rapido's largest single revenue stream. Different vehicle types can carry different money models, so the platform supports both subscription and commission settlement behind a shared matching core.
Data platform
The analytics and machine-learning backbone. Kafka ingests millions of events a day into a layered lake, queried with Trino across several clusters and processed with Spark, on Google Cloud with low-cost spot machines. It processes more than 15 petabytes a month and powers the learned driving times and pricing.
Data model
captains. The captain and current state. subscription_state records whether they hold an active subscription, which decides settlement. Live position is not here; it lives in the…
Every table for Rapido, its keys, and which store fits it and why.
Deep dives
Two-wheeler dispatch: from radius to hex grid and learned driving time. Rapido has published its dispatch evolution, which makes for a concrete matching discussion. The first version was a simple radial system: on a request, draw a circle of…
5 deep dives on the parts that break at scale: Two-wheeler dispatch: from radius to hex grid and learned driving time; The subscription model and how it changes settlement; Why straight-line distance is the wrong metric.
Trade-offs to discuss
Subscription and full-fare settlement versus per-ride commission. A per-ride commission scales revenue directly with rides and needs no upfront commitment from captains, but it means captains give up a cut of every fare, which hurts…
5 decisions an interviewer expects you to defend, each with the alternative and why it loses here.
What the interviewer asks next
A captain's subscription expires in the middle of a shift, while a ride is in progress. How should settlement behave?
4 follow-up questions with model answers, the interview scorecard for this question, and a mock interview on Design Rapido with the AI tutor.
How Rapido actually does it
Rapido's dispatch evolution and data platform are documented on its own engineering blog, its business and money model are well covered in press and stated by its founders, and the internal subscription-entitlement design is reasoned from the stated model rather than published. On dispatch, Rapido described moving from a radial system that ordered captains by straight-line distance to partitioning geography with the H3 hexagonal grid and learning driving times from historical rides, predicting both captain-to-rider time and trip time bucketed by time of day and day of week, and reported a meaningful reduction in estimated arrival time from a two-week A/B test in one city. On its data platform, Rapido reported Kafka ingesting millions of events a day into a layered lake, queried with Trino across several clusters and processed with Spark on Google Cloud with low-cost spot machines, processing more than 15 petabytes a month across about a thousand pipelines and three thousand datasets, with about 1.5 million rides a day across 100-plus cities as of late 2022. On the business, Rapido reported about 50 million monthly active users and 2 million active captains in 2025, roughly half of India's ride-hailing overall with leadership in bike taxis, revenue of about 934 crore rupees in FY25, and, distinctively, about 275 crore rupees of subscription income growing many times year on year, with delivery now its largest single revenue stream. Three accuracy notes for the interview. First, the strongest Rapido-published ride figure is about 1.5 million rides a day from 2022; larger recent daily-ride numbers come from secondary blogs and should be treated as unverified. Second, the exact subscription entitlement and billing internals are not published, and which vehicle types use subscription versus commission is reported inconsistently, so describe the model at the concept level, a flat pass and full-fare settlement, which is well verified. Third, live-location streaming and surge internals are not published for Rapido and are the general ride-hailing pattern.
Sources
Lessons to study before this interview
If any of these topics are fuzzy, the interviewer will catch it. Each lesson is 15 to 60 minutes with diagrams, code, and a quiz.
Geospatial Indexing
intermediate / database types storage
WebSockets
intermediate / messaging event systems
Message Queues
intermediate / messaging event systems
Cache-Aside Pattern
foundation / caching strategies
Load Balancing
foundation / core fundamentals
High Availability
advanced / reliability resilience
Rate Limiting for Resilience
advanced / reliability resilience
System design interviews at Indian tech companies
28 walkthroughs of the products Indian interviewers ask about, each with the real scale numbers, the architecture and the trade-offs that company had to make.
Food delivery and quick commerce
Payments and fintech
E-commerce
Travel and ticketing
Rides, logistics and services
- Ola system design
- Rapido system design (this page)
- Delhivery system design
- Urban Company system design
Streaming and gaming
Frequently asked questions
interview readiness
Are you ready for Design Rapido?
Three questions from this guide. Answer them without scrolling up, the way you would have to in the room.
Go deeper
This guide is built on these 6 lessons. Each one teaches one piece of the Rapido design above, step by step.
- Geospatial IndexingSystem Design · database types storage · 16 min
- WebSocketsSystem Design · messaging event systems · 22 min
- Message QueuesSystem Design · messaging event systems · 20 min
- Cache-Aside PatternSystem Design · caching strategies · 25 min
- Load BalancingSystem Design · core fundamentals · 34 min
- High AvailabilitySystem Design · reliability resilience · 25 min
Practice with 770 system design lessons
Lifetime access for ₹1,111 in India or $35 elsewhere. Interactive diagrams, quizzes, and 20 capstone projects to practise on.
This one question is not enough for the interview.
Get all 200 questions in the System Design and Distributed Systems pack
Each question has why it is asked, a full answer, what the interviewer listens for, the follow-ups, the common mistakes and a diagram (268 diagrams in all). A PDF you keep, junior to staff level.
Pay by UPI, cards or netbanking through Razorpay. Pay by card or PayPal, in US dollars. Download at once from My packs.
NEWSystem Design Hands-On
Included in the System Design course: real systems, built live
Postgres Sharding: Complete Hands-On (PgBouncer + Citus). 2 h 36 min and 20 chapters: one PostgreSQL loaded until it breaks, then four shards behind a router you write, PgBouncer and Citus, with the 139-page slide deck. The first 15 minutes are free to watch.


