If you're interested, please send me a copy of your resume and the following details as soon as possible
Candidate Details
- Last 4 Digit of SSN-
- Date of Birth (DOB) - MM/DD --
Job Description:
Project Scope
AEI (Aetna Enterprise Integrations) is an enterprise-wide integration function responsible for designing and defining integration solutions across the organization. The team produces integration artifacts that translate high-level solution architecture into actionable, implementation-ready designs for delivery teams.
The current environment is heavily service-oriented (SOA), with an ongoing transition toward microservices and event-driven architecture. The organization follows an API-first approach and leverages standardized enterprise data models to ensure consistency across domains.
Integration solutions are primarily built on IBM App Connect Enterprise (ACE), interfacing with mainframe systems (z/OS), and orchestrating across distributed services.
Current State: Centralized orchestration using IBM ACE
Target State: Decentralized Spring Boot microservices with event-driven patterns
Team Size & Structure
- ~50 Integration Architects (IA team)
- Centralized integration function supporting the enterprise
- Key stakeholders include:
- Product Owners (PO)
- Solution Architects (SA)
- Delivery Teams (Development & QA)
Development Methodology
- Primarily Waterfall at the program level, with iterative design practices within delivery cycles
- API-first development approach
- Adoption of Domain-Driven Design (DDD) principles
- Balance between:
- Canonical enterprise data models (for consistency)
- DDD bounded contexts (for domain autonomy)
- Strong emphasis on standardized naming conventions and cross-domain alignment
- Ongoing architectural evolution:
- SOA Microservices / Event-Driven Architecture
Key Responsibilities
- Translate high-level solution architecture (from PO/SA) into detailed integration designs
- Design APIs, services, and orchestration flows
- Develop API specifications using OpenAPI 3.0 (YAML)
- Apply RESTful design principles with a strong emphasis on design rationale
- Evaluate trade-offs and ensure long-term sustainability of integration solutions
- Provide feedback and influence architectural decisions made by Solution Architects
- Ensure alignment with enterprise standards (API-first, DDD, canonical models)
- Produce clear, consumable artifacts to support delivery team implementation
- Serve as a design authority across integration domains
- Collaborate with both technical and non-technical stakeholders
Note: This is not a hands-on development role, but requires strong technical depth to effectively design, review, and guide implementation.
Required Qualifications
Core Concepts
- Deep understanding of API design and REST principles (focus on why vs. how )
- Strong knowledge of Microservices architecture and SOA
- Domain-Driven Design (DDD) and canonical data modeling
- API-first development using OpenAPI 3.0
- Event-driven and loosely coupled architectures
- Strong design thinking, analytical reasoning, and problem-solving skills
- Ability to clearly communicate design intent, trade-offs, and architectural decisions
Tools & Technologies
Preferred Qualifications (Nice-to-Haves)
- Experience with API modeling tools (e.g., RSA or similar model-driven tools)
- Healthcare industry experience
- Familiarity with hybrid / poly-cloud environments (on-prem + cloud integrations)
- Exposure to API proxy patterns and enterprise API governance
- Understanding of legacy/mainframe integrations (z/OS)