Product Lead, Bond OS Platform

About Us

At The Pharmacy Hub , we collaborate with pharmaceutical brands, manufacturers, health brands, telemedicine providers, and healthcare companies to deliver essential products directly to patients. Our expertise allows us to seamlessly distribute pharmaceuticals, medical devices, and other healthcare products to consumers, ensuring greater accessibility and convenience.

Build the operating system for patient-centric care

Bond OS is the platform layer for modern care delivery. It connects structured patient intake, longitudinal patient context, provider review, clinic and admin operations, orders, prescriptions, commerce rails, platform APIs, analytics, support workflows, and applied AI/ML into one coherent system.

Healthcare delivery is usually fragmented: intake in one place, clinical review in another, ordering and prescription status somewhere else, operations in spreadsheets, support in tickets, and analytics after the fact. Bond OS is built to make those flows work together: one patient context, clear workflows for every role, durable platform primitives, and intelligent assistance where it improves speed, quality, and safety.

We are hiring a Product Lead to own the roadmap for Bond OS across product surfaces and platform primitives. This is a senior, hands-on product leadership role for someone who can move between client conversations, patient and provider workflows, technical contracts, data models, operational edge cases, AI/ML release discipline, and crisp execution with engineering and design.

Why this role matters

Bond OS is entering a new chapter. The core platform is live, the product surface area is expanding, and the opportunity is to make the system more unified, more patient-centric, more operationally powerful, and more intelligent.

This role will shape how the platform scales: how intake becomes usable clinical context, how providers and clinic teams move through work, how orders and prescriptions are tracked, how clients understand performance, how APIs and permissions become stronger platform primitives, and how applied AI/ML earns its way into high-consequence workflows.

The mandate is clear: turn a powerful care-delivery platform into a sharper operating system.

What you will lead

Bond OS roadmap

Own the product roadmap across the full platform:

Patient intake, patient portal, and longitudinal patient context

Provider workflows, review queues, clinical decisioning, and safety review

Clinic and admin operations, group management, permissions, and oversight

Orders, prescriptions, catalog, commerce, payments, promotions, and fulfillment handoffs

Platform APIs, integrations, auditability, data contracts, and status models

Analytics for operations, outcomes, quality, and performance

Applied AI/ML across intake, summarization, triage, drafting, operations, and decision-support context

You will set priorities, make tradeoffs, sequence dependencies, and keep the roadmap grounded in client value, patient impact, operational leverage, and engineering reality.

Platform primitives

Define and protect the core primitives of Bond OS: patient, intake, encounter, decision, order, prescription, catalog item, group, role, permission, audit event, status, and AI artifact.

Great product work here makes the platform simpler and more durable. It turns repeated workflows into shared systems, edge cases into explicit states, and client-specific needs into reusable capabilities.

Client and user discovery

Partner directly with clients, providers, clinic/admin teams, operators, support, design, engineering, and leadership. You will watch real workflows, understand where care delivery breaks down, and translate that signal into product decisions.

Discovery should change the roadmap. The goal is not to collect opinions; it is to understand where Bond OS can create measurable leverage for patients, providers, clients, and internal teams.

Applied AI/ML product direction

AI/ML is a first-class part of Bond OS. The first opportunities include assisted intake summarization, missing-data detection, suggested triage priority, provider-facing drafting, operational intelligence, quality analytics, and decision-support context.

You will define which use cases are worth pursuing, what good output means, how model-backed features are evaluated before launch, how humans review or override outputs, how failures are handled, and how performance is monitored after release.

The standard is practical and serious: assistive, evaluated, observable, auditable, human-overseen, and suppressible when confidence or safety conditions are not met.

Product execution and spec quality

Write product specs that engineering and design can execute from. Strong specs should include user goals, role-specific flows, states, API contracts, validation behavior, data requirements, audit/logging needs, i18n requirements, acceptance criteria, rollout plan, and release criteria.

For AI/ML-backed features, specs sho…