Senior Product Manager - Games Platform

Senior Product Manager - Games Platform

Location: Europe (Remote)

About Entity

Entity is building the home for console-quality gaming in the browser - a full platform spanning game technology, developer tools, distribution, and a next-generation social and live-ops layer built into the core.

For players, we make real, full-scale games instantly playable on any device with no downloads or installs - click a link and you're playing in seconds. For developers, we're building the new channel for instant gaming: self-serve tools to publish, operate, and grow their games directly to players, backed by a distribution and growth engine that changes the economics of growing a game.

We're led by a team that has founded and exited studios, scaled global gaming platforms, and shipped some of the most successful games in the industry - now focused on making the browser a serious home for the games people love and building the defining platform of a new era in gaming.

Joining Entity at this stage is a rare opportunity to help shape our company and our mission.

About the Role

We are hiring our first dedicated product manager. This is a focused role: you will own the platform build, the player-facing Games Hub, and live game operations as we move from concept to first live release and beyond.

Your remit is to ensure we build the right platform for our players and developers - with the right foundations, the right features, and the right approach to live operating the product. (Growth, distribution, and UA will be covered by a separate hire at the right stage - but broad knowledge of these areas would be an advantage).

This role combines strategic product thinking with deep analytical and systems-oriented design. You will be responsible for helping define the early product strategy, shaping core platform capabilities, and ensuring decisions are grounded in clear assumptions, metrics, and an understanding of how games actually perform.

You will work closely with leadership, design, and engineering to help define what we build, why we build it, and how success is measured - setting strong product foundations that scale as the platform grows.

This is not a feature-factory role. It is a foundational product role with real influence over Entity’s long-term direction.

Key Responsibilities

• Work with CEO / CTO / Head of Product Design to define the product vision and platform feature set, spanning player experience, developer tools, and game operations.
• Take core platform features from concept through to live release, working closely with engineering, design, and leadership.
• Translate ambiguous ideas into clear, focused product definitions that align teams without over-prescribing solutions.
• Define success metrics, KPIs, and assumptions for early platform features
• Apply deep understanding of games KPIs (retention, engagement, monetisation, funnel conversion, etc.) to product decisions and tailored for a platform business
  
• Balance speed and rigour by producing “just enough” documentation to support high-quality delivery (Work with design and engineer groups to get the process right)
• Facilitate strong alignment across stakeholders before and during development, ensuring clarity on goals, trade-offs, and priorities.
• Work collaboratively with engineering and UX/design throughout delivery, refining scope and direction in real time.
• Contribute to roadmap definition and prioritisation, balancing strategic impact, effort, and sequencing.
• Prepare the platform for post-launch iteration, defining hypotheses and instrumentation from day one.
• Use live data and player/developer feedback to guide ongoing optimisation and evolution after launch.

Requirements

• 5+ years’ experience in product management or a closely related product role in the games or games platform space.
• Proven experience taking early-stage products from concept to first release.
• Strong ability to structure ambiguous, complex problems into clear product direction.
• A proven product thinker, able to conceptualise and communicate vision for creative and technical audiences alike.
• Truly understands games platforms and ecosystems including Steam, EGS, Roblox, Playstation, Twitch, Discord at a minimum.
• Highly data-literate, with hands-on experience defining and working with product and games KPIs.
• Deep understanding of games performance metrics, especially free-to-play and/or live-operated products.
• Solid grasp of player retention, engagement funnels, and how product decisions impact long-term player value.
• Strong written communication skills, able to create clear, concise product specs that align teams.
• Comfortable working in fast-moving, highly collaborative environments without heavyweight process.
• Able to explain trade-offs and priorities clearly to technical, creative, and commercial stakeholders.

Nice to Have

• Experience building platforms, tools, or ecosystems, not just single consumer features.
• Background in free-to-play, live-ops, or platform-adjacent games products.
• Familiarity with browser or web-based products, including performance and distribution considerations.
• Some technical background or strong technical fluency when working with engineering teams.
• Experience defining MVP scopes and making pragmatic decisions under real constraints.
• Strong interest in where games distribution is heading.
• Experience with Figma or other collaborative design workflows.

Working Conditions

Entity is remote-first. Team members can work from anywhere in Europe within ±3 hours of GMT, with a suitable home-working setup. We value autonomy, clear ownership, and outcome-driven work. Some flexibility in working hours is expected to support collaboration across time zones. Occasional travel may be required for team sessions, industry events, or visits with development partners.

Application Note

When applying, please include the phrase “decisions create constraints” somewhere in your application.

In addition, briefly answer the following (3–4 sentences is enough):

Describe one product decision you believe was right because of good prioritisation — and one that was wrong because of poor prioritisation. Explain what information should have mattered most in each case.