About the role
You test hardware ideas early enough that they can still change, building prototypes that let software and architecture teams learn before anyone commits to custom silicon. A useful prototype with honest measurements is worth far more here than an impressive demo.
The work
Map proposed subsystems to FPGA platforms, connect host software and collect workload traces. Build practical interfaces and instrumentation. Explain which prototype results transfer to an ASIC and which are artifacts of the FPGA implementation.
What good looks like
In your first 90 days, demonstrate one end-to-end prototype with a correctness suite and a written assessment of its architectural value.
Evidence we look for
Bring experience with FPGA toolchains, digital logic, host interfaces and debugging physical systems. A useful prototype and honest measurements matter more than an impressive demo video.
What we need to see
- FPGA toolchains, digital logic, host interfaces, and debugging real physical systems
- You produce honest measurements, including the ones that kill an idea
- You build for someone else to learn from, with the harness and the documentation
- Comfort at the boundary between hardware and the software that will run on it
Nice to have
- High-speed host interfaces such as PCIe
- Emulation platforms
- You have prototyped something that then became silicon
The exercise
Choose a prototype boundary for a new memory subsystem and explain what the prototype can and cannot validate.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.