About the role
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.
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.
What good looks like
In your first 90 days, demonstrate a complete grant-use-revoke flow with durable evidence and clear behavior for offline devices.
Evidence we look for
Bring identity or authorization engineering experience and strong distributed-systems reasoning. Understand the separation between identity, authentication, permission and consent.
What we need to see
- Identity or authorisation engineering with strong distributed-systems reasoning
- You hold the separation between identity, authentication, permission and consent clearly, and design to it
- You make revocation work promptly and verifiably, including across machines
- You reason about delegation chains and where authority stops
Nice to have
- Capability-based security or macaroons
- OAuth, OIDC, or verifiable credentials at depth
- You have implemented a consent or permission model somebody audited
The exercise
Design a temporary accountant delegation that permits selected records but cannot expand into the user's complete vault.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.