About the role
You build the isolation around models, plugins and remote jobs, so a person can add a useful tool without giving that tool access to their life. The distinction that matters here is between restricting a process and defending against a host that is already compromised, and this role is about the second.
The work
Evaluate processes, containers, virtual machines and capability-based restrictions against the actual threat model. Implement filesystem and network boundaries, resource quotas and safe lifecycle management. Work with security researchers to test escapes and confused-deputy behavior.
What good looks like
In your first 90 days, deliver an isolated tool runner with explicit permissions, reproducible attack tests and measured startup and memory costs.
Evidence we look for
Bring experience with kernel isolation, hypervisors or hardened execution environments. Understand the difference between restricting a process and protecting against a compromised host.
What we need to see
- Experience with kernel isolation, hypervisors, or hardened execution environments
- You understand the difference between restricting a process and protecting against a compromised host, and design for the second
- You can reason about an escape path before somebody demonstrates it
- Systems programming depth in a language without a garbage collector
Nice to have
- Secure enclaves, confidential computing, or TEEs
- Sandbox escape research, or offensive security experience
- WASM or comparable portable isolation
The exercise
Design a document-conversion sandbox that handles malicious files while preventing credential access and unintended network use.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.