How to Hire a Live-Ops Manager for a Mobile Game Studio

Hire a live-ops manager when your game has a stable retention curve and a content calendar you are already struggling to run manually — usually somewhere between soft launch and the first scaled UA push. The role you are hiring for is not "someone who schedules events." It is the person who owns the revenue your existing players generate over the next 90 days, which means they need to read cohort data, design an economy, write a calendar, and ship it with the team you already have. Most studios get the hire wrong because they write a job description for a producer and then expect a product owner.
Here is how to define the role, where to find people who have actually done it, and how to test for it without a six-week trial project.
What the role actually owns
In a mobile game that makes money after launch, live-ops sits at the intersection of three things: the event calendar, the in-game economy, and the segmented offer system. A live-ops manager who is doing the job well is making decisions like these every week:
- Which event runs next weekend, for which segment, and what it is supposed to move — session count, D7 retention, ARPDAU, or conversion of non-payers
- What the reward curve looks like, and whether it inflates the economy enough to depress next month's purchases
- Which offers appear to a lapsed whale versus a 14-day-old non-payer, and at what price point
- When to kill an underperforming event format instead of iterating on it for the fourth time
The deliverable is a calendar with a thesis behind every slot. The failure mode is a calendar that exists because the slots needed filling.
Before you write the job ad, decide whether this person owns the number or supports it. If your product manager owns monetization and the live-ops hire executes, you are hiring a senior live-ops producer and should pay accordingly. If the live-ops manager carries the revenue target for the installed base, they need authority over pricing, economy tuning, and at least part of the art and engineering roadmap — and they need to be senior enough that your PM does not quietly override them. Studios that blur this spend a year arguing about who decides the price of the battle pass.
Live-ops manager, product manager, UA manager: the real boundaries
The three roles overlap enough that candidates will claim all three titles. A useful separation:
- UA buys the install. Their world is CPI, ROAS by channel, creative testing, and payback window.
- Product decides what the game becomes — new modes, new systems, the long-arc roadmap.
- Live-ops monetizes and retains what already exists, inside the systems product has shipped.
If your studio is small, one person may wear two of these hats, and that is fine for a single title. It stops working the moment you have two live games, because live-ops is a cadence job: someone has to be looking at yesterday's event numbers every morning. Product thinking can wait a week. Live-ops cannot. If you are also working out how the UA side of the team should be structured, the specialist technical and product recruitment side of hiring for live games is worth planning as one sequence rather than three separate searches.
The three profiles you will see in the pipeline
Almost every live-ops candidate comes from one of three backgrounds, and they fail in different ways.
The analyst who moved into live-ops. Comes from a data or BI seat, usually in a studio with a strong analytics culture. Strong on segmentation, cohort reading, and A/B test design. Weak on content instinct — they will optimize offer timing brilliantly and then propose an event theme nobody wants to play. Best fit when your game is systems-heavy: 4X, RPG, card battlers, anything with a deep economy.
The community or content person who moved into live-ops. Knows what the players want, writes good event narratives, has a feel for pacing and surprise. Weak on economy math — they will approve a reward bundle that undercuts your core sink without noticing. Best fit for casual and social-casino titles where theme and novelty drive engagement more than economy depth.
The economy or game designer who moved into live-ops. The rarest and usually the most expensive. Thinks in sinks and faucets, understands where inflation comes from, can model a season pass in a spreadsheet before anyone builds it. Weak on execution cadence — may over-design when the calendar needs filling on Thursday.
You are not looking for someone with all three. You are looking for the profile that matches your genre and the gap in your current team, and then for evidence that they are curious about the other two.
The work sample that actually separates candidates
Skip the case study about a fictional game. Use your game, with real numbers, lightly anonymized.
Give the candidate: a retention curve, ARPDAU by cohort, the last three months of event performance with dates and formats, and the current economy sources and sinks. Ask for a four-week calendar with a one-paragraph rationale per event, one offer segmentation proposal, and a note on what they would stop doing.
What you are reading for:
- Do they ask questions before they build? A candidate who proposes a calendar without asking about your content production capacity has never worked with a real art pipeline.
- Do they tie each event to a metric and a mechanism, or do they list themes?
- Do they identify the thing you should kill? Almost every live calendar has a legacy format running on inertia. Spotting it is the single best signal of someone who has actually operated a game.
- Does the plan survive your art team's bandwidth? Ask them to estimate asset cost per event. Good live-ops people think about production constraints automatically, because they have been told no before.
Two to three hours of candidate time is enough. Pay for it if the exercise runs longer.
Sourcing: Turkey, and the rest of Europe
Istanbul and Ankara have an unusually deep pool for this role, and the reason is structural. Turkey's studio scene grew up on casual and hyper-casual publishing, which means a large number of people spent their first five years running events, testing offers, and reading retention dashboards on games with enormous install bases. That is exactly the rep count a live-ops manager needs, and it is compressed into fewer years than in markets where people arrive at live-ops through long console or PC careers.
The trade-off: hyper-casual backgrounds often mean shallow economy experience, because those games monetized through ads rather than deep IAP systems. If you run a mid-core title, probe hard on economy design and expect to filter heavily. Candidates from Turkish studios that shipped mid-core or social-casino titles are the ones to prioritize.
Elsewhere in Europe, the Nordics and Poland hold strong mid-core live-ops talent, generally at higher cost and with longer notice periods. Spain and Portugal have grown pools attached to publisher offices. If you are building a live-ops pod rather than a single hire — manager plus analyst plus economy designer — a dedicated team built in Turkey is usually faster to assemble than three separate searches across three markets, because the candidates already know each other's studios.
Pay structure, not just pay level
The cost gap between Istanbul, London, and Berlin for this role is large and well known, so the more useful question is how to structure the package. Live-ops is one of the few game roles where variable compensation makes sense, because the output is measurable within a quarter. A reasonable structure ties a bonus to installed-base revenue or a retention metric the person genuinely controls — not to total revenue, which UA spend dominates.
Two cautions. First, do not tie the bonus to a single-quarter ARPDAU lift, or you will get aggressive offers that strip-mine your payers. Pair any monetization metric with a retention or payer-count floor. Second, be honest in the offer conversation about who owns pricing. Senior live-ops candidates have all been burned by a studio where the CEO vetoed every price change, and they will ask.
If the hire is a live-ops director who will build the function and own P&L for a portfolio of titles, that is a leadership search with a different candidate pool and a different process — closer to executive search for studio leadership than to a standard role posting.
When to make the hire
The trigger is not revenue size. It is calendar complexity. The moment your events need segmentation, your economy has more than two currencies, or you are running two live titles, the job exceeds what a product manager can do alongside the roadmap. Hiring before that point gives you an expensive person with nothing to operate. Hiring six months after it means half a year of flat revenue on a player base you already paid to acquire.