Product Operations Manager

Amae Health•San Francisco, CA

15h•$150,000 - $175,000•Onsite

About The Position

Amae Health is seeking a Product Operations Manager to own the delivery, adoption, and improvement of products in the real world. This role sits at the intersection of Product, Engineering, and Clinical teams, translating strategy into execution and execution into outcomes. It is a high-ownership, high-ambiguity role where the successful candidate will be instrumental in building the product operations system. The company is a Series B, venture-backed Public Benefit Corporation focused on delivering specialty outpatient care for individuals with severe mental illness. They are building proprietary clinical protocols, novel measurement techniques, and an AI-driven data platform to address the long-standing lack of tools and care delivery methods for this population. Amae Health collaborates with leading health systems to expand this level of care, aiming to reduce hospitalizations and improve patient stability and community living.

Requirements

5+ years in Product Operations, GTM, Business Operations, or similar execution-heavy roles.
Tech-focused healthcare startup experience required, ideally with direct exposure to providers/clinicians and their work environment.
Proven track record of launching products and driving adoption.
Track record of measuring adoption and outcomes post-launch, as well as ongoing product KPIs.
Strong analytical instincts; comfortable defining metrics, working with product analytics/data, and building/maintaining trusted dashboards and reports.
Experience writing for non-technical operational audiences (release notes, documentation, enablement material).
Strong systems thinker; experience building scalable cross-team processes.
Exceptional communicator; ability to translate between engineers, clinicians, and operators.
Experience managing feedback loops, support workflows, or ticket triage.
Comfortable operating in ambiguity; ability to create clarity.
High urgency and ownership; ability to move fast and finish tasks.
Fluency with AI tools (especially Claude) to increase speed and leverage.
Deep alignment with the mission to improve mental health care.
Able to work in-person from the San Francisco HQ with frequent travel to clinics in San Mateo and Los Altos.

Responsibilities

Drive product launches from initial rollout planning through go-live.
Build and maintain scalable launch playbooks to ensure seamless and effective feature adoption across all clinic environments.
Translate product into practice by designing training, materials, and workflows for clinicians, and conducting live training sessions.
Provide clinic operations with a rolling quarter of visibility into upcoming releases to facilitate planned training capacity and batch related releases.
Own release notes end-to-end, creating plain-language descriptions with a focus on the 'why this matters' for busy providers.
Own documentation standards, including structure, ownership, and review cadence.
Drive coordination across Product, Engineering, and Clinical teams to bring structure to ambiguity.
Track dependencies and remove cross-team blockers to ensure initiatives are completed.
Maintain the central roadmap and establish an operational cadence (e.g., quarterly planning) for a unified view of engineering work, timelines, and goals.
Design and manage processes for stakeholder feedback and reprioritization to support Product Leadership's strategic decisions.
Manage the intake of support tickets and product feedback, translating real-world insights into actionable inputs.
Run the release tracker to monitor target windows, desired clinical or member outcomes, affected roles, and post-launch adoption signals.
Monitor and report on product KPIs at both the product and launch-by-launch levels.
Track outcomes beyond adoption, measuring improvement on the dimensions a launch was intended to affect.
Maintain dashboards and a reporting cadence for Product and leadership visibility into clinical and product performance.
Step in wherever needed to move the work forward, as is typical in a startup environment.