Founding Product Engineer

hatch I.T. is partnering with Kinstead to find a Founding Product Engineer. See details below:

We're hiring a founding product engineer to own the user-facing experience of their platform.

You'll work closely with the CTO, founders, designers, and clinical stakeholders to turn complex clinical and operational workflows into software that feels simple, reliable, and intuitive. This isn't a role where product requirements are handed to you in finished form. You'll help discover the right solution alongside clinicians and designers, make thoughtful product and technical tradeoffs, and build features from idea to production.

You'll own the frontend, but not in isolation. You'll influence API design, data models, and overall architecture to make the entire product feel cohesive. We expect engineers to think beyond components and pages, thinking about how the entire product should behave.

This role is a great fit if you enjoy turning messy real-world workflows into polished software, making product decisions, and building alongside customers. It is probably not the right role if you prefer narrowly scoped implementation work or highly specified roadmaps.

Kinstead is building the AI-native operating system for independent healthcare, enabling nurse practitioners to launch and run their own clinics. They replace the fragmented, manual infrastructure behind healthcare with a single, intelligent system so clinicians can spend their time on care, not paperwork.This creates a new model of care, one where clinicians practice on their terms and patients get consistent, community-rooted care. They’re backed by Wisdom Ventures and founders and executives from Pomelo Care, Flatiron Health, Roivant, and PathAI on their mission to deliver better care.

We’re building something ambitious, and we care deeply about how we show up while we do it.

We spend time with the people we serve, in their practices and in their communities. The best ideas come from understanding their reality and building alongside them.

If something matters, we don’t wait for perfect clarity. We step in, make progress, and figure it out together.

We solve problems in real time, then step back and build the systems that make it easier for the next clinician.

We look for ways to reduce manual work so clinicians can focus on care. If something feels repetitive, we treat it as an opportunity to improve how we operate.

We’re here to help clinicians create independent, community-rooted practices. That responsibility shapes how we make decisions and how we grow.

We support each other, give honest feedback, and focus on getting to the right answer. We take the work seriously, but not ourselves.