How I Think About Healthcare Product Management

The Core Difference: Compliance, Operations, and Lives

Three years building telehealth platforms taught me that healthcare PM requires a fundamentally different mindset than consumer tech. Here's why:

1. Compliance Isn't a Checkbox—It's a Design Constraint

Most product managers treat compliance as something you bolt on after building features. In healthcare, that approach fails spectacularly.

• <strong>HIPAA isn't optional:</strong> Every feature touching patient data needs encryption, audit logging, and access controls from day one. You can't retrofit security.
• <strong>State pharmacy boards have real authority:</strong> When you're processing prescriptions across 48 states, each state's pharmacy board can shut you down if you violate their rules.
• <strong>SOC 2 compliance takes 6+ months:</strong> Enterprise healthcare clients won't sign contracts until you're certified. This isn't a feature—it's a business requirement.

At Teligant, we built HIPAA compliance into our architecture from the beginning. Cross-tenant data isolation, explicit consent workflows for data transfer, and comprehensive audit logging weren't features we added—they were foundational design decisions that enabled everything else.

2. Operational Workflows Matter More Than Features

The prescription routing workflow I built at Teligant was more valuable than any fancy AI feature. Here's why:

If any step fails, the patient doesn't get their medication. No amount of beautiful UI compensates for broken operational workflows. We achieved zero prescription routing errors across 200+ monthly prescriptions because we obsessed over the operational reality, not just the feature list.

3. Technical Depth Enables Better Product Decisions

My engineering background isn't a nice-to-have—it's the reason I can make good product decisions in healthcare. Here's what technical depth enables:

• <strong>Reading API documentation:</strong> When integrating DoseSpot or PayTheory, I don't wait for engineers to tell me what's possible. I read the docs, test the endpoints in Postman, and map the data model myself.
• <strong>Writing implementable specs:</strong> Engineers don't come back with 10 clarifying questions because I understand data models, edge cases, and technical constraints. I write the JSON schema before I write the user story.
• <strong>Debugging production issues:</strong> When lab results aren't syncing, I can read the server logs, trace the webhook failure, and identify the root cause (e.g., a missing patient_id in the payload).
• <strong>Realistic timelines:</strong> I know the difference between 'change a config' (1 hour) and 'rebuild data architecture' (2 weeks) because I understand the underlying code.

My Core Principles

After teaching 170+ students, engineering at Rugiet, building frameworks at CompoundLive, and co-leading product at Teligant, these are the principles that guide my approach:

What I'm Looking For

Three years in telehealth taught me that healthcare technology is one of the few domains where product decisions have measurable real-world impact. When you ship a prescription routing workflow that enables 48-state fulfillment with zero errors, that's not just a metric—it's real patients receiving care.

I'm seeking senior product roles where I can:

• Apply healthcare domain expertise and technical depth to complex product challenges
• Build 0-1 products or scale existing platforms in B2B healthcare SaaS
• Work with cross-functional teams where compliance, operations, and engineering intersect
• Contribute to organizations where product excellence directly improves patient outcomes

Ideal fit: Series A-C health tech startups, B2B healthcare SaaS companies, telehealth platforms, or digital health infrastructure where technical PMs drive strategy.