You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Be the first to open itNo views yet
Company hidden

Founding Engineer

  • Remote
  • 3-6 years

Salary

$160,000 - 220,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

About the company

Our systems read real patient records, find clinical and regulatory risk, and put it in front of the people who can act on it. We run on production PHI for paying customers, so every design decision reaches actual patients.

We're also architected differently from most healthcare AI companies: all model inference runs inside our HIPAA-compliant Azure environment. No external LLM APIs ever touch patient data. That data-sovereign architecture is a core reason enterprise customers choose us, and you'll own it.

The founders

You'd be joining three founders, not just a company. He also comes from a family of physicians, which is why claims denied over documentation errors are personal, not abstract.

You'll work with all three of us daily, and your line to a decision is one Slack message long.

Responsibilities

  • 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

Requirements

  • 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)
  • Details
  • Full-time, remote (US), with team meetups in San Francisco
  • Competitive salary plus founding-level equity
  • Direct line to the founders; short path from idea to production
  • Stack: TypeScript, Node.js, NestJS, React, Next.js, SQL/NoSQL, Azure-hosted LLM inference, Docker, Kubernetes
  • Experience: 6+ years
  • Visa: US citizen/visa only

Where you’d work

Fully remote

No visa sponsorship

You must already be able to work in the United States

About the company

Company hidden

  • Industry: HealthTech

Offices in San Francisco, United States, Austin, United States

Your chances

Still hiring, moderately crowded, and a person reads your message.

  • 19 checks run
  • 8 good signs
  • 3 red flags

Still hiring?

12 checks

Actively hiring

In its favour4

  • Still on the company's own careers site, checked 5 h agoModerate evidence
  • Specific about the basics: pay, place, level, stack and contract all statedSlight evidence
  • States its salarySlight evidence
1 moreFewer
  • A hiring contact is attached to itSlight evidence

Against it1

  • Posted 6 weeks ago, older than 91% of the open roles we trackModerate evidence

How crowded?

7 checks

Moderate

In its favour4

  • You can message the hiring contact and skip the queueModerate evidence
  • Only for people already authorized to work in United StatesSlight evidence
  • Senior level: far fewer people qualifySlight evidence
1 moreFewer
  • Asks for Next.js, which only 1% of open roles doSlight evidence

Against it2

  • Open for 6 weeks: applications have had time to pile upModerate evidence
  • Remote from anywhere: the widest pool of applicants there isModerate evidence
10 roles like this are in their Early WindowFound before the big job boards, while the crowd hasn’t arrived

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details14 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Kubernetes
  • Docker
  • React
  • TypeScript
  • Next.js
  • Node.js
  • SQL
  • JavaScript
  • Azure
  • LLMs
Type
Full-time
Equity
Equity offered
Industry
HealthTech
Specialty
Frontend
Region
United States
Show 8 more factsShow less

Role

Category
Development
Specialty
Frontend
Experience
6+ years
Tech stack
  • Kubernetes
  • Docker
  • React
  • TypeScript
  • Next.js
  • Node.js
  • SQL
  • JavaScript
  • Azure
  • LLMs

Location

Work model
Remote
Region
United States
Offices
  • San Francisco, United States
  • Austin, United States
Visa sponsorship
Not sponsored
Must already work in
  • United States

Compensation

Salary
$160,000 - 220,000 / year
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Company

Industry
HealthTech

Something wrong with this vacancy?

Similar vacancies

  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Software Engineer I

    €40,000 - 70,000 / year

    • Office · Greece
    • Junior
    Direct apply
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Software Engineer I

    €35,000 - 65,000 / year

    • Office · Portugal
    • Junior
    Direct apply
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Software Engineer I

    €45,000 - 75,000 / year

    • Office · Spain
    • Junior
    Direct apply
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Software Engineer

    $130,000 - 190,000 / year

    • Hybrid · Mountain View
    • Junior

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason