Senior Product Manager, AI Infrastructure

Job description

Senior Product Manager, Infrastructure, Scaling & Core Workflow Primitives

Transform healthcare with us.

At Qualified Health, we're redefining what's possible with Generative AI in healthcare. Our infrastructure provides the guardrails for safe AI governance, healthcare-specific agent creation, and real-time algorithm monitoring, working alongside leading health systems to drive real change.

This is more than just a job. It's an opportunity to build the future of AI in healthcare, solve complex challenges, and make a lasting impact on patient care. If you're ambitious, innovative, and ready to move fast, we'd love to have you on board.

Job Summary

Qualified Health is seeking a Senior Product Manager to own how the platform compounds: the core workflow primitives that every product is assembled from, the builder tools that let teams create assistants, abstractors, and workflows, and the scaling discipline that turns one-off builds into products that generalize. Builder tools are the velocity engine of our platform. This role makes the engine compound: a component built once for one application becomes a primitive available to every application after it.

This is a three-prong role. First, identify and productize the scalable primitives: the triggers, ingestion patterns, extraction steps, review gates, and serving patterns that recur across products, so they are built once, versioned, and reused everywhere. Second, make sure products ship scalable, not as one-offs: generalization requirements are set before build, and the second customer costs a fraction of the first. Third, drive the builder tools themselves: the roadmap for Workflow Factory and its sibling builders, and the runtime underneath them, including registries, config-driven backends, and the path from a built workflow to production.

You are not the infrastructure owner. Engineering owns the runtime, the architecture, and their technical decisions. You are the scalability partner: the person who has written down what must generalize, who catches the one-off before it ships, and who owns the product definition of the primitives and the tools that assemble them.

Your success is measured by reuse. If the second product built on a primitive takes as long as the first, the role has failed.

You will sit on the Platform pod, reporting to the SVP of Product, and partner daily with engineering leadership, the Workflow Factory team, the data and analytics product manager, and peer product managers.

What You Will Own

You own products, catalogs, and requirements. Engineering owns the domains.

Core workflow primitives as a product: The catalog of shared components that workflows, assistants, and abstractors are assembled from. Each primitive is defined once, versioned, discoverable, and stable enough that engineering can refactor underneath without breaking the products built on top. You own what exists in the catalog, its interfaces, and its adoption.

The promotion path from one-off to primitive: The intake, criteria, and process for when a component built for one application gets promoted into the shared catalog, who migrates to it, and how deprecation works. Pattern recognition across products is the core skill of this role.

Builder tools: The co‑own product roadmap for Workflow Factory, Assistant Builder, and Abstractor Builder: what builders can create, what guardrails apply, and what it takes to go from built to deployed in production.

The builder tools runtime as a product surface: Registries, config-driven backends, and the pipeline that ships a built workflow to production, including automated review gates. Engineering owns the implementation; you own the requirements, the interfaces, and the roadmap.

Scalability and generalization requirements: The non‑negotiables written before any new product build starts: multi‑tenancy, configuration over code, performance at full population scale, and reuse of existing primitives. You partner with infrastructure engineering to make these real; you do not let a bespoke build reach a second customer.

Key Responsibilities

Own the roadmap for builder tools and core primitives, balancing customer commitments, internal builder needs, and platform reuse

Build and maintain the primitive catalog: what exists, its interface, its version, and who consumes it

Define and run the promotion process that turns per‑customer builds into reusable platform components with clear interfaces

Set generalization and scalability requirements at the start of every new product build, and enforce them at review gates

#J-18808-Ljbffr

Worksite address

palo alto, CA, 94306, US

Who can apply

Review the original listing for work authorization, qualifications and employer requirements.