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.
Open for applications. Starts at: Pilot expansion.
We are taking applications for this role now and building the pipeline for it. The stage above is when the work itself is expected to begin, which is something you deserve to know before you apply rather than after. It is context, not a gate.
Where
In the office together five days a week, in one of our garages, and remote-friendly around your family, arranged one person at a time. We hire across the United States 🇺🇸, India 🇮🇳 and the UAE 🇦🇪.
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.
Required
Nice to have
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.
The package
Indicative pay ranges by market and level are on the compensation page. Plan numbers are confirmed in your offer letter.
Apply
One short form. A person reads every application and you hear back either way. You will get your own link to check where things stand, and you can withdraw or delete your application from it at any time, without an account.
