4195- Software Development Engineer-III Backend (Gravity)

Own the design and evolution of complex interoperability solutions spanning multiple healthcare systems, building scalable, cloud-native integration architecture that holds up at volume.

Lead architecture reviews, set engineering standards, and drive technical decisions that balance immediate priorities with the platform's long-term direction.

Evaluate emerging interoperability standards and push modernization — moving legacy integrations toward API-first and event-driven patterns where it makes sense.

Build and maintain healthcare interfaces across HL7 v2, FHIR, CDA/CCDA, X12/EDI, REST, and SOAP, using Python, Go, Java, or similar.

Develop reusable integration frameworks and shared tooling that make the whole team faster.

Own production reliability for critical integrations — retries, idempotency, monitoring, alerting, and error recovery for workflows that can't afford to fail quietly.

Lead incident investigations and root-cause analysis, and take part in on-call for critical services.

Build with HIPAA and PHI handling front of mind — encryption, authentication, authorization, and audit trails aren't an afterthought here.

Mentor engineers through design reviews, code reviews, and pairing.

Work closely with Product, R&D, Implementation, and Customer Success to turn complex requirements into solutions that actually ship.

Champion good engineering habits — automated testing, CI/CD, observability, documentation.

What success looks like in your first 6–12 months: you're owning technical delivery on critical interoperability initiatives end to end, you've measurably improved reliability and observability across integration services, you've set standards and reusable frameworks the team builds on, and Product/R&D/Implementation see you as the go-to person for interoperability strategy.

Experience integrating with EMR/EHR or Practice Management systems (Allscripts, NextGen, Epic, athenahealth, eClinicalWorks, Cerner, or similar).

Familiarity with event-driven architectures and Kafka.

Exposure to observability platforms like New Relic or KFuse.

Experience with Docker and Kubernetes.

Familiarity with US healthcare workflows, HIPAA, CMS requirements, and payer-provider integrations.

We know engineers with this exact combination of deep interoperability depth and platform-scale engineering experience are rare — if you're a strong distributed-systems engineer without direct healthcare exposure but you're excited to go deep on the domain, we'd still love to talk.

Innovaccer builds software that helps hospitals, clinics, and health insurance companies make sense of all the scattered data they deal with every day — patient records, appointments, insurance claims, lab results — and turns it into something useful and actionable.

Think of a typical hospital: patient information often lives in a dozen different systems that don't talk to each other well. This causes delays in scheduling, slows down doctors, and makes it harder to catch health problems early. Innovaccer's platform connects all of that data together, and increasingly, uses AI "agents" to actually do some of the manual work for healthcare teams — things like scheduling appointments, preparing insurance paperwork, or drafting clinical notes — so that staff can spend more time with patients and less time on admin work.

Some of the largest healthcare systems in the US — including CommonSpirit Health, Atlantic Health, and Banner Health — use Innovaccer's platform today.

The company is also investing heavily in this direction: in June 2026, Innovaccer signed a multi-year partnership with AWS to run its AI agents at a much larger scale, using AWS's cloud AI tools (Amazon Bedrock) and healthcare-specific data infrastructure (AWS HealthLake). This is a strong signal of where the platform — and this engineering team — is headed next. For more information, visit www.innovaccer.com and check us out on YouTube , Glassdoor , LinkedIn , Instagram , and the Web .