Make the computer start safely, understand its devices and recover when an update fails. You will work where hardware and software meet.
Not open yet: Pilot expansion
This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.
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.
The milestone
In your first 90 days, demonstrate reliable bring-up and an interrupted-update recovery path on the selected reference platform.
Evidence
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.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Review a firmware update design for power-loss behavior and the risk of accepting a vulnerable older image.