Rust Software Engineering Intern, Chip Design Tools - Summer

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 We are building the software that silicon chip designers should have had 20 years ago. Designing a chip today means stitching together a pile of desktop software, much of it decades old. We have a lot of respect for those tools, but in many ways they are behind. They've carried the industry this far, but we see enormous room to do better. For example: real version control, real collaboration, and interfaces that give you intuition rather than requiring it. We've concluded that we must build a lot of it from scratch. Studio is a fast, browser-based, multiplayer platform for designing and assembling whole chips. Figma plus GitHub, for silicon. The primary goal is simple: a user should never have to install anything or leave our app to take a chip from idea to finished design. Schematic capture, physical layout, and simulation, all in one place, end to end. Studio is one half of a bigger idea at Fab2: making chips should be fast. We [... source excerpt omitted ...] ed to WebAssembly, with custom rendering with wgpu/WebGPU, one code path native and in the browser. About the Role Fullstack, Rust end-to-end, working on the application itself. You will own major features from design through shipping and touch the whole stack. These are some of the problems on the table right now: Deeply interactive, low-latency editing tools: drag a wire and watch it auto-route, place a block, measure, annotate, catch mistakes the instant they happen. Careful handling, some algorithms and computational geometry. We need to constantly fight to keep the tools simple. A document model that can be diffed and merged like source code and at the same time real-tim [... source excerpt omitted ...] behind it. There is also plenty nearby as the application grows: a plugin system built on sandboxed WebAssembly components, a scripting API where a script is the same first-class client as the mouse, and integrations that send finished designs to the fab. Who Does Well Here The people who have done well on this team tend to come from deep, rich applications: tools and engine programmers, people who have built game level editors, DAWs, CAD tools, rendering pipelines, or software where the hard problems live in the seams between data, rendering, and input. It is tools programming where the output of the tool is silicon. You don't need to know anything about chip design, but y