Ola PM Interview — Driver Cancellation Spike RCA

It tests whether you can diagnose a sudden driver-side trip-cancellation spike in one city before proposing any fix. The interviewer checks that you define the cancellation metric and its time window first, segment by city, vehicle category like Auto and Mini, and time-of-day, separate driver-side from rider-side causes, and split internal causes such as an app release or incentive change from external ones such as fuel, weather, a festival, or a competitor promo. You are also tested on naming a cheap validation for each hypothesis and proposing fixes with a guardrail metric and a rollback path.

Start by clarifying the exact cancellation metric, its denominator, the magnitude, and the time window. Then pick a segmentation and say why, isolating the affected city, categories, and time-of-day. Split candidate causes into Ola-internal changes and external shocks. Prioritize a few hypotheses, and for each one name the single fastest way to confirm or kill it, such as a specific log cut or talking to drivers at the moment they cancel. Only then propose a fix, and attach a guardrail metric and a rollback trigger. Keep the marketplace two-sided in view throughout.

The biggest one is proposing solutions before structuring the problem. Others include treating the platform as a single funnel and forgetting drivers are independent partners, reasoning about the spike in aggregate without segmenting, reciting framework names without applying them to the Ola case, hand-waving numbers instead of sizing the spike, ignoring driver incentives and pickup distance, and proposing a fix with no measurement plan or rollback. Failing to change course when the interviewer hands you data that contradicts your first guess is also a frequent cause of rejection.

It behaves like the real product execution round in pressure and follow-up depth, but it never coaches you, never praises mid-answer, and never tells you the framework to use. It probes every claim for the underlying number, asks why you believe a hypothesis and how you would confirm it cheaply, and introduces a constraint such as a recent incentive-slab change to see if you adapt. It stays in character as an Ola product interviewer the entire time and will not reveal how you are doing during the round.

Your transcript is scored against dimensions drawn from how Ola actually evaluates this round: structuring before solving, marketplace segmentation, internal-versus-external hypothesis quality, validation design, prioritization with a measurement plan, and how you hold up under pushback. After the session you get a scorecard that names the specific moment your reasoning was not grounded in a number and where you did or did not separate driver-side from rider-side causes. Nothing about your score is revealed while the round is still running.

Do not start solving. Spend the opening confirming what you are looking at: which cancellation metric, measured how, over what window, and how large the move is against the normal city baseline. Ask one or two sharp diagnostic questions, such as whether the spike is concentrated in specific vehicle categories or times of day, and whether anything shipped recently. This signals you diagnose before prescribing, which is the single behaviour this round rewards most in the opening.

Expect the interviewer to drop in a fact such as a recent incentive-slab revision or a driver-app release once you have a working hypothesis. Do not abandon your structure. Fold the new fact into your existing internal-versus-external split, say explicitly how it raises or lowers the probability of each hypothesis, and adjust which one you would validate first. The round rewards reworking the proposal around the new constraint while keeping the diagnosis coherent, not starting over or ignoring the new information.

A strong answer defines the cancellation metric and window before theorizing, segments crisply by city, category, and time-of-day, and keeps driver-side and rider-side causes separate. It splits internal causes like an app release, incentive change, surge tuning, or an allocation or ETA change from external shocks like fuel, weather, a festival, or a competitor promo. It prioritizes a few hypotheses, attaches the fastest cheap validation to each, and closes with a fix that has a guardrail metric and a rollback trigger. It also visibly revises when handed contradicting data.

Driver cancellation and ETA inflation are the most-cited consumer complaints for app-based taxis in India, so cancellation is effectively a board-level metric at Ola. A Bengaluru consumer survey of over three thousand Ola taxi users found a large majority citing driver-cancelled rides as a top issue. Because rates already vary widely by city and category, a single-city spike has to be read against a noisy baseline, which is exactly why the interviewer wants disciplined structuring and segmentation rather than a quick fix.

No. The round tests transferable root-cause reasoning on a two-sided marketplace, not memorized Ola internals. What matters is that you define the metric, segment the problem, separate the supply side from the demand side, generate prioritized hypotheses with cheap validations, and propose a measured fix. Knowing Ola-specific vocabulary such as allocation, incentive slabs, pickup distance, and surge helps you sound fluent, but disciplined diagnosis under pushback is what actually earns the score.

It runs about twenty minutes as a single product execution round with four phases: a structured warm-up on framing the spike, a core segmentation challenge, a pressure phase where the interviewer adds a marketplace constraint, and a short reflection. At the end you receive a transcript-backed scorecard mapped to the dimensions Ola evaluates, including where your structure held, where a number was missing, and how you responded when the data contradicted your first hypothesis.