XUS_LATAM_IntegrationEngineer

Required Skills and Qualifications

•
10-12 years

Description of Skills/Needs : Role Summary Design, build, and operate custom integration flows for a Product Catalog program built around a centralized digital catalog platform. This platform manages a rich, multi-attribute product data model where a significant portion of the attributes are generated or enriched through integrations — not entered manually. Keeping that data accurate, complete, and timely depends entirely on integration quality. The connected ecosystem is heterogeneous and complex, spanning ERPs, e-commerce and retail platforms, internal proprietary APIs, and external supplier systems — each with distinct protocols, data formats, and latency requirements. Because no off-the-shelf iPaaS or ESB will be adopted for this program, the engineer must be capable of building integration logic from the ground up: designing lightweight custom middleware components, implementing transformation and routing logic in code, and ensuring production-grade reliability across all flows. The engineer will work iteratively alongside a Tech Lead and product stakeholders, translating integration requirements into deliverable work packages from discovery through go-live and stabilization. 2. Integration Ecosystem The integration surface covers four distinct source / target domains: ERPs (SAP, Oracle, or equivalent) — master product data, pricing, and supply chain feeds that populate core catalog attributes. E-commerce and retail platforms — inbound catalog requirements and outbound product content distribution to sales channels. Internal proprietary APIs — custom services exposing business rules, digital assets, and operational data that enrich product records. External supplier and partner systems — heterogeneous formats, variable SLA, limited API maturity; often the most demanding integration surface. Integration patterns in scope include synchronous REST/SOAP APIs, file-based batch pipelines (SFTP/FTP), webhook and event-driven flows, and scheduled reconciliation jobs. No single pattern dominates; the engineer must be comfortable operating across all of them. A core challenge of this program is ensuring that integration-generated attributes arrive with correct structure, at the right moment in the product lifecycle, and in the exact format expected by the catalog data model. Data quality at the integration layer directly determines catalog completeness. 3. Required Qualifications Software Engineering Foundation Proficiency in at least one general-purpose backend language (Python, Node.js/TypeScript, Java, or equivalent) to build integration components from scratch. Ability to design and implement lightweight custom middleware: routing, transformation, retry logic, error handling, and dead-letter queues — without relying on iPaaS tooling. Strong understanding of data serialization formats: JSON, XML, CSV, flat files, and EDI variants. Experience building and consuming REST and SOAP APIs; familiarity with OAuth2, API keys, and basic auth schemes. Integration Patterns & Protocols Hands-on experience with file-based pipelines: SFTP/FTP ingestion, scheduling, retry/backoff strategies, and reconciliation reporting. Experience implementing webhook consumers and event-driven flows (polling, push, at-least-once delivery guarantees). Ability to design idempotent processing logic to handle duplicate events and partial failures safely. Familiarity with data validation, schema enforcement, and attribute-level transformation mapping between source and catalog data models. Operational Readiness Proven ability to implement monitoring, alerting, and structured logging for production integration flows. Experience building runbooks, interface specifications, mapping documents, and handoff materials for support teams. Strong end-to-end troubleshooting skills: able to trace failures across transformation logic, transport layer, and target system. Experience supporting release planning, cutover coordination, and post-go-live stabilization. 4. Responsibilities Work with the Tech Lead and stakeholders to translate integration requirements into scoped, deliverable work packages. Architect and develop custom integration components (inbound and outbound) connecting the digital catalog platform to the enterprise ecosystem. Ensure integration-generated product attributes arrive correctly structured, well-timed, and compliant with the catalog data model. Implement transformation logic, routing rules, error handling, retry strategies, and reconciliation reporting in code. Build monitoring and alerting coverage for all integration flows; ensure failures are visible and actionable. Maintain up-to-date documentation: interface specs, data mappings, runbooks, and SOPs. Participate in Agile ceremonies (sprint planning, reviews, retrospectives); support continuous delivery and incremental releases. Support cutover planning and provide hands-on stabilization during and after go-live. Produce handoff materials and knowledge-transfer documentation for production support teams. 5. Nice to Have Experience integrating with PIM, PXM, or digital catalog platforms — particularly their import/export APIs, channel configuration, and attribute/data model conventions. Experience integrating SAP (IDocs, BAPIs, or REST/OData APIs) or Oracle ERP systems. Familiarity with message broker or queue patterns (RabbitMQ, Kafka, AWS SQS, or equivalent) for async flows. Prior involvement in product catalog, PIM, or MDM implementation programs. Experience working in nearshore / distributed Agile teams across LATAM or US time zones. 6. What This Role Is Not This is not an iPaaS configuration or drag-and-drop middleware administration role. There is no pre-existing integration platform to configure. The engineer must be comfortable writing integration logic in code, making architectural decisions in collaboration with the Tech Lead, and operating in an environment where the middleware layer is being built — not purchased. Candidates with exclusively low-code or visual-mapping integration backgrounds will not have the depth required for this engagement. Version 2.1 — Revised March 2026 — PDP /