Scan your resume against ATS criteria for this Developer Infrastructure Engineer (Silicon) role at Matx.
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.
##
The role covers three areas of equal weight:
Which branches exist, what each is for, how a change reaches each, and how that is verified.
Keeping a large, EDA-heavy test suite fast, affordable, and reliable, and finding the cause when it is not.
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, take feedback, and decline a change that is wrong. Where that is weak, we teach it
Protected release branches run alongside the main branch, each with its own rulesets, presubmit checks, and notifications. Each has its own failure modes; for example, a push-triggered workflow runs the copy of itself that exists on the pushed branch. You would own the branch structure and make "did this change land where it was supposed to?" answerable from a report rather than by inspection.
Several views of the same deliverable have to agree: a build from source, an archived release artifact, and whatever a downstream consumer is actually running. Drift detection should run continuously and its results should be visible without anyone asking.
EDA-heavy test suites are slow and expensive by nature, which makes gradual degradation easy to miss. The work includes critical-path analysis, remote-execution behavior under real resource limits, runner-pool sizing and cost, and flake triage that ends in a fix rather than a re-run.
## How we'd work together:
This section describes how the role operates day to day. It suits some people well and others poorly, so it is worth reading closely.
You would receive objectives rather than instructions. In return, a task is complete when the change is pushed, CI is green, and the resulting state has been checked. Handing back work with the final verification still pending is the main thing that causes friction.
You will be asked how you know something, and the question is not a criticism. Asserting something unchecked, such as that a resource does not exist, a pool is too small, or a limit cannot be avoided, is what draws pushback. The expected answer to "how do you know?" is the command you ran and its output. "I have not verified that yet" is always an acceptable answer.
The best outcome from a request is usually that the request does not need to be made again. Updating the runbook or adding the check that would have caught the problem is part of the work, not extra scope.
##
Deep experience in 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.
You can explain what a rebase does to commit identity, recover a branch that was deleted, verify by content that a cherry-pick landed, and describe what a squash merge queue does to history. You have built tooling on top of Git rather than used it.
Merge queues, required checks, event-trigger semantics, app-based authentication, concurrency controls, and self-hosted runners. Given a slow or flaky pipeline, you can identify the cause and quantify it. This includes reading a Bazel query and a build profile, and working in Python and shell against REST and GraphQL APIs.
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.
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 a guideline for compensation.
Early Career - $160,000 - $275,000 + equity
Mid Career - $175,000 - $400,000 + equity
Senior Career - $250,000 - $600,000 + equity
As part of our dedication to the diversity of our team and our focus on creating an inviting and inclusive work experience, MatX is committed to a policy of Equal Employment Opportunity and will not discriminate against an applicant or employee on the basis of race, color, religion, creed, national origin or ancestry, sex, gender, gender identity, gender expression, sexual orientation, age, physical or mental disability, medical condition, marital/domestic partner status, military and veteran status, genetic information or any other legally recognized protected basis under federal, state or local laws, regulations or ordinances.
_
_
This position requires access to information that is subject to U.S. export controls. This offer of employment is contingent upon the applicant's capacity to perform job functions in compliance with U.S. export control laws without obtaining a license from U.S. export control authorities.
_
_
MatX does not accept unsolicited resumes from individual recruiters or third-party recruiting agencies in response to job postings. No fee will be paid to third parties who submit unsolicited candidates directly to our hiring managers or People team and any resumes submitted are deemed to be the property of MatX.
PTO (accrued) + 12 company Holidays + up to 3 weeks remote work
How to apply for Developer Infrastructure Engineer (Silicon) at Matx?
Click the "Apply on Company Website" button on this page to submit your application directly on the employer's official portal.
What is the salary for this role?
The salary for this role is $160,000 - $275,000 per annum.
What experience is required?
This position is open to freshers and experienced candidates.
Is this position still open?
Yes, currently active and accepting applications.
Developer Infrastructure Engineer (Silicon)
Matx · Mountain View (HQ) or Remote
