The posting, in Voyant Photonics's own words
archived Oct 19, 2026Embedded Firmware Engineer, Hardware Bring-up & Controls
About us:
Voyant Photonics builds silicon photonic chips that steer and switch light at high speed. They power next generation, chip-scale FMCW LiDAR for robotics and autonomy, and optical circuit switches (OCS) for AI data centers. Based in NYC, we’re a hands-on team designing, building, and deploying frontier hardware to solve problems that matter, from how machines see to how AI scales.
Read the full posting ↓
The Role:
We're hiring an embedded software engineer to bring up our new boards quickly and own the drivers and control firmware that run on them. You care how an algorithm is implemented in firmware, but you're just as comfortable with the schematic open, a probe on the board and the soldering iron warm. About half your time goes to board bring-up, changing the firmware and the board together until everything comes up; the other half goes to implementing control loops and proving they work on hardware. We are a collaborative, close knit team who love to solve complex problems and building robust systems. If you enjoy the challenge of working with frontier hardware, bringing up both brand new boards and cutting-edge control loops, we are excited to talk to you.
Your impact:
Code is cheaper to write than ever. Knowing what should be written, and what "done" means, is the job. A board is done when it works, not when the firmware compiles; a loop is done when it meets its requirements on hardware, not when the simulation looks good. We want someone with strong, well-reasoned opinions about how control algorithms and drivers should be implemented in firmware, and how to prove they work, who argues for them, and who changes their mind when the evidence says so.
A few strong opinions the team holds:
Fix it at the source. A bug gets fixed where it lives, even when that's someone else's code. The friction of working in each other's areas is worth it. Live at the tip. Every repo tracks the latest of everything it depends on. Small, frequent bumps surface breaks while they're still cheap to fix. Duplicated code is broken code. Two copies drift apart, and then one of them is wrong. It doesn't work until someone else has run it on hardware. Your own simulation or bench is where you start, not where you're done. Disagree with one? Tell us why when you apply.