Lead Integration Architect

Responsibilities

• Design and own integration architecture solutions across the software platform, instruments, applications, and enterprise systems.
• Define integration standards and reference architectures: API design, event-driven patterns, schema governance, and versioning, and validate their implementation in practice.
• Architect and hands‑on guide containerized integration solutions using Kubernetes, ensuring platform‑grade reliability, scalability, and operability.
• Review and approve critical integration designs across product teams, making binding architecture decisions where standards are at stake.
• Build and maintain a library of reusable integration patterns and reference implementations, working code and blueprints, not just documentation.
• Partner across divisions as the go‑to integration authority, solving complex cross‑system and cross‑organizational architecture problems directly.
• Define integration contracts between platform services, instruments, and enterprise systems, owning technical quality of those interfaces.
• Identify and actively remediate integration patterns that introduce technical debt, bypass governance, or create cross‑team coupling risks.

• 10+ years of software engineering or architecture experience.
• 5+ years in hands‑on integration architecture roles.
• Deep practical expertise across the full integration stack: REST/GraphQL API design, event-driven architecture (Kafka, MQTT, or equivalent), asynchronous messaging, and schema governance.
• Strong hands‑on experience with Kubernetes, deploying, operating, and architecting containerized workloads at platform scale.
• Experience with Docker and cloud-native deployment patterns across edge and cloud environments.
• Demonstrated track record of delivering integration solutions, not just defining patterns but owning their design and technical quality through implementation.
• Experience setting and enforcing API versioning, schema management, and contract-based integration standards.
• Ability to make and defend binding architecture decisions across teams with competing priorities.