Clinical Product Builder

Nest Health

11d•Remote

About The Position

Nest Health is hiring a Clinical Product Builder to own the clinician-facing product experience across the tools clinicians use during their workday, including athenaOne and the clinician surface Nest is building. The role spans strategic EHR configuration, product design and hands-on building, and the clinical side of migrating workflows from Salesforce. The builder will work directly with clinicians and engineers, using clinical judgment to distinguish workflow, training, and content problems and to turn clinician needs into working solutions. The position is not solely an Athena administration, traditional product management, engineering, or patient-care role. The hire will build prototypes, tools, pipelines, or automations and a meaningful share of the clinician application, while product engineers own the underlying production systems. Clinical safety, PHI, and documentation requirements must remain central to design decisions. Nest is a fast-paced startup where roles can be broad and changing, and employees are expected to be autonomous, flexible, accountable, collaborative, and comfortable communicating and learning asynchronously. The company is remote, and many decisions are made in writing.

Requirements

Clinical training such as RN, NP, PA, LCSW, or similar, or at least 3 years of clinical informatics work directly alongside clinicians.
At least 3 years across clinical informatics, EHR build, or clinical product management, including hands-on building of templates, order sets, or documentation workflows.
Fluency in SQL and ability to reason about clinical data, including encounters, problems, orders, claims, and discrepancies among them.
At least one real project built with an agentic coding tool such as Claude Code, Cursor, or a similar tool, whether at work or independently; a prototype that helped engineers understand what to build qualifies.
Clear writing; the role is remote and most decisions are made in writing.
Ability to distinguish a requested feature from the underlying problem and explain design tradeoffs to clinicians and engineers.
Understanding of how PHI, clinical safety, and documentation requirements affect product design, with willingness to maintain rigor under timeline pressure.
Willingness to communicate directly with clinicians, including after visits and sometimes in the passenger seat.
Submit an example of something built, or, if all work is proprietary, a two- or three-paragraph written critique of a familiar clinical workflow and how it should be improved.

Nice To Haves

athenaOne experience.
FHIR/HL7 interoperability experience.
Value-based care experience, including quality measures or outcomes measurement.
Home-based or complex care experience.
A clinical build such as a template or workflow, or a teardown of an EHR flow, to share in addition to the required work sample.

Responsibilities

Own the clinician's overall workday experience across the tools used between the car and patients' homes.
Design, build, and retire athenaOne encounter plans, templates, text macros, order sets, and clinical content; establish the playbook for routine administration for the support team to run.
Decide what belongs on the clinician-facing product surface, which begins as a sidecar in the EHR and is intended to grow into an application centered on family care, and build a meaningful share of it.
Review clinical workflows being migrated from Salesforce, decide what should carry forward, and ensure clinicians do not lose workflows they rely on.
Work directly with clinicians, including follow-up conversations after visits and occasionally accompanying them in the passenger seat.
Build and show prototypes, tools, pipelines, or automations to help communicate product concepts and support implementation with engineers.
Apply clinical judgment to identify whether reported issues are workflow, training, or content problems and uncover the problem behind feature requests.
Protect PHI, clinical safety, and documentation requirements when designing and building, including checking agent-generated work that clinicians may act on.
Communicate product tradeoffs clearly to clinicians and collaborate with engineers through written work and reviews.
Provide and receive feedback and communicate changes, challenges, and opportunities across functions.