Free-to-Paid Conversion in India round·Product Management·Medium·20 min

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

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

Z
ZeroPitch Research Desk
Updated 2026-05-16 · Newly added · be among the first to take it
Field
Product Management
Company
Spotify
Role
Product Manager
Duration
20 min
Difficulty
Medium
Completions
New
Updated
2026-05-16

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

  • Topic focus. You design features that move Spotify's ad-supported free listeners in India into paying Premium subscribers, under real low-ARPU and price-sensitivity constraints.
  • Conversation dynamic. Priya, a senior India growth product manager, walks you through the scenario and pushes on every assumption rather than letting you monologue.
  • What gets tested. Whether you clarify before pitching, pick one concrete listener segment, tie features to a conversion goal, prioritize, and name the tradeoffs you accept.
  • Round format. A spoken twenty-minute product-design conversation, one scenario explored several turns deep rather than many shallow prompts.

What strong answers look like

  • Segment specificity. You name one concrete listener group and stay with it, for example lapsed trial users in tier-2 cities rather than all free users.
  • Conversion-linked features. Each feature you propose maps to a stated metric, for example trial-to-paid rate for a named cohort, not a general engagement claim.
  • India localization. You reason from price sensitivity, low ARPU, and free-tier habit, for example why a micro-plan at a few rupees fits this market better than a Western monthly plan.
  • Tradeoff honesty. You close each feature by naming what you sacrifice, for example accepting some ad-revenue loss to lift paid conversion.

What weak answers look like (and how to avoid them)

  • All-users design. Designing for everyone signals no point of view, fix it by committing to one segment in your first ninety seconds.
  • Metric-free features. Proposing features with no success measure reads as ideation not product work, attach a conversion metric to each one.
  • Guardrail-free north-star. Naming one growth number with nothing protecting it invites gaming, always pair it with a counter-metric like ad-revenue cannibalization.
  • Generic playbook. An answer that could describe any app in any country fails here, anchor every choice in the India constraint.

Pre-interview checklist (2 minutes before you start)

  • Recall one consumer feature you shipped. Have a recent example where you personally moved a metric, with the number ready.
  • Identify your target segment. Decide which Indian listener group you will design for before you propose anything.
  • Pull up the free-versus-Premium gap. Be ready to name what free lacks and what Premium adds in this market.
  • Think of one conversion metric. Have a primary measure and a guardrail in mind for any feature you propose.
  • Recall the competitive constraint. Be ready to address telecom bundling and the free-experience alternative without being prompted.

How the AI behaves

  • Probes every claim. It asks for the underlying number, the segment, or the baseline rather than accepting the headline.
  • No mid-interview praise. It will not say great answer or validate, it acknowledges the specific content and pushes deeper.
  • Interrupts on generality. If your answer could apply to any product it stops you and asks what makes it specific to this market.
  • One question at a time. It asks a single question, waits, then follows up before moving on.

Common traps in this type of round

  • Pitch before discovery. Listing features before asking about platform, segment, or competition.
  • Segment never named. Talking about free users in general and never committing to one group.
  • Metric with no denominator. Saying conversion will improve without stating for which cohort over what timeframe.
  • Ignoring migration risk. Restricting the free tier without addressing where those users go.
  • Feature list with no order. Proposing several features and never saying which ships first or why.
  • Framework recital. Naming a textbook method instead of reasoning through the actual decision.
Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 5 dimensions. The full rubric with definitions is below.

Segment Specificity
Whether you commit to one concrete Indian listener group and design for them, instead of treating all free users as one block.
22%
Conversion Metric Rigor
Whether each feature is tied to a stated conversion measure with a cohort and timeframe, plus a guardrail against gaming.
22%
India Market Localization
Whether your design reasons from price sensitivity, low ARPU, and free-tier habit rather than a copied Western subscription play.
20%
Prioritization Reasoning
Whether you pick what ships first and give a defensible reason rather than presenting an unordered feature list.
18%
Tradeoff And Competitor Honesty
Whether you name what each feature sacrifices and account for JioSaavn bundling and YouTube Music migration risk.
18%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

  • India Listener Segment Evidence18%
  • Conversion Outcome Articulation18%
  • India Low-ARPU Localization Rigor16%
  • Conversion Constraint Recalibration16%
  • Personal Product Decision Ownership16%
  • Competitor Migration Tradeoff Honesty16%

Common questions

What does the Spotify product-design round actually test for this India conversion scenario?
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.
How should I structure my answer in this round?
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.
What are the most common mistakes candidates make here?
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.
How is this AI interviewer different from a real Spotify interviewer?
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.
How is scoring done in this practice round?
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.
What should I do in the first two minutes of this round?
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.
How do I handle the objection that restricting the free tier will push users to JioSaavn?
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.
What does a strong answer in this round sound like?
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.
Is this aimed at the seniority of a mid-level Spotify PM?
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.
Do I need to know Spotify's exact India pricing to do well?
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.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.