Sr. Supply Chain Systems Architect

Nextpower•Fremont, CA

About The Position

Owns the architecture of systems that plan, source, make, move, and fulfill products, ensuring they work together as a coherent landscape. This is a hands-on senior role with enterprise influence, partnering with Supply Chain, Operations, Sourcing, Logistics, and Planning, as well as Engineering and Finance, to translate business operations into target-state architecture. The role owns architecture and shares accountability with the IT delivery team for building it at an accelerated pace. The architect works across the full supply chain, from planning and sourcing through manufacturing, movement, fulfillment, and returns. They assess existing processes and systems, identify gaps and risks, simplify or standardize processes before automating them, and guide delivery of improvements. They also own integration patterns and master data across ERP, PLM, planning, WMS/TMS, and supplier portals, and develop a multi-year roadmap for application rationalization, migrations, technology decisions, and acquired-business onboarding. Nextpower develops integrated clean-energy technology for utility-scale power plants, combining structural, electrical, and digital solutions. Its platform is intended to help customers deliver projects faster and improve performance and reliability as solar power plants are designed, built, and operated.

Requirements

15+ years of experience in supply chain technology.
At least 5 years as an architect or technical lead on multi-system landscapes.
Bachelor’s degree in Engineering, Computer Science, or a related field.
Deep, practical understanding of end-to-end supply chain processes and credibility in design discussions with supply chain leaders and process owners.
Hands-on knowledge of BOM and engineering-change management, multi-echelon inventory, constrained supply and allocation, supplier collaboration, landed cost, and trade compliance.
Understanding of how process decisions—including planning cadence, lead time and safety-stock policy, and sourcing rules—shape data models and integrations.
Architecture experience across ERP, PLM, planning, and WMS/TMS platforms; examples include Oracle Fusion Cloud SCM, SAP, Blue Yonder, and Kinaxis.
Strong integration and data architecture knowledge, including APIs, event-driven patterns, iPaaS/EDI, and master data governance.
Experience leading architecture through a major transformation, such as an ERP migration, platform consolidation, or post-acquisition integration.
Experience with emerging supply chain technology, such as AI/ML-driven planning and forecasting, control towers and digital twins, intelligent automation, and composable cloud-native architectures, with sound judgment about production readiness.
Ability to explain architecture trade-offs clearly to supply chain executives and engineers and collaborate across functions to influence outcomes.

Nice To Haves

Experience unifying an acquisition-built portfolio under a shared architecture, including PLM-to-ERP and procurement consolidation.
Master’s degree in Supply Chain, Engineering, or Computer Science, or an MBA.
TOGAF or ASCM (CSCP/CPIM) certification.

Responsibilities

Work with supply chain stakeholders and the IT delivery team to understand current business operations, assess gaps and pain points, and define future-state architecture.
Analyze end-to-end supply chain flows and identify system boundaries, handoffs, or data gaps that create cost, delay, or risk.
Challenge legacy workarounds and design processes and systems together, simplifying or standardizing processes before automation.
Drive delivery of architectural patterns and improvements in close collaboration with technical teams.
Identify quick wins and deliver solutions that fit the overall architecture.
Advise on and pilot emerging technologies to address supply chain problems.
Design resilience, security, SOX, and trade-compliance controls into the architecture.
Own integration patterns and master data across ERP, PLM, planning, WMS/TMS, and supplier portals, including the PLM-to-ERP handoff.
Build a multi-year roadmap, rationalize overlapping applications, sequence migrations, make build/buy/retire decisions, and onboard acquired businesses.