You design key custody and recovery, so protecting somebody's information does not mean a lost device ends their digital life. These two goals genuinely conflict, and the quality of this role is in how honestly you handle the conflict rather than in picking a side.
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
Use established cryptographic libraries and protocols for encryption, key hierarchy, rotation and secure sharing. Work with platform hardware protections where available. Model recovery contacts, service compromise and malicious insiders, and document exactly who can decrypt which data.
The milestone
In your first 90 days, deliver a reviewed key-management design and a tested recovery prototype with explicit security assumptions.
Required
Nice to have
Evidence
Bring applied cryptography and secure implementation experience. Be able to reason about entropy, authentication, protocol composition and the limits of cryptographic erasure.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Explain how a user can recover after losing every device without introducing an undisclosed service-side master key.
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.
