It protects and speeds up web applications without requiring hardware, software installs, or code changes, and traffic routed through its global network gets smarter with each request, improving performance and reducing spam and attacks.
The team wants people who notice the Internet problems others have accepted, who are comfortable using current AI tools to build fixes, and who favor iteration and shared improvements over bureaucracy. AI is treated as a tool in solving hard problems.
The company is hiring a Head of Zero Day Engineering to build and lead a team that turns newly discovered vulnerabilities into verified protection for the company and its customers.
Serious vulnerabilities usually cross team lines. A fix can involve kernel work, changes to software dependencies and trust stores, fleet-wide rollout, customer-facing WAF protections, and checking whether attackers already exploited the flaw. You will coordinate these efforts and keep clear ownership from first disclosure through verified remediation.
This is a hands-on leadership role. You will hire the team, define how it operates, and build tooling that speeds up and stabilizes response. Experienced judgment stays central, with AI-assisted workflows that are carefully evaluated and never remove human accountability.
The company runs a free program protecting journalism and civil society groups, and a free service for U.S. state and local election websites. It also operates a public DNS resolver, 1.1.1.1, which does not store client IP addresses and does not sell user data to advertisers.
Responsibilities
Build and lead the team
Set the team's mandate, priorities, operating model, and working relationships across the company.
Hire, grow, and lead engineers in vulnerability response, exposure analysis, mitigation, patching, artifact provenance, release coordination, and automation.
Set up a sustainable incident-command rotation, clear escalation paths, and smooth handoffs across teams and time zones.
Build a culture of technical depth, calm execution, blameless learning, and shared accountability.
Own vulnerability response from start to finish
Create one consistent intake and triage process covering public vulnerabilities, private disclosures, and internal findings.
Make sure every significant vulnerability has a named owner, an exposure assessment based on evidence, and a route to verified remediation.
Decide between mitigation and patching by weighing urgency, exploitability, exposure, and production risk.
Let the team apply fixes itself where it makes sense, and coordinate changes owned by other teams through verified production deployment.
Work with SIRT on suspected compromises, exploitation analysis, threat hunting, and confirming eviction. Make sure stopping an exploit is never treated as removing an existing compromise.
Build for speed and safety
Improve artifact and dependency provenance so responders can quickly see what the company runs and where it is exposed.
Build repeatable ways to validate exploits safely, deploy mitigations, qualify patches, and remediate across the fleet.
Coordinate managed WAF response with SRA, Managed Rules, Firewall/ERE, and WAF engineering, while each group keeps ownership of its specialty.
Keep strong review, staged release, health monitoring, and rollback practices in place, including during urgent response.
Turn repeated response problems into lasting engineering fixes instead of ongoing manual coordination.
Develop AI-assisted operations responsibly
Build AI-assisted workflows for triage, research, exposure analysis, drafting, and release tracking.
Set up replay evaluations, measurable quality thresholds, access controls, and human approval gates before any production use.
Keep release authority, disclosure approval, risk acceptance, and other major decisions with accountable people.
Measure real operational benefit and failure rates instead of assuming productivity gains.
Set direction and communicate clearly
Define and report response metrics, including time to assess exposure, mitigate, patch, and verify remediation.
Turn technical uncertainty into clear decisions, priorities, and executive updates.
Work with Product Security, Legal, Communications, and engineering leaders on coordinated disclosure and customer communication.
Use workload and outcome data to guide staffing, investment, and capability growth.
Requirements
Experience building and leading engineering teams that own security-critical systems, vulnerability response, production infrastructure, or closely related work.
A track record of delivering complex technical changes across organizational boundaries, including when priorities conflict and authority is spread out.
Solid technical judgment in several of these areas: Linux and operating systems, vulnerability analysis, software supply chains, application security, distributed systems, fleet management, or production reliability.
Experience leading high-pressure response with incomplete information, making defensible decisions, and communicating what is known, unknown, and next.
A working understanding of mitigation, patching, exploitation detection, and remediation verification, and how they differ.
Experience setting up safe deployment, validation, and rollback practices at scale.
Ability to recruit and develop strong engineers while staying credible in technical reviews and operational decisions.
Clear written communication and the ability to work with engineers, security specialists, executives, and legal partners.
A considered approach to AI-assisted engineering that covers evaluation, security boundaries, and human accountability.
Helpful but not required: experience coordinating responses to embargoed vulnerabilities or working with upstream maintainers and security researchers; kernel patching, backporting, runtime or trust-store remediation, or large dependency updates; WAF rule development or deployment, exploit reproduction, host forensics, or threat hunting; building artifact inventories, dependency graphs, or provenance systems; developing and running AI-assisted engineering tools with rigorous evaluation and access controls; building a new team or function while keeping good relationships with existing owners.
The role may require access to information controlled under U.S. export laws, including the Export Administration Regulations. Any offer may depend on your ability to receive controlled software or technology without sponsorship for an export license.
Success looks like: every vulnerability has a clear path from intake to an accountable owner and verified remediation; exposure questions are answered quickly with evidence; urgent fixes move faster without skipping production safety or disclosure controls; the company can tell apart an exploit being blocked, a vulnerability being patched, and a compromise being removed; AI-assisted workflows show proven value within explicit safeguards; the team's size and skills change based on measured demand and results.
Conditions
Applicants who reach the offer stage may be asked to attend an in-person interview at a the company office or hub. Details will be shared at that stage.
Where you’d work
Part of the week in the office
No visa sponsorship
About the company
Hidden companyCompany hidden
Industry: Cybersecurity
Good
Your chances
Still hiring, not crowded yet, and you'd be among the first.
15 checks run
4 good signs
0 red flags
Still hiring?
10 checks
Actively hiring
StaleHiring
In its favour2
Still on the company's own careers site, checked 1 h agoModerate evidence
Found in the last 48 hours, before the big job boardsModerate evidence
How crowded?
5 checks
Low
QuietCrowded
In its favour2
In its Early Window: not on the big job boards yetStrong evidence
Lead level: far fewer people qualifySlight evidence
?
Fits Me
How well does this role fit you?
Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.