What You'll Do
- Audit the current build and test pipeline (Bun for TypeScript, Cargo for Rust, buf for protobuf, plus Docker and Helm) and write down where it fails on reproducibility, hermeticity, and speed
- Pick a build system and migrate us onto it without breaking shipping
- Stand up remote execution and remote caching that actually move CI and local build times
- Pin toolchains, seal dependencies, and stop the host environment from leaking into builds
- Run the long-term roadmap for build, test, and CI as the team and codebase grow
- Work alongside application and infrastructure engineers throughout, since the migration touches all of them
What We're Looking For
- Senior or staff-level experience running Bazel, Buck2, Pants, or a comparable system somewhere the build system genuinely mattered
- Experience operating remote execution and remote caching in production
- Comfortable across language ecosystems. We run TypeScript and Rust today, with Python showing up
- Strong opinions on determinism and reproducibility, with the judgment to know when full hermeticity is worth the cost and when it isn't
- CI ops chops: queue health, flake budgets, real test signal, build time budgets you can defend
- Able to scope your own work. There's no spec for what our build system should look like
Nice to have: experience moving a codebase onto Bazel (or off of it), polyglot or protobuf-heavy monorepos, prior work on developer infrastructure at an autonomy, robotics, or systems company