Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Senior Clinical Product Lead | 100% Remote within Europe
Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.
- Remote from
- Europe
- Salary
- Undisclosed
- Department
- Healthcare & Medical
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 31 Oct 2026
- Listing views
- 161
- Application actions
- 8
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
The role, at a glance.
Docplanner is seeking a physician with digital-health product experience to lead the clinical-product direction and quality standards for Noa's AI products. The role translates real clinician workflows, peer feedback, and clinical judgment into product roadmaps, model evaluations, and safety thresholds. It partners closely with Product, AI/ML, Design, Engineering, Regulatory, and a clinician network, including alignment with EU MDR-related requirements. The lead will review AI outputs and clinical workflows, identify failure modes, and establish scalable clinical evaluation processes. This is a senior individual-contributor role with substantial influence over safe, trusted clinical AI used by doctors.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
5/5Autonomy Level
5/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 begin by defining the product's intended use, user population, clinical context, and unacceptable harm scenarios. I would translate these into measurable quality dimensions such as factual accuracy, completeness, relevance, uncertainty handling, safety escalation, and workflow usability. I would then build representative evaluation sets, define specialty-specific thresholds, establish clinician review processes, and use post-launch feedback to continuously monitor performance.
I would use peer-to-peer interviews and workflow observation to understand the underlying job to be done rather than treating individual requests as requirements. I would synthesize recurring themes by user segment, specialty, frequency, clinical risk, and expected workflow impact. I would then partner with Product to prioritize opportunities using evidence, expected adoption, safety implications, and technical feasibility.
I would classify the failure mode, assess severity and likelihood, and determine whether it stems from prompting, retrieval, workflow design, model limitations, or missing guardrails. The immediate response could include blocking the output, adding uncertainty or escalation logic, narrowing intended use, and updating evaluation tests. I would ensure the case becomes a regression test and communicate the risk and mitigation clearly to clinical, technical, and regulatory stakeholders.
I would involve Regulatory early when defining intended use, claims, clinical evidence, risk controls, and change-management expectations. Clear documentation and shared decision criteria allow teams to identify what requires formal assessment before implementation rather than reviewing only at the end. This creates practical guardrails that let product teams move quickly within an agreed safe operating boundary.
I would combine qualitative and quantitative evidence. Qualitatively, I would interview clinicians about usefulness, clarity, perceived safety, and where the tool fits or disrupts their workflow; quantitatively, I would track activation, repeat use, completion, edits or overrides, escalation behavior, and outcome-quality measures. I would segment findings by specialty and setting, then iterate on the workflow and evidence presentation based on the highest-impact barriers.
About this role.
About Docplanner and Noa
Docplanner is a global healthcare platform connecting more than 300,000 doctors with approximately 100 million patients every month across 13 markets.
Within Docplanner, Noa is on a mission to help people live longer, healthier lives. We build AI that works alongside doctors to:
Remove their administrative work.
Help them make better decisions and handle repeatable cases, so they can spend their time where it matters most.
Help patients navigate healthcare using their medical history as personalized context.
We’re already in doctors’ hands: Noa Notes takes documentation off their plates, while Noa Evidence brings trustworthy medical evidence to the point of care.
The next frontier is the hardest—and the most valuable: helping doctors, and eventually patients, make decisions while our AI safely takes on repeatable clinical work. That’s where a doctor’s judgment has to live inside the product itself. That’s this role.
About the role
You’ll help take Noa from writing notes and providing evidence to helping doctors decide—and make sure that doctors and users trust it.
This isn’t a traditional CMO, advisory or regulatory role. It’s a hands-on clinical-product role: the clinician–product–AI. You’ll do two things:
Help decide what we build for doctors by bringing their real needs, habits and workflows into the product.
Define the clinical quality of what we ship: what’s correct, useful and safe, and make sure we can prove it.
Because you’re a doctor yourself, you can talk to our users peer-to-peer and get the honest answers a survey never will. As our first dedicated clinical hire on the product, you’ll set the approach, then help grow clinical expertise across Docplanner’s AI product teams.
You’ll work day-to-day with Product, AI, Design, Engineering, Regulatory and our doctor network.
What you’ll do
Shape what we build
Bring how doctors really work (habits, preferences, workflow, admin) into the product.
Talk to doctors, doctor-to-doctor, and turn candid feedback into product decisions.
Partner with Product on the roadmap: what to build and what will actually get used.
Make sure it’s clinically sound
Define the clinical quality bar and intended outcomes for our AI products.
Review and improve prompts, model outputs, clinical templates, workflows and terminology.
Spot clinical failure modes: what good and unacceptable outputs look like.
Direct clinical evaluation: decide what to test, in what mix (specialty, population, complexity and edge cases), and set the bar. You’ll bootstrap this with a dedicated owner who runs the process, tooling and annotation guidelines for doctors, while our clinical network performs the annotation.
Turn model errors and clinician feedback into concrete product and model improvements.
Keep it safe and scalable
Work with ML/LLM teams, Regulatory experts and the PRRC to keep intent, evidence, risks and controls aligned, including EU MDR-related and similar requirements.
Build feedback loops with practising clinicians and our consultant-doctor network.
Define how clinical-product expertise scales across future products, teams and markets.
What we’re looking for
A medical degree and meaningful experience practising medicine, with a strong understanding of clinicians’ day-to-day work. Active licensure and current clinical practice are not required, although recent or ongoing practice is valuable.
You’ve helped build and ship a digital health, clinical software or AI product—either within a product team or through meaningful entrepreneurial experience.
You’ve turned clinical problems into product decisions, not just provided advice or review.
Strong clinical judgment: you turn quality and safety into standards technical teams can use.
You win doctors’ trust quickly—you are the peer who gets the honest answer.
You communicate clearly and directly across clinical, product, technical, regulatory and leadership teams.
You’re comfortable working at a senior, hands-on level in a fast-moving, international team.
You actively use generative AI and understand its potential and limitations. Hands-on experience with prompting, evaluation, error analysis, human oversight or AI-assisted development tools such as Cursor and Claude Code is a plus.
Bonus: experience with ambient documentation, clinical templates, medical-knowledge systems, clinical coding, evaluation datasets or building and certifying regulated Software as a Medical Device (SaMD).
What success looks like after six months
A clear clinical quality framework for our priority AI products.
Clinically grounded evaluation sets and thresholds in place.
A repeatable way to turn medical expertise into better product and model decisions.
Why join Noa at Docplanner
Real impact at real scale: Your work reaches hundreds of thousands of doctors and their patients.
Shape what comes next: You’ll influence what Noa and Docplanner’s AI products become—and whether doctors and patients trust them.
Ship to learn: A feature in front of users beats another month of planning.
Work flexibly: The role is 100% remote within Poland or Spain, with the team coming together regularly.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
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.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
