NL · 2026 / Luscii · OMRON Healthcare / Senior Product Manager

Roy Pereira

Senior Product Manager shipping a CE-marked medical device used by patients managing chronic conditions at home. The connector between people and possibilities — building digital health with empathy at scale.

01
—
WHO

I help digital health teams ship things patients actually trust. Empathy first, then the roadmap.

01 · DOMAIN

Digital health

Remote patient monitoring, chronic-condition care, MDR-regulated software as a medical device.

02 · CRAFT

Product & UX

iOS HIG, Material 3, Liquid Glass. A PM who prototypes in Figma and reads the codebase.

03 · SUPERPOWER

Connecting people, across cultures

Coordinate product across teams in India, Japan, US, Mexico & NL. Async-first written discipline, cultural calibration, the patience to know a "yes" isn't always a yes.

02
—
PROOF

Each strength, one line of evidence. No fluff.

→ 01

AI-native operatingSignature

Claude Code daily — for UX prototypes, PRDs, iOS debugging, multi-agent automation. The work that used to take a PM, an engineer, and a designer two weeks now takes me a day.

↗
→ 02

Delivery & executionSignature

Shipped a multi-agent Linear triage and RCA pipeline on GitHub Actions — polls 14 teams every 15 minutes, classifies tickets, posts code-level root-cause analysis straight onto the ticket.

↗
→ 03

Roadmap & prioritizationSignature

Helped take a CE-marked SaMD from monthly to weekly releases — coordinating a single iOS/Android codebase across 5 product teams under MDR. Used by ~70% of Dutch hospitals.

↗
→ 04

Stakeholder managementSignature

Authored the shared release process aligning developers, testers, designers and POs across 5 teams — the doc people link to in Slack when there's ambiguity. Now onboarding for every new hire.

↗
→ 05

Cross-cultural coordinationSignature

Ship product across teams in India, Japan, US, Mexico & NL. Async-first written discipline, cultural calibration, and the patience to know a "yes" isn't always a yes.

↗
→ 06

Agile transformationSignature

Co-led a 100+ engineer org from chapter-based Scrum to Team Topologies value streams running flow-based Kanban — and took the release cadence from monthly to weekly on a CE-marked SaMD.

↗
→ 07

Technical fluencySolid · growing

Full-stack and iOS background — Swift, React/Node, SQL, CI/CD. A PM who reads the code, prototypes screens, and ships PRs alongside engineers.

↗
→ 08

Product strategy & visionSolid · growing

Reframed onboarding for OMRON Connect's "continue without account" path — benefit-first UX writing that respected privacy, drafted in Claude, refined in Figma.

↗
→ 09

Healthcare domainSolid · growing

Shipping MDR-compliant SaMD across 150+ conditions, 11 countries, and 25M+ patient registrations. Fluent in RPM, chronic-condition care, clinician-patient handoff.

↗
→ 10

Discovery & user researchSolid · growing

Audited OMRON Connect data flows from the patient's perspective to surface privacy decisions worth raising in-app.

↗
→ 11

Data & analyticsSupporting

Firebase, Mixpanel, BigQuery as a working PM toolkit — instrumenting and querying flows directly, not waiting on handoffs.

↗

03
—
STACK

A typical day, re-tooled.

I work with Claude Code daily. PRDs that took half a day take an hour. Screens that needed a designer's queue ship the same morning. iOS bugs get triaged before standup. The PM workflow rebuilt around a tool that compounds.

→ Morning

Draft PRDs & specs

Claude Code · Notion · Linear

→ Midday

Prototype UX flows

Claude · Figma · iOS HIG

→ Afternoon

Debug & ship code

Claude Code · Xcode · Swift

→ Evening

Run automations

Claude · GitHub Actions · BigQuery

→ Always

Read the codebase

Claude Code · GitHub · grep, like an engineer

→ Always

Talk to patients

Voice · transcript → Claude for synthesis

Most PMs spent 2025 writing PRDs about AI features. I spent 2025 operating with AI — and the output looks different.

04
—
METHOD

Every cycle earns the next.

A patient interview reframes the problem. Shared understanding aligns five teams. A prototype turns the insight tangible. The ship improves an outcome.

And the trust earned by shipping something useful opens the next conversation — deeper than the last. That's empathy at scale.

05
—
WORK

Four things I built recently. All shipped.

Case · 01 — automation

  ┌───────────┐
  │ 14 teams  │
  └───────────┘
        │
        ▼
     triage
        │
        ▼
      route
        │
        ▼
       RCA
        │
        ▼
  ┌───────────┐
  │   ✓ PR    │
  └───────────┘

Linear triage & RCA pipeline

Multi-agent system that polls Linear every 15 minutes, classifies tickets, routes them to the right of 14 teams, and posts code-level root-cause analysis straight onto the ticket.

GH Actions·Claude·Octokit

→ shipped

Case · 02 — process

  T1   T2   T3   T4   T5
   │    │    │    │    │
   └────┴──┬─┴────┴────┘
          ▼
       main
          │
          ▼
      qa build
          │
          ▼
     staging
          │
          ▼
      RELEASE
          │
          ▼
      ┌───────┐
      │ MDR ✓ │
      └───────┘

5-team release process for a CE-marked SaMD

Authored the source-of-truth release doc coordinating 5 product teams on a single iOS/Android codebase — the playbook that lets us ship weekly (from monthly) under full MDR compliance. The doc people link to in Slack when there's ambiguity.

Process·MDR·Scrum

→ shipped

Case · 03 — AI tooling

  crashlytics
       │
       ▼
   ┌───────┐
   │BigQry │
   └───────┘
       │
       ▼
   claude -p
       │
       ▼
   ┌───────┐
   │Linear │
   │ticket │
   └───────┘

Crashlytics investigation pipeline

Daily headless Claude run that pulls new fatal crashes from BigQuery, reads the iOS codebase, and files a draft Linear ticket with a proposed fix — before anyone's even at their desk.

BigQuery·Claude Code·Swift

→ shipped

Case · 04 — transformation

  ┌──────────┐
  │ chapters │
  │ ┌─┬─┬─┐  │
  │ │C│C│C│  │
  │ └─┴─┴─┘  │
  │  scrum   │
  │ monthly  │
  └──────────┘
       │
       ▼
   100+ eng
       │
       ▼
  ┌──────────┐
  │  value   │
  │ streams  │
  │ ┌──────┐ │
  │ │  T1  │ │
  │ │  T2  │ │
  │ │  T3  │ │
  │ └──────┘ │
  │  kanban  │
  │ weekly   │
  └──────────┘

Agile transformation, 100+ engineers

Co-led a global engineering org from chapter-based Scrum to Team Topologies value streams running flow-based Kanban. Outcome that stuck: release cadence went from monthly to weekly on the CE-marked app.

Team Topologies·Kanban·Org design

→ shipped

❝

Master in agile transformation and experienced product manager.

— Reference · former colleague

06
—
HELLO

Let's build something that matters.

Connect on LinkedIn /in/rpereira ↗ Send a message roy@pereira.nl ↗ Download as PDF this page · 644 KB ↓