tags.newtags.featured

Full-stack engineer

We build the software a home-infusion pharmacy runs on — ordering, referral intake, clinical workflow, delivery. Real hospitals use it today. We're looking for the engineer who takes it from one pharmacy group to a product other pharmacies buy.

Role: Full-stack engineer (individual contributor)
Location: Stockton, CA — on site
Type: Full-time
Experience: 5–7 years
Start: As soon as you can
Domain: Healthcare / pharmacy — a major advantage, not a requirement

The stack

Backend: Python · FastAPI · SQLAlchemy 2 · PostgreSQL
Frontend: TypeScript · Next.js · React
Cloud: GCP
AI: Claude and Gemini
Testing: pytest with coverage gates · Playwright · ruff · mypy

What we're looking for

5–7 years building and running production web applications — not just writing them, but keeping them up.
Strong Python and strong SQL. You're comfortable owning a schema, writing the migration, and reasoning about what a query costs.
Genuinely full-stack: you can build the interface people actually use, and you care whether it's any good.
You understand why multi-tenant isolation belongs in the database and not only in a WHERE clause.
You write tests that describe behaviour, and you're specific in review — about your own work as much as anyone else's.
You're comfortable being one of a few engineers, where the thing you finish this week is in front of a nurse next week.

Healthcare experience is a major advantage

Not a requirement, and we'll teach the domain to the right engineer. But if you've worked with PHI before — HIPAA in practice, business associate agreements, HL7 or FHIR, pharmacy or infusion workflow, claims, immunization registries, EHR integration — you'll start months ahead, and it will show in what we offer you.

What matters most is the instinct that comes with it: knowing which mistakes are recoverable and which ones involve a patient.

What this role is not

Not a management track. We want a builder, and the job stays hands-on.
Not greenfield. Real systems are live with real customers; you'll be improving software people already depend on, with the care that requires.
Not remote. This is on site in Stockton, with the pharmacy team you're building for down the hall — which is most of why the software fits how they actually work.