Product Associate, Waymark

• Two or more years in a product management role shipping software used by non-technical operational or clinical staff, with at least one product you owned from discovery through launch and outcomes measurement
• Strong written communication. Your specifications, acceptance criteria, and decision documents are clear enough that engineers and designers design, build, and validate the right thing without a meeting
• Practical fluency with agile delivery — refinement, estimation, sprint cadence, flow and cycle-time metrics — and the judgment to know which ceremonies are earning their cost
• Comfort with quantitative evaluation: you define success metrics before launch, read an instrumented result honestly, and change course when the data says so
• A humble learner who seeks out the perspectives of care team members and welcomes challenges to your own conclusions, and who thrives in a fast-paced environment where scope is set rather than received
• An excellent cross-functional collaborator — you build trusted working relationships with product design, engineering, and data science, and move comfortably between writing a spec, reviewing a Figma file, and triaging a bug
• Operate with a self-starter, scrappy mentality — pick up ambiguous problems and move work forward without waiting for a heavy process or a fully-staffed team
• Don’t check off every box in the requirements listed above? Please apply anyway!

Desirable

• Your primary product to manage will be Lighthouse, the platform our care teams use every day to find, reach, and care for Medicaid members
• Today Lighthouse records care after it happens
• Over the next eighteen months you will help it become a place where care is delivered: a member texts a symptom, agentic models draft a structured history and assessment, a licensed clinician reviews the treatment plan and approves pended orders, and Lighthouse executes the resulting prescription, laboratory order, or referral — then documents the encounter, submits the claim, and updates the health information exchange
• Alongside that build, you'll keep shipping the improvements care teams depend on right now — panel management nudges, clinical history context, task and goal automation from outreach and preventative care campaigns, and the steady stream of feature work that keeps a growing patient-facing care team maximally effective
• That is a large surface, and you will need to develop specifications for it
• You will spend real time with operations leaders directing the care team; you will decide how their needs will translate into building; and you will write the specifications, acceptance criteria, and measurement plans that let a growing engineering team move quickly without guessing
• You’ll collaborate closely with a cross-functional team spanning product design, engineering, and data science
• You’ll partner with design on user research, shaping user flows, and reviewing prototypes; with engineering on technical feasibility, implementation, and QA; and with data scientists to turn powerful predictive models into useful, actionable experiences for care team members
• Waymark is a small, fast-moving team, so you should expect to be a self-starter and get hands-on rather than wait for a fully-formed brief
• You will report to the VP of Product and work as part of a small Product and Design organization and larger Clinical Product Development department
• In eighteen months, success looks like this: Lighthouse supports safe clinical triage with human-in-the-loop approvals, our predictive models reach care teams as pre-drafted work rather than notifications, and our engineers ship against a backlog they trust
• Own the Lighthouse product backlog end to end — problem framing, written specifications, acceptance criteria, sequencing, QA, and release readiness — spanning both new clinical/agentic capabilities and the ongoing feature enhancements care teams rely on day to day
• Partner daily with the Lighthouse engineering and design pod — run project kickoffs, scope refinement, sprint planning, and delivery plan; keep a refined backlog at least two sprints deep; hold the definition of ready and definition of done
• Partner with cross-product PMs to specify how predictive model outputs and drafted agentic actions surface inside Lighthouse — which decision each score informs, how work is ordered and rate-limited, and where a human reviews and confirms before any action is taken
• Maintain a continuous discovery practice: a weekly cadence of structured contact with product, design, engineering and operations team members, an opportunity map for Lighthouse, and prioritized, testable bets rather than a feature request queue
• Define and instrument outcome metrics before each launch, weighted toward completed clinical actions and reduced care-team workload rather than volume of suggestions produced, and run the post-launch read-out
• Coordinate clinical safety review, compliance, and partner readiness across Compliance, Security and Legal teams for each major feature release