Startups

Hardware Tools Engineer

MatX · Mountain View (HQ) or Remote · Remote

← All jobs
About MatX

We make the best chips physically possible for the large model needs of frontier labs.

About the role

The areas below are where the work starts today. The hardware teams' needs change from one chip to the next, and we expect you to help decide what the team builds next Work with the hardware teams: Find out where architects, designers, and verification engineers spend their time, and decide with them what to build. A tool is finished when the engineers it was built for are using it and you can show what it changed for them Found on 1752vc Careers, the job board for startup and VC roles.

What they're looking for

  • Senior-level self-direction: You can take an ambiguous request from another team, work out the underlying problem, and drive it to a shipped tool without close supervision
  • Strong Haskell: You can write, debug, and profile production Haskell in a large codebase. The Bluespec compiler is written in Haskell and you will be changing it. Prior knowledge of GHC internals is not required
  • Strong Rust: You write production Rust. Our hardware libraries, code generators, simulators, and reference models are written in Rust
  • You can read RTL: You can read Bluespec, Verilog, or SystemVerilog well enough to understand what the compiler produced and why a design, test, or proof behaves the way it does. Hardware design experience is helpful but not required
  • You build for other engineers: You have built tools that other engineers depend on, and you have changed them based on what those engineers told you. You are comfortable with Python, build systems (Bazel preferred), and CI
  • On-site or remote: You would work with teams across MatX, and the role can be based in our Mountain View, CA office or remote
More about this role

MatX's mission is to make the world's best AI models run as efficiently as allowed by physics, bringing the world years ahead in AI quality and availability. We build the full stack, from silicon and rack design through compilers, kernels, and ML models.

Most of our chip is written in Bluespec, a high-level hardware description language, and the Bluespec compiler turns it into Verilog. Our architects write executable models in Rust, and our verification engineers check the RTL with simulation and formal methods. The Hardware Tools team owns the Bluespec compiler, our hardware libraries, and the tools that connect them.

The team's customers are MatX's own engineers in Architecture, Design, Design Verification, and Formal Verification. Every change we make to the language, the compiler, or our tools has to make one of those teams faster or help them find problems earlier. You will learn what each team needs by working with them directly, and your work will be measured by its effect on their schedules.

You will be working in an existing system, not starting one. The Bluespec compiler is a mature open-source Haskell codebase with MatX extensions, and our engineers use it every day on...

Read the full posting on MatX's site ↗

Hardware

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.