You give the private agent a trustworthy foundation beneath the operating system, connecting device identity and boot integrity to security decisions people can actually use. You will also be the person who explains what attestation does not prove, which is most of what people assume it does.
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
Integrate supported roots of trust, protected key storage, measured boot and attestation. Evaluate TPMs, secure elements and trusted execution environments against a specific threat model. Coordinate provisioning, debug access and lifecycle changes with hardware and firmware teams.
The milestone
In your first 90 days, demonstrate a platform-specific attestation or protected-key workflow and document the attacks it does and does not address.
Required
Nice to have
Evidence
Bring hardware security or low-level platform security experience. Explain why attestation does not prove that an agent's decision is correct or that all side channels are closed.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Design a policy for a device with a valid identity but an unexpected firmware measurement.
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.
