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
- 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.
- 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.
- 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.
- 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.
- 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.
- State the estimate clearly labeled as built on stated assumptions, not measured fact.
What a strong answer includes
- Reframes the ambiguous question into a concrete, answerable one, offline cache retention policy, and states that framing explicitly.
- Breaks the estimate into per-activity size times activity frequency times retention window, showing clear decomposition.
- Uses illustrative numbers as assumptions: assume 300 KB per activity, 20 activities a month, a 60-day rolling cache, roughly 12 MB of cached data.
- Distinguishes local device storage constraints from server-side unlimited history, correctly scoping what offline actually requires.
Common mistakes
- Treating this as a pure data-volume estimate without addressing the offline caching and retention angle the question implies.
- Giving a number with no shown decomposition or stated assumptions.
- Ignoring that offline storage on a phone is a meaningfully constrained resource compared to server storage.
Likely follow-up questions
- How would you decide what to evict from the cache when storage is limited?
- How would you handle syncing conflicts once the device is back online?
- What's the trade-off between caching more data and app performance?
More estimation questions
- YouTube Red is a premium service without ads. Assume that 1.5% of initial YouTube user base signs up for the service. What is the lifetime revenue Google generates from those users?Google · Estimation · Hard
- How much would it cost to set up WiFi in New York?Google · Estimation · Medium
- How many dentists are there in New York?Google · Estimation · Easy
- How many Pianists are there in New York city?Google · Estimation · Easy
- Estimate the total number of videos on YouTube.Google · Estimation · Easy
- How many airports are in the US and in the World?Google · Estimation · Easy
More questions from these companies
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 2: Data fluency: SQL, logs, and reading the truth yourself
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop