Vigilance
Always watching, never anxious.
You notice the small thing early. You would rather flag a risk on Tuesday than explain an incident on Friday, and you say it calmly.
How we work
Our values are the job description.
We hire for three things before any skill on a résumé. You will see them in every review, incident and launch.
Precision
Every pixel, packet and word is deliberate.
You measure before you claim, write it down before you ship, and treat accuracy as part of the craft rather than a final check.
Resilience
Systems that bend and recover.
You design for failure, recover fast, and run blameless reviews. You hold up in the incident room and in the boardroom.
Open roles
Find your post.
Own the single-file agent and the hooks that record what AI tools do on Linux, macOS and Windows.
- Keep the hooks fast: write one line and exit
- Support new releases of Claude Code, Cursor and Antigravity as they ship
- Make the agent hard to switch off quietly
Grow the bpftrace watcher that sees what hooks miss: subprocesses, scripts and files outside the hook path.
- Catch more indirect access without slowing machines down
- Keep the watcher running as a protected system component
- Research what similar visibility could look like on macOS and Windows
Write and test the rules that spot secrets, credentials and risky commands in what AI tools touch.
- Grow and tune the 61 built-in rules
- Cut false positives without missing real leaks
- Track new secret formats as providers change them
Research the protections on our roadmap, starting with stripping secrets before they reach a model.
- Prototype secret stripping and package checks
- Test them against real AI tool sessions
- Decide, with evidence, what is ready to ship
Design a dashboard a security lead can read in one glance, and a feed anyone can follow.
- Own the plain-English activity feed and alert review
- Shape the daily report teams file as evidence
- Test with real security and platform teams every sprint
Run the demo on a customer's own network, then stay with them until every developer machine is covered.
- Lead technical evaluations with security and platform teams
- Help customers set up the self-hosted server
- Bring field feedback straight into the roadmap
Teach developers to build fearlessly with AI tools without leaking secrets.
- Write guides on keeping secrets inside the network
- Share sample detection rules for common stacks
- Turn real incidents into lessons, with permission
How we hire
Four steps. No surprises.
The same process for every role, so you always know what comes next and how long it takes.
1
Intro call
30 minutesA conversation about your work, the role and what the watch looks like day to day.
2
Work sample
About 3 hoursA realistic task from the team you'd join, done on your own time. No trick questions.
3
Team loop
Half a dayWalk us through your sample, then meet the people you'd work with every week.
4
Decision
Within a weekA clear yes or no with reasons, and an offer you can compare line by line.
Don't see your post? Write to us anyway.
Tell us what you'd build and how it would keep secrets inside the network. Reach us through the contact page.