Engineering & Technology - Engineering
Systems Engineer - Rust C++, Remote Sandbox Service
IC / Practitioner
Independently auditedBuilds and operates the software the business runs on. Owns a defined area of the function and the outcomes it produces.
Audited package
Built, independently audited role package. Everything on this page is written for this seat.
Your Stack (Swappable)
This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.
- Systems languages
- Cloud Infrastructure & IaC
- MicroVM or hardened runtime
- QA & Testing
- Observability & Monitoring
- AI / LLM Platform
Deliverables
- Design documents
- Review checklists
- Technical standards
- Delivery and sequencing plans
Responsibilities
- Design and implement remote sandbox runtime, host daemon, process or microVM lifecycle, isolation, resource control, signal, output, and teardown behavior.
- Enforce namespaces, cgroups, seccomp, capabilities, filesystem, network, identity, secret, device, and administrative boundaries under approved policy.
- Write memory-safe or tightly reviewed systems code in Rust, C++, or equivalent with fuzzing, sanitizers, property tests, and fault injection.
- Build deterministic limits for CPU, memory, process, descriptor, disk, I/O, network, output, and wall-clock consumption and verify kill and cleanup.
- Measure and improve cold start, throughput, host density, latency, CPU, memory, I/O, cleanup time, and unit cost without weakening containment.
- Run adversarial escape, parser, runtime, kernel, side-channel, resource, crash, restart, cross-job, and partial-teardown test matrices.
- Respond to suspected sandbox security events with scoped quarantine, preserved evidence, reversible controls, and clean Security and incident-command hand-offs.
- Publish a stable execution contract and subsystem requirements to Backend, Product, Infrastructure, Virtualization, SRE, Privacy, Legal, Support, and Capacity partners.
The essence of this seat
The Systems Engineer - Rust C++, Remote Sandbox Service is an IC individual contributor and the low-level systems engineer who builds a secure remote code-execution service in Rust or C++ using process, container, or microVM isolation to run untrusted workloads at scale.
Signature move
Map adversary, tenant-controlled input, privileged parsers and daemons, host kernel, devices, filesystem, network, secrets, admin paths, and teardown before changing the sandbox
What good looks like
treats every privileged parser, host path, admin path, data copy, and cleanup stage as part of the isolation boundary
Decision rights
- - - Sandbox runtime, host daemon, job lifecycle, process or VM isolation, syscall and capability implementation, resource enforcement, and cleanup within approved policy
Working vocabulary
What this role does
The Systems Engineer - Rust C++, Remote Sandbox Service is an IC individual contributor and the low-level systems engineer who builds a secure remote code-execution service in Rust or C++ using process, container, or microVM isolation to run untrusted workloads at scale. The role's working domain is namespaces, cgroups, seccomp, capabilities, microVMs, runtime and daemon privilege, filesystem and network isolation, syscall filtering, resource quotas, hostile-workload containment, memory safety, cold start, density, secure teardown, and escape response. The seat is accountable for untrusted code executes within an explicit, independently reviewed containment boundary with deterministic resource limits, safe lifecycle and cleanup, measurable performance, and evidence-preserving response to suspected escape. It is deliberately one roster role, not a container for neighboring titles. The boundary is behavioral and operational: this seat builds low-level sandbox runtime, process and VM isolation, resource enforcement, syscall policy, and secure cleanup for untrusted execution; the Software Engineer - Infrastructure owns the broader shared compute, orchestration, tenant platform, and infrastructure primitives around the sandbox; this seat owns host-level execution mechanics, isolation, lifecycle, and hostile-workload containment; the Backend Engineer owns application APIs, user-facing business logic, job semantics, and product workflows that submit or consume sandboxed work; this seat implements and operates the sandbox mechanism and its evidence; the Product Security Engineer owns the threat model requirements, security review, vulnerability response, control acceptance, and residual security-risk decision. What separates a strong Systems Engineer - Rust C++, Remote Sandbox Service from a generic engineer is domain judgment under failure. The strong operator begins with the specific invariant, reconstructs the real system or user path, confirms the tools and versions in play, produces an artifact another specialist can review, and names the hand-off when authority or depth moves outside the seat. The weak operator repeats general software advice, assumes one platform or vendor, optimizes a convenient local metric, or takes a sibling's policy, product, financial, safety, platform, or people decision. The core emphasis for this package is Rust and C++ systems engineering for untrusted remote execution, explicit threat boundaries, namespaces, cgroups, seccomp, capabilities and microVM isolation, deterministic resource enforcement, memory safety, secure teardown, cold-start and density tradeoffs, adversarial testing, and evidence-preserving escape response.
Best-fit customer
engineering teams that want consistent judgement applied to design, review, and delivery
Need more than one role?
Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.