Odyssey
Member of Technical Staff, Security Engineering
- Location
- Palo Alto, CA, US
- Employment type
- Full-time
- Level
- Staff
- Posted
- 12 November 2026 (2 days ago)
Checked 2 days agoApplications go to the employer, never to RoleSprint
About this role
WHO WE ARE
Odyssey https://odyssey.ml is an AI lab pioneering general world models: causal, multimodal systems that learn to predict and interact with the world over long horizons. This foundational technology promises to revolutionize robotics, science, healthcare, education, gaming, defense, and beyond.
Odyssey’s founders previously pioneered the most complex application of physical AI: self-driving cars. They’ve now brought together a world-class research team from DeepMind, Tesla, Waymo, Meta, Apple, and Wayve, who have made significant contributions to language models (DeepMind Gemini), video models (DeepMind Veo), world models (Wayve GAIA), and autonomous systems (Tesla FSD).
Odyssey has raised significant venture capital from GV, Amazon, AMD, EQT, NVIDIA, Natural Capital, In-Q-Tel, Elad Gil, Jeff Dean, Guillermo Rauch, Garry Tan, Kyle Vogt, and researchers from OpenAI, DeepMind, MSL, Recursive, and Thinking Machines.
WHAT WE'RE LOOKING FOR
We’re hiring a MTS, Security Engineering to protect Odyssey’s research, models, data, and infrastructure. You’ll own our security priorities, build practical defenses, and work directly with researchers and engineers to keep our systems secure as we scale.
WHAT YOU'LL DO
- Map our most valuable assets, and devise strategies on how people, devices, and services can access, copy, or share them.
- Identify systematic risks through threat modeling and risk assessment, then build the controls and infrastructure that address them
- Strengthen security across cloud infrastructure, identity and access, secrets management, and development workflows.
- Create useful logs, detections, and incident response for account compromise, sensitive downloads, external sharing, and permission changes.
- Test defenses and recovery procedures, manage external security assessments, and drive remediation.
- Partner with People and Legal on data-handling practices, onboarding, and offboarding.
WHO YOU ARE
- 8+ years of software engineering experience with deep security expertise, including leading company-wide security initiatives independently.
- Track record of delivery in threat modeling, incident response, and prioritization, with clear communication across leadership, technical and nontechnical teams.
- Experience with cloud IAM, Linux, containers, networking, secrets, and CI/CD; familiarity with ML infrastructure is a plus.
- Experience managing penetration tests and external security partners.
- Clear communicator who works effectively with leadership and technical and nontechnical teams.
- Working knowledge of Kubernetes security primitives including RBAC, namespaces, network policies, and service accounts
- Passion for AI safety and the role security engineering plays in building trustworthy AI systems
Our staff is expected to be in office at least three times a week. A lot of our progress comes from working through problems together, and we want you in the room for that.
Work location
- Palo Alto, CA, US
Related jobs
Ready to make a decision?
This role is either worth your time or it isn’t.
Analyze the posting against your experience, see the gaps clearly, and build the right materials only if the opportunity makes sense.
Nothing is submitted automatically. You choose what happens next.
About this listing
Published on Ashby under the board identifier Odysseyml, which is the name the employer’s own job board carries. RoleSprint has not verified the company’s registered or trading name, so it is shown exactly as published rather than tidied up.
RoleSprint is not the employer and not a recruiter. Applications are made on the employer’s own site and never reach us; what RoleSprint does is help you decide whether a role is worth your time and prepare for it if it is.
Published 12 November 2026, last checked 2 days ago. A posting stops being advertised here 90 days after the employer published it, and one the employer takes down is marked closed rather than quietly removed.