Lead the Zero Day Engineering team to turn vulnerabilities into verified protection for Cloudflare and its customers.
Posted by employer 2 days ago
First seen on Joblaze 1 day ago
Last verified on the company career page 1 day ago
What you'll build
Must have
Nice to have
AI in the day-to-day
Build AI-assisted workflows for triage, research, exposure analysis, drafting, and release tracking.
Not disclosed in this posting: compensation, years of experience, visa sponsorship.
Joblaze summary
The Head of Zero Day Engineering at Cloudflare is responsible for leading a team that transforms newly identified vulnerabilities into effective protections for the company and its clients. This role requires a strong background in security-critical systems, vulnerability response, and the ability to manage complex technical changes across teams. Ideal candidates will have experience in high-pressure environments and a practical understanding of mitigation and patching processes. The position emphasizes collaboration and the integration of AI-assisted workflows to enhance operational efficiency.
Joblaze insights
Quick facts
From the original posting
Cloudflare is hiring a Head of Zero Day Engineering to build and lead the team that turns newly discovered vulnerabilities into verified protection—for Cloudflare and its customers.
High-priority vulnerabilities rarely fit within one team’s boundaries. A fix may require kernel expertise, changes across software dependencies and trust stores, fleet-wide deployment, customer-facing WAF protections, and investigation of prior exploitation. You will bring those efforts together, with clear ownership from initial disclosure through verified remediation.
This is a hands-on engineering leadership role. You will recruit the team, establish its operating model, and build the tooling that makes response faster and more reliable. You will combine experienced human judgment with carefully evaluated AI-assisted workflows—not automate away accountability.
Build and lead the team
- Establish Zero Day Engineering’s charter, priorities, operating model, and partnerships across Cloudflare.
- Recruit, develop, and lead engineers spanning vulnerability response, exposure analysis, mitigation, patching, artifact provenance, release coordination, and automation.
- Build a sustainable incident-command rotation, clear escalation paths, and effective handoffs across teams and time zones.
- Create a culture of technical depth, calm execution, blameless learning, and shared accountability.
- Establish a consistent intake and triage process for public vulnerabilities, private disclosures, and internal findings.
- Ensure each significant vulnerability has a clear owner, an evidence-based exposure assessment, and a path to verified remediation.
- Lead decisions about mitigation versus patching, balancing urgency, exploitability, exposure, and production risk.
- Enable the team to implement fixes directly where practical and coordinate partner-owned changes through verified production deployment.
- Partner with SIRT on suspected compromise, exploitation analysis, hunting, and eviction verification. Ensure blocking an exploit is not mistaken for removing an existing compromise.
- Drive artifact and dependency provenance so responders can quickly determine what Cloudflare runs and where it is exposed.
- Build repeatable capabilities for safe exploit validation, mitigation, patch qualification, and fleet-wide remediation.
- Coordinate managed WAF response with SRA, Managed Rules, Firewall/ERE, and WAF engineering while preserving specialist ownership.
- Maintain strong review, staged-release, health-monitoring, and rollback practices—including during urgent response.
- Turn recurring response problems into durable engineering improvements rather than repeated manual coordination.
### Develop responsible AI-assisted operations
- Build AI-assisted workflows for triage, research, exposure analysis, drafting, and release tracking.
- Establish replay evaluations, measurable quality thresholds, access controls, and human approval gates before production use.
- Keep release authority, disclosure approval, risk acceptance, and other consequential decisions with accountable people.
- Measure actual operational benefit and failure rates rather than assuming productivity gains.
- Define and report response metrics, including time to assess exposure, mitigate, patch, and verify remediation.
- Translate technical uncertainty into clear decisions, priorities, and executive updates.
- Partner 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 development.
- Experience building and leading engineering teams responsible for security-critical systems, vulnerability response, production infrastructure, or closely related work.
- A record of delivering complex technical changes across organizational boundaries, including when priorities compete and authority is distributed.
- Strong technical judgment across several of the following: Linux and operating systems, vulnerability analysis, software supply chains, application security, distributed systems, fleet management, or production reliability.
- Experience leading high-pressure technical response with incomplete information, making defensible decisions, and communicating what is known, unknown, and next.
- A practical understanding of mitigation, patching, exploitation detection, and remediation verification—and the differences between them.
- Experience establishing safe deployment, validation, and rollback practices at scale.
- The ability to recruit and develop strong engineers while remaining credible in technical reviews and operational decisions.
- Clear written communication and the ability to work effectively with engineers, security specialists, executives, and legal partners.
- A thoughtful approach to AI-assisted engineering, including evaluation, security boundaries, and human accountability.
- Coordinating responses to embargoed vulnerabilities or working with upstream maintainers and security researchers.
- Kernel patching, backporting, runtime or trust-store remediation, or large-scale dependency updates.
- WAF rule development or deployment, exploit reproduction, host forensics, or threat hunting.
- Building artifact inventories, dependency graphs, or software provenance systems.
- Developing and operating AI-assisted engineering tools with rigorous evaluation and access controls.
- Building a new team or function while maintaining effective partnerships with existing owners.
- Vulnerabilities have a clear path from intake to an accountable owner and verified remediation.
- Exposure questions are answered quickly with evidence rather than repeated manual investigation.
- Urgent fixes move faster without bypassing production safety or disclosure controls.
- Cloudflare can distinguish between an exploit being blocked, a vulnerability being patched, and a compromise being removed.
- AI-assisted workflows deliver demonstrated value within explicit safeguards.
- The team’s capabilities and staffing evolve based on measured demand and outcomes.
Standard company text repeated across Cloudflare's postings is omitted here.