Product Manager - App

Napster
· Full-time
· Remote
· Reports to the Chief Product Officer

In 1999, Napster gave everyone access to the world’s music. Today the Napster App gives everyone a personal crew of AI experts for everyday life: finance, wellbeing, learning, music, and more.

A single assistant answers questions. A crew works a problem. Each agent has its own expertise and its own memory of you, you can see and talk to them on video, and they hand work to each other the way a good team does. That is the bet the Napster App makes, on iOS, Android, and Web, and it is the consumer surface of everything Napster builds.

We need someone to own it.

You lead the Napster App squad and own the roadmap end to end: what gets built, what gets cut, what ships this sprint. You work directly with engineering, design, and the agent team, and with the Partnerships team on everything a partner’s customer will see.

This is an early product in a new category. Most people opening it for the first time have never heard the phrase “AI crew.” Your job is to make the first ten minutes obvious and the first month indispensable.

• Own the roadmap. The launch lineup is three crews: music, productivity (finance and wellbeing), and tutors. You set the order of what comes after, make the trade-offs, and ship.
• Make partner distribution work. Not everyone finds the app through a store search. You own the journey for people who arrive through a partner: activation, onboarding, trial and entitlement flows, billing, localization, and per-market store presence. You translate partner requirements into a product plan without forking the product.
• Run the crews as a product. Each crew is a set of agents with a defined job. You set the quality bar for what a crew must do on day one, work with the agent managers who own each agent, and decide when a crew is ready to ship.
• Define and track what matters. Activation and trial conversion by channel and market. Agents used per user per week. Return sessions. Creation rates. Retention by cohort. Free-to-paid conversion. You define the metrics, instrument them, and hold the team to them.
• Design for sharing. The artifact people share isn’t always the one you’d expect. Sometimes it’s the cover art with their face on it rather than the song. The song gets saved; the cover gets posted. You design for the moments that drive organic growth, not the moments that look important on a roadmap slide.
• Own the launch playbook. Store listings, screenshots, release notes, partner-facing assets, and the sequence that gets each market live, so every surface a partner’s customer checks tells the same story.

You’ve owned a paid consumer subscription on mobile. Acquisition, trial, conversion, churn, and the pricing and packaging decisions behind them. Five or more years in product, at least two on iOS or Android; if you have three and have shipped more than people with ten, we want to talk. Loyalty programs and B2B tools are useful background; they are not this.

You build with AI, and you can prove it. You’ve shipped working products to real users with Claude Code, Cursor, or similar. You understand foundation models, real-time voice, video synthesis, and agent orchestration as trade-offs you make weekly, and you can hold a real conversation with engineers about APIs, streaming architectures, and model orchestration.

You’ve shipped where there was no playbook. You wrote it while executing, decided with 60% of the information, and drove direction through influence rather than org-chart authority.

• AI-native consumer products (beyond adding an AI feature to an existing app)
• Distribution through carriers, OEMs, banks, or other bundled-subscription…