Firmware and Boot Engineer
The work
The code that runs first. Boot ROM, multi-hart startup, the measured handoff into the trust core, the drivers that touch the outside world, and the attestation client.
You would own
The trusted boot path, platform drivers, and the client that gathers and signs what the platform reports.
Your first quarter
Bringing firmware up on the prototype board alongside the engineer who owns the platform, and taking the boot path as yours from the first commit.
We look for
Bare-metal C and RISC-V assembly. Boot ROMs written, not just read. Drivers built from a datasheet and debugged on the wire. Deep low-level debug when nothing boots and there is no console.
Why it matters
On a root of trust the startup sequence is a security property, not boilerplate. Subtly wrong, and everything above it is worthless while looking fine.
Apply
Email careers@felsite.com with what you have worked on that you would want to talk about, a link to anything public, and where you are and what you are looking for. No cover letter.
Every application answered within five working days.