Principal Middleware Architect – Healthcare Integrations

Experience:

Openings:

Domain:

Role Overview

central integration and interface platform

Principal Middleware Architect

setting direction, designing core patterns, and removing systemic integration friction

What You’ll OwnIntegration Architecture & Standards

• Define and evolve the

  central interface / middleware architecture

• Establish

  clear boundaries

  between core systems and integrations
• Design

  canonical APIs and events

  used across devices and partners
• Own

  API versioning, contract standards, and compatibility policies

API & Event Governance

• Design

  internal vs external API contracts

  with long-term stability in mind
• Guide teams on

  RESTful and event-driven integration patterns

• Review and unblock backend integration designs with architectural clarity
• Ensure integrations are

  contract-first, versioned, and observable

Device & Partner Integrations

• Enable

  device-agnostic, adapter-based integration patterns

• Ensure vendor or device changes do not ripple into core Software systems
• Define normalization strategies for device, lab, and partner data

Non-Functional Architecture

• Guide latency, throughput, and rate-limiting strategies
• Define

  integration-specific database schemas and data boundaries

• Ensure

  end-to-end traceability and auditable integration flows

• Partner with DevOps on deployment, scaling, and observability concerns

Cross-Team Leadership

• Work with the

  Architecture Board

  to enforce standards pragmatically
• Act as a trusted advisor to backend teams—not a gatekeeper
• Shape long-term integration roadmaps and reference implementations

Required Skills & Experience

• Strong experience with

  Python-based backend systems

  (Django / FastAPI or similar)
• Hands-on experience designing

  REST APIs and API contracts

• Deep understanding of

  API versioning, backward compatibility, and governance

• Experience with

  event-driven architectures

• Solid grounding in

  distributed systems fundamentals

• Experience designing

  integration-specific data models or schemas

• Exposure to

  regulated domains

  (healthcare preferred)

Nice to Have

• Experience with

  Kafka, RabbitMQ, or similar messaging platforms

• Familiarity with

  API Gateways

  and traffic management concepts
• WebSockets or real-time data flows
• Medical device or diagnostics integration experience
• Audit, compliance, or traceability-driven system design

How Success Is Measured

• Integrations remain

  stable despite vendor or device changes

• API consumers experience

  predictable, versioned contracts

• Backend teams integrate faster with fewer production issues
• Integration flows are

  auditable, observable, and scalable

• Architectural decisions reduce long-term integration complexity

Why This Role Is Different

• You’re defining

  how integrations are done

  , not fixing broken ones
• Architectural authority is backed by the

  Architecture Board

• Focus on

  patterns, standards, and leverage

  , not one-off adapters
• Real impact across devices, partners, and core healthcare systems