Skip to main content

D-Matrix

Contract Site Reliability Engineer — AI Accelerator Infrastructure

Santa Clara (Remote)$155k–$235kfulltimemidAdded today

About this role

d-Matrix seeks a Site Reliability Engineer for a 6-month contract role (with potential full-time conversion) to build, operate, and automate infrastructure supporting AI chip development. You'll own reliability across colocation, on-premises labs, and cloud environments, with hands-on responsibility for provisioning, incident response, and platform services that enable silicon development and customer deployments.

What you'll do

  • Own reliability and availability of colo server fleets, on-premises lab clusters, and cloud environments (AWS, Azure, GCP)
  • Perform hands-on infrastructure work including server provisioning, OS configuration, networking, storage, and hardware troubleshooting
  • Support high-speed interconnect environments (InfiniBand, RoCE, high-speed Ethernet) in lab and colo settings
  • Design and maintain monitoring, alerting, and SLIs using Prometheus/Grafana or DataDog; participate in on-call rotation for incident triage and resolution
  • Build Infrastructure as Code and automation (Terraform, Ansible) to eliminate toil and enable self-service tooling for engineering teams
  • Support customer-facing platform services and produce RCA reports for P0/P1 incidents

What they're looking for

  • Infrastructure operations and bare-metal hardware troubleshooting
  • Infrastructure as Code (Terraform, Ansible)
  • Linux/Unix system administration
  • High-speed networking (InfiniBand, RoCE, Ethernet configuration)
  • Cloud platforms (AWS, Azure, GCP)
  • Monitoring and observability (Prometheus, Grafana, DataDog)
  • Incident response and root cause analysis
  • Python or shell scripting for automation
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

D-Matrix

View all jobs at D-Matrix

Likely interview questions

  • Walk us through your experience managing infrastructure across multiple environments (colo, on-premises, cloud)—how do you approach ownership and reliability?
  • Describe a time you used Infrastructure as Code to eliminate toil or automate a repetitive process. What tools did you use and what was the impact?