The Team

Our Team

Infrastructure engineers, security researchers, and deployment specialists who built the tool they wished existed.

Ana Kowalski

Ana Kowalski

CEO & Co-Founder

Previously infrastructure lead at Booz Allen Hamilton, where she managed patch compliance for federal agency environments with 2,000+ endpoints. Holds a CISSP and led the team that reduced their average patch deployment time from 21 days to under 4 hours through process automation. Founded PatchGuard in 2022.

Marcus Delroy

Marcus Delroy

CTO & Co-Founder

Former senior engineer at Crowdstrike, focused on distributed scanning systems. Designed the PatchScore™ engine and PatchGuard's agentless cloud connector architecture. Contributed to OSV (Open Source Vulnerabilities) schema before joining PatchGuard full time. MS in Computer Science from Georgia Tech.

Priya Venkatesh

Priya Venkatesh

VP Engineering

Eight years at HashiCorp building Vault and Nomad, with deep expertise in secrets management and job orchestration. Joined PatchGuard to lead platform engineering in 2023. Architected the rollback engine and the YAML-based patch policy system. Holds three AWS certifications.

How We Work

Small team. High trust. Async-first.

PatchGuard is a 9-person team. Everyone ships code or talks directly to customers — sometimes both. We operate async by default, document decisions in writing, and don't have standing meetings that could be an email.

Security is a domain that demands precision. We extend that standard to how we build the product: every feature has a written spec, every deployment has a rollback plan, and every on-call rotation has a written runbook. We practice what we sell.

9
Full-time team members
4
Countries represented
100%
Remote-first workforce
2
Years shipping weekly
Careers

What we look for

We hire for specific experience in infrastructure and security, not for general engineering potential.

Production experience

You've run Linux or Windows Server environments at scale. You've been on-call for infrastructure incidents. You know what a patch breaking a production workload looks and feels like.

Written clarity

We work async. You write specs before you write code. Design decisions are documented, not decided verbally in a standup and immediately forgotten. Strong writing is a core job requirement.

Customer proximity

Engineers here talk to customers directly. You'll sit in on demos, read support tickets, and occasionally hop on a call when a customer is debugging a deployment issue. Customer feedback drives the roadmap.

Interested? We're growing the engineering and security research teams.

View Open Roles