MatX
System Software Engineer — Node & Cluster Management
About this role
MatX is hiring a System Software Engineer to design and build node and cluster management systems for AI silicon. You'll develop management APIs, CLI tools, telemetry daemons, and failover logic while collaborating with firmware engineers to create unified hardware observability across in-band and out-of-band management paths.
What you'll do
- Design and implement node-level management APIs (REST/Redfish-style) for health, inventory, telemetry, and control operations
- Build cluster management solutions including failover algorithms and fleet-wide health aggregation
- Develop CLI utilities for operators to query state, run diagnostics, update firmware, and recover devices
- Partner with BMC firmware engineers to align host-side and BMC-side management behind common interfaces
- Debug production issues spanning APIs, daemons, kernel drivers, firmware, and hardware boundaries
- Build lab automation tooling for system bring-up, provisioning, and regression testing
What they're looking for
- Linux systems development and kernel driver debugging
- C programming with proficiency in Go, Rust, C++, or Python
- HTTP/REST API design and implementation
- Hardware management and telemetry (PCIe, device drivers, BMC subsystems)
- Datacenter management standards (Redfish, OpenBMC, IPMI preferred)
- CLI tool development for infrastructure management
- Low-level userspace and daemon programming
- Cross-layer debugging across software and hardware
Opens the official application on the employer’s site. No login required.
MatX
MatX builds cutting-edge AI silicon and the system software stack to power it, focusing on optimizing hardware and software for large-scale machine learning workloads. The company is hiring system software engineers, kernel developers, compiler engineers, hardware simulators, and SOC integration engineers to design high-performance AI compute platforms.
View all jobs at MatXLikely interview questions
- Walk us through your experience debugging an issue that spanned kernel drivers, userspace daemons, and hardware—how did you approach it?
- Describe your experience designing REST APIs for hardware management. What was tricky about exposing hardware state through APIs?