Skip to content
Cheiron

Product Manager, Technical (Los Altos)

Los AltosLocation unclear
FullTime · Product
POSTED 16 SEPTVERIFIED 15H AGO
Apply Ask
Role
66 days opentrue age
Posted 16 Sept
CompanyCheiron →
13open roles
Opened · 30d
+0
Closed · 30d
−0
3d of snapshots · 30d window
Market
3,793open · Product
Opened · 7d
+41011% of open
All product
7,885open
All tracked boards · live 21 Nov · n=3,793
Distributed systems

Onsite, Los Altos, CA · Product · Full time · 3–6 years experience

■ Company Overview

Cheiron raised an $11 million seed round led by Menlo Ventures, bringing total funding to $16 million to date, with the backing and strategic support of industry veterans including Moderna co-founder and MIT Institute Professor Robert Langer, former Pfizer Chief Medical Officer Freda Lewis-Hall, Chai Discovery co-founder and CEO Josh Meier, former Starbucks CEO Laxman Narasimhan, and former Apple AI chief John Giannandrea.

Cheiron is building the first AI-native operating system designed to represent an entire drug program as a single connected system. The company’s platform helps biopharma teams represent, reason over, and stress-test the full state of a drug development program, including the claims, evidence, assumptions, risks, decisions, and commitments that determine whether a therapy advances. In less than six months since launch, Cheiron has been adopted by tens of thousands of biopharma professionals and deployed by major drug developers, and is already used by 7 of Korea’s top 10 biopharma companies.

Cheiron is expanding into pharmaceutical CMC (Chemistry, Manufacturing, and Controls) teams. CMC governs how a drug is made, tested, and kept consistent across its entire commercial life. The work involves hundreds of regulatory commitments, post-approval changes, and cross-market submissions. Today it runs on documents, spreadsheets, and institutional memory. Cheiron augments manual workflows with a CMC regulatory-specific intelligence and reasoning layer.

Founded in 2024 by Stanford-trained AI researchers. The team includes leaders with combined decades of experience across pharma and biotech. Headquartered in Los Altos, California. We are building and deploying the product now with rapid expansion into global markets.

■ About the Role

You solve product problems end to end. You go deep into how CMC and regulatory teams actually work and how they use our product: how a manufacturing change moves from the plant through QA and regulatory affairs to a filing in each market, who decides what, and where today’s tools fail them. You keep going until you understand the problem better than the brief that named it, then turn it into real user workflows, engineering-ready specs, and data models, settled on paper before a line of code is written.

CMC is a specialized world with its own regulatory frameworks and its own workflows. You do not need to know it coming in. You’ll learn it first-hand, from the regulations and guidance themselves, from customers’ own trackers and filings, and from the people who do the work, with a life sciences team alongside you who own the regulatory rules and check your reasoning. What matters is that you’re the kind of person who immerses until you can reason from first principles.

You’ll work directly with the founders and the product/design, life sciences, and engineering teams.

We are also hiring an Associate Product Manager, Technical (0–3 years) at https://jobs.ashbyhq.com/cheiron/a8514f9b-17d9-40a0-8674-a07543bb86d0 and Technical Product Management Interns at https://jobs.ashbyhq.com/cheiron/e193c411-f175-480e-a341-72e7131e009a

■ What You'll Do

Go deep on how our users work: talk to customers, read the trackers, SOPs, and filings they work from, and map each workflow step by step across regulatory affairs, QA, and manufacturing before deciding what to build

Know what customers’ existing systems, such as RIM and QMS, already cover and where they stop, and decide what Cheiron adds on top, including when the honest answer is nothing

Turn what you learn into real user workflows (who does each step, what they need to see, what they decide), then break them into components, define relationships and boundaries with the product team and SMEs, and scope what goes into the build

Write numbered feature stories with acceptance criteria, edge cases, and state transitions that an engineer can pick up cold

Design data models and API contracts against the existing schema; identify what to extend, what to refactor, and what to leave alone

Source · CheironFirst seen 2 Nov1 editsOriginal ↗