Product Manager

In 1999, Napster gave everyone access to all the world’s music. Now we’re giving everyone access to expertise — AI companions you can see, talk to, and create with. Not a chatbot. A crew of specialists with persistent memory, video presence, and real domain knowledge, working together on your behalf.

The Napster App is the consumer face of this platform. iOS, Android, and Web. It’s where people create music with AI producers in real time, get coached by wellness experts, learn languages, explore interactive audio books, and build things they couldn’t build alone. It launched in late 2025, replacing the old music streaming app entirely. No more licensed catalogs. No more playlists.

This is a completely new product.

We need someone to own it.

Ship the product that proves AI companions belong on everyone’s phone.

You’ll own the Napster App roadmap end to end. What gets built, what gets cut, what ships this week. You’ll work directly with engineering, design, and AI/ML. You’ll coordinate with platform and infrastructure teams across the company to ensure the app leverages the latest capabilities. You’ll define what success looks like and hold the team to it.

This is not a role where you inherit a mature product and optimize conversion funnels. The Napster App is early. The category is new. Some of our former streaming subscribers are upset we killed their playlists. New users don’t have a mental model for what this product is yet. You need to be the person who figures that out and ships accordingly.

If you want to manage a backlog someone else defined, this isn’t it. If you want to define what a new category of consumer AI looks like, keep reading.

Own the roadmap — You decide what the Napster App builds next. Music creation with genre‑specific AI Companions. Agent feeds where Companions share work even when you’re not talking to them (this is live today — our chief of staff, Jane, already generates content autonomously). Crew orchestration through Kai. Cross‑domain expansion into wellness, education, business. You set the priorities. You make the trade‑offs.

You ship.

Move at our speed — One day here feels like one month. Development cycles are measured in days, not quarters. If you need three rounds of stakeholder alignment before writing a spec, you’ll drown. If you default to done and iterate in public, you’ll thrive.

Go deep on AI — This isn’t a product where AI is a feature. AI is the product. You need to understand foundation models (GPT, Gemini, Claude), real‑time audio generation, video synthesis, agent orchestration, and persistent memory — not as buzzwords, but as engineering trade‑offs you make weekly. You should be building with these tools, not just using them. We expect you to have opinions about when to vibe‑code something in Lovable, when to fork a Git Hub repo, and when to build from scratch.

Navigate the transition — Some users loved the old Napster. They built playlists over years. They’re frustrated. You need to acknowledge that reality without letting it anchor the product in the past. The job is to build forward — to find the users who want AI‑powered creation and make the product irresistible to them.

Define and track what matters — Active creation rates. Crew engagement (how many Companions per user per week). Return sessions. Cross‑platform sync usage. Time spent in 30+ minute conversations. Credit consumption and conversion from free to paid tiers. You define the metrics, you instrument them, you hold the team accountable.

Design for sharing — The artifact people share isn’t always the one you’d expect. Sometimes it’s not the song — it’s the cover art with their face in it. The song gets saved. The cover gets posted. You need to think like that — designing for the moments that drive organic growth, not the moments that feel important on a roadmap slide.

5+ years in product management, at least 2 on consumer mobile (iOS/Android). But if you have 3 years and have shipped more than people with 10, we want to talk.

Production‑level AI fluency. Not "I read about AI" and not just "I use Claude daily." You’ve built working products…