SAP Architect

About the Role

Microvast runs SAP S/4HANA on RISE as the backbone of its global battery manufacturing business, with company codes and business processes spanning the US, Germany, and China. Following our S/4HANA upgrade, priority has shifted from implementation to disciplined operation: every change to the system needs to be tracked, justified, documented, and reflected in our process and architecture documentation. The SAP Architect owns that discipline. This is not a hands-on-keyboard configuration role, though you need the technical depth to review and challenge configuration and development work. Your job is to keep the SAP landscape documented and audit ready as the business changes it.

Primary Responsibilities

• Change request governance: Own the intake, tracking, and disposition of all SAP change requests affecting business processes, from submission through deployment and documentation closure.
• Run the SAP change advisory process: assess business justification, cross-module impact, SOX/ITGC implications, and licensing impact (FUE) before changes are approved.
• Maintain a single system of record for design documentation and change requests with status, ownership, approvals, and links to transports and documentation.
• Business process documentation and architecture: Build and maintain the current-state business process documentation library for all SAP-supported processes, covering US, Germany, and China variants.
• Create as-built architecture diagrams for all existing SAP solutions where none exist today, then keep them current: system landscape, integration map, data flows, custom development inventory, and authorization concept.
• Define the documentation standard and hold process owners to it.
• Ensure every approved change request results in updated process documentation and diagrams before the change is considered closed.
• Architecture and advisory: Own SAP solution design decisions, review custom development for architectural fit and remediation debt, and support annual ITGC audit cycles.
• Team development and mentorship: Develop the architecture mindset within the current SAP functional team, write the reference documentation set, and coach functional team members and offshore consultants.

What You Bring

• 10+ years in SAP roles, with at least 3 years in architecture or design authority capacity on S/4HANA (RISE experience strongly preferred).
• Working knowledge across at least two core modules (FI/CO plus supply chain or manufacturing).
• Demonstrated experience running a change governance process in a SOX-regulated environment.
• Strong documentation practice, with experience with process documentation and diagramming tools (Visio, Draw.io, or equivalent) and ITSM platforms for change tracking.
• Track record of mentoring functional consultants or module leads.
• Ability to work hours that overlap with Microvast Power Systems (China) and Germany operations, with early-morning availability (US Central) several days a week.

Preferred Qualifications

• Manufacturing or process industry background (battery, chemicals, automotive, energy).
• Exposure to SAP BTP, integration suite, and clean core extension patterns.
• TOGAF or SAP Enterprise Architecture certification.

First-Year Outcomes

• A functioning SAP change request process with 100% of production changes tracked, approved, and documented.
• As-built architecture diagrams completed for all existing SAP solutions, and current-state process documentation in place for all Tier 1 & 2 processes.
• The reference documentation set published and adopted as the team standard, with at least two functional team members independently producing documentation that meets it.
• A documentation-debt backlog from the S/4HANA upgrade identified, prioritized, and at least 50% retired.
• A catalog of all custom objects in existing SAP environment mapped to process and stakeholders.

Why This Role Matters

Microvast’s SAP environment supports financial reporting for a NYSE-listed company across three regulatory jurisdictions. Undocumented changes become audit findings. Knowledge that lives only in people’s heads leaves when they do. This role exists to close both gaps.