IPaaS Engineer

Role Summary

Designs, builds, and supports integrations between enterprise applications using iPaaS platforms (e.g., Boomi, MuleSoft, Workato), enabling reliable real-time and batch data flows across Aon's global business.

Key Responsibilities

•     Design, build, test, and deploy integrations between enterprise systems (ERP, CRM, HRIS, finance) using iPaaS tooling

•     Develop real-time and scheduled integrations supporting processes such as order-to-cash, procure-to-pay, and master data synchronization

•     Implement robust error handling, logging, monitoring, and retry mechanisms for integration reliability

•     Collaborate with business/functional consultants to translate requirements into technical integration designs

•     Manage API integrations (REST/SOAP), data mapping/transformation, and data quality validation

•     Monitor integration performance and resolve incidents within SLA

•     Maintain integration documentation, runbooks, and reusable connector/component libraries

•     Support platform upgrades and governance of the iPaaS environment (connections, environments, access)

Required Qualifications & Experience

•     Bachelor's degree in Computer Science, Information Systems, or a related field

12+ years in IT infrastructure

•     3-6 years of experience building integrations, with hands-on experience on at least one iPaaS platform (Boomi, MuleSoft, Workato, Tray.io, or similar)

•     Experience integrating enterprise systems such as Salesforce, Workday, NetSuite, SAP, or similar

Technical Skills

•     iPaaS platforms: Boomi, MuleSoft, Workato, Tray.io (at least one, hands-on)

•     API integration: REST, SOAP, JSON, XML, event-driven/API-led patterns

•     Scripting: Groovy, JavaScript

•     SQL and relational databases

•     Enterprise application connectors (Salesforce, Workday, NetSuite, SAP, ADP)

•     Monitoring/error handling and integration security (OAuth, API keys, certificates)

Core Competencies

•     Strong analytical and problem-solving skills

•     Attention to detail in data mapping and validation

•     Effective collaboration with business and technical stakeholders

•     Ownership of integration reliability and incident response

•     Clear technical documentation