Senior Product Manager - Platform

Senior Product Manager, Platform

Noida Reports to SVP Product 7–10 years

Your customers are mostly inside the building. Discovery, growth, content, partnerships

and finance all build on the systems you own, and none of them should have to think

about how those systems work. You'll turn a set of services that grew up separately into

one platform with clear contracts, owners and SLAs.

Growth PMs decide who subscribes and why. You make sure that once someone pays,

that fact is true everywhere, instantly, on every device and every partner app. You don't

own a conversion funnel; you own the rails the funnel runs on.

What you'll own

1. Entitlements and rights. One resolution layer that answers "can this user watch this, here, now" across plan types, partner services, linear TV and DTH, exposed as a serviceevery team calls
2. Billing infrastructure. Payment orchestration and gateway routing, UPI autopay and mandates, reconciliation, and partner revenue-share settlement that finance can close the books on
3. Partner integration framework. A standard way to plug in a new OTT service: catalogue ingestion, SSO and deep links, entitlement callbacks, usage reporting. Success is weeks to onboard, not quarters
4. Identity and devices. Login, OTP, profiles and device management across phone, web and TV
5. Content and config backbone. The metadata pipeline, CMS and remote-config layer that discovery and editorial teams build their surfaces on
6. Platform health. Service SLAs, observability, and a single event and data layer the whole company trusts...

How you'll be measured

Entitlement accuracy, payment-rail uptime and reconciliation gaps, API latency, time to

onboard a partner, and how often other teams are blocked waiting on platform.

You'll likely have

Built platform, billing, identity or integration products at a consumer company at scale; streaming, telecom or fintech backgrounds fit well

The technical depth to shape service boundaries, API contracts and data models with architects, not just review them

Taken a messy set of legacy systems to a single source of truth without stopping the

business

Written specs that other PMs and engineering teams build against

It'll suit you if you'd rather design a clean contract between two systems than a launch

campaign, and you judge your work by how rarely anyone has to talk about it.