Central Park Running Volume: Sizing Total Jogger Mileage per Year

Quick Overview

A product manager estimation prompt that asks for the total distance joggers cover inside New York's Central Park over one year. It tests scoping who counts as a jogger, segmenting runners by how often and how far they run, clean round-number arithmetic, and sanity-checking the total against how crowded the park's paths could realistically get.

Central Park Running Volume: Sizing Total Jogger Mileage per Year

Company: Google

Role: Product Manager

Category: Product / Decision Making

Difficulty: medium

Interview Round: Other

In a product manager interview you are asked for a quick, rough estimate: over one full year, how many miles in total do joggers run inside Central Park in New York City? Give one number with a believable range, state each assumption as you make it, and explain why you think the order of magnitude is right. ```hint Segment the runners A daily regular, a local who jogs there a few times a year and a tourist trying one loop run very different distances. Size each group separately, and count only the distance run inside the park. ``` ### Clarifying Questions - Does "jogger" mean anyone running at any pace, including people in organized races, and are walkers, cyclists and skaters out of scope? - If someone's route only passes through the park, should only the miles run inside the park boundary count? - Should the estimate describe a typical year, ignoring one-off events such as an unusually harsh winter or a long closure? - Is a rough order of magnitude enough, or does the interviewer want a point estimate with a stated range? ### What a Strong Answer Covers - A clear equation for yearly mileage (runners in each segment × runs per year × miles inside the park per run), plus a scope that says who counts as a jogger and which miles count. - Sensible segments (frequent local runners, occasional local runners, visitors, organized races), with frequency and distance assumptions tied to the park's real loop lengths. - Round numbers carried through correct arithmetic, with seasonality and weather built into the frequency on purpose. - A sanity check from a separate angle, such as how crowded the paths would have to be if the total were true. - Which assumption moves the answer most, and a final range instead of false precision. ### Follow-up Questions - Which single assumption would you research first to narrow the range, and where would you get data for it? - The parks department is deciding whether to widen the runners' lane on the park drive. How would you turn this yearly total into a peak-hour crowding estimate? - How would your approach change for a small neighborhood park with one short loop?

Overview: A product manager estimation prompt that asks for the total distance joggers cover inside New York's Central Park over one year. It tests scoping who counts as a jogger, segmenting runners by how often and how far they run, clean round-number arithmetic, and sanity-checking the total against how crowded the park's paths could realistically get.

Google logo
Google
Jan 15, 2025
mediumProduct ManagerOtherProduct / Decision Making
0
0

In a product manager interview you are asked for a quick, rough estimate: over one full year, how many miles in total do joggers run inside Central Park in New York City? Give one number with a believable range, state each assumption as you make it, and explain why you think the order of magnitude is right.

Clarifying Questions Guidance

  • Does "jogger" mean anyone running at any pace, including people in organized races, and are walkers, cyclists and skaters out of scope?
  • If someone's route only passes through the park, should only the miles run inside the park boundary count?
  • Should the estimate describe a typical year, ignoring one-off events such as an unusually harsh winter or a long closure?
  • Is a rough order of magnitude enough, or does the interviewer want a point estimate with a stated range?

What a Strong Answer Covers Guidance

  • A clear equation for yearly mileage (runners in each segment × runs per year × miles inside the park per run), plus a scope that says who counts as a jogger and which miles count.
  • Sensible segments (frequent local runners, occasional local runners, visitors, organized races), with frequency and distance assumptions tied to the park's real loop lengths.
  • Round numbers carried through correct arithmetic, with seasonality and weather built into the frequency on purpose.
  • A sanity check from a separate angle, such as how crowded the paths would have to be if the total were true.
  • Which assumption moves the answer most, and a final range instead of false precision.

Follow-up Questions Guidance

  • Which single assumption would you research first to narrow the range, and where would you get data for it?
  • The parks department is deciding whether to widen the runners' lane on the park drive. How would you turn this yearly total into a peak-hour crowding estimate?
  • How would your approach change for a small neighborhood park with one short loop?