ppAt Medicilio, we're building the bridge from remote patient monitoring to remote patient intelligence — software that doesn't just track healthcare operations, but actively improves clinical decisions and patient outcomes at scale.
/ppWe are a Milan-based company with teams across Italy, building products for Italy's NHS reform (DM77) today and expanding across Europe tomorrow.
/ppYou'll work closely with engineering, design, clinical stakeholders, and operations to solve complex real-world problems in a high-trust environment where ownership matters more than process.
/pullishipping meaningful products that work in clinical environments, /lilibuilding systems that remain trustworthy over time, /lililearning fast and adapting continuously, /liliand enjoying the process of building together.
/li /ulpMilan-based.
Travel required for client and hospital visits across Italy.
/ph3About the role /h3pThis is the Product Lead role for our Centro Servizi domain — our care coordination and operational workflow platform.
This role reports directly to the CPO and is a Critical Q****** hire that unblocks the CS domain structure.
/ppCentro Servizi is Medicilio's operational layer: the platform CS operators use to manage caseloads, resolve alerts, onboard patients, and coordinate care.
It is being built for multi-CS architecture at regional scale — integrating with external telephony and workforce management systems, and eventually serving as the operational brain for distributed care networks.
/ppYou will own the CS product domain end-to-end — roadmap, discovery, specification, quality, and stakeholder alignment.
You partner directly with the CS Engineering Lead and Design, and engage daily with clinical operations teams (CS, nursing, care coordination).
/ppThis role starts in CS.
As the product matures and the team grows, the Product Lead scope expands.
/ph3What you'll do /h3h3Own the domain /h3ulliDefine and maintain the CS domain roadmap — priorities, trade-offs, and sequencing decisions /liliBe the single point of accountability for what ships and why it matters /liliTranslate business strategy and clinical requirements into product decisions /liliResolve conflicts between domain needs and platform-wide coherence /liliPartner with the Engineering Lead on technical trade-offs and delivery planning /li /ulh3Run discovery and specification with AI in the loop /h3ulliUse agentic workflows to run user research synthesis, competitive benchmarking,

and requirements structuring — faster and more rigorously than manually /liliProduce specs that are clear enough for both human engineers and AI-assisted build pipelines to act on without ambiguity /liliGenerate and review AI-generated outputs (specs, designs, prototypes) with the critical eye of someone who knows the domain deeply — you define intent, AI generates the first cut, you validate and own it /liliDesign for probabilistic systems: know how to define success criteria when the output isn't binary /liliSet evaluation frameworks for AI-assisted features: offline metrics, edge?case coverage, and feedback loop design /li /ulpExample: CS had a queue management tool used inconsistently across operators.
Ran a structured AI?assisted synthesis of CS team feedback, identified three root?cause patterns, and produced a spec that resolved all three in a single UX redesign — delivered to engineering in 48 hours with no ambiguity.
/ph3Be the quality gate, not the bottleneck /h3ulliOwn feature testing for your domain — you verify what ships meets the original intent /liliCoordinate with the QA Coordinator on regression risk and release readiness /liliMaintain documentation as a living system — use AI to generate, your judgment to validate /li /ulh3Navigate a regulated, clinically sensitive context /h3ulliUnderstand the MDR boundary — know which features touch regulated territory and which don't, and act accordingly /liliWork closely with compliance and cybersecurity functions before design freeze on any sensitive feature /liliEngage with clinical users directly — not just through data /liliWrite product requirements that would survive a regulatory audit, not just a sprint review /li /ulpExample: A new alert escalation feature touched both clinical workflow and patient data access.
Flagged the MDR boundary before the sprint started, aligned with compliance on what required documentation, and shipped with a clear audit trail — without delaying the release.
/ph3How we work /h3pWe operate in small, high-trust teams with strong ownership and minimal process overhead.
/ph3A typical week for the CS Product Lead includes /h3ullishaping and scoping upcoming work with Engineering and Design /lilidirect engagement with CS operators, clinical coordinators, and hospital clients /liligenerating and reviewing product specs, prototypes,

and decision documents /lilirunning or reviewing QA on features in your domain /lilialigning with the CPO on roadmap priorities and cross-domain coherence /li /ulpWe optimize for: /pulliclarity over process theater /liliownership over handoffs /lilifast iteration with high clinical standards /lilicontinuous improvement of how we build /li /ulh3What we're looking for /h3h3Must-haves /h3ulli4+ years of product management experience with demonstrated domain ownership /liliAI tool fluency — daily use in a real product context, not theory /liliSystems thinking — you see the whole, not just the ticket /liliStrong written communication — specs, decisions, and rationale that hold up under review /liliProbabilistic reasoning — you can define success when the output isn't binary /liliCross?functional collaboration across product, engineering, design, and clinical /liliFeature testing ownership — you verify what ships /li /ulh3Nice?to?haves /h3ulliDigital health or regulated software background /liliExperience with care coordination, clinical operations, or CS/CRM platform design /liliSQL or basic data fluency /liliExperience with agentic workflow design or AI?assisted product development /li /ulh3Skills that matter most in the AI era /h3pAs AI handles more of the documentation, synthesis, and generation work, the most valuable product leadership skills become: /pullijudgment over output /lilisystem?level thinking over feature?level thinking /liliclinical and regulatory domain depth /liliquality ownership across the full lifecycle /lilithe ability to define what "good" looks like — and hold it /li /ulh3Compensation /h3pTop of band for Product Leads with demonstrated domain ownership, clinical context depth, and AI?assisted workflow fluency.
/ppEquity is part of the package, with allocation and vesting discussed openly at offer stage.
/ph3Location /h3pMilan-based.
Travel required for client, hospital, and team visits across Italy.
/ph3Our values /h3h3Trust /h3pWe communicate directly, keep our word, and operate with high autonomy.
Trust increases speed by reducing unnecessary process.
/ph3Care /h3pWe care about the people we work with and the problems we solve.
We give honest feedback, support each other, and create space to learn from mistakes.
/ph3Curiosity /h3pWe stay open, ask questions, and continuously learn from systems, users, and each other.
/ph3Expansion /h3pWe take on ambitious problems and grow through them.
We value progress over perfection.
/ph3Joy /h3pWe build serious systems without losing enjoyment in the process.
Strong morale improves both outcomes and quality of work.
/p /p #J-*****-Ljbffr

Product Management Lead - Centro Servizi | Ref. 86Ca51Urq

Macchinista 1° Agente

Progettista elettrico

Ricevi nuove offerte di lavoro

RESPONSABILE QHSE | Qualità, Sicurezza e Ambiente

Automation Engineer