Product Builder

Position Summary The Product Builder owns a feature from technical kickoff through merged, released code. Working from a validated problem, prototype, and specification produced by Product and Design, the Product Builder designs the system, plans the implementation, and directs AI coding agents to produce the code - then carries accountability for its correctness, security, and long-term maintainability.

This role is defined by ownership of a complete feature. Product Builders produce architecture, contracts, program design, and verified working software. The primary means of producing code is the direction and review of AI agents, which makes judgment, system design decisions, and rigorous review the central skills of the role.

Product Builders work on an applications platform maintained by the Application Platform Architect, and against data contracts and standards owned by the Data Platform Architect.

What You Own Feature architecture. System design, component and feature contracts, data model, endpoint and API design, and the constraints and requirements the feature must satisfy.

Program design. Test approaches and seams, program layout and call stacks, component trees and dependencies — defined before implementation begins, because agents build from the plan you write. There can be crossover here with the Application Platform Architect making for collaborative opportunities with that role.

Vertical slices. Implementation order, the multi-repository coordination map, and incremental pull requests linked to their tracked issues. You decide how the work is sequenced and how the agent is orchestrated to build it.

Agent orchestration. Translating architecture and program design into effective agent tasking; evaluating agent output critically; recognizing when generated code is plausible but wrong, subtly unsafe, or architecturally inconsistent. Keeping your agent orchestration flow up to date, effective and efficient for the product(s) you work on and own.

Pull request quality. Agentic code review, CI/CD checks, unit tests, and security and SAST scans. Human review of the evolving codebase and validation that the implementation matches the intended architecture.

Release readiness. Shared accountability with Product, Design, and Leadership that a feature is ready to go to the field.

What You Participate In Technical kickoff. You join the walkthrough of problem, outcomes, prototype, and constraints, and you are expected to surface technical risk early - before architecture begins - rather than discovering it mid-implementation. Collaboration with the Product team is essential throughout product building and starts here.

Cross-functional review. You work directly with Design on QA against the prototype, with Product on AI evaluation results and scope drift, and with the platform architects when a feature requires a capability or data contract that does not yet exist.

What You Do Not Own Problem framing, success metrics, research, prioritization, and the product specification are owned by Product, Design, and Leadership. The shared repositories, CI/CD pipeline, and data platform are owned by the platform architects. Product Builders influence all of these and are expected to push back when something is wrong - but the decisions rest elsewhere.

Required Qualifications Bachelor's degree in Computer Science or a related field, or equivalent practical experience

Experience building and shipping production software

Demonstrated ability to design a system - not just implement one - including data modeling, API design, and defining contracts between components

Strong code review skills, with the judgment to identify correctness, security, and maintainability problems in code you did not write

Working knowledge of automated testing strategy: what to test, where the seams are, and what adequate coverage looks like Familiarity with CI/CD pipelines, version control workflows, and secure development practices including static analysis and dependency scanning

Ability to decompose a feature into incremental, independently reviewable slices

Clear written and verbal communication with non-engineering partners, including Product, Design, and clinical stakeholders

Ability to work with protected health information in accordance with HIPAA and internal data governance requirements

Preferred Qualifications Experience directing AI coding agents or working extensively with AI-assisted development tooling

Experience in healthcare technology, particularly home…