Senior Software Engineer - API

NexHealth
United States
On-site

Who this role is best for

Strong fit for experienced backend engineers who lead ambiguous projects and design robust APIs, with a preference for those familiar with healthcare interoperability or developer platforms.

Best fit for

  • Experienced backend engineers with a history of leading ambiguous projects and shipping APIs
    — “Lead large API projects from an ambiguous problem to rollout”
  • Candidates who have designed maintainable APIs with versioning and deprecation strategies
    — “Design endpoints, data models, and versioning that stay simple and maintainable”
  • Individuals who have worked on developer platforms with third-party integrations and tooling
    — “Build the events and webhooks developers rely on to know when appointments change”
  • Candidates with a background in distributed systems and handling third-party failure modes
    — “Experience with distributed-systems failure modes: retries, timeouts, eventual consistency”

Things to consider

  • The role requires ownership of system behavior, incident management, and developer escalations
    — “Own the operational health of your area. Write the design docs, run incidents”
  • Candidates must be comfortable with coding agents and have clear opinions on their use
    — “Comfort with coding agents (Claude Code, Codex, Cursor, or similar)”

How to stand out

  • Emphasize projects where you simplified complex systems and improved developer experience
    — “Deep, end-to-end ownership of a system: you knew how it behaved in production”
  • Highlight experience with API versioning, rate limiting, and error handling in your resume
    — “Strong API design instincts: resource modeling, pagination, versioning”
  • Showcase your ability to cut scope and ship products despite ambiguity
    — “You can tell us how you brought clarity to an ambiguous one”
  • Demonstrate your understanding of healthcare data standards like FHIR or HL7
    — “Experience with healthcare data or interoperability standards (HL7, FHIR)”
  • Include examples of developer tooling you've built or improved, such as sandboxes or logs
    — “Improve the path from signup to a working product: sandboxes, request logs”
Pace · Fast PacedCollaboration · HighAutonomy · HighDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • Successfully launched and maintained a robust API system
  • Improved developer experience through better documentation and tools
  • Ensured high availability and reliability of API services
Typical background
Experience in designing and implementing large-scale API systemsStrong background in software architecture and design patterns

Skills & requirements

Required

API DesignRestful ServicesMicroservices ArchitectureVersion ControlCi/cd PipelinesCloud ServicesAPI SecurityEvent-driven ArchitectureWebhooksDeveloper ExperienceOperational Health Monitoring

Preferred

KotlinJavaGoRustC++AndroidLinuxHalsSystem ServicesMiddlewareDrivers

Stack & domain

API DesignData ModelsVersioningIdempotent WritesWebhooksDeveloper PortalSandboxesRequest LogsUsage And Billing VisibilityAi-coding ToolingMCPLeadershipProblem-solvingCollaborationCommunicationOwnershipTechnical ExpertiseHealthcareSoftware EngineeringAPI DevelopmentEHR Systems

About the role

Original posting from NexHealth

About NexHealth

Our healthcare system remains frustratingly analog. When you live in a world of one-tap car rides, instant meal delivery, and unlimited streaming, why do you still have to call to schedule a doctor’s appointment and fill out a clipboard in the waiting room?

NexHealth’s mission is to accelerate innovation in healthcare by connecting patients, providers, and developers. We’re building the infrastructure layer for modern healthcare, connecting thousands of fragmented, on-premise, and closed EHR systems into a single, modern platform that powers software, APIs, payments, and patient experiences across the ecosystem.

Founded: 2017

Headquarters: San Francisco, CA

Funding: $177M Series C 

Employees: 200+

Trusted by tens of thousands of providers and hundreds of health-tech developers — forging the infrastructure layer that modern healthcare needs

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 Senior 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

Lead large API projects from an ambiguous problem to rollout, often with contributors from other teams. Define the metrics, milestones, risks, and trade-offs up front so the project is derisked early.

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.

Shape the team's roadmap with the investment your systems need to stay healthy, working with product, support, and partner engineering teams.

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$165,000—$230,000 USDBenefits

Full Medical, Dental, and Vision (up to 100% covered)

401K and commuter benefits

Flexible PTO

High-impact work that directly improves the healthcare experience for millions

Our Values

Solve the customer’s problems, not yours

When making decisions, think from the perspective of the customer. It’s easy to make decisions that make our lives simpler, but not the customers.

Do the things others are not willing to do

As a Nexer, always go after the hardest problems. Pursue things at the highest quality. Move at the fastest pace. 

Take ownership

Act like a founder. Own your roles, destinies, mistakes, behavior, and our mission. The buck stops with each of us - no blaming or excuses.

Say what’s on your mind, with positive intent

Be direct, proactive, transparent, and frequent in your communication.

Default trust

As a Nexer, you do not have to earn trust, trust is given to you by default. If we by default trust each other, our speed of communication, feedback, information sharing, and overall improvements will be a lot faster.

Think in first principles

We first identify the problem and then break it down to its fundamentals before diving into solutions. We constantly ask “why” to validate our assumptions.

We are an equal opportunity employer and value diversity at our company. We do not discriminate on the basis of race, religion, color, national origin, sex, gender expression, sexual orientation, age, marital status, veteran status, or disability status. We provide reasonable accommodation for individuals with disabilities to participate in the application or interview process. Contact talent@nexhealth.com to request assistance.

Source: NexHealth careers

Similar roles

More roles at NexHealth