Product Engineer

Nest Health
•Remote

About The Position

Nest Health is building a product ecosystem with the family at the center and a surface for each audience around them: the clinician in the home, the coordinator planning the week, the operator running a market, and eventually the family on their own phone. One team owns all of it, with no design team or PM layer between you and users. We are hiring a Product Engineer to help us build it. This role involves owning a product surface end-to-end, from discovery through shipping and measurement, including the underlying API. You will shape the product based on one-pagers and conversations, not a spec backlog. A significant part of the role involves owning a slice of the migration, understanding current workflows on Salesforce or Athena, and deciding what carries forward.

Requirements

  • Taste: ability to discern and prioritize user experience, caring about details even when not explicitly checked.
  • Depth in one half of the stack (Python/FastAPI or React/TypeScript) and range across the other.
  • Product sense: ability to distinguish a request from the underlying problem and push back on ineffective features.
  • Design as practice: understanding of information hierarchy, interaction design, and prototyping.
  • AI across the whole job: experience building with agents, understanding how far they've been pushed, where they run unattended, where custom code is written, and how to catch errors.
  • Judgment about where to be rigorous: moving fast at the edges and carefully at the core (PHI, access control, clinician actions).
  • Healthcare data literacy, or a fast path to it.
  • 4+ years shipping user-facing product.
  • Strong in TypeScript/React or Python, competent in the other.
  • Has designed interfaces people use, not only built them.
  • Comfortable in AWS, or a clear path to it, ideally in a HIPAA-aligned environment.
  • Works in an agentic coding harness daily and writes clearly.
  • Send a link to something you built: a product, a tool, a side project, a teardown. Tell us what you were trying to do, one decision you'd defend, and one you'd take back. If your work is proprietary, pick a product you use constantly and tell us what's wrong with it and what you'd do about it, in two or three paragraphs.

Nice To Haves

  • LLM features
  • offline-first
  • EHR integration
  • mobile development

Responsibilities

  • Own a product surface, end to end, from discovery through shipping and measurement, including the API.
  • Shape product requirements based on one-pagers and conversations with stakeholders.
  • Own a slice of the migration, understanding current workflows and deciding what carries forward.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service