How to Hire a Product Manager for a Mobile Game Studio

How to Hire a Product Manager for a Mobile Game Studio

A mobile game product manager is not a feature-roadmap owner. They own a number — ARPDAU, D7 retention, LTV on a specific cohort — and they move it by changing the economy, the live-ops calendar, the onboarding funnel, or the offer placement. If you screen for generic PM craft (roadmaps, user stories, stakeholder alignment), you will hire someone who writes excellent tickets and cannot tell you why your D1 fell after the last content update.

So the first decision is not "what does a good PM look like." It's "which of my numbers is this person responsible for, and can they show me a time they moved that number somewhere else."

The three archetypes — hire for your stage, not for the title

Most studios post one job called "Product Manager" and interview three fundamentally different people against it. Split the role before you write the description.

  • Monetization / economy PM. Owns pricing, IAP ladders, ad placement and frequency, soft-currency sinks and faucets, and the sale calendar. Comes from a title with real revenue, often with a spreadsheet habit bordering on obsessive. This is the hire when the game retains but doesn't earn.
  • Live-ops / content PM. Owns the event calendar, the seasonal cadence, the battle pass, and the pipeline that feeds it. Spends half the week with art and design because content velocity is their constraint. This is the hire when the game earns but goes quiet between updates.
  • Core-loop / new-product PM. Works pre-soft-launch, owns CPI, tutorial completion, and early retention. Works closely with UA on creative testing because in hyper-casual and casual, the creative is the product hypothesis. This is the hire when you're prototyping, not operating.

A studio with one live title and a handful of prototypes needs the first or second. A publisher testing a steady stream of games every quarter needs the third, and probably needs more than one of them. Hiring an economy specialist into a prototyping team is the most common and most expensive version of this mistake — they will spend months tuning an economy for a game that should have been killed in its first few weeks.

What actually separates candidates in the screen

Everyone who has worked at a mobile studio can name the metrics. Fewer can tell you what they did when the metrics disagreed with each other. That's your filter.

Ask for one shipped change, end to end:

  • What did you believe before you shipped it, and what was the evidence for that belief?
  • How did you size the test, and what had you decided to do if it came back flat?
  • What did it break? (Every monetization win breaks something. A candidate who says nothing broke either didn't own it or didn't look.)
  • What did you ship next because of what you learned?

The strong answers have texture: a specific segment, a specific trade-off between early revenue and long-term retention, a decision made with incomplete data and a reason for making it anyway. The weak answers describe a process — we ran a test, the variant won, we rolled it out — with no view of why it won or who it won with.

The second filter is their relationship with data. Ask whether they wrote their own queries or asked an analyst. Neither answer is wrong, but the follow-up matters: a PM who always asked an analyst should be able to describe exactly what they asked for and why. A PM who claims SQL fluency should be able to describe how they'd segment a cohort to isolate a change in spender behavior. In a studio without a dedicated live-ops analytics function, the PM is the analyst, and you need to know that up front.

A case exercise that doesn't waste anyone's time

Skip the take-home that asks for a feature spec. Run a short working session instead, inside a single meeting, with real-ish numbers from your own title (sanitized if you need to).

Give them a dashboard snapshot: installs by source, retention curves by cohort, ARPDAU split between IAP and ads, a conversion funnel, and the last couple of months of the event calendar. Then give them a situation — revenue is flat, UA spend is rising, the last two events underperformed the one before them — and ask what they'd look at first.

What you're watching for:

  • Do they ask about the UA mix before concluding anything about the product? A retention drop caused by a channel shift is not a product problem, and the PM who confuses the two will push a roadmap that fixes nothing.
  • Do they separate the metric from the decision? "D7 is down" is an observation. "D7 is down for players who hit the first paywall early in the progression, so I'd test moving the gate" is a product manager.
  • Do they propose something testable within one sprint, or do they design a half-year overhaul?
  • Do they ask what the art and design team's capacity is before proposing a new content format?

That last one separates people who have shipped live-ops from people who have planned it. Content velocity is a staffing question, and a PM who treats the art pipeline as infinite will burn out your 2D artists and technical artists within a couple of quarters.

Where this talent sits in Turkey and Europe

Istanbul is unusually deep for this role, and for a specific structural reason: the casual and hyper-casual publishers that scaled out of Turkey ran enormous volumes of tests, which produced a generation of people who have genuinely seen a lot of soft launches, creative tests, and economy iterations. That experience compresses years of judgment into a short career. The trade-off is that much of it skews toward the core-loop and UA-adjacent archetype — strong on CPI, early retention and creative testing, thinner on deep mid-core economies and long-tail live-ops.

For mid-core and long-session titles, the deeper pools sit in Helsinki, Stockholm, Warsaw, Barcelona and London — and they price accordingly. If your title is mid-core but your budget is casual, the practical path is a Turkey-based PM with strong analytical instincts plus a senior product voice above them, rather than a mid-level mid-core PM in a high-cost market who'll be your most expensive hire and still need support.

On compensation, the structure matters more than the headline figure. Mobile game PMs in Western Europe typically expect a bonus tied to title performance; Turkish packages more often concentrate value in base salary, with equity or bonus as a smaller component and currency expectations frequently pegged to EUR or USD. Before you benchmark, decide whether you're paying for a number they own or a function they run — that distinction, not geography, drives most of the spread you'll see in offers.

PM, producer, or game lead — settle this before you post

A large share of failed game PM hires are org-design failures, not sourcing failures. Three roles overlap:

  • The producer owns schedule, scope and delivery.
  • The game lead or creative director owns the vision and the feel.
  • The PM owns the commercial performance of the live product.

In a small studio, one person often does two of these. That's fine — but say which two in the job description, and make sure the person you hire wants the combination. A commercially sharp PM who discovers they've been hired to chase Jira tickets will leave quickly, and the market is small enough that they'll tell people why. The same goes for the reverse: a producer promoted into a PM title without the analytical grounding will stall at the first economy decision.

If the real gap is above the PM layer — you need someone to own product across a portfolio of titles, set the testing discipline, and hire the PMs underneath them — that's a different search with a different candidate pool, and it's worth treating as a director-level search rather than a scaled-up PM hire.

What to say in the pitch

Good game PMs choose roles by scope, not by salary band. The three things they want to know: what title or portfolio they'd own, how much authority they have over the economy and the calendar without escalating, and whether the studio ships fast enough to learn anything. If your answer to the second is "the founder signs off on every price change," expect your best candidates to drop out at offer stage. Studios that win these hires are usually explicit about decision rights — and a clear, honest picture of how the studio actually works converts better than another round of perks slides.

Plan for a search measured in months, not weeks. The strongest people in this role are rarely on the market; they're one conversation away from a counteroffer, and they move when the scope is bigger than what they have now. Write the role for the number you want moved, and the rest of the process gets much simpler.

← All posts