Software Engineer - API

NexHealth · United States · Engineering

Posted 2026-11-17

Apply for this role →

About the Role

An API is easy to launch and hard to trust. This role is about earning that trust.

The NexHealth API gives hundreds of health-tech developers a single, modern interface to read and write data across dozens of practice management systems and EHRs. Behind every clean endpoint sits a system of record holding protected health information, synced in near real time with on-premise software that was never designed to be an API. So the hard problems aren't CRUD. They include consistency across systems that disagree, idempotent writes, webhooks that fire when they should, versioning that doesn't break integrations, and a developer experience good enough that a two-person startup can go from signup to a working product in an afternoon.

The work spans three areas:

Public API. The endpoints, data models, versioning, rate limits, and reliability guarantees that developers build their businesses on.

Events and webhooks. Telling developers when something changed, or when something broke, before their customers notice.

Developer platform. The developer portal, sandboxes, request logs, usage and billing visibility, docs, and AI-coding tooling (MCP, skills) that take a developer from zero to a working product.

As a software engineer, you'll own one of these areas end to end: its design, its operations, and its roadmap. You'll be the person who knows how it behaves under load, how it fails, and what it should become next.

What You'll Do

Design endpoints, data models, and versioning that stay simple and maintainable as we add EHRs, with a clear view of the operational load each decision creates.

Make writes back to EHRs safe: idempotent, observable, and recoverable when an on-premise system goes offline mid-request.

Build the events and webhooks developers rely on to know when appointments change or a sync goes down, so they hear about problems before their customers do.

Improve the path from signup to a working product: sandboxes, request logs, debugging tools, usage and billing visibility, and AI-coding tooling such as our MCP.

Own the operational health of your area. Write the design docs, run incidents, take ownership of developer escalations, and drive root-cause fixes that stick. You'll be trusted to talk directly with developers when things break.

Fix broken windows and build the tools that make the team faster, and set the example others follow.

Make engineering better beyond your team by interviewing, mentoring, onboarding new engineers, and giving honest, useful feedback.

What You'll Bring

5+ years as a software engineer building production back-end systems, including ownership of a public or partner-facing API used by external developers.

A record of leading large projects without a playbook. You can tell us how you brought clarity to an ambiguous one, and what you cut to ship it.

Deep, end-to-end ownership of a system: you knew how it behaved in production, ran its incidents, and left it simpler to operate than you found it.

Strong API design instincts: resource modeling, pagination, versioning and deprecation, idempotency, rate limiting, and error contracts developers can act on.

Experience with distributed-systems failure modes: retries, timeouts, eventual consistency, and syncing with third-party systems you don't control.

Empathy for developers as customers. You've read their support tickets, debugged their integrations, and changed the product because of it.

A firm grasp of security and data-handling principles. Healthcare experience isn't required, but care about getting PHI right is.

Clear written communication. You write design docs, postmortems, and decision records that people actually use.

Comfort with coding agents (Claude Code, Codex, Cursor, or similar) as part of how you ship, with clear opinions on where they help and where they don't.

We weigh what you've built, and how fast you're learning, over where you've worked. If you match most of this and the work excites you, apply.

Bonus Points For

Experience on developer platforms with many third-party integrations, such as Stripe, Plaid, Twilio, or Merge.

Experience building developer portals, sandboxes, request logs, or usage-based billing.

Experience with healthcare data or interoperability standards (HL7, FHIR).

Experience with our stack: Ruby on Rails, PostgreSQL, AWS, Kubernetes.

Compensation

Actual salaries will vary depending on factors including but not limited to location, experience, and performance. The range listed is just the base salary component of NexHealth’s total compensation package for employees. Other benefits may include stock options, an unlimited paid time off policy, and up to 100% coverage on medical, vision and dental insurance.

NexHealth Compensation Range

$141,000—$190,000 USD

Apply for this role →

← Back to all jobs