Senior Product Owner

At Appodeal, we’re more than just a company—we’re a team united by a common mission: Help people discover and grow their talents through products that enable successful mobile app businesses!

We take pride in our cutting-edge product and our internationally dispersed team of talented professionals.

Here’s what we value, and what we hope you do too:

• Continuous Learning and Growth: We are passionate about learning, growing personally, and building rewarding careers.
• Making an Impact: We are committed to building a history-defining company that leaves a lasting impact on the mobile app industry.
• Solving Exciting Challenges: We tackle complex problems every day, supported by a team of world-class professionals and mentors.
• Enjoying the Journey: We believe in having fun while working toward our goals.

The Senior Product Owner is the single person accountable for the profit of a set of live casual mobile games. These are cards, words, board and simple puzzle titles, monetized mainly through ads, with a long evergreen life. The role owns the whole picture for its games:

• Releases.
• Experiments.
• Monetization tests.
• The performance of the marketing campaigns.

It directs the specialists who execute UA, creative and store work on those games. It is a product manager and a developer in one person. It writes the PRDs, pulls its own data, and ships code where that is the fastest way to get something live. It has real authority to match the accountability, and it has no people-management duties.

Appodeal runs product work on an AI-native model:

• Moving to internal AI systems: aggregation, status, reporting, competitive research and first drafts. Some of these systems are live today, and more are being built. Until they land, you will do some of this work by hand.
• What stays with this role: choosing what to test next, making kill-or-scale calls on partial data, and owning the profit number.
• What the role builds: the automations and agents that make the next experiment faster.
• There are no status meetings. The pace is a release and a written experiment every week, per game, and it does not let up.

Own the profit of your games: 

• →Own profit growth end to end across product, monetization, UA, store and creative.
• →Set the growth trajectory each quarter and re-set it when reality shifts.
• →Know at any moment where each game is heading and which two experiments are most likely to move it.
• →When profit falls, write down why, with a date, before anyone asks.

Decide what to build, and what to kill: 

• →Run the roadmap for each game, ranked by expected profit impact.
• →Read competitors as sources of feature ideas.
• →Bring an evidence-based proposal when a game has reached its ceiling for the current growth phase.

Ship every week: 

• →Per game, every week: at least one release, and at least one qualified experiment shipped and written up.
• →Own the LiveOps calendar and the go/no-go on every release.

Write code: 

• →Ship features, analytics events, LiveOps changes and experiment infrastructure yourself, wherever that is the fastest path.
• →Pull your own data from BI.
• →Prototype without waiting on engineering.

Run monetization and marketing on your games: 

• →Run monetization changes, A/B tests and ad-ops work hands-on.
• →Own campaign performance.
• →Direct creative production, UA execution and store optimization, which are carried out by specialists on the team.

Experiment, write down, repeat: 

• →Write every experiment as hypothesis, method, result and next hypothesis, so the next owner can pick it up cold.
• →Put what you learn about infrastructure into the codebase.

Automate what repeats:

• →Build agents, scripts and tools for any task that repeats.
• →Measure what each one does to cycle time: experiment setup, LiveOps turnaround.

Handle the exceptions:

• →Triage revenue anomalies, traffic-quality flags, broken experiments and store-policy incidents.
• →Escalate the same day when there is store, legal or partner exposure.

• 3+ years as a Product Manager or Product Owner on casual, ad-monetized, evergreen mobile games: cards, words, board or simple puzzles. Match-3, midcore, IAP-heavy, social casino and hypercasual experience does not count toward this.
• Named metrics you moved with features you shipped. For example revenue, profit, ARPDAU, IPM, ad LTV, D7/D30 retention. You should be able to give the before and after, and your part in it.
• Working-level code. This is a hard requirement. You pull your own data from BI, script automations, and prototype without engineering.
• Demonstrated AI experience, required. You have automations or agents running in production in your product work. You can describe the specific workflows you improved, the results they delivered, and how you validated the output. Prompt literacy on its own does not meet this.
• Strong data analysis. You can pull and join cohort, retention, monetization and UA data yourself, and validate it. You can tell a UA-quality problem from a product problem from a monetization problem. You can explain a profit read to someone outside product.
• Senior autonomy. You decide on partial data, kill your own ideas when the data says so, and own outcomes without status meetings or hand-holding.

• Experience with IAP-hybrid monetization.
• Unity or C#.
• A public or shareable SQL or Python portfolio.