Product Manager

Limbic
Remote

About The Position

Product Manager - Limbic Access Limbic builds AI-powered mental healthcare. Our front-door Access product talks to thousands of patients a month across the NHS and major US health systems. Access is past 0→1 in the UK and US: the product exists, customers are live, the model is proven. We're hiring a Product Manager to take it 1→10 in the US, against a growing pipeline of enterprise customers, owning the team's day-to-day product cadence. The job is to ship and ship well.

Requirements

  • You've shipped product before. Maybe one or two roles in. You want real product management. The kind where you own outcomes, not Jira tickets.
  • You ship features and projects that move metrics and create outcomes. Not work that's about looking good.
  • Comfortable with engineers and engineering concepts. You build strong mental models for how products work and apply them in your day-to-day.
  • You write clearly and quickly. You think clearly from first principles.
  • You think critically with data. You can pull insights yourself, interrogate how they were generated, and reason about what they actually mean. Not 'I made a decision with data once.'
  • You never produce AI slop, but you do heavily rely on AI in your day-to-day. You go beyond using AI to write PRDs.
  • You are 'client safe' - you can represent Limbic to customers professionally.
  • You can say no to someone and make them feel it's in their best interest.
  • You build products. You know the difference between a feature that creates repeatable value and a one-off that introduces drag and tech debt.

Nice To Haves

  • Healthcare experience is a bonus, but not a requirement. EHR integration and working knowledge of health-data standards (HL7, FHIR) especially.

Responsibilities

  • Run the team's ceremonies: effective, alignment-creating, always followed up on.
  • Own roadmap prioritisation. Understand the projects in play, weigh their relative impact, and sequence them. Ground the sequencing in customer signal, and user feedback, usage, and behaviour.
  • Triage the inbound: bugs, debt, CS asks, scope additions. Separate real issues from noise, route to the right owner, decide what gets iterated when.
  • Scope and define the work. Write project overviews the team can act on, ensuring the next-highest-value project is always lined up.
  • Own the incident loop. Triage, root cause, fix, follow-up. Engineers get space to fix; you hold the loop.
  • Keep the product well instrumented. Mixpanel today and whatever's next. Ensure the team can answer its own questions from the data, and that you can read user behavior out of it.
  • Protect engineering focus. Hold the line on scope creep from any sources. Check in 1:1 mid-cycle with anyone who's blocked or drifting.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service