Spotify PM Interview — Free-to-Paid Conversion in India

It tests whether you can design features that move free Indian listeners to paid Premium under real constraints: low ARPU, a strong free-tier habit, and competitors like JioSaavn that bundle through telecom. The interviewer probes how you clarify the problem, pick one concrete user segment, design features tied to a measurable conversion goal, prioritize what ships first, and name the tradeoffs you accept. It is a product-sense and product-design conversation, not a coding or estimation drill, and generic answers that could apply to any app are pushed on hard.

Open by clarifying scope, platform, and the competitive picture before proposing anything. Name one specific listener segment, for example lapsed trial users in tier-2 cities, and stay with it. Design two or three features that each tie to a conversion goal, then pick what ships first and say why. State a primary success metric with a guardrail that protects against gaming it, such as ad revenue cannibalization. Close every feature with the tradeoff you are accepting. The interviewer rewards localized, prioritized reasoning over a recited template.

The frequent ones: jumping to features without asking any clarifying questions, designing for all users instead of one segment, proposing features with no success metric, naming a metric with no guardrail, and giving an answer that could describe any product in any market. Candidates also lose ground by ignoring the competitive context, never accounting for JioSaavn telecom bundling or the risk that restricting free pushes users to YouTube Music, and by listing features with no reason for what ships first.

The behavior is close to a real loop interviewer. The persona, Priya, has a fixed role, real opinions, and an emotional arc: she warms up when you clarify well and cools off when you stay generic. She never coaches you, never names the structure she wants, and never praises an answer. The difference is consistency and transparency. Every claim gets probed, timing is even, and you receive a transcript-backed scorecard afterward rather than vague verbal feedback or silence.

Your transcript is scored against role-specific dimensions such as segment specificity, conversion-metric rigor, India market localization, prioritization reasoning, and tradeoff honesty. Each dimension has observable signals: naming a concrete segment, stating a metric with a baseline and a guardrail, tying features to a conversion goal, and accounting for competitor migration. The scorecard names the specific moment a trade-off went undefended or an assumption was not grounded in a number, so feedback points to exact lines rather than general impressions.

Do not pitch yet. Ask two or three sharp clarifying questions about which platform, which listener segment, the current conversion baseline, and the competitive constraint around telecom bundling. State the one segment you will design for and why it is the highest-leverage place to start. Restate the goal in one line so you and the interviewer share a definition of success. This early discipline is what separates strong candidates from those who free-associate features for ten minutes.

Take the objection seriously rather than dismissing it. Name the specific free-tier change you are making, the segment it targets, and why that segment is unlikely to churn to a competitor, for example because their listening is habitual and the friction is small relative to the Premium value. Quantify the migration risk you are willing to accept and the counter-metric you would watch, such as free-tier weekly active retention. Show that you weighed the JioSaavn bundling advantage and YouTube Music free experience explicitly instead of pretending the risk does not exist.

A strong answer names one concrete Indian listener segment, designs two or three features that each map to a stated conversion metric, and picks what ships first with an explicit reason. It localizes every choice to India price sensitivity and low ARPU rather than reusing a Western playbook. It names a primary metric with a guardrail, treats JioSaavn bundling and YouTube Music migration as real constraints, and ends each feature with the tradeoff being accepted. It sounds specific, prioritized, and honest about cost rather than a list of ideas.

Yes. The bar is calibrated to a mid-level product manager with roughly two to five years of experience. You are expected to own a feature area and reason about impact sizing, not to set company strategy or run an organization. The interviewer probes for segment specificity, metric rigor, prioritization reasoning, and tradeoff honesty at the altitude a Spotify hiring manager would expect, and will push past a first answer rather than accept it without a follow-up.

Knowing the rough shape helps but precise numbers are not required. It is useful to know that India pricing is low and tiered, that there is a heavily discounted multi-month Premium trial, and that micro-plans exist for daily or weekly access. What matters more is reasoning about why a price-sensitive, low-ARPU market behaves differently and how that constrains the features you can profitably build and operate. The interviewer cares about judgment under these constraints, not pricing recall.