Back
Senior Software Engineer
Remote
Fulltime
Advanced
Data Science
Data Engineering
DevOps & Site Reliability
Security Engineering
Price Transparency
Member Support
The Role
Own a product area and ship. This is ~75% full-stack / ~25% integrations.
Minimum Qualifications
You ship. You’ve built useful, mission-critical tech.
You’re comfortable owning the whole loop: design → code → test → deploy → operate → learn.
You think in systems: contracts, boundaries, failure modes, and cost/perf trade-offs.
You communicate clearly and crisply (design docs/ADRs, postmortems) and raise the bar in code reviews.
Proof of impact. Years and logos don’t impress us. Results do. If you have 4–6+ years, great; if you’ve built more in 2 than most do in 10, even better.
Nice to have
Domain experience in healthcare, payroll, or finance software.
Experience with agentic systems, event-driven architectures, schema registries, EDI/FHIR/HL7.
Experience applying LLMs to antiquated systems.
What you'll do
Full-stack (~75%)
Design and deliver modular TypeScript services and React Native features.
Define versioned API contracts, auth, pagination and ship backward-compatible changes.
Model data and run safe migrations in Postgres, use Redis for cache/queues.
Engineer resilience: idempotency keys, retries with jitter, timeouts, circuit breakers, rate limits.
Write the right tests (unit/integration/contract/E2E) and short, surgical design docs/ADRs.
Integrations (~25%)
Build and own connectors to payroll systems, insurance EDI feeds, and vendor app feeds (webhooks, sandboxes, replay/DLQ).
Normalize messy partner payloads to canonical models; maintain versioned adapters and deprecation paths.
Track success-rate/latency SLOs; drive incidents to ground with partners.
Security & compliance
Security as architecture: PII minimization, envelope encryption with rotation, least-privilege IAM, purpose-of-use audit trails, and break-glass workflows. HIPAA/SOC 2 ready by design.
How to apply (resume optional)
Send a short pitch about you plus links to 1–3 things you built (demos, repos, screenshots, docs) to [email protected]
For each, tell us:
what problem it solved,
what you owned end-to-end,
the hardest trade-off, and
how you measured success.