Solution Architect – Supply Chain Engineering

The candidate may come from a strong Java, Microsoft / .NET, enterprise application architecture, cloud, integration, or platform engineering background.

Strong exposure to Java-based enterprise systems is valuable, but candidates with strong Microsoft / .NET enterprise architecture experience are also relevant if they demonstrate architecture breadth, integration thinking, data/platform maturity, and ability to operate across heterogeneous enterprise platforms.

The key requirement is not mastery of one programming language, but the ability to design scalable enterprise solutions across:

enterprise applications

integrations / APIs

data flows

platform components

security, resiliency, and maintainability considerations

engineering and operational realities

Experience in Retail / Supply Chain technology environments.

Exposure to complex enterprise ecosystems involving multiple applications, integrations, data flows, and vendor / partner platforms.

Experience with data readiness, analytics enablement, AI enablement, or AI-assisted engineering initiatives.

Experience building reusable architecture standards, technical playbooks, reference designs, or modernization roadmaps.

Experience working with global engineering teams, technology specialists, CoPs, and architecture governance forums.

Enterprise solution architecture

Application and platform architecture

Integration architecture and API patterns

Data flow and data readiness thinking

Architecture governance and design reviews

Reusable architecture patterns and reference designs

Supply Chain / Retail technology understanding

AI-readiness mindset

Cross-team technical influence

Technical documentation and knowledge sharing

This role is not:

A narrow application architect for one platform.

A pure Java, .NET, integration, or platform specialist with limited enterprise architecture breadth.

A day-to-day delivery manager.

A replacement for existing technology specialists or architecture teams.

An additional management layer.

A role that works independently of Staples’ existing technology, architecture, and CoP ecosystem.

Instead, this role is intended to strengthen architecture consistency, platform scalability, integration maturity, data readiness, reusable solution patterns, and future technology direction across Supply Chain SDS.

Success in this role would include:

Reusable architecture patterns established for priority Supply Chain Engineering areas.

Stronger alignment with Staples’ technology standards, CoPs, and architecture practices.

Improved integration and cross-platform solution consistency.

Better visibility into platform dependencies, data flows, and modernization opportunities.

Stronger data and AI-readiness foundation for future initiatives.

Improved solution quality and architecture consistency across teams.

Reduced technology fragmentation through practical architecture guidance and reusable patterns.