Software Integration Engineer
Posted 8 Sep 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 3+ yrs
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
- Visa sponsorship
- Offered
No salary listed for this role.
About fab2
The fab2 team can build anything. We design all the hardware and software needed to make chips and we make the fabs, tools, and components ourselves.
We're looking for exceptional, hands-on people who can iterate to the limits of what's possible.
fab2 was founded by Sam Zeloof and Jim Keller. Sam is best known for making chips in his garage, and Jim has been a leader in the semiconductor industry for the past 40 years.
About the Team
The tool software group builds Linux control software and microcontroller firmware for fab2’s in-house semiconductor manufacturing equipment. This includes software for sequencing, recipe execution, interlocks, operator user interfaces, diagnostics, and real-time microcontroller firmware.
About the Role
As the Software Integration Engineer, you ensure the whole tool works end to end. You are the person who knows how firmware, control software, electronics, and actuators fit together. You do whatever it takes to make sure our systems can move from prototype to a qualified tool running in production. This could involve wearing a variety of hats, such as project management, system design, software development, testing on physical systems, and data analysis.
This is an ideal role for a person with a software, electronics, or robotics background who wants to work on physical systems.
Responsibilities
-
Serve as the technical owner and software point of contact for semiconductor manufacturing equipment, from early prototype through handoff to production use
-
Lead bring-up, debug, and engineering test of new hardware
-
Write and modify control software and firmware (C, Rust, Python) to bring up new hardware, integrate subsystems, and unblock testing
-
Understand hardware changes (electronics, actuators, sensors) and translate them into software requirements
-
Use data analysis and statistical modeling to triage problems and identify root causes
-
Drive fixes for issues across domains that span firmware, electronics, mechanical, and process teams
-
Apply systems engineering discipline to develop interface definitions, requirements, and participate in system level FMEA
-
Own integration schedules, and track milestones and dependencies
-
Communicate constraints, risks, and tradeoffs clearly across software, hardware, and electrical design changes