AI-Native Product Release Owner (Product Owner/PM) — Release Readiness and Go/No-Go at MUST Company | Torre

AI-Native Product Release Owner (Product Owner/PM) — Release Readiness and Go/No-Go

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: To be defined

Provide your expected compensation while applying
location_on
Remote (anywhere)
Shared by
Agustina Favuzzi
4 days ago

Responsibilities


The code works is not a release.MUST Company is hiring an AI-Native Product Release Owner to own exactly that gap.This is not a project coordinator role, and it is not about adding more features. You define what "releasable" means for each product, hold every release to that bar, and personally make sure a new user can get value without help. You will say "not ready" — and then remove what is blocking it.What you own:Release-readiness criteria per product: access and login, plans and permissions, one clearly named live version, onboarding, empty and error states, docs, support path, analyticsReadiness audits on existing products, turned into prioritized owned tasksThe version story — retiring or merging duplicates so everyone knows what is liveOnboarding and time to first value, with no manual admin in the pathPRDs and acceptance criteria that engineers and AI coding agents can build againstActivation, key-flow success, retention and support-tickets-per-user, reported weeklyGo/no-go, release notes, post-release reviewYou'll fit if you have:3+ years as a PO or PM, including one product you took from build to real adoptionExperience defining release criteria and making go/no-go callsOwnership of onboarding, account, plan and permission design, and activation metricsHands-on product sense — you test products yourself and find what breaks for a new userComfort saying "not ready"Tell us about one release you stopped or rolled back, and why.Remote, full-time. Every role runs a role-specific Quest — a CV tells us what you were near, a Quest tells us what you can do.