Infrastructure Security Engineer, Runway

• Hands-on experience securing Kubernetes in production: you've written admission policies, debugged RBAC and workload identity problems and understand how a cluster gets compromised
• Working knowledge of cloud IAM and networking on at least one major cloud platform, including how identity federation and short-lived credentials actually work
• Experience with infrastructure as code and GitOps-style deployment, and the habit of shipping security changes through the same pipeline as everything else
• Comfort writing Python, Typescript, Rust or another language to build tooling, not just scripts
• An understanding of software supply chain attacks and the controls that stop them: signing, provenance, SBOMs, admission enforcement
• Clear writing. Design docs, threat models and explanations to engineers who don't work in security are all part of the job
• Judgment about which controls to enforce, which to recommend and how to roll out a breaking change without breaking the company

Desirable

• Runway is hiring an Infrastructure Security Engineer to secure the platform our models are trained and served on. The role covers Kubernetes platform security, cloud identity and access, software supply chain, tenant isolation in the serving layer and the research infrastructure behind our models
• Securing a company that trains and serves frontier video models is a different problem from securing a typical SaaS product. The environment includes research compute, large training datasets, a fast-moving build pipeline, and engineers who work inside AI-assisted tooling every day. Each of those changes what an attack looks like and what the platform has to enforce to stop it
• This is a hands-on engineering role on the Security team. You'll write policy, tooling and infrastructure code, work in the platform team's repositories, and ship controls that hold up in production
• Design and ship security controls in our Kubernetes ecosystem: admission policy, RBAC, workload identity, network policy and runtime hardening across every cluster we run
• Harden the software supply chain from dependency intake through build and deploy, including package firewalling, artifact signing and provenance, and admission controls that block what doesn't pass
• Own cloud IAM and identity architecture: least-privilege roles, short-lived credentials and workload federation
• Secure research infrastructure and training pipelines, including access to model weights and datasets, without slowing down the people using them
• Threat model new platform components before they ship and turn the findings into concrete requirements the owning team can act on
• Build guardrails for AI agents and developer tooling operating inside our infrastructure
• Write infrastructure as code and policy as code, and treat security configuration with the same review and rollout discipline as any other change
• Give the incident response team what they need when infrastructure is involved: fast answers about how a system works and what to shut off