Software Engineer

HHAeXchange is the leading technology platform for home and community-based care. Founded in 2008, HHAeXchange was created to build a complete, end-to-end homecare solution that helps people who are aging or have disabilities live well in their homes and communities. Our employees work to transform healthcare by building one homecare platform that connects patients, personal care providers, managed care organizations, and states. 

The Principal Software Engineer is a senior, hands-on technical leader who sets technical direction for one or more engineering teams. This role does not manage people. It leads through technical expertise, clear written decisions, and working directly with engineers. 

The role guides the design of API-first software and healthcare data exchange solutions that run on Amazon Web Services (AWS). The Principal Software Engineer is accountable for the technical quality of the software its teams produce: performance, reliability, scalability, security, and accessibility. Our engineering organization includes employees and contract engineers, so this role also defines and maintains clear standards, templates, and review practices that help every engineer deliver consistent work. 

To perform this job successfully, an individual must be able to perform each essential job duty satisfactorily. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. 

This position is open for candidates who are located within the EST or CST time zones within the US only.

Essential Job Duties

• Technical direction: Set the technical direction for the systems that one or more teams own. Record major decisions, the options considered, and the reason for each choice in Architecture Decision Records (ADRs).
• Hands-on delivery: Write, review, and ship production code on a regular basis. Focus on work that carries high risk or that sets a pattern other engineers will follow.
• Incremental modernization: Guide the gradual modernization of legacy applications into modern services. Replace one part at a time while the old and new parts run together (the strangler pattern), so that feature delivery continues. Define the order of work, the rollback plan for each step, and the measures that show progress.
• Healthcare interoperability: Design and review solutions that exchange healthcare data using HL7, FHIR, and X12 EDI. Account for differences between trading partners, version changes, error handling, and reconciliation of data between systems.
• Quality attributes: Own the system-wide qualities of performance, reliability, availability, scalability, security, and accessibility. Define measurable targets, such as service level objectives (SLOs), and review results with the teams.