2027 Summer Intern, MS/PhD, Software Engineer, Multiverse

Required

• 8+ years of relevant experience, including 5+ years of technical program management delivering hardware, embedded, or device-to-cloud products.
• A hands-on security background (e.g., security engineering, embedded or firmware security, product security architecture). You can explain how security controls work, how they fail, and what they cost to build, and you act as a technical peer to security and systems engineers.
• Experience delivering security capabilities on shipped hardware or embedded products, such as secure or verified boot, hardware roots of trust (HSM, TPM, secure element, TEE), PKI and key management, code signing, secure OTA updates, or authenticated communication.
• A track record of delivering cross-functional programs through teams you did not manage, including getting security work prioritized against competing product goals.
• Experience framing technical risk for decision makers and driving decisions through to execution, with clear communication to both engineers and executives.
• A BS in Computer Science, Electrical or Computer Engineering, Cybersecurity, or equivalent practical experience.
• Prior engineering experience in security, firmware, or embedded systems before moving into technical program management.
• Experience securing production fleets of connected devices (vehicles, robots, drones, consumer or industrial devices), including vulnerability response and verifying remediation across the deployed fleet.
• Experience with secure manufacturing at contract manufacturers: device identity, key injection, and factory signing infrastructure.
• Experience with real-time or in-vehicle networks and their security (e.g., CAN/CAN FD, Automotive Ethernet, SecOC, diagnostic authentication), or with safety-critical systems (e.g., ISO 26262, DO-178C, IEC 61508).
• Familiarity with product security standards and regulation (e.g., ISO/SAE 21434, UN R155/R156, IEC 62443, EU Cyber Resilience Act, FIPS 140-3) and threat analysis methods (TARA, STRIDE); experience building release security metrics and exception and risk-acceptance processes.
• Travel requirements: