Software Engineer
Stealth Healthtech Startup
| Company | Stealth Healthtech Startup |
| Category | Engineering |
| Location | North America |
| Remote | On-site (inferred) |
| Employment | Not stated |
| Level | Not stated |
| Salary | Not stated by the employer |
| Posted | 27 Jul 2026 |
| Last verified | 30 Jul 2026 |
| Source | Employer career page (ashby) |
Description
About the Company
We’re building infrastructure that makes healthcare innovation easier. Our customers already serve 3+ million patients and manage $15+ billion in annual medical spend. Today, we work with leading healthcare groups backed by top Silicon Valley investors such as Sequoia, General Catalyst, Y Combinator, Kleiner Perkins, Stanford, Khosla Ventures, and others. Our mission is to enable more innovation in healthcare—so more patients receive affordable care.
About our Team
Our leadership previously founded and led a national digital health company (>$15M raised), with a team of 100+ employees across the US and that sold to a 1,000+-person incumbent. We’re a tight-knit team that’s driven to move fast and take on some of the biggest problems in healthcare and ultimately improve patient lives.
About the Role
As our business grows, we're looking for a Software Engineer who will own our internal tools, client-facing products, and infrastructure underlying our operations.
You'll be our founding offshore engineer, working async with a US-based operations team to build the data architecture, integrations, internal tools, automations, and agents that operations runs on. One month you might stand up a clean data model and sync it across our tools; the next, build an internal console the ops team uses daily; the next, ship an AI agent that drafts, triages, or matches — and earns enough trust to run with light human review. You'll go deep enough to understand each operational workflow, then replace it with a system that runs better without you. Backend and data are the core; you'll build serviceable internal UIs when needed (AI-assisted is fine), with correctness and reliability mattering more than polish
What You’ll Own:
- Own the data architecture — the entities, relationships, and sources of truth behind physician sourcing/matching, client onboarding, PC-MSO structures, and billing state — and keep it clean as requirements change.
- Build and harden integrations between our systems (CRM, e-sign/DocuSign, scheduling, spreadsheets, Google Workspace, our datastore) so data flows reliably instead of by hand — with sane handling of auth, webhooks, rate limits, retries, and idempotency.
- Replace manual ops work with automations and AI agents — and make them observable and trustworthy enough to run with minimal supervision.
- Build lightweight internal tools the ops team uses to run the business; ship serviceable client-facing UI when needed (AI-assisted acceptable, behind a review gate when durable).
- Take an ambiguous operational need from a non-engineer stakeholder, clarify the real requirement, scope pragmatically, ship it, and own it in production — monitoring, fixing, and documenting as you go.
- Instrument the business — the pipelines and definitions behind the metrics and dashboards ops and leadership run on.
Key Performance Indicators
In your first 6-12 months, you will have (outcomes, not activities):
- Stood up a clean, documented data model plus the integrations that keep it current — the trusted source of truth for at least one core domain (e.g., physician supply, client onboarding).
- Shipped at least one automation or agent that removed meaningful recurring manual effort and runs reliably with only light human review.
- Delivered at least one internal tool the ops team uses daily to run the business without you in the room.
- Left systems documented and observable enough that a teammate — or the next engineer — can run and extend them.
About You
Core Experience
- 5+ years building and shipping production backend / data / integration systems, with real ownership (not just closing feature tickets).
- Strong at data modeling and systems design — you design schemas and services that survive changing requirements and messy real-world data.
- Fluent with integrations — third-party APIs, webhooks, auth, rate limits, and the failure modes of sy
You found the opening. Now track it.Tracker, radar and AI drafts in one place.erioun.com →