MatX
Emulation Engineer
About this role
MatX is looking for a Senior/Staff Emulation Engineer to develop and optimize emulation infrastructure for advanced connectivity SoCs. This role involves collaborating across various engineering teams and requires a versatile engineer with strong debugging and software skills to create reusable flows and tools.
What you'll do
- Define and execute emulation strategies for complex SoCs.
- Debug large-scale models on commercial emulation platforms.
- Integrate external components for connectivity protocols.
- Develop co-emulation flows with RTL and software models.
- Build automation for engineering productivity and model usability.
- Create tooling using AI for log analysis and debugging.
What they're looking for
- Hands-on experience with SoC emulation.
- Familiarity with commercial emulation platforms.
- Verilog/SystemVerilog waveform debugging.
- Strong software skills in Python and other programming languages.
- Ability to build tools and infrastructure.
- System-level debug instincts across RTL and software.
- Collaboration across functional teams.
Benefits
- Equity compensation.
- Company-subsidized health and wellness benefits.
- Flexible cash compensation options.
- [Unknown]
- [Unknown]
- [Unknown]
Opens the application — the Jobs AI extension fills it for you. Set up autofill
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 bringing up a large-scale model on a commercial emulation platform like Palladium, Zebu, or Veloce—what were the biggest bottlenecks you hit and how did you solve them?
- Describe a time you built a custom transactor or agent from scratch for an interface (PCIe, Ethernet, HBM, AXI, etc.) that wasn't well-supported off-the-shelf. What was your approach?