Principal Product Manager — Ecosystem

Fanatics Betting & Gaming•New York, NY

22h•$200,000 - $230,000

About The Position

Fanatics operates as a set of separate companies — Betting & Gaming, Commerce, Collectibles, Live, Retail — that happen to share the same fans. Our team's job is to make those companies feel like one thing to a fan: one identity, one loyalty currency, one set of habits, and a platform underneath that means we build an experience once and deploy it everywhere. This is the widest product seat we have. It runs from the surfaces a fan actually touches — the Fanatics app, scores, free-to-play, the places loyalty shows up — down to the infrastructure that makes any of it work across five businesses. You'll own both ends, and the connection between them is where most of the value is. It is also the role we point at the hardest open problem in the ecosystem. When something matters and nobody owns it, or someone owns it and it's stuck, you go in, get deep enough to actually solve it, and then either keep it or hand it off cleanly and move to the next one. If you want one product area and a settled roadmap, this is the wrong job. If the best work you've done was the work nobody had scoped yet, keep reading.

Requirements

Eight or more years in product, with genuine consumer product ownership and genuine platform or infrastructure ownership.
Range, evidenced by having owned meaningfully different problems and getting useful in an unfamiliar domain in weeks rather than quarters.
Experience carrying acquisition or retention numbers and ability to defend what actually moved them.
Technical depth to be a real partner to platform engineering, including understanding of APIs, SDKs, authentication and identity flows, data models, service boundaries, and what breaks under load.
Data fluency, including ability to write own queries, design experiments, and differentiate between a metric moving and a metric mattering.
Cross-organisational influence where the outcome was owned but not the roadmap; experience in multi-brand, multi-P&L, holding-company, super-app or marketplace environments.
Comfort in a regulated environment, having shipped inside legal and compliance constraints and treated compliance partners as collaborators.
Strong writing skills sufficient to carry a decision without being present.
Low ego and a bias to action.
Judgment to go deep on the right thing and stop working on the wrong one.

Nice To Haves

A consumer app where a daily-habit or retention metric was owned and moved, with supporting data.
Free-to-play, fantasy, predictions or games-of-skill experience, especially where it fed a paid product.
Loyalty, rewards or membership experience across multiple brands, including the economics: liability, breakage, margin, and what a point is actually worth.
Experience building or scaling an identity, auth or accounts platform used by several products.
Experience driving internal adoption of a shared platform against teams who'd rather build their own.
Experience being handed ambiguous, politically complicated problems.
Experience killing something that was built.
Experience working in an ecosystem that was the product (e.g., super-app, multi-vertical marketplace, multi-brand membership program).
A document written that changed a company's decision.

Responsibilities

Own the Fanatics app and the daily habit, including what a fan sees first, what brings them back tomorrow, and how following a game turns into a bet, a card, a ticket or a conversation with their friends without feeling like a funnel.
Own how fans get into the ecosystem, including registration, onboarding, the first session, cross-sell, referral and invite mechanics, and a single login across every product.
Own how fans are retained through habit loops, notifications, and cohort retention by product and by entry point.
Own the future of free-to-play, including game design, cadence, prizing, how it ladders into paid products, and its value as an acquisition and retention channel.
Own how loyalty (FanCash) shows up in-product, including earn and burn moments, bonus engine surfacing, and fan understanding of the currency.
Own scaling the infrastructure, including identity, shared SDKs, common components, and ensuring adoption by other teams.
Own what breaks at ten times the traffic, where service boundaries should sit, and what needs to be built for future scalability.
Take on the biggest problems in the ecosystem, go deep to solve them, and either keep the area or hand it over.