IBM API Connect/IIB Integration Architect

IBM API Connect/IIB Integration Architect

Posted 2 weeks ago by Tech Tandem Inc

Apply
Negotiable
Undetermined
Remote
Remote
Apply
Adaptive Communication Environments API Design API Gateway Application Programming Interface (API) Cloud Computing Cloud Technology Datamodel Data Modeling Design Elements And Principles Design Thinking Document-Oriented Databases Domain Driven Design Google Cloud Google Cloud Platform (GCP) IBM Software Information Architecture Management Microservices Multi-Cloud Naming Conventions OpenAPI RESTful API RSA (Cryptosystem) Solution Architecture Spring Boot Stakeholder Management YAML z/OS

Summary: The IBM API Connect/IIB Integration Architect role focuses on designing and defining integration solutions within an enterprise-wide integration function. The position requires translating high-level architecture into actionable designs, primarily using IBM App Connect Enterprise and transitioning towards microservices and event-driven architecture. The architect will collaborate with various stakeholders to ensure alignment with enterprise standards and produce clear artifacts for implementation. This role emphasizes strong technical depth without being hands-on in development.

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

Key Skills:

  • 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
  • Experience with IBM App Connect Enterprise (ACE)
  • Familiarity with Spring Boot and API Gateway evolution
  • Experience in multi-cloud environments (Google Cloud Platform preferred; AWS/Azure acceptable)

Salary (Rate): £66,000 yearly

City: undetermined

Country: undetermined

Working Arrangements: remote

IR35 Status: undetermined

Seniority Level: undetermined

Industry: IT

Detailed Description From Employer:
If you're interested, please send me a copy of your resume and the following details as soon as possible
    • 1st References Name-
      Title-
      Company -
      Email (Official email)
      Contact -
      2nd References - Name-
      Title-
      Company -
      Email (Official email)
      Contact -
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
  • IBM App Connect Enterprise (ACE) primary orchestration platform
  • Spring Boot strategic, forward-looking requirement
  • API Gateway evolution:
    • Transition from IBM API Connect (APIC) to Kong (runtime) and Apigee (management)
  • Containerization and deployment via OpenShift
  • Kafka (event streaming platform)
  • ODM (Operational Decision Manager) rules engine
  • Experience in multi-cloud environments (Google Cloud Platform preferred; AWS/Azure acceptable)
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)
Apply
Similar Jobs
Loading data...