Earn the right to hold a person's most sensitive information. You will make protection, consent and recovery requirements part of every engineering decision.
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
Own the threat model across hardware, software, people and external agents. Define release security criteria, incident response and vulnerability handling. Review key custody, authentication, authorization, update integrity and data deletion with the engineers who build them.
The milestone
In your first 90 days, establish the security architecture, test the highest-risk boundaries and run an incident and device-loss recovery exercise.
Evidence
Bring hands-on security engineering and experience making clear decisions under uncertainty. You should be able to teach threat modeling, review cryptographic system design and work constructively with product teams.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Threat-model a household with separate users, an untrusted plugin and a stolen device; explain what remains at risk.