Role Overview :

Single point of accountability for the integration architecture across the MedRisk estate. Defines it, governs it, and answers for it to the design authority and the engagement sponsor.

Experience and Skills :

- 14+ years in enterprise integration, with 4+ years as a lead or enterprise architect accountable for a multi-system landscape.

- Proven design ownership of an enterprise integration platform spanning APIs, event streaming, bulk and CDC data movement, and file or document ingestion.

- Hands-on depth in at least two of: MuleSoft, Boomi, TIBCO, webMethods, Azure Integration Services, Oracle Integration Cloud, Kafka or Confluent, Azure Service Bus and Event Hubs, AWS EventBridge and MSK.

- Experience designing identity and entity resolution or master data management across systems with conflicting keys.

- Experience with coexistence architectures: dual running, write-back, reconciliation, idempotency and replay during legacy drawdown.

- Healthcare or insurance domain exposure; working knowledge of PHI handling and HIPAA constraints on data flows.

- Credible with both executives and engineers: able to defend a recommendation to a sponsor and to specify it precisely enough to build.

- Desirable: exposure to Palantir Foundry integration patterns, data platform or lakehouse architectures, and TOGAF or equivalent architecture certification.

Core Responsibilities:

- Own the target architecture: Define the integration layer end to end: business object APIs, event backbone, bulk load and change data capture, document and channel ingestion, identity resolution, coexistence and write-back.

- Set architecture principles and standards: Integration design principles, non-functional requirements, latency tiers, error handling, security and PHI handling, observability, and the pattern catalogue.

- Govern decisions: Own the decision backlog and the Architecture Decision Record (ADR) register.

- Hold the estate view: Map every Foundry roadmap workstream to shared capabilities so each is built once and reused.

- Own the boundary with Palantir: Agree what Foundry calls, what it consumes and what it writes back.

- Own coexistence and cutover architecture: Record ownership by drawdown stage, dual-write reconciliation, idempotency, replay and recovery.

- Converge the legacy estate: Define the migration path that retires legacy processors, aligned with the Platform and Architecture Modernization evaluation.

- Produce the roadmap: Sequence the build against the Foundry roadmap and legacy drawdowns, with estimates, team shape, dependencies and risks.

- Govern delivery quality: Review the designs of others on the team, chair or represent at design authority, and run architecture assurance into build.