Google PM Interview — Two-Wheeler Maps in Indian Cities

It tests whether you can structure an ambiguous product problem before solving it. The interviewer wants you to state the product goal, segment two-wheeler riders into distinct groups, prioritise one segment with a reason, name the single most painful unmet need for them in congested Indian traffic, then propose and prioritise solutions on impact versus effort, and close with a primary success metric plus a guardrail. Rambling without structure or jumping straight to features is read as poor prioritisation.

Open by clarifying the goal in one sentence. Then segment riders, for example daily office commuters, gig delivery riders, occasional riders, and pillion-carrying riders, and pick one with explicit rationale. Identify that segment's most painful unmet need in Indian congestion. Brainstorm three to four solutions, then prioritise them on impact versus effort and defend the order. End with one primary metric and a guardrail metric. State every assumption out loud as you go.

The biggest is listing features before naming a goal or a segment. Others include trying to serve every rider at once, not stating assumptions so the interviewer cannot follow the logic, ignoring pushback instead of re-grounding in the rider problem, ending with no success metric or a vanity metric with no guardrail, and giving a generic global Maps answer that never engages Indian reality like narrow-lane shortcuts, landmark navigation, or vernacular voice.

It behaves like a senior Google Maps PM running the round. It interrupts, challenges your segment choice, argues your painful need is not the most painful, and questions your metric. The difference is it never praises you mid-round, always probes at least once before moving on, and produces a transcript-backed scorecard afterwards naming exactly where your structure or prioritisation broke. It will not coach you on the framework during the round.

Your transcript is scored against dimensions a real product sense interviewer uses: goal framing, rider segmentation and prioritisation, problem-space depth, solution prioritisation with a defended tradeoff, primary metric with a guardrail, and how you respond to pushback. Each dimension has observable anchors, so the scorecard quotes the specific moment a behaviour appeared or was missing rather than giving a vague grade.

Do not start solving. Spend the first two minutes restating the goal in your own words, naming your assumptions out loud, and laying out the structure you will follow: segment riders, pick one, find the painful need, generate and prioritise solutions, define a metric. This signals prioritisation discipline immediately, which is the single strongest early signal the interviewer is looking for.

Do not abandon your segment instantly or defend it rigidly. Acknowledge the alternative the interviewer raises, restate why your segment has the larger or more painful unmet need with a quick assumption, and offer the condition under which you would switch. Re-grounding in the rider problem under pushback is exactly what separates a strong answer from a candidate who folds or gets defensive.

A strong answer sounds like: here is the goal, here are four rider segments, I am choosing gig delivery riders because their trip volume and time pressure make routing errors most costly, their most painful need is losing time in narrow-lane congestion the map routes them into, here are three solutions, I would ship landmark-anchored rerouting first because it is high impact and medium effort, my primary metric is rider-reported time saved per trip with a guardrail on navigation-related near-miss reports.

It can include a quick estimation aside, for example sizing daily two-wheeler commuters in a metro to justify which segment is biggest. You are not graded on the exact number but on whether you decompose it cleanly, state assumptions, and sanity-check the result. Use estimation to support your segment prioritisation, not as a separate exercise that derails your structure.

It runs about twenty minutes. Aim to keep your opening structure under two minutes, then move in tight exchanges where you make a point, the interviewer pushes, and you respond. Long monologues without converging read as poor prioritisation. The interviewer will interrupt if you ramble, so make a claim, defend it briefly, and invite the next probe rather than covering everything at once.