Founding Engineer

The role You'll own the technical direction of the platform end to end. This is not a senior IC role with a bigger title. You decide how clinical data is modeled, how our AI pipelines are evaluated and trusted, and what the platform looks like in two years. Then you build it. You'll sit in customer calls with Directors of Compliance, leave with a problem nobody has written down yet, and ship it within the quarter. When there's a hard call on architecture, or on whether a model output is safe to show a clinician, you're in the room making it. This is right for you if you've been the technical center of gravity on something real, and you'd rather own an ambiguous problem than a well-specified ticket. It's wrong for you if you want a defined scope or a team that already exists. You're the person who creates them. Your first 90 days First 30 days: ship to production. Take over one of our five live modules (Documentation QA is the busiest), get its evaluation harness under your control, and ship an improvement a customer notices. By day 60: own the EHR data layer. We integrate with the behavioral-health-native EMRs (Kipu, Alleva, BestNotes and others), and the ingestion and normalization architecture across them is yours to set. By day 90: you've made at least one architecture decision the company will live with for years, defined how we evaluate model output before a clinician sees it, and set the bar the next engineering hires will be measured against. What you'll own Architecture across the full stack: data model, ingestion, AI pipelines, application layer, infrastructure The clinical data layer: ingesting and normalizing messy EHR data: FHIR, HL7, and the many formats that pretend to be them AI systems clinicians actually trust: evaluation, ground truth, error analysis. Calling a model is easy. Proving the output is right is the job Product judgment from data: go into real client data, find quality gaps nobody has flagged, turn them into shipped features The engineering bar: as the team grows, you define how we hire, review, test, and ship What we're looking for 5+ years shipping production software, with real ownership of systems that outlived your involvement Deep TypeScript/Node/NestJS; advanced React and Next.js Data engineering at scale: schema design, query optimization, pipelines over large volumes of semi-structured records Production LLM systems, not demos. You've built the evaluation harness that kept them honest Communication that carries weight: equally clear with a clinician, a founder, and an engineer Strong signals Founding or early engineer at a startup that reached real scale Healthcare experience: you’ve shipped software handling real patient data (PHI) — been through a HIPAA or SOC 2 audit, not just read about one Hands-on with EHR/EMR data and clinical formats (FHIR, HL7); familiarity with behavioral-health EMRs (Kipu, Alleva, BestNotes) is a big plus Embeddings and retrieval in production Self-hosted or private model inference experience (Azure ML, vLLM, or similar) APPLY HERE! https://docs.google.com/forms/d/e/1FAIpQLSeor9RN2ALAnNo-iayDYr0yxvEUcqW6Z0r0s4JQ-se9DD5p4g/viewform?usp=dialog