Product Management interview prep.

A games PM owns the game-as-product: KPIs (retention curves, ARPDAU, LTV), live-ops cadence + content calendar, monetization roadmap, A/B + experimentation, feature prioritization in partnership with design + art + eng.

What interviewers look for

  • Can the candidate frame any product question as player-experience hypothesis + KPI - not feature-listing?
  • Do they read retention curves (D1/D7/D30) + cohorts fluently and reason about which lever moves which?
  • Do they understand monetization design ethically + commercially - cosmetics + battle pass + fair offers vs predatory gacha + pay-to-win?
  • Do they respect the design team's creative ownership while owning the commercial outcome - partner not override?
  • Are they live-ops-disciplined - content calendar, event cadence, economy stewardship, hotfix readiness - not just launch thinking?
  • Can they design A/B tests in a games context - small samples, guardrails, segmentation, the difference between a live game and a SaaS funnel?

Behavioural questions to expect

  1. Walk me through your CV.

    What it tests: Story coherence + genuine fit for the games PM seat. Teams want evidence of game-as-product ownership (live KPIs, live-ops, A/B), not just SaaS PM or pure gameplay design.

  2. Tell me about your most impactful product launch or feature on a live game.

    What it tests: Depth of ownership + KPI impact. Tests whether the candidate frames player problem -> hypothesis -> A/B or rollout -> measured KPI delta - not feature description.

  3. Tell me about a weakness, a failure, or feedback you've received and worked on.

    What it tests: Self-awareness + PM discipline in a live-game context. Cross-role canonical. Gaming PM mistakes (the over-monetized event that burned retention, the A/B with no guardrails, the feature shipped over the design lead's objection) carry real KPI + relationship cost.

  4. Why games product management - and why this genre / studio vs SaaS PM or pure design?

    What it tests: Authentic fit for the player-experience-meets-KPI-meets-live-ops seat. Tests whether the candidate WANTS games specifically (the live operating rhythm, the player-experience metric, the design partnership) vs treating it as a generic PM seat.

  5. Which game lifecycle stage or genre would you want to PM, and why?

    What it tests: Genuine fit + grasp of how PM work differs by lifecycle + genre (soft-launch tuning / global-launch / mature live-ops / sunset / new-IP pre-launch). Tests whether the candidate has a reasoned preference.

  6. Why this firm?

    What it tests: Whether the candidate has done the homework. Bar: specific evidence from the firm's titles, genre + lifecycle posture, live-ops cadence, monetization philosophy, and people - not generic 'great studio'.

  7. How would you describe this firm's portfolio + product approach in your own words?

    What it tests: Whether the candidate has internalized HOW the firm builds + operates games - genre, lifecycle mix, live-ops cadence, monetization philosophy - not just 'they make games'.

  8. How does product management actually create value at a games studio?

    What it tests: Whether the candidate understands games PM economics: PM converts the design team's creative output into a KPI-shaped operating cadence; the right feature + event + monetization decisions compound retention + LTV; the wrong ones burn the audience.

Technical concepts to master

Game KPI literacy

Retention curve - D1 / D7 / D30
Percentage of new installs returning on day 1, 7, 30. D1 reflects onboarding + first-session value; D7 reflects early engagement + early monetization; D30 reflects long-term product-market fit.
ARPDAU + ARPPU + LTV
ARPDAU = avg revenue per daily active user. ARPPU = avg revenue per paying user (segment-skewed by whales). LTV = expected revenue over a player's lifetime, typically modeled as ARPDAU x expected retained days.
Payer mix + segmentation (whale / dolphin / minnow)
Heavy payers (whales) drive disproportionate revenue but are concentration risk; minnows + dolphins drive base; non-payer experience drives retention + acquisition referral.
Cohort + acquisition source analysis
Slice KPIs by install week, acquisition source (paid vs organic, which channel), platform, country - aggregates hide cohort effects.

Live-ops + content calendar

Content calendar + event cadence
Weekly / monthly events + feature drops + collaborations mapped months ahead; cadence sustains retention + monetization without burning the team.
Economy stewardship
Live games have in-game economies (currencies, resources, time) that need stewardship - inflation, deflation, exploit-driven imbalance, monetization-economy interaction.
Hotfix + LiveOps readiness
Live games break - exploits, balance issues, server incidents. PM partners with eng + production on hotfix readiness + post-incident review.
Soft-launch + global-launch gating
Mobile games soft-launch in limited geos (smaller English-speaking + emerging markets) to tune KPIs to bands before global launch; PM owns the gating decision.

A/B + experimentation in games

Cohort-based assignment
Assign player to treatment or control once + persistently; avoids contamination across sessions; required for retention measurement.
Primary + guardrail metrics
Primary KPI (e.g. battle pass conversion) drives the decision; guardrails (retention, non-payer sentiment, support volume) catch unintended harm.
Sample size + duration
Sample size + duration depend on baseline KPI variance + minimum detectable effect; live games often need longer durations to see retention effects than SaaS funnels.
Phased rollout + kill-switch
5% -> 25% -> 50% -> 100% staged exposure with daily monitoring + a kill-switch + revert path; lets bad changes be caught before broad harm.

Monetization design + ethics

Monetization model spectrum
Premium (one-time + DLC), F2P + IAP (cosmetics + convenience + power), subscription, ad-supported, hybrid. Each has different design + KPI implications.
Ethical monetization spectrum
Cosmetic + convenience monetization (sustainable, brand-positive) vs pay-to-win + dark-pattern monetization (loot box opacity, FOMO timers - retention + brand corrosive).
Battle pass + season design
Tiered seasonal progression with free + premium tracks; standard recurring monetization that pairs progression + cosmetics + content.
Offer design + player segmentation
Different player segments need different offer cadence + value; whale offers vs minnow offers vs non-payer onboarding require distinct design.

Practical drills

  • Pitch a feature for one of this firm's live titles. Walk me through your reasoning from player problem to A/B rollout.
  • this firm's flagship is seeing D7 retention drop from 22% to 17% over 4 weeks. Walk me through diagnosis + response.
  • Design an A/B test for a battle pass price + content change on a live mobile F2P title. Walk me through design + analysis.

Smart-question anchors

  • Portfolio + lifecycle - which titles, what stage, what the PM would own first
  • Operating model - design-PM partnership, analytics maturity, A/B platform, live-ops cadence
  • Monetization philosophy - commercial posture vs player + brand stewardship
  • Retention + KPI bar - what 'good' looks like at the studio, where the focus is
  • Cross-functional - design, eng, art, analytics, marketing, publishing relationships

Related roles

Sourced from

Ready to Generate Your Own Prep?

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.

Generate my first prep