Build Systems Engineer (Bazel)

Rules, providers (or equivalent), aspects, toolchains, platforms, configuration/select, transitions, query.

, whatever — and predict what its action graph will look like.

If you've done equivalent work in Buck2, Shake/Hadrian, Pants, Nix, or a homegrown Blaze-shaped system, read the bullets as concepts — Bazel is what you'll write here, but the principles port.

Module extensions, lockfile management, vendoring third-party deps cleanly

RBE, Buck2 RE, BuildBuddy, BuildBarn, your own — they all teach the same lessons.

Cache-key debugging, Build without the Bytes, diagnosing "works locally, fails remote." If you've owned one end-to-end, the next one is a port

The US base salary for this full-time position is determined based on a variety of factors including role, experience, location, job related skills, and relevant education and training. Career length is only a guideline for compensation.

Early Career - $120,000 - $250,000 + equity

Mid Career - $175,000 - $362,500 + equity

Senior Career - $250,000 - $475,000 + equity

A Stake in our success

New EDA tool integrations.

Wrap a closed-source tool in a hermetic Bazel rule with proper providers, runfiles, and execution constraints.

Add a new front-end stage to an existing toolchain; add a rule for test variants that share configuration; wire a third-party generator into our verilog graph as a first-class dep

Bazel version migrations.

Lead upgrades (8.x → 9.x) and the bzlmod/

housekeeping that comes with them