About the role
You earn the right to hold a person's most sensitive information, and you do it by making protection, consent and recovery part of every engineering decision rather than a review at the end. You own the threat model across hardware, software, people and external agents, plus release criteria, incident response and vulnerability handling.
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.
What good looks like
In your first 90 days, establish the security architecture, test the highest-risk boundaries and run an incident and device-loss recovery exercise.
Evidence we look for
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.
What we need to see
- Hands-on security engineering, current enough that you could still do the work
- You make clear decisions under genuine uncertainty and can explain the reasoning afterwards
- You can teach threat modelling and review a cryptographic design credibly
- You work constructively with product teams rather than only blocking them
Nice to have
- Consumer-device or endpoint security specifically
- You have run an incident that went public and handled it well
- NIST 800-53, FedRAMP, or equivalent control-framework experience
The exercise
Threat-model a household with separate users, an untrusted plugin and a stolen device; explain what remains at risk.
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.