Global Enterprise and Solution Architecture Expert

Job description:

Role Summary The Solution Architect (Contract Logistics IT CoE) is a senior design authority responsible for end-to-end solution architecture on complex, multi-system contract logistics programs. As a cross-domain expert, this role ensures that all components of a solution - from WMS, TMS, and OMS to integrations, automation, and customer systems - are architected into a holistic, cohesive design. The Solution Architect engages early (pre-sales/demand stage) and stays involved through delivery to guarantee technical integrity, bridging application silos and preventing late-stage design gaps. Two positions will be filled (one in Europe, one in the Americas), reporting into the CL IT CoE's Integration & Architecture unit, with coverage of their respective regions (and support to other regions as needed).

Key Responsibilities

End-to-End Solution Design: Own the overall technical design for assigned complex CL programs (multi-site or high-complexity implementations). Define how all solution components (WMS, TMS, OMS, integration middleware, automation, customer systems) will work together to meet requirements.

Early Engagement in Demand/Pre-Sales: Participate in opportunity shaping - reviewing new customer requirements at demand and RFP stage. Determine if the solution is standard vs. non-standard, and if complex or bespoke elements warrant Solution Architect involvement. Provide guidance on solution options and ensure proposed designs are viable and optimized (e.g. attend architecture board reviews).

Design Authority During Delivery: Act as the design authority throughout the project lifecycle. Make or approve key architecture decisions, ensuring domain architects’ and product teams’ designs align into a unified solution. Veto or adjust design choices when needed to safeguard end-to-end integrity.

Cross-System Integration: Develop and document integration architecture (interfaces, data flows, process touchpoints) across all systems in scope. Address cross-domain design questions (e.g. WMS-TMS-automation interactions), leveraging standard integration frameworks where possible.

Technical Oversight & Handover: During build and testing, oversee design adherence – verifying that implementation aligns with the approved architecture. Identify and resolve any design deviations or integration issues early. Sign off on technical readiness for go-live and ensure smooth handover of the solution design knowledge to Run/Support teams (in coordination with platform owners).

Continuous Improvement: Contribute learnings from projects to refine CL solution design standards, templates, and decision criteria (e.g. helping to maintain the "Solution Architect engagement decision tree"). Mentor other architects and solution designers in cross-domain best practices.

Decision Authority & Governance

Design Decision Rights: The Solution Architect is empowered with decision-making authority for solution design on assigned projects. They ensure all design decisions align with global architecture standards and business objectives. If necessary, unresolved design conflicts are escalated to formal governance bodies (e.g. Architecture Review Board or WMS/IT Design Authority boards) for guidance or approval of exceptions.

Scope of Triggers: This role is primarily deployed on programs that present non-standard, complex, or high-risk requirements - such as new technical components or custom integrations, cross-domain processes, significant automation, or strategic/high-value deals. For standard/templated implementations, the Solution Architect may not be engaged but remains available in an advisory capacity if a regional team requests a design validation ("sanity check").

Collaboration & Boundaries

Within IT CoE: Work within the Integration & Architecture team of the CL IT Centre of Excellence, partnering closely with Platform/Product Architects (WMS, TMS, OMS, Integration, Automation, etc.). The Solution Architect leverages their deep domain expertise and ensures each domain design fits into the bigger-picture solution.

Project Teams: Collaborate with Delivery Project Managers and IT Business Partners - especially at project kickoff and initial design phases. The Solution Architect provides architectural vision while the PM drives execution; the two work in tandem to balance ideal design vs. practical delivery considerations.

No Duplication of Roles: The Solution Architect does not replace Enterprise Architects, application-specific architects, or other domain experts, nor carry project management duties. Instead, the role complements these stakeholders by focusing on integration of all parts into a cohesive whole. The Solution Architect is not responsible for day-to-day project delivery or detailed configuration that falls to product teams - rather, they ensure those efforts collectively meet t