This position defines and communicates a shared architectural vision for a complex product (highly integrated, multiple applications) that supports current and future business needs. The architect collaborates with Agile teams to consider solutions, validate technology assumptions, evaluate alternatives, and converge on a solution, and works closely with Enterprise and Solution Architects to deliver solutions aligned to the broader architecture guardrails.
This role owns the integration architecture for Eaton's external, API-first layer. This includes designing how External Customer platform and the back-end engines (Salesforce Commerce Cloud, External facing Commerce platform, ERP platforms, MuleSoft, Apigee, Azure Services, Redis Cache, Data Platforms, and third-party applications) connect to external customers and partner-hosted APIs, and defining the standards, patterns, and framework for External APIs push + pull modernization.
- Own the integration strategy and define the future-state architecture aligned with business and digital transformation goals.
- Design and govern scalable, secure, and reusable integration solutions across the developing platform.
- Establish API-led connectivity standards, API governance, and reusable integration patterns to enable seamless data exchange across systems.
- Provide architectural oversight, review solution designs, enforce standards, and ensure compliance with enterprise architecture principles.
- Ensure integration solutions meet security, compliance, data privacy, and operational risk requirements across all connected systems.
- Define standards for integration performance, availability, monitoring, and operational support to ensure stable and reliable services.
- Support the successful delivery of integration initiatives through standardized design approaches, CI/CD adoption, automation, and release governance.
- Own end-to-end integration designs (REST API and MuleSoft) and unblock the build team through timely design reviews
- Define integration standards, reusable patterns, and a framework for consuming partner-hosted APIs
- Design for throughput, reliability, and observability (monitoring, end-to-end tracing, SLAs), addressing External APIs timeout and throughput issues
- Architect event-driven / push integration (webhooks, pub/sub, messaging) alongside existing pull APIs
- Partner with Identity (Okta / Saviynt) to design external-customer authentication and coarse/fine-grained entitlements at the integration layer
