Integration & API Architect

About the role

The Integration & API Architect is responsible for defining and governing the enterprise integration landscape, ensuring secure, scalable and reusable integration patterns across platforms, applications, cloud services and smart solutions. The role works closely with architecture, cloud, security, infrastructure and data teams to deliver high‑performance, resilient and compliant integrations.

Key responsibilities

• Define and maintain enterprise integration architecture covering APIs, messaging, event streaming and interoperability standards.
• Establish API governance standards, including lifecycle management, naming conventions, versioning, documentation and deprecation policies.
• Design secure API access models using OAuth2, OIDC, JWT, mTLS, token scopes and best‑practice security controls.
• Set event‑driven architecture standards such as schemas, retries, dead‑letter queues, idempotency and event ordering.
• Govern data contract practices, including schema validation, contract testing and CI/CD integration.
• Define resiliency patterns like retries, circuit breakers, failover, throttling, caching and timeout management.
• Lead onboarding and integration activities for internal systems, external platforms and third‑party vendors.
• Establish observability standards covering logging, distributed tracing, telemetry, monitoring and SLA/SLO reporting.
• Conduct architecture reviews and provide technical assurance for production‑ready integration implementations.
• Develop reusable integration standards, reference architectures, technical documentation and operational runbooks.

Required profile

• Bachelor’s degree in Computer Science, Information Technology, Software Engineering or a related field; Master’s preferred.
• 8+ years of experience designing and governing integration solutions in large enterprises.
• Proven ability to lead cross‑functional teams and enforce governance across multiple vendors.

Required skills

• API design and governance (REST, OpenAPI, versioning, documentation).
• Event‑driven architecture (Kafka, event schemas, retries, dead‑letter queues, idempotency).
• Security protocols (OAuth2, OIDC, JWT, mTLS, token scopes).
• Integration platforms and API gateways.
• Observability tools (logging, distributed tracing, telemetry, monitoring, SLA/SLO reporting).
• Resiliency patterns (circuit breakers, retries, failover, throttling, caching, timeout management).
• CI/CD pipelines with contract testing and schema validation.