About the Role The same systems work as our senior role, aimed at someone earlier in their career who gets real work done in a hard codebase with agentic tools. Systems programming has a reputation for being locked behind ten years of experience. We don't fully buy that. Someone with solid fundamentals, real curiosity about how machines work, and deep control of agentic coding tools can contribute here much sooner — as long as they have the judgment to check what the tools hand back. That judgment matters more here than almost anywhere: the agent runs as root and SYSTEM, and the codebase forbids unwrap, panic, and unchecked indexing, so you can't ship code you don't actually understand. What you'll work on • Real pieces of the sensor across macOS and Windows: inventory, telemetry, the policy enforcement path, installers, and the integrations that hook into AI coding tools and browser extensions. • Moving through unfamiliar OS APIs quickly with agentic tools, then checking the result against the docs, the tests, and a real machine. • Small tools and tests that make the codebase easier for everyone to work in. Tech you'll work with Rust (2024 edition), macOS and Windows systems APIs, Tokio, SQLite, and Rego policy, plus whatever agentic toolchain you already work in (Claude Code, Codex, Cursor, or similar). There's a nice symmetry here: the sensor installs its own shims into Claude Code, OpenClaw, and Codex CLI, so the tools you use are close to the tools you'd be working on. What we're looking for (the part that matters most) • You've built real, working software and can show it. Projects that run count for more than a CV. • Deep, hands-on control of at least one agentic coding tool: you steer it, feed it the right context, and know when to trust it and when to verify. • Solid fundamentals (memory, processes, files) and enough systems knowledge to read what the tools produce and catch what's wrong. • The discipline to verify. Here, “it compiled” is not the same as “it's correct.” • Genuine curiosity about operating systems and low-level work, and drive to learn the parts you don't know yet. Explicitly not required • A specific degree, a set number of years, or prior Rust or systems experience in a paid job. If you taught yourself this with good tools, that's the whole point. Nice to have • Personal projects in Rust, C, or C++, or anything close to the metal. • Reverse engineering, CTFs, a homelab, or OS tinkering. • Contributions to agentic-dev tooling.