Senior IT Solution Architect - Logistics Integrations

IT Solution Architect

CEVA Logistics provides global supply chain solutions to connect people, products, and providers all around the world. Present in 170+ countries and with more than 110,000 employees spread over 1,500 sites, we are proud to be a Top 5 global 3PL.

We believe that our employees are the key to our success. We want to engage and empower our diverse, global team to co‑create value with our customers through our solutions in contract logistics and air, ocean, ground, and finished vehicle transport. That is why CEVA Logistics offers a dynamic and exceptional work environment that fosters personal growth, innovation, and continuous improvement.

DARE TO GROW! Join CEVA Logistics, and you will be part of a team that values imagination and continued learning and is committed to excellence in everything we do. Join us in our mission to shape the future of global logistics. As we continue growing at a fast pace, will you “Dare to Grow” with us?

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).

• 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.
• 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).
• 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.
• 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.
• 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).
• 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.

• 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.
• This role is primarily deployed on programs that present non‑standard, complex, or high‑risk requirements – such as new technical components or custom integrations,…