We make the best chips physically possible for the large model needs of frontier labs.
About the role
Branch and release methodology. Which branches exist, what each one is for, how a change reaches each one, and how that is verified. CI performance and debugging. Keeping a large, EDA-heavy test suite fast, affordable, and reliable, and finding the cause when it is not.
What they're looking for
- Deep experience in one of the three areas plus working knowledge of the other two is preferable to moderate experience in all three. Tell us which area is your strongest
- Judgment under a schedule. You would be telling leadership what is and is not in a milestone. That requires saying "not yet" when it is true, and preferring a change that can be reverted to a migration that cannot
- Developer-infrastructure work under hard deadlines in another industry (silicon, aerospace, games)
- Experience with repository structure at scale, whether monorepo or polyrepo
- Familiarity with EDA flows
- This is not the SRE role for the compute fleet, and it is not a process role that hands the tooling to someone else
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.
Branch and release methodology. Which branches exist, what each one is for, how a change reaches each one, and how that is verified.
CI performance and debugging. Keeping a large, EDA-heavy test suite fast, affordable, and reliable, and finding the cause when it is not.
Measurement and diagnostics. Instrumenting the above so that the state of the system is visible without anyone having to ask.
We expect every engineer to handle everyday collaboration: open a clean PR, review one, take feedback, and decline a change that is wrong. Where that is weak, we teach it. The specialized work is different: release branch structure, freeze enforcement, version pinning, merge-queue and runner behavior. That work is centralized because it requires specific expertise and consistency, not because other engineers are unable to do it. You would own the specialized work and improve the tooling and documentation that everyone else relies on. Success means people need your direct help less over time, not more.
Operating the long-lived branches....
Browse similar: Startup jobs · Remote jobs · San Francisco Bay Area