Staff Software Engineer, Developer Automation

d-Matrix•Santa Clara, CA
•$155,000 - $235,000•Hybrid

About The Position

At d-Matrix, we are focused on unleashing the potential of generative AI to power the transformation of technology. We are at the forefront of software and hardware innovation, pushing the boundaries of what is possible. Our culture is one of respect and collaboration. We value humility and believe in direct communication. Our team is inclusive, and our differing perspectives allow for better solutions. We are seeking individuals passionate about tackling challenges and are driven by execution. Ready to come find your playground? Together, we can help shape the endless possibilities of AI.

Requirements

  • Deep Bazel experience as an owner: custom rules, toolchains, and target graph design in a large repository.
  • Experience migrating a real codebase onto Bazel, including the long tail.
  • Hands-on experience deploying and operating remote caching or remote execution, self-hosted or vendor-provided.
  • Experience with hermetic, reproducible, and observable builds, including custom toolchains.
  • Strong knowledge of C++, Rust, Python, and container image builds.
  • Persistence in debugging non-reproducible builds and unexplained cache misses to root cause.
  • A track record of partnering with other teams to understand their needs and spread best practices.
  • A pragmatic bias toward incremental migration that keeps people productive.

Nice To Haves

  • Experience migrating test suites to Bazel.
  • Kubernetes-based executor pools.
  • Embedded or firmware cross-compilation. Firmware is not in Bazel today, and you would help decide whether it should be.
  • Open source contributions to the Bazel ecosystem.

Responsibilities

  • Complete the Bazel migration, including the hardest remaining components.
  • Migrate the test suite to Bazel, with correct tagging and sharding, and route hardware-dependent tests to executors that have the hardware.
  • Design, deploy, and operate remote execution in production.
  • Build hermetic toolchains and reproducible builds across developer machines, CI, and hardware-attached runners.
  • Raise cache hit rate to target and build trust in the cache, so no one runs a clean build "to be safe."
  • Establish a build-time baseline in your first quarter, then reduce median incremental build time and CI critical path against it.
  • Evolve the CI/CD system to keep pace with agent-assisted development.
  • Raise the standard of Bazel usage across teams by making the correct path the easy one and sharing best practices.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service