Principal Enterprise Architect, Strategic Initiatives – ERP Program

Sherwin-Williams•Cleveland, OH

1d•Remote

About The Position

The Principal Enterprise Architect, Strategic Initiatives is the architecture owner for the company's largest multi-year business transformation programs, beginning with a cloud ERP program that replaces legacy ERP and boundary systems region by region in waves. The role owns the initiative's end-to-end architecture, including its target state, integration and data architecture, and current-state architecture for each release and wave. It serves as the architecture voice in program steering and design forums and as the counterpart to system integrators. The work is hands-on and includes maintaining architecture, reviewing designs, resolving cross-workstream conflicts, and preparing roadmap options for leadership decisions. This is a remote position. The role is not eligible for work-authorization sponsorship now or in the future. The company requires a criminal-history review because the role involves contact with employees and access to confidential, proprietary, or other valuable information. Applicants must be at least 18 years old. Travel is 10–15%.

Requirements

Must be at least 18 years of age.
Must be legally authorized to work in the country of employment without now or in the future requiring employment-visa sponsorship.
Bachelor's degree in Computer Science or Information Technology, or at least 18 years of experience in technology delivery in lieu of a degree.
At least 15 years in technology, including at least 5 years of hands-on software or systems engineering and at least 8 years in architecture or deep technical leadership roles.
Must have served as lead architect on at least one full-lifecycle, enterprise-scale, multi-wave Oracle Fusion Cloud ERP or SCM program through go-live and hypercare; advisory-only program experience does not qualify.
Deep knowledge of the boundary landscape around a cloud ERP, including warehouse management, transportation management, labeling, plant and quality systems, master data management, tax and banking, and connecting integration patterns.
Hands-on experience with ERP integration and data conversion, including Oracle Integration Cloud or equivalent middleware, Informatica or equivalent conversion tooling, master-data flows, and cut-over design.
Experience with multi-region rollouts, including global-template design, local variants, retrofits to earlier waves, and architecture version control by release.
Track record of producing and defending roadmap and scenario material for a steering committee and holding system integrators to an architecture.
Willingness to travel 10–15%.

Nice To Haves

TOGAF Level 2 certification.
CISSP certification.
CEAP certification.
CSA certification.
CSEA certification.

Responsibilities

Own the end-to-end architecture of the initiative, including the ERP core, boundary applications, integrations, and data flows across order-to-cash, source-to-pay, plan-to-produce, and record-to-report.
Maintain version-controlled current-state architecture for every release and wave, making process, application, and master-data changes from deployments and retrofits visible to the program, business, and architecture community.
Own the target-state and transition architecture for remaining waves and regions, including deployment sequencing, parallel operations, system retirements, and global-template versus local-variant decisions.
Produce roadmap options for leadership, including sequence, pause, accelerate, and consolidate scenarios with costs, risks, benefits, and dependencies for the steering committee.
Own the program's integration and data-conversion architecture, including integration patterns, conversion and migration approach, master-data flows, and cut-over design within enterprise standards.
Review internal-team and system-integrator solution designs for conformance to program architecture and enterprise standards, and hold integrators accountable to those standards.
Own non-functional architecture covering performance, resilience, hypercare readiness, and operability of end-to-end flows, along with remediation plans when releases fall short.
Align the initiative with Principal Portfolio and Practice Architects so it reuses enterprise platforms and retires legacy systems rather than expanding the landscape.
Serve as the architecture member of program steering and design authority forums and as the escalation point for cross-workstream architecture conflicts.
Transfer program architecture knowledge to Solution and Domain Architects to build the bench and reduce dependence on one person.