Our client, a well-known electric vehicle manufacturer that develops off-road and utility vehicles is hiring an IT Project Manager to join their joint venture system engineering team in Palot Alto, CA.
Our client has built an arm of the business that partners with other OEMS to design and build a shared software platform and electrical architecture for electric vehicles. This team needs an IT Project Manager to help map and integrate internal IT systems. Currently, the systems across both OEM's are not well documented and rely on individual knowledge. As a Project Manager, you would help document and map system integrations and build knowledge base articles. The ideal candidate would have previous experience leading end-to-end system architecture, permissions and governance, and building intake forms.
** This is not a "build" project manager role.**
Requirements
- Bachelor's Degree or related field
- 6+ years of recent software project management experience
- End-to-end system integration and system mapping experience
- Strong system documentation and knowledge base management experience
- Experience creating technical intake forms
- Experience presenting and working with stakeholders
What You Will Do:
- System inventory. A complete register of IT systems used across the OEM's interface
- Understand purpose, owner on each side, hosting model, data flows, integration points, licensing and contract references.
- Architecture and configuration documentation. Per system and end to end: network topology and routes, firewall rules and IP allowlists, VPN and proxy paths, DNS, authentication and identity model, user and group structures, role definitions, and joiner-mover-leaver handling.
- Data protection documentation. GDPR records of processing for the interface systems, controller/processor roles, DPAs and transfer mechanisms for EU-US flows, data classification and retention mapping, and the control evidence relevant to the RVT TISAX scope.
- Stakeholder map. Named roles on both sides for each system: business owner, technical owner, security, data protection, procurement, escalation path, and current de-facto contacts where these differ from the formal ones.
- Support process concept. Intake channels, ticket categories, severity definitions, response and resolution targets, escalation ladder with named contacts, on-call expectations, and the interfaces to existing VWG and RVT service desks.
- Stakeholder alignment. The concept reviewed and signed off with owners on both sides, with dissent and open points documented rather than smoothed over.
- Handover to Enterprise IT. Runbooks, working sessions, a transition checklist, and a defined acceptance point at which Enterprise IT owns the process.
- Criticality assessment. Identification of critical systems and single points of failure, with concrete measures (redundancy, documented workarounds, named backups for key people, monitoring gaps) to make support sustainable beyond the contract.