Responsibilities

1. Own end-to-end solution architecture based on MACH: microservices, API-first, cloud-native, headless/composable.
2. Design headless platforms integrating CMS, BFF layers, API gateways, and domain microservices.
3. Define clear boundaries: experience layer, integration/orchestration layer, domain services, external systems.
4. Ensure architecture meets enterprise NFRs: scalability, performance, security, availability, observability.
5. Lead BPM-driven orchestration using Camunda; define orchestration vs choreography.
6. Design event-driven workflows with Kafka/Pub-Sub, aligned with BPM; handle retries, compensations, SLA tracking.
7. Keep BPM process-centric; avoid embedding core business logic.
8. Define API-first standards (REST, async events); enforce contract-driven development and schema governance.
9. Establish API gateway patterns for security, rate limiting, versioning, observability. ...