nest-health - Clinical Product Builder

• Clinical depth. You've practiced, or you've spent years in clinical informatics working alongside people who do. You can sit with a nurse practitioner after a visit and tell the difference between a workflow problem, a training problem and a content problem. • EHR build, not just EHR use. You've built the templates, order sets and documentation workflows clinicians work in, and you know from experience how a small configuration change becomes a documentation gap or a billing problem six weeks later. athenaOne experience is a strong plus. • Taste. A pre-visit summary can dump the whole chart, or it can read like a colleague briefing you on a family you're about to meet. You can see the difference and say why one is better. • Product sense. You can tell a request apart from the problem behind it. When a clinician asks for another field, you find out what they were trying to decide. • You build things. You've built real projects with Claude Code, Cursor or a similar agentic tool, at work or on your own time. They don't need to be production software: a prototype, a tool, a pipeline or an automation someone still uses all count. You've probably been doing this since before the tools existed, by building a clickable prototype or a spreadsheet model so engineering could see what you meant. You can say where you trust an agent and where you check every line. Anything a clinician acts on in a home, you check. • Rigor where it counts. You understand how PHI, clinical safety and documentation requirements shape a design, and you don't let timeline pressure move them. • Clear writing and two-way collaboration. You can explain a tradeoff to a clinician who doesn't care about the system, and you can take a hard review from an engineer and give one back. • WHAT THIS IS NOT • It is not an Athena admin role. Configuration is part of the job. Doing only configuration is not. • It is not a PM role in the traditional sense. You won't write requirements and hand them off. Engineers here work from something you built and can show them, not from a document. • It is not an engineering role. You'll build real things every week, but product engineers own the production systems underneath them. • It is not a clinical role. You'll use your clinical judgment every day, but you won't be seeing patients for us. • If you'd rather not talk to clinicians, don't apply. You'll be on calls with them after visits, and sometimes in the passenger seat. • This is not greenfield. A clinical team depends on today's tools every morning. Everything new gets built next to something old that still has to work. • Clinical training (RN, NP, PA, LCSW or similar) or 3+ years of clinical informatics working directly with clinicians. • 3+ years across clinical informatics, EHR build, or clinical product management, including hands-on build of templates, order sets or documentation workflows. • Fluent in SQL, and comfortable reasoning about clinical data: encounters, problems, orders, claims, and why they disagree. • Has built at least one real project with an agentic coding tool (Claude Code, Cursor or similar), at work or on your own. Prototyping that helped engineers understand what to build counts as well. • Writes clearly. We're remote, and most decisions get made in writing. • A plus: athenaOne, FHIR/HL7 interoperability, value-based care (quality measures/outcomes measurement), home-based or complex care. • SHOW US SOMETHING YOU MADE • Required, and we read it before your resume. If you have a clinical build you're proud of as well, like a template, a workflow or a teardown of an EHR flow that annoyed you, send that too. If everything you've built is proprietary, write about it instead. Pick a clinical workflow you know too well, then tell us what's wrong with it and what you'd do about it. Two or three paragraphs is plenty.