You make the phrase my agent mean something precise: who may ask for an action, who may perform it, and how permission ends. Revocation is the part most systems get wrong, and it is the part that decides whether consent is real.
Open for applications. Starts at: First team.
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 device enrollment, authentication, consent records and scoped delegation. Use established identity protocols with purpose, audience, expiry and resource constraints. Keep household members separate, support explicit sharing and test revocation across devices, connectors and workers.
The milestone
In your first 90 days, demonstrate a complete grant-use-revoke flow with durable evidence and clear behavior for offline devices.
Required
Nice to have
Evidence
Bring identity or authorization engineering experience and strong distributed-systems reasoning. Understand the separation between identity, authentication, permission and consent.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Design a temporary accountant delegation that permits selected records but cannot expand into the user's complete vault.
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.
