Estimate infrastructure or operational capacity needed for Playlists

Problem Statement Description

Product context: Spotify is an audio streaming company; its products include music, podcasts, audiobooks, playlists, recommendations, creator tools, subscriptions, and ads.

Spotify Playlists are a core part of the premium subscriber experience, supporting personal libraries, collaborative playlists, editorial playlists, algorithmic playlists, playlist recommendations, downloads, and cross-device playback. In this guesstimate, estimate the infrastructure or operational capacity required to support Playlists for Spotify’s premium subscribers globally.

Your estimate should define what “capacity” means for this problem before calculating it. You may choose to focus on one or more relevant capacity dimensions such as storage for playlist metadata, read/write request volume, recommendation or personalization compute, sync traffic across devices, download-related operations, moderation or editorial operations, or customer support load related to playlists.

The estimate should be grounded in the real user workflow: creating playlists, adding/removing tracks, saving Spotify-generated playlists, sharing playlists, collaborating, searching within playlists, and accessing them across mobile, desktop, web, and connected devices. Make reasonable assumptions where data is unavailable, and clearly state what is in scope versus out of scope.

The experience should consider:

- The target population, especially premium subscribers, and how many actively use playlists.

- The unit of estimation, such as playlists per user, tracks per playlist, actions per day, reads per session, or storage per playlist object.

- Adoption and frequency assumptions across casual, moderate, and heavy playlist users.

- Differences between user-created, collaborative, editorial, and algorithmically generated playlists.

- Peak versus average demand, including commute hours, weekends, major releases, and seasonal listening moments.

- Storage, request throughput, sync, caching, and personalization workload implications.

- Sensitivity of the estimate to the largest assumptions and which assumptions most affect capacity.

- Sanity checks against comparable consumer-scale audio or media products.

The goal is to produce a structured, defensible estimate that helps Spotify understand the scale of infrastructure or operational support needed for Playlists, while showing clear assumptions, logical decomposition, and awareness of product usage patterns.