Integration Platform Sr Manager_2988

About the role

The Senior Manager of Digital Integration & Platform is a hands-on engineering leader responsible for the foundation that all five digital domains depend on. This role owns the API layer, microservices platform, event streaming infrastructure, cloud-native architecture, and the integrations that connect AllianzLife.com to financial product systems, downstream platforms, and third-party services. This is a platform-first role in the truest sense and the team this manager leads enables every other domain to ship faster, more reliably, and with greater consistency.

Responsibilities

• Own the full API layer for AllianzLife.com including design, development, versioning, deprecation, and contract governance across all domains
• Build and maintain the AWS API Gateway configuration including WAF rules, rate limiting, routing, and security policies
• Establish and enforce API standards used by all five engineering domains: REST conventions, error handling, versioning strategy, and documentation requirements
• Implement and maintain API catalog and developer documentation so internal teams can self-serve integrations without reliance on tribal knowledge
• Manage Vault for secrets management, certificate rotation, and secure credential distribution across services
• Lead the engineering and ongoing operations of the Java/Spring Boot microservices that power AllianzLife.com’s core capabilities and build Account Service, Money Out Service, Claims Service, and Service Requests
• Own MongoDB per-service schema design and data governance and ensuring schemas are right-sized, versioned, and maintained independently per service
• Own Salesforce CRM integrations and all third-party API integrations that connect digital capabilities to back-office systems
• Own middleware orchestration and data transformation patterns across the integration layer
• Own the EBS Kafka event streaming bus that underpins real-time integration across AllianzLife.com and downstream systems
• Design and maintain event schemas, topic governance, consumer group management, and producer patterns
• Drive adoption of event-driven patterns across domain teams to reduce synchronous coupling and improve platform resilience
• Own the cloud-native platform on AWS including ECS/EKS container orchestration, networking, IAM, and service mesh configuration
• Own the GitHub Actions CI/CD pipeline including branch strategy, PR gates, build and test automation, and deployment to AWS ECS/EKSDrive legacy system decommissioning with a sequenced, risk-managed migration plan that minimizes disruption to downstream consumers
• Own platform SLAs for availability, latency, and deployment frequency tracked through Dynatrace observability
• Own on-call rotation and incident response for platform-layer issues — building a culture of blameless post-mortems and continuous improvement
• Own platform health metrics are visible to all domain teams as a shared signal for release readiness
• Embed AI-augmented engineering practices into the team’s engineering workflow: AI code review and generation, automated test coverage, and intelligent PR analysis
• Partner with the Architecture domain to evaluate and adopt emerging AI-first tooling (Anthropic Claude Code and equivalent) that improves platform engineering velocity
• Champion the AI-first operating model within the Integration & Platform domain as a foundational practice, not an optional add-on
• Lead a full-stack platform engineering team — hiring, developing, and retaining engineers with deep expertise in Java, AWS, event-driven architecture, and API platform engineering
• Participate in technical decisions — conduct code reviews on microservices, infrastructure-as-code, and API contracts; shape architectural choices with the team
• Own the Integration & Platform team’s slice of the single prioritized backlog — ensuring stories are ready, sequenced, and clearly prioritized against platform stability and new capability work
• Use DORA metrics — deployment frequency, lead time, change failure rate, and MTTR — as active coaching tools, not reporting artifacts

Requirements

• 8–10 years of experience in platform, integration, or backend engineering, with at least 3–4 years leading and managing engineering teams
• Demonstrated engineering background in Java/Spring Boot microservices — must be able to conduct meaningful code reviews, evaluate architectural tradeoffs, and engage credibly on implementation details
• Hands-on experience with AWS cloud-native services including API Gateway, ECS/EKS, IAM, CloudWatch, and networking — not just familiarity, but production ownership
• Experience building and operating event-driven architectures using Apache Kafka or equivalent event streaming platforms
• Experience with API gateway management, REST API design standards, and OAuth2/JWT authentication patterns in production environments
• Proficiency with infrastructure-as-code using Terraform and/or AWS CDK — all infrastructure version-controlled and peer-reviewed
• Experience with GitHub Actions or equivalent CI/CD tooling — building pipelines that deploy to containerized cloud environments
• Proven track record leading agile teams with sprint planning, backlog management, and delivery execution in a platform engineering context
• Bachelor’s degree in Computer Science, Software Engineering, or related discipline

Preferred

• Experience with Dynatrace or equivalent full-stack observability platforms (APM, distributed tracing, SLO management)
• Familiarity with Ping Identity products — PingFederate SSO, JWT token management, or Ping/OAuth2 identity flows
• Experience with MongoDB and per-service schema design in a microservices context
• Experience with HashiCorp Vault or equivalent secrets management platforms in a cloud-native environment
• Experience in financial services or insurance technology, including familiarity with downstream policy administration and financial transaction systems
• Exposure to AI-augmented development tooling — AI code review, automated test generation, or LLM-assisted PR analysis
• Experience operating within a full-stack engineering model where teams own their full delivery stack without discipline silos