Product Management Lead

4 giorni fa

monzabrianza, lombardia, Italia Medicilio Tempo pieno

About Medicilio

 

At 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.

 

We are a Milan-based company with teams across Italy, building products for Italy’s NHS reform (DM77) today and expanding across Europe tomorrow.

 

You’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.

 

We care about:

 

  • shipping meaningful products that work in clinical environments,
  • building systems that remain trustworthy over time,
  • learning fast and adapting continuously,
  • and enjoying the process of building together.

 

Milan-based. Travel required for client and hospital visits across Italy.

 


About the role

 

This 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 Q3 2026 hire that unblocks the CS domain structure.

 

Centro 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.

 

You 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).

 

This role starts in CS. As the product matures and the team grows, the Product Lead scope expands.

 


What you’ll do

 

Own the domain

 

  • Define and maintain the CS domain roadmap — priorities, trade-offs, and sequencing decisions
  • Be the single point of accountability for what ships and why it matters
  • Translate business strategy and clinical requirements into product decisions
  • Resolve conflicts between domain needs and platform-wide coherence
  • Partner with the Engineering Lead on technical trade-offs and delivery planning

 

Run discovery and specification with AI in the loop

 

  • Use agentic workflows to run user research synthesis, competitive benchmarking, and requirements structuring — faster and more rigorously than manually
  • Produce specs that are clear enough for both human engineers and AI-assisted build pipelines to act on without ambiguity
  • Generate 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
  • Design for probabilistic systems: know how to define success criteria when the output isn’t binary
  • Set evaluation frameworks for AI-assisted features: offline metrics, edge-case coverage, and feedback loop design

 

Example: 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.

 

Be the quality gate, not the bottleneck

 

  • Own feature testing for your domain — you verify what ships meets the original intent
  • Coordinate with the QA Coordinator on regression risk and release readiness
  • Maintain documentation as a living system — use AI to generate, your judgment to validate

 

Navigate a regulated, clinically sensitive context

 

  • Understand the MDR boundary — know which features touch regulated territory and which don’t, and act accordingly
  • Work closely with compliance and cybersecurity functions before design freeze on any sensitive feature
  • Engage with clinical users directly — not just through data
  • Write product requirements that would survive a regulatory audit, not just a sprint review

 

Example: 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.

 


How we work

 

We operate in small, high-trust teams with s