May we use cookies so Meta, Google, LinkedIn and ChatGPT see your visit and we learn which ads work? PrivacyMay we use cookies to see which pages help, and let Meta, Google, LinkedIn and ChatGPT see your visit, so we know which of our ads work? That way we spend less on ads that do not work. We do not sell your data, and the site works the same if you decline. You can change your answer at any time under Cookie settings at the foot of the page. Privacy policy
Loading...
System Design and AI Engineering, by Roni Das. 989 interactive lessons in two courses.: 770 in System Design and 219 in AI Engineering.
Start LearningSystem design interview guide
in this guide
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.
A services marketplace breaks the ride-hailing assumptions most candidates reach for. There is no nearest-driver dispatch, because the service is scheduled for a future slot and requires a specific skill, so the system must decide which time slots are even safe to show and which professional to route a request to. The hardest part is that a professional can decline, so the real question is not who is closest but who is likely to accept and deliver a scheduled job well. Urban Company published how it treats this as a prediction and reliability problem. It also manages its supply, training and certifying professionals, which changes the design from an open pool to a controlled asset. Interviewers use Urban Company to check whether you can design scheduled skill-based matching, reason about predicting acceptance and fulfillment reliability, and think about a marketplace where supply is curated rather than open.
This page is the free part.
₹1,111 in India$35 everywhere elseonce, for the whole course
The System Design course covers the Urban Company design across a run of lessons, not one page. These 4 alone are about 96 minutes of step-by-step reading, every one with a quiz.
Always clarify these in the first 5 minutes of the interview. Do not start drawing boxes until both lists are agreed.
This guide is built on these 6 lessons. Each one teaches one piece of the Urban Company design above, step by step.
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.
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.
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
Urban Company does not dispatch the nearest worker like a cab app. It books a plumber or a beautician into a time slot up to three days ahead, and the hard question is whether anyone will actually accept that slot. To answer it, Urban Company scores on the order of 1,100 professional-and-slot combinations for a single customer session, predicting the chance each pro accepts, serving about 6.8 million customers a year through tens of thousands of trained partners across 51 cities.
Designing Urban Company is the services-marketplace problem, which is different from ride-hailing. There is no instant dispatch of the nearest driver. A customer books a service, cleaning, a salon appointment, a repair, into a future time slot, and the system has to decide which slots to even offer and which professional to send, based on skill, location, availability, and, crucially, the predicted chance that a professional will accept the job. Urban Company has published how it models this with machine learning, treating reliability, the chance a booking is actually fulfilled, as the thing to optimize. It also manages and trains its supply rather than using an open pool. This walkthrough centers on the scheduled matching and reliability modeling Urban Company published, and is honest about which pieces are the general marketplace pattern.
Where it shows up
Commonly asked at Urban Company and marketplace and consumer-services teams, and the general forms, meaning design a services marketplace, a scheduling and matching system, or an appointment-booking platform, show up at most product companies for SDE2 and SDE3 rounds. Urban Company is a good question because it replaces instant dispatch with scheduled, skill-based matching and makes fulfillment reliability the core problem.
Spec sheetUrban Company
worked through below, with the maths
The hard parts of this design are taught step by step in the System Design course: Geospatial Indexing, Cache-Aside Pattern and Message Queues.
How databases efficiently answer 'find everything near me'. R-trees, geohashes, and spatial queries.
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.
Decouple producers from consumers with a buffer that holds messages until they're processed.
Splitting a database across multiple servers, the nuclear option for scaling writes, and the architecture behind Instagram, Uber, and YouTube.
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
Real interview questions, live diagrams and measured lab results, pulled at random from the lessons. A new set every time you come back.
Show your math. Pulling numbers from thin air signals you have not thought about the load.
Annual transacting customers
~6.8M (FY25)
Urban Company reported about 6.8 million annual transacting customers in FY25. This is the demand side of the marketplace.
Active service partners
~48K monthly active
Urban Company reported about 47,888 average monthly active service partners in FY25. This managed, trained supply is what requests are matched to.
Cities and micro-markets
51 cities, 12,000+ micro-markets
Urban Company operates in 51 cities and divides them into more than 12,000 micro-markets of roughly 3 to 5 kilometers each, so matching and fulfillment are localized.
Scoring load per session
~1,100 scores/session
Urban Company reported scoring on the order of 1,100 combinations for a customer session, roughly 24 slots by 15 providers across 3 days, to decide which slots to show and whom to route to.
Slots offered
~72 per customer
Urban Company offers 24 slots a day from 8 AM to 7:30 PM, shown up to 3 days ahead, so about 72 bookable slots per customer. Deciding which of these are safe to show is the core problem.
Revenue
~1,144 crore rupees (FY25)
Urban Company reported revenue of about 1,144 crore rupees in FY25, up about 38 percent, turning profitable, and listed publicly in 2025. A sizing signal for the business.
Design Urban Company around scheduled matching and fulfillment reliability, because those are what make it different from a cab app, and they are what Urban Company has published. The supply management and hyperlocal structure are stated facts, and the serving stack is described from Urban Company's own, somewhat older, engineering posts. The booking flow starts with slots, not dispatch. A customer chooses a service, and the system shows time slots, 24 a day from morning to evening, up to 3 days ahead, so about 72 slots. The critical decision is which of those slots to even offer, because showing a slot that no professional will accept leads to a booking that cannot be fulfilled. Urban Company answers this with prediction. It computes a Lead Score, the machine-learned probability that a specific professional will accept a specific request, and a Request Score, the probability that at least one eligible, available professional will accept a request for a given slot. The Request Score is what decides whether a slot is safe to show. Because there are many slots, many candidate professionals, and several days, a single customer session involves scoring on the order of 1,100 combinations, so the scoring has to be fast and is served by a dedicated matching service. The matching itself is skill-based and multi-signal, not nearest-first. Urban Company filters candidates by category skill, a facial specialist is not sent for a pedicure, by location proximity within the hyperlocal micro-market, and by availability state, whether a professional is on a job, at home, or offline, and by their history of accepting work. It scores the survivors with a gradient-boosted model, trained and tuned on managed cloud machine-learning infrastructure, across many service supercategories, and the scores are calibrated so that a predicted acceptance probability matches reality. Not every eligible professional sees every request; filtering happens first, and a request is routed to those most likely to accept and deliver well. The objective tying it together is reliability, framed as a trade-off. Urban Company optimizes between two failure modes: a No-Response request, where a booking is shown but no professional accepts, and a Requests-Lost outcome, where being too cautious blocks a request that could have been fulfilled. It uses causal modeling to balance these, with the guiding rule that blocking a likely-bad request must not cost more than one good request, and it reported measurable reductions in no-response rates after rolling this out. Around this sit the platform pieces Urban Company has described: a separate matchmaking service, an event-driven backbone using Kafka to connect microservices, Redis for caching, scheduling, and listing professionals, and a data pipeline feeding analytics, on cloud infrastructure. Supply is a managed asset: Urban Company trains and certifies professionals at scale and progresses them through quality tiers, and ratings feed back into who receives future requests. 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.
Walk through each service. The interviewer wants to hear what each one owns, not just the names.
Presents bookable time slots, 24 a day up to 3 days ahead, and decides which are safe to show. A slot is only offered if a professional is likely to accept it, which is the Request Score's job. This is the scheduling core that replaces instant dispatch.
A dedicated service that scores professional-and-slot combinations and routes a request to the professionals most likely to accept and deliver. Urban Company runs this as a separate service because the scoring load, on the order of 1,100 scores per session, is heavy and specialized.
The machine-learned probability that a specific professional will accept a specific request, given skill match, location proximity, availability state, and their acceptance history. A gradient-boosted model, trained and tuned on cloud machine-learning infrastructure and calibrated so a predicted probability matches real acceptance.
The probability that at least one eligible, available professional will accept a request for a given slot, computed from the Lead Scores of candidates. This gates which slots are shown, so customers are not offered slots that cannot be fulfilled, which is the central reliability lever.
The layer that balances the two failure modes, no-response bookings versus lost good requests, using causal modeling, with the rule that blocking a likely-bad request must not cost more than one good one. Urban Company reported reduced no-response rates from this.
The systems around a managed, trained workforce: onboarding, certification, and quality tiers that professionals progress through, plus ratings that feed back into matching. Because supply is curated rather than open, its quality and availability are part of the platform, not external.
An event-driven architecture using Kafka to connect microservices asynchronously, with Redis for caching, job scheduling, and listing professionals, and a data pipeline feeding analytics and the machine-learning models, on cloud infrastructure. This is the platform Urban Company described in its engineering writing.
customers. The customer, placed in a hyperlocal micro-market so matching is localized. About 6.8 million transact a year.
Every table for Urban Company, its keys, and which store fits it and why.
Scheduled slot matching, not instant dispatch. The defining difference from ride-hailing is that Urban Company does not send the nearest available worker right now. A service is booked into a future time slot, up to…
6 deep dives on the parts that break at scale: Scheduled slot matching, not instant dispatch; Lead Score and Request Score; The matching model and its signals.
Scheduled slot matching versus instant nearest-worker dispatch. Instant dispatch is simpler and works when the service is immediate and interchangeable, like a ride. Home services are scheduled and skill-specific, so the system…
5 decisions an interviewer expects you to defend, each with the alternative and why it loses here.
A professional accepted a booking for tomorrow but goes offline the morning of the job. How does the system recover?
4 follow-up questions with model answers, the interview scorecard for this question, and a mock interview on Design Urban Company with the AI tutor.
Urban Company's matching and reliability engineering are documented on its own engineering blog, its scale and financials are reported through its 2025 IPO filings, and the serving-stack details come from its earlier engineering writing and are directionally accurate. Urban Company described its platform as a matchmaker that must find the right professional, get them to accept, and deliver quality, and it published a machine-learning system built on this: a Lead Score predicting the probability a specific professional accepts a specific request, and a Request Score predicting whether at least one eligible available professional will accept a slot, which gates whether a slot is shown. It offers 24 slots a day up to 3 days ahead, about 72 slots, and scores on the order of 1,100 professional-and-slot combinations per customer session, using a gradient-boosted model trained and tuned on managed cloud machine-learning infrastructure across many supercategories with calibrated outputs, filtering candidates by skill, location proximity, availability state, and acceptance history. It frames the objective as reliability, balancing no-response requests against lost good requests with causal modeling, and reported reduced no-response rates after rollout. It described a separate matchmaking service, an event-driven architecture using Kafka, Redis for caching, scheduling, and listing professionals, and a data pipeline, on cloud infrastructure. On scale, Urban Company reported about 6.8 million annual transacting customers and about 47,888 average monthly active service partners in FY25, across 51 cities divided into more than 12,000 micro-markets, with revenue of about 1,144 crore rupees, turning profitable, and it manages a trained, certified workforce with quality tiers where repeat professionals drive most transaction value. Three accuracy notes for the interview. First, Urban Company has not published a total gross transaction value figure or a clean per-year job count, so do not quote those. Second, the stack details are from its older engineering posts and should be treated as directional, while the matching and reliability posts are the recent, load-bearing sources. Third, demand forecasting and dynamic pricing are not published Urban Company systems and are the general marketplace pattern rather than stated facts.
Sources
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
Cache-Aside Pattern
foundation / caching strategies
Message Queues
intermediate / messaging event systems
Database Sharding
foundation / database fundamentals
Load Balancing
foundation / core fundamentals
High Availability
advanced / reliability resilience
Rate Limiting for Resilience
advanced / reliability resilience
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.
interview readiness
Three questions from this guide. Answer them without scrolling up, the way you would have to in the room.
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
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.
Free PDF · 79 pages
25 real tech interview questions, answered in full
Five from each of our AI, GenAI, Inference, Maths for ML and Forward Deployed packs. Each with a diagram and a model answer. Free by email.
free tool
Check these numbers yourself
Put in your own guesses for Urban Company and see requests per second, storage, bandwidth and servers, with every sum written out.
Open the Capacity EstimatorIt is really nice and good Please join the course