Technical Project Manager (Hardware Testing)

Profile Focus: A hands-on technical executor who can test environments, write and maintain documentation, and manage deployments.

On-Site Presence in SVL: Both roles may be required to come onsite to SVL office as on-site collaboration is needed and for occasional hardware testing.
Professional Executive Presence: While these roles are not required to directly service executives, the candidates will be in a building where senior leadership are present. Professional communication and appropriate attire are needed while working onsite.
Self-Directed Work Style: We need proactive executors who can take a defined outcome, complete the work independently, self-starters and are willing to take initiative to take documentation of process, can collaborate with team members effectively, and participate in periodic intermediate check-ins, rather than requiring daily micro-management.
Testing & Vetting (RACI Phase 2): Testing new content types within the Boba 2.0 and Chameleon environments to ensure they run smoothly before global deployment. Testing complex physical installations on-site. This may include interacting with touchscreens, multi-screen synced canvas architectures, and physical peripherals that provide input or output such as RFID readers and printers.
Technical Documentation (RACI Phase 3): Writing detailed technical setup guides for the BOM and creating short "Train-the-Trainer" setup videos so local site technicians can deploy demos easily.
Pipeline Deployment (RACI Phase 4): Working closely with FTE and XRX to support the daily deployment pipeline by uploading approved assets to Feltboard and scheduling "Boba Bubbles" across global screens.
Lifecycle Auditing (RACI Phase 6): Work with Creative Producer, XRX team members, and FTEs to conduct physical/technical audits to remove expired or broken demo assets from the Feltboard rotation, document the changes as needed.
Internal Utilities creation as a part of the regular day to day operations responsibilities suggest and potentially implement utilities as either shell scripts or small cloud functions to perform selective tasks in a routine manner. (this could be combined with phase 4)