Delivery Architect

JD

Delivery Architect

Product Area HMIS — deployed to pods per business need

Level Principal / Staff (player-coach)

Location India — Infinia Split ~50% hands-on engineering · ~50% architecture and design · 100% mentorship

About the Role

We builds sovereign health data infrastructure for governments and ministries of health and businesses. Our portfolio spans a national payer exchange platform, pharma track and trace, and a health data platform — each with active engineering pods and live government client commitments. This is a player-coach role with an explicit split: roughly half your time is hands-on engineering on critical path work, and the other half is architecture, design, and technical oversight. Both halves are non-negotiable. The mentorship dimension is not a fraction of your time — it is woven into everything you do. Every PR you review, every design session you lead, and every production issue you resolve is an opportunity to raise the technical floor of the engineers around you. You will be deployed to pods based on where the business needs senior technical delivery most. Your remit within each deployment is the same: define the architecture, build the hard parts, own the delivery standard, and leave the devs around you measurably better than you found them.

What You Will Do

• Design and own the technical architecture for the pod you are deployed to — FHIR R4 resource structures, API contracts, data models, service boundaries, and integration patterns. Decisions made here carry downstream consequences for regulatory compliance, interoperability, and system longevity. – Write production code on critical path work — NestJS services, FHIR endpoint design, Kafka event schemas, PostgreSQL data modelling. You are expected to be a meaningful code contributor, not a reviewer who occasionally commits. – Lead technical design reviews — engaging with requirements before code is written, catching architectural drift early, and ensuring implementation matches intent. You set the design standard, not just the review checklist. – Own delivery accountability within your deployed pod — you define release criteria, review what ships, and hold the bar for production readiness. Delivery ownership here means technical accountability, not ceremony facilitation. – Mentor engineers at every level — pairing on hard problems, conducting structured code reviews that teach rather than just correct, running design sessions as learning exercises, and investing in the long-term technical capability of the team. This is a standing obligation, not a calendar item. – Identify and address technical debt and skill gaps in parallel — when you spot a pattern of poor decisions, you fix the code and build the understanding so it does not recur. – Provide remote technical oversight for the implementation team as it relates to your pod's domain — reviewing deployment configurations, resolving field-escalated issues that require architectural judgement, and ensuring design intent holds across in-country implementation. – Maintain architectural documentation — ADRs, FHIR profile specifications, integration diagrams, and data flow documentation that the pod and Kenya team can rely on as a source of truth. – Contribute to technical hiring — reviewing take-home assignments, conducting deep technical screens, and calibrating what good looks like for the domain you are embedded in.

What We Are Looking For

• 8-12+ years of hands-on software engineering experience with a strong backend and systems design track record. You are still writing production code and intend to keep doing so — this is a baseline requirement. – A demonstrated history of raising the technical capability of the engineers around you — through mentorship, code review, pairing, or structured knowledge transfer. – FHIR R4 depth — production FHIR API experience, resource structure design, and an understanding of how FHIR composes into clinical and payer workflows. Implementation experience, not spec familiarity. – module architecture, DTO design, Kafka consumer patterns, guard and interceptor usage. – PostgreSQL schema design depth — partitioning, indexing strategy, ORM trade-offs, and JSONB versus relational decisions for FHIR resource storage. – Payer or clinical domain experience — eClaims and adjudication data models, or clinical encounter and care workflow structures is good to have – Comfort owning delivery through technical authority rather than hierarchy — you hold a standard through what you build and what you teach, not through org structure. – Remote cross-geography technical experience — maintaining design intent across a field team operating in a different country, time zone, and implementation context.

Nice to Have

• Experience with international health data regulatory context – Keycloak, CASL, or SMART on FHIR auth patterns — clinical and payer access control is a first-class concern across our domains. – Kafka event schema design and consumer architecture — used across domains for HIE notifications and payer event streams. – HL7 v2 ADT feed handling and the FHIR R4 translation layer. – Prior experience in a healthtech environment where SLAs, audit trails, and regulatory signoff are part of the definition of done.

What This Role Is Not – This is not an architecture-only role. If you are not writing production code, you are not doing this job fully. – This is not a fixed-scope role. You will be deployed where the business needs senior technical delivery — moving as priorities evolve. – This is not a role for someone who wants to design systems and hand them off. You will live with the consequences of your architectural decisions because you are also responsible for delivery against them. – This is not a role where mentorship is optional. Raising the technical floor of the team is as much a part of your job as the code you write.