Infrastructure Engineer

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified not verified - source not recorded; timestamp not recorded

401(k) match

Not verified not verified - source URL not recorded; timestamp not recorded

Was this benefit information wrong? Tell us.

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Infrastructure Engineer Mountain View, CA What MatX Is Building We're a small engineering team designing a custom chip. The work is compute-heavy and tooling-heavy: hermetic builds, large verification jobs, custom developer environments, a self-hosted CI fleet, and a steadily growing collection of internal services that engineers depend on every day. The infrastructure that supports all of this - CI/CD, compute, shared filesystems, networking, internal tooling - already exists and has a system owner. We're hiring a second infrastructure engineer to broaden our capacity and add depth in areas adjacent to what we already have. We're looking for a strong generalist with a network and systems bent. Someone who's comfortable debugging a Linux kernel issue in the morning, untangling a cloud networking problem at lunch, and writing a new MCP server for an unfamiliar protocol in the afternoon. What You'll Do Here - Day to day, the work spans: Linux and networking work (the core of the role) - Diagnose and fix issues across the OS, network, and cloud stack - Reason about routing, DNS, firewalls, VPCs, private connectivity, and trust boundaries - Track down "permission denied" that's actually a mount option, or "build is slow" that's actually a metadata-server timeout - Improve, harden, and extend the network and host configuration we already have Building tools and integrations - Write internal tools, scripts, and small services that make the engineering team faster - Pick up unfamiliar protocols and codebases and ship working integrations against them Supporting the infrastructure stack - Pair

Read the full description at job-boards.greenhouse.io. FewerJobs shows a source-linked preview and links to the original posting.