Meaningful equity
Equity grants as part of the early team.
Careers
Work on what
control requires.
AI security needs people who can turn difficult questions into useful systems. Join the team building practical infrastructure and examining what growing AI capability will demand.
5 open rolesSan Francisco and Washington, DCOn-site by default
Open roles
Find your contribution.
Research, engineering, field work, sales, and operations.
5 open rolesLocation / Type
Engineering
San FranciscoMember of Technical Staff, AI Products
Build agents and reasoning pipelines that turn security data into findings an analyst can examine.
On-site · Full-time
Research
San FranciscoMember of Technical Staff, AI Security Research
Study how AI agents violate security policy, then build and evaluate methods for detecting and controlling that behavior.
On-site · Full-time
Field
San Francisco or Washington, DCForward Deployed Engineer, Security
Work alongside customer security teams to deploy the platform, write detections, and respond to incidents.
On-site · Full-time
Go-to-market
San FranciscoFounding Account Executive
Work with the founders to build a sales process grounded in technical understanding and useful customer evaluations.
On-site · Full-time
Operations
San FranciscoFounding Ops
Build the people, finance, and recruiting operations that support a growing team.
On-site · Full-time
If your work belongs here but the right role is not listed, write to [email protected] with a short introduction.
Working at Zaun
The conditions for good work.
Comprehensive health
Medical, dental, and vision covered for you and your dependents.
Daily meals
Lunch and dinner in the office.
Fitness and wellness
A gym and wellness stipend.
Team offsites
Time together outside the office several times a year.
San Francisco and DC
On-site by default, with headquarters in San Francisco and a satellite office in DC.
How we work
Care in the details.
Make the work useful.
Work on real problems, release on weekly cycles, and stay close to the people using what you build.
Understand what you build.
Read the code, examine the evidence, and be able to explain the behavior and limits of a system.
Stay close to the problem.
Technical understanding matters across engineering, field work, and customer conversations.
Think together.
Write decisions down, make room for questions, and ask for help when it improves the work.