Staff Software Engineer, Developer Automation - Bazel
Santa Clara
$155k–$235k a yearHybridLead & above
Job details
- Santa Clara
- Hybrid
- $155k–$235k a year (posted by the company)
- Full-time · Lead & above
- Software Engineering
- Posted 1 month ago
Sponsorship history
Past filings by D Matrix in public government data. Not a promise of sponsorship.
- Filed 2 H-1B LCAs in FY2025
Full job description
Join d-Matrix and help build the future of AI inference. We’ve pioneered a memory-centric architecture that brings compute directly into memory, making AI faster, more energy efficient, and accessible on a global scale. From chips and software to rack-scale systems, our team is tackling some of AI infrastructure’s hardest challenges — and shipping breakthrough technology today. If you want to create what comes next and help make infinite inference possible, we’d love to hear from you.
Our culture is built on respect, collaboration, and direct communication. We value humility, we believe our different perspectives lead to better solutions, and we’re looking for people who are driven by execution and energized by hard problems.
Location
Santa Clara, CA (Hybrid 3 days a week)
Role Overview
Build time is a tax every engineer pays on every change, and our stack collects it at a high rate. An MLIR-based compiler, Rust and C++ runtimes, and a large Python ML codebase have to produce identical results on a laptop, in CI, and on a machine with an accelerator in it. You will lead d-Matrix's Bazel build-out. That means finishing the in-progress migration and designing the distributed build infrastructure that doesn't exist yet. You will own the build graph, toolchains, caching and remote execution, and the conventions every engineering team builds against. You will partner closely with development groups and with the engineers who run our runner fleet and cloud environments. When build and test time drops, every group in the company moves faster.
What You Will Do
- 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.
