Product Engineer at Nest Health

Nest Health sends clinicians into people's homes. We're the primary care provider for entire households: families managing chronic conditions, caregivers juggling complex needs, and people who can't easily get to a clinic.

We treat the home as the unit of care, and nothing off the shelf was built that way. We're 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.

What you'll own

• You'll own a product surface, end to end. You take a real problem a market is having and own it from discovery through the shipped thing and the measurement afterward, including the API underneath.
• You'll shape what it should be. We have a roadmap, not a spec backlog. Requirements arrive as one-pagers and conversations with the people doing the work. If you need a groomed ticket to start, this will be uncomfortable.
• You'll own a slice of the migration. Every surface we build takes a workflow off Salesforce or Athena. That means understanding how it works today and deciding what carries forward.

What you bring

• Taste. The thing we care most about. A coordinator's screen can hold every field we have, and the version showing far fewer is usually better. You see that difference, care about it when nobody is checking, and can say why.
• Depth in one half of the stack, range across the other. Our stack is Python and FastAPI on Fargate, Postgres on RDS, and React/TypeScript, with product AI through Bedrock, all on AWS.
• Product sense. You can tell a request from the problem behind it, and you'll push back on a feature that would ship cleanly and change nothing.
• Design as practice, not polish. Information hierarchy, interaction design, and prototyping to learn before you build, for a nurse practitioner on a tablet in a living room and a coordinator with nine tabs open.
• AI across the whole job. Everyone here builds with agents daily. What interests us is how far you've pushed them, where you let them run unattended, where you write it yourself, and where you've caught one being confidently wrong.
• Judgment about where to be rigorous. Move fast at the edges and carefully at the core: PHI, access control, and anything a clinician acts on. HIPAA does not move under timeline pressure.
• Healthcare data literacy, or a fast path to it. No prior healthcare experience needed, but you'll learn what a care gap is and what PHI means for a design decision in weeks, not quarters.

What this is not

• This isn't a front-end or back-end role. If your interest ends at the boundary of one, this role will frustrate you.
• This isn't a big-team role. No dedicated PM, designer, or platform team. You'll be on calls with clinicians and sometimes in their passenger seat.
• This isn't greenfield. A live business runs on Salesforce every morning. Everything new gets built next to something old that still has to work.

Experience

• 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.
• LLM features, offline-first, EHR integration, or mobile are a plus.

Show us something you made

Required, and we read it before your resume. 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.