Manage Clinical is Auditdata's greenfield bet on clinical audiology software — a market that AI is about to reshape, and that has been underserved by modern software for years.
This is the PM role that shapes it.
You'll own the product end-to-end: you define the product, validate it with clinicians, navigate regulatory decisions with specialists at your side, and ship something that genuinely improves how audiologists work.
AI is central to how we're building — not as a feature, but as the foundation.
Real ownership. Real specialists around you. A market that's genuinely ready for something better.
You will report to the VP Product, work as a pair with a Product Owner and coordinate with the PMO on anything that touches the shared platform, so Manage Clinical strengthens the platform rather than forking it.
This is a clinical software role for a strong, AI-fluent SaaS PM — not an AI PM role. AI is the technology shift you're building through, the same way mobile reshaped software a decade ago. The product is what matters.
If you want to own something consequential from v1, with the specialists around you to do it well — we'd like to hear from you.
Product scope and direction:
Define and validate the product scope across the clinical audiology spectrum — from EHR add-in to standalone deployment — and the customer segments each configuration serves (advanced clinics, ENT, cochlear implant programmes, hospitals).
Own the Manage Clinical roadmap end-to-end, including decisions about which capabilities are AI-native, which are AI-assisted, and which are gated by regulatory classification (decisions made with Regulatory Affairs, not alone).
Use modern AI tooling fluently in your own discovery, prototyping, and customer validation work, and bring your Product Owner with you.
Make the case for each major product decision through written artefacts the rest of the organisation can build on.
Customer discovery and validation:
Stay close to the clinical audiology market through constant interaction with clinicians, clinic leaders, hospital partners, and users. Clinical product decisions cannot be made from a desk.
Establish a small number of design partner relationships across the deployment spectrum — at least one EHR add-in partner and one standalone partner — to validate the product as it develops.
Translate clinical reality into product requirements the engineering team can execute against.
Partnership across functions:
Pair with your Product Owner — you own scope and direction, they own backlog and prioritisation. This relationship is the core engine of delivery.
Partner with Regulatory Affairs on medical-device classification and compliance. They own the regulatory track; you own the product decisions that shape it.
Partner with clinical SMEs to stay grounded in clinical reality.
Partner with the AI PM, who leads AI capability work across our portfolio. You bring sharp clinical product context to that partnership; they bring AI craft.
Coordinate with the Senior PM Manage on anything that touches the shared platform — architecturally, operationally, or commercially. You are peers.
How the success looks like in your first year:
Product scope is validated with design partners across the deployment spectrum (EHR add-in and standalone), with written learnings that informed real product decisions.
A v1 roadmap is agreed, prioritised, and in active execution.
Regulatory classification decisions are made — with Regulatory Affairs — for each major capability, with a defensible record of why each decision was taken.
The PM and PO partnership is working fluidly, with a healthy backlog and clear sprint-level execution.
Cross-product synergies with Manage are identified, agreed with the Senior PM Manage, and governed rather than accidental.
You are visibly growing — taking on more clinical depth, more regulatory judgement, more product leadership every quarter.
5+ years in B2B SaaS product management with a track record of shipping real products that customers pay for.
Strong customer-facing product craft: discovery, prototyping, validation, outcome-based roadmapping, clear engineering handoffs.
Strong writing. Roadmaps, product briefs, customer validation write-ups, regulatory decision logs. The role produces as much writing as talking.
AI-fluent in how you work and how you think about product. You use modern AI tooling in your daily craft and have been part of bringing AI features to market — enough to make sound product judgements about what AI can and cannot do, not necessarily enough to qualify as an AI specialist.
Bonus points for:
Clinical software PM background — audiology, ENT, EHR-adjacent, digital health, medtech, or regulated healthcare SaaS. Any of these shorten the ramp considerably.
Working knowledge of medical device software boundaries (what crosses into device classification and what does not), or willingness to learn this fast with Regulatory support.
Experience with clinical data standards (FHIR, HL7), EHR integration patterns, or clinical workflows.
Experience building net-new products on top of an existing platform — the political and architectural craft of shared-platform product work.
A clear personal arc toward clinical software product leadership. This role is designed to grow.
Key traits:
Curious about clinical audiology — actively interested in how clinicians work and how software changes their practice.
Comfortable with structured ambiguity — there are specialists around you, and you are the person making the product decisions.
A strong communicator in writing and in conversation, with the judgement to know which mode fits which moment.