Estimation question

How long will it take to store Strava's data on the phone while offline?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

Start a mock interview on this question · Mock interview from a job description

What this question tests

Tests structured estimation combining data-size reasoning with a systems constraint (offline caching), rather than a pure market-sizing exercise.

How to approach it

  1. State the assumption: this is asking how much of a user's workout history and route data Strava needs to cache locally to support offline access, not literally all server-side data.
  2. Estimate per-activity data size: GPS points every few seconds for a typical hour-long activity, plus metadata (pace, heart rate), roughly a few hundred KB per activity.
  3. Estimate the offline window needed: likely a rolling recent window (last 30 to 90 days of activities) rather than a user's entire multi-year history, since offline caching is about immediate access, not full backup.
  4. Multiply activities per period by size per activity to get a total local storage estimate, then state it as a range given the uncertain assumptions.
  5. Address the actual question, how long to store, by reasoning about cache eviction policy and sync timing rather than treating it purely as a data-size problem.
  6. State the estimate clearly labeled as built on stated assumptions, not measured fact.

What a strong answer includes

Common mistakes

Likely follow-up questions

More estimation questions

More questions from these companies

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank