Company
Building the team.
Protocol is hiring across security operations, engineering, intelligence, and public-sector development. The company is early, and the roles are correspondingly broad.
Open areas
Where Protocol is hiring.
Protocol does not publish individual job descriptions at this stage, because the shape of each role is still being set by the people who take them. The areas below are genuinely open.
- 01Security operations and program management
- 02Cybersecurity architecture, identity, and cloud security
- 03Physical security design and systems integration
- 04Protective operations and program design
- 05Intelligence analysis and written product
- 06Public-sector business development and teaming
- 07Product engineering — platform, identity, and operational tooling
- 08Design and technical writing
Protocol is early. Joining now means building the systems, not operating them.
What the work looks like
Protocol's output is architecture, coordination, and written judgment — not a product demo. The people who do it well have usually been accountable for a program rather than for selling one.
How this works
What to expect.
A conversation before a process
Protocol would rather understand what you have run than receive an application against a specification written for a later-stage company.
Early, with what that implies
The products described across this site are in development. Joining now means building them. That suits some people and not others, and it is better established early.
Discretion is part of the role
Protocol's work is not discussed, displayed, or attributed. That applies to how the company talks about its clients and how its staff talk about their work.
Introduce yourself.
A short note about what you have been accountable for is more useful than a formal application. Protocol reads every one.