About this role.
Limbic is hiring an APM/Mid Product Manager for its AI-powered mental healthcare Access product, focused on expanding an established UK and US offering across US enterprise health systems. The role owns delivery cadence, roadmap prioritization, inbound triage, product scoping, incident follow-through, and product instrumentation. The successful candidate will use customer signals, behavioral data, and engineering context to ship valuable work while protecting team focus from scope creep. This is a high-load, execution-oriented role in a small team, with an expected path toward broader strategic ownership within 4–6 months.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Job Complexity
4/5Pace & Pressure
5/5Autonomy Level
4/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first make the work visible in one prioritized view, then assess customer impact, patient/user impact, urgency, strategic fit, risk, effort, and reversibility. I would reserve capacity for operational work such as serious defects, make trade-offs explicit, and communicate why lower-value requests are deferred. I would revisit the sequence regularly as usage data and customer signals change.
I would define the intended user behavior and success metrics before launch, then instrument the critical funnel, feature adoption events, and relevant cohorts. After release, I would compare activation, completion, retention, and error patterns against a baseline, segmenting by customer or user type where appropriate. I would combine those findings with qualitative feedback before deciding whether to iterate, scale, or retire the feature.
I would clarify the underlying problem, urgency, expected outcome, and whether the need is shared by other customers. I would explore simpler configuration, workflow, or process alternatives before committing to bespoke product work. If a custom build is not justified, I would decline clearly and respectfully, explain the trade-off, and offer the most useful viable alternative.
I would establish a clear incident owner and communication channel, assess severity and customer impact, and ensure the engineering team has the context and space needed to restore service. I would keep affected stakeholders informed with concise, fact-based updates and track decisions, mitigation, and follow-up actions. After resolution, I would facilitate root-cause review, assign preventative actions, and verify that they are completed.
I start by identifying the user problem, desired outcome, constraints, and evidence behind the request. I write a concise project overview covering scope, non-goals, success metrics, key flows, dependencies, and open questions, then validate it early with engineering and relevant stakeholders. This provides enough clarity to move quickly while preserving room to learn during delivery.
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.
What You’ll Own
You’ll own the week-to-week rhythm that turns engineering into shipped product:
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.
What We’re Looking For
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.
Healthcare experience is a bonus, but not a requirement. EHR integration and working knowledge of health-data standards (HL7, FHIR) especially.
You won’t fit if you need polished process, a heavy spec phase, or a team that loves meetings. We’re ahead of our process.
Why This Role
Two things to know.
One. It’s a delivery role for now, with a clear set of projects to execute on (but prioritize and sequence effectively). You’ll grow into more strategic scope over the next 4-6 months. The immediate brief is to make the engineering team’s product cadence quieter and more predictable.
Two. The team is small and load is high. The hire exists because we need to free senior product time for discovery and strategy on a separate product. You might feel the pressure of that. In return: real customers (millions of lives) and the opportunity to iterate the product in a company-defining direction.
Practical
Level: APM / Mid Product Manager
Location: East Coast USA
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
Upload your resume now
- To unlock remote work opportunities and be discovered by global employers.
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
