IT Project Manager

Job Title: IT Project Manager
Location: Palo Alto California 94304 (Hybrid)
Type: Contract
Duration:  4 months initial term, with conversion to full-time employment possible based on performance
Schedule: 8-5 (1 hour non-billable lunch) Mon-Fri

• The IT interface has grown organically alongside the joint venture. Systems, network paths, access models and support routes exist and work, but they are documented unevenly and depend heavily on individual knowledge. This role produces the written baseline for that interface and converts ad-hoc support into a defined process owned by Enterprise IT.
• This is a documentation and process role, not a build role. Success means that six months after the contract ends, someone new can operate the interface from the artifacts you leave behind.

• System inventory. A complete register of IT systems used across the VWG/RVT interface: 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.

• Enterprise IT Architecture
• Hands-on IT Project Manager
• IT Operations and Support

• IT Network Analyst
• IT Security