AI Infrastructure Engineer, Sandbox Platform

Scale AI · London, UK · Horizontals EPD · listed July 23, 2026

The shape of it

Seniority
Mid level
Experience asked
4+ years
Where
Remote
Requirements listed
7
Length
774 words

In the posting’s own words

As a Software Engineer on the AI Infrastructure team, you'll help build and evolve our agent sandboxing platform — the secure, high-performance code execution layer powering our agentic workflows, deployed across both internal and customer-managed environments. This is a role for someone who cares as much about the experience of the engineers and researchers using this system as they do about the kernel internals underneath it.

What it asks for · 7

  • 4+ years of experience building high-performance systems software, with meaningful time spent maintaining libraries, SDKs, or developer-facing APIs
  • Experience with containerisation and virtualisation technologies (e.g., Docker, Firecracker, gVisor, QEMU, Kata Containers)
  • Proficiency in a systems programming language such as Go, Rust, or C/C++
  • A track record of obsessing over developer experience — API design, error propagation, documentation, and the small details that make a library feel well-crafted
  • Strong debugging skills and the ability to navigate performance/security tradeoffs in production systems
  • Comfort with ambiguity, and the ability to context-switch between reactive incident work and proactive product development
  • Familiarity with LLM agents and agent frameworks (e.g., OpenHands, Agent2Agent, MCP)

Also a plus

  • Experience as a founder or early engineer at an infrastructure-focused startup, owning a product end-to-end
  • Familiarity with LLM agents and agent frameworks (e.g., OpenHands, Agent2Agent, MCP)
  • Experience running secure workloads in multi-tenant or untrusted environments (e.g., FaaS, CI sandboxes, remote notebooks)
  • Exposure to snapshotting and restore techniques (e.g., CRIU, VM snapshots, overlays)
  • Open-source contributions to systems or developer-tools projects
  • History of on-call/incident response for production systems

Tools and skills named

Cloud & infra
  • Docker
  • Kubernetes
  • Linux
Languages
  • C++
  • Go
  • Rust
Ways of working
  • Cross-functional
  • On-call
  • Technical writing
Product & design
  • Roadmap2×
Security & compliance
  • Security2×
Models & research
  • LLM

Words the posting leans on

  • experience7×
  • systems7×
  • e.g5×
  • internal5×
  • platform4×
  • agent3×
  • build3×
  • design3×
  • engineer3×
  • error3×
  • isolation3×
  • issues3×
  • product3×
  • secure3×
  • api2×
  • apis2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Scale AI

every open role at Scale AI

How this page was made

An automated read of a public job posting, fetched August 25, 2026 and last changed by Scale AI on August 25, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.