Data Integration Lead

Job Description

COMPANY OVERVIEW

\n

American Bath Group is a North American manufacturer of bathware products with a portfolio of established brands serving residential, commercial, retail, wholesale, and showroom channels. The organization operates across multiple businesses and technology environments, creating a need for enterprise platforms and integration capabilities that can scale with the company while remaining practical for the teams that use them.

\n

\n

THE OPPORTUNITY

\n

American Bath Group is creating stronger internal ownership of enterprise integration and is looking for a senior technical leader to shape that capability.

\n

\n

The company already operates MuleSoft and a live integration landscape connecting important enterprise systems. The next stage is to make that environment more standardized, observable, reusable, and internally owned.

\n

\n

The Data Integration Lead will establish the architecture, standards, roadmap, documentation, support model, and technical leadership needed to scale integration across the organization. This person will work closely with ERP teams, Salesforce, application owners, EDI/B2B stakeholders, internal developers, and technology partners.

\n

\n

This is not an architecture-only position. The successful candidate must remain close enough to the technology to evaluate designs, challenge implementation choices, guide technical contributors, and understand what happens when integrations reach production.

\n

\n

SUCCESS IN YEAR ONE

\n

Success will mean that ABG has moved from individual integration delivery toward a more coherent enterprise integration capability.

\n

\n

The integration landscape should be better documented, architectural standards should be operating consistently, monitoring and exception handling should be materially stronger, and MuleSoft should be governed through a clear company-owned maturity roadmap.

\n

\n

The organization should also have stronger internal technical ownership, with knowledge, design authority, supportability, and reusable patterns residing inside ABG rather than being dependent on individual projects or external partners.

\n

\n

THE MANDATE

\n

Build an internally owned enterprise integration capability that can design, govern, scale, document, and support MuleSoft and EDI/B2B connectivity through reusable architecture, stronger observability, disciplined technical standards, and a clear operating roadmap.

\n

\n

The Data Integration Lead will own enterprise integration strategy and architecture while remaining close to implementation. This includes API standards, integration patterns, documentation, lifecycle discipline, monitoring, exception handling, design governance, partner direction, and the development of internal technical capability.

\n

\n

The role must create an operating model that can support the integration estate after projects go live, not simply deliver interfaces and move to the next request.

\n

\n

YEAR ONE CRITICAL OUTCOMES

\n

• Build a governed inventory of the enterprise integration landscape, including source and target systems, dependencies, technical ownership, and support context.

\n

• Establish standardized monitoring and exception-handling practices that make integration health visible and improve supportability after deployment.

\n

• Translate current platform assessments and business demand into an ABG-owned MuleSoft maturity roadmap and begin executing the highest-value architecture and governance priorities.

\n

• Establish reusable integration architecture, API standards, design patterns, and review practices that reduce one-off development and improve consistency across future work.

\n

• Strengthen internal ownership of integration architecture, technical knowledge, code/design review, and production support while using external partners selectively.

\n

• Establish meaningful reliability, incident, reuse, supportability, and vendor-management baselines so future improvement can be measured rather than assumed.

\n

\n

WHY THIS ROLE IS HARD

\n

The role sits between enterprise architecture and real delivery.

\n

\n

ABG already has live integrations, multiple enterprise applications, ERP environments, Salesforce, EDI/B2B requirements, current technology partners, and active demand. The new leader must improve the architecture while continuing to support business needs that cannot simply wait for a future-state model.

\n

\n

They will need to recognize where a one-time solution creates long-term support debt, establish standards without creating unnecessary bureaucracy, and build credibility with technical teams that already own important source and target systems.

\n

\n

The person who succeeds will be able to move comfortably from an enterprise integration roadmap to a detailed conversation about API design, event-driven versus batch patterns, monitoring, failure handling, or why a particular implementation will become difficult to support at scale.

\n

\n

LEADERSHIP PROFILE

\n

• A builder who creates durable technical capability rather than simply operating what already exists.

\n

• A technically credible integration leader who remains close enough to MuleSoft and production delivery to evaluate designs and guide technical contributors.

\n

• An enterprise systems thinker who can see individual integrations as part of a broader architecture rather than as isolated projects.

\n

• A standards builder who creates practical reuse, observability, documentation, and lifecycle discipline without slowing execution unnecessarily.

\n

• A player-coach who can provide architectural direction while helping internal technical capability grow.

\n

• A cross-functional translator comfortable working with ERP teams, Salesforce, EDI/B2B specialists, application owners, business stakeholders, and external technology partners.

\n

• A leader who deliberately transfers knowledge and decision authority into the organization rather than allowing external partners to become permanent owners of the architecture.

\n

\n

EXPERIENCE REQUIREMENTS

\n

• Hands-on MuleSoft experience in live enterprise integration environments, with enough technical depth to evaluate designs, guide developers, and challenge implementation decisions.

\n

• Prior ownership of an enterprise or organization-level integration strategy, architecture roadmap, or integration platform, rather than responsibility limited to individual projects.

\n

• Demonstrated architecture experience with API-led connectivity, reusable integration patterns, event-driven architecture, and batch versus real-time design.

\n

• Experience establishing or operating integration governance, API/design standards, lifecycle practices, documentation, and production supportability.

\n

• Working knowledge of EDI/B2B integration and the ability to partner effectively with deeper subject-matter specialists where needed.

\n

• Experience working across ERP and other enterprise application environments with complex source/target dependencies.

\n

• Demonstrated ability to build or strengthen internal technical capability in an environment that also uses external implementation partners.

\n

• MuleSoft certifications, deeper EDI standards experience, broader iPaaS exposure, event-streaming, ETL/ELT, data-governance, or master-data experience can accelerate ramp but are not substitutes for demonstrated integration ownership.

\n

\n

WHY THE RIGHT CANDIDATE WILL BE EXCITED

\n

This role offers the opportunity to shape an enterprise integration capability rather than inherit a finished model.

\n

\n

The successful candidate will have meaningful influence over architecture, engineering standards, platform maturity, team capability, supportability, and how ABG uses external partners. They will be able to establish technical practices that become the foundation for how future systems connect across the organization.

\n

\n

For someone who enjoys building systems that outlast individual projects, this is a chance to leave behind reusable architecture, stronger internal expertise, and an integration operating model that can scale with the business.

\n

\n

WHY THIS ROLE MATTERS

\n

Enterprise systems create value only when information can move between them reliably and in a way the organization can support.

\n

\n

As American Bath Group operates across multiple businesses, applications, and technology environments, integration becomes an enterprise capability rather than a series of isolated technical projects. The Data Integration Lead will help determine whether that complexity becomes easier to manage as the organization grows or increasingly dependent on one-off solutions.

\n

\n

This role gives ABG the internal ownership necessary to build the former.