🤫husshhussh
🤫husshhusshOnePuppy
Private information and trust · H41

Identity Consent and Delegation Engineer

Make 'my agent' mean something precise. You will define who can ask for an action, who may perform it and how permission ends.

See what is open todayAll roles

Not open yet: First team

This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.

The work

What this person actually does

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

What it looks like when it is working

In your first 90 days, demonstrate a complete grant-use-revoke flow with durable evidence and clear behavior for offline devices.

Evidence

What would show us you can do it

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

How we would look at it together

Design a temporary accountant delegation that permits selected records but cannot expand into the user's complete vault.

← All 72 roles in the catalog