Product Manager, Mobile Games Portfolio

We run a portfolio of casual free-to-play mobile games for one of our clients. We are hiring a Product Manager to own the product work for multiple of these titles.

You will be the main product person for these games. You will find what to fix, decide what to test, and help the team ship it. You will work with data, design, engineering and QA. You will use AI tools every day to move faster.

• →Own the product plan for a group of games: set goals, keep a backlog, and rank what to do next.
• →Find growth chances in ad revenue, retention and engagement. Turn them into clear tests.
• →Write short, clear specs and A/B test plans. State the goal, the KPI, who is in the test, and how long it runs.
• →Read A/B test results and tell the team what to do next: ship, iterate or stop.
• →Track the daily health of each game: DAU, retention, ARPDAU, ad impressions per DAU, eCPM, and revenue.
• →Use AI to pull data, check the numbers, and write up insights fast. 
• →Build quick prototypes (clickable mockups or simple working demos) so the team can see an idea before we build it.
• →Work with LiveOps on events, schedules and content.
• →Work with the ad monetization team on placements, cooldowns and ad rules.
• →Run release checklists with QA and engineering. Know what is in each build.
• →Watch competitors and the app store. Bring ideas back to the team.
• →Give short, regular updates to the team and leadership.

• 2–5 years in product, game design, live ops, or analytics for free-to-play mobile games.
• Real experience with ad-driven monetization: interstitials, rewarded video, banners, and how they affect play and retention.
• Comfort with data. You can write basic SQL or use AI to help you write it, and you can tell when a number looks wrong.
• Hands-on experience with AI prompting. You use tools like Claude, Gemini or ChatGPT for real work and know how to get good answers and spot bad ones.
• Experience using AI for data analysis: asking good questions, checking the results, and not trusting numbers blindly.
• Experience with prototyping: Figma, or AI tools that build quick demos or small web pages.
• Basic understanding of A/B testing: control groups, significance, and why small samples can mislead.
• Clear, simple writing and speaking. You can explain a result in a few sentences.
• Good time management. You can keep many games moving at once.

• Experience with BigQuery, Looker or similar tools.
• Experience with ad mediation (AppLovin MAX, ironSource, AdMob) and attribution tools (Adjust, AppsFlyer).
• Experience with word, puzzle, or casual games.
• Experience with in-app purchase offers and game economies (coins, hints, boosters).
• Experience with Jira, Miro, Notion and Slack.
• A portfolio, side project, or shipped prototype you can show us.

• Curious: You ask "why did this number move?" before anyone asks you.
• Careful: You check your work. You say "directional" when something is not proven.
• Fast: You use AI to cut hours of work down to minutes, and you still verify.
• Practical: You pick the small test that teaches us something over the big plan that takes months.
• Clear: People understand your notes the first time.
• Team-minded: You make designers, engineers and QA want to work with you.

• Each game has a clear plan and a ranked backlog.
• A steady flow of well-designed A/B tests, with a clear call on each one.
• Improvement in ad revenue per player, retention and engagement across your games.
• Fewer surprises. Problems are caught early because you watch the numbers.
• Fast, clear prototypes that help the team decide.