About the role
You work where hardware and software meet: making the computer start safely, understand its devices, and recover when an update fails. Recovery is the part most teams underinvest in, and it is the part that decides whether a bad update is an inconvenience or a brick.
The work
Build or integrate boot firmware, embedded-controller logic and drivers. Support measured or verified boot where the platform exposes it, signed updates, rollback protection and recovery. Document boundaries controlled by vendors and use supported interfaces.
What good looks like
In your first 90 days, demonstrate reliable bring-up and an interrupted-update recovery path on the selected reference platform.
Evidence we look for
Bring embedded systems experience and strong debugging skills across registers, interrupts, DMA and operating-system interfaces. Explain how you protect secrets during diagnostics and factory provisioning.
What we need to see
- Embedded systems experience with strong debugging across registers, interrupts, DMA, and operating-system interfaces
- You can explain how you protect secrets during diagnostics and factory provisioning
- You design an update path that survives failing halfway
- Comfort with hardware bring-up alongside an engineer holding a scope
Nice to have
- Secure boot and measured boot
- UEFI, U-Boot, or comparable
- Device driver work on a mainstream operating system
The exercise
Review a firmware update design for power-loss behavior and the risk of accepting a vulnerable older image.
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.