The Security TeamExamples of key problems the team is working on- You're securing the frontier of AI. The model weights training on our infrastructure are the most valuable and most targeted artifacts in technology, and we're standing up the compute to hold them faster than anyone ever has. A breach isn't a leak, it's the frontier walking out the door.
- Build the entire security program from scratch. Most leaders inherit someone else's system and spend a career patching it. Here you own it end to end, bare metal to boardroom, as we scale across continents.
- Your threat surface is measured in gigawatts. The customers running on our infrastructure are building the most consequential technology in human history, and being responsible for the physical and logical security of that work makes everything else feel small.
Role Scope- Own exposure and vulnerability management across the estate: external attack surface, cloud and Kubernetes, corporate endpoints, network infrastructure, and the bare-metal fleet beneath them.
- Extend exposure and vulnerability management across the corporate fleet (macOS, Windows, Linux): OS and application patch posture, first-party and third-party software, and drift from approved baselines.
- Cover software outside our managed and approved catalogs: unmanaged apps and SaaS, package-level software on endpoints (npm, PyPI, Homebrew), and browser and IDE extensions. Identify it, assess it, and drive it to remediation or removal.
- Build the engineering that makes it work: asset inventory, scanner orchestration, deduplication, and prioritization built on reachability and real-world exploitation rather than raw CVSS.
- Engineer remediation into the workflows teams already use, so findings land as owned tickets, fixes ride existing pipelines, and closure verifies automatically.
- Remediate alongside the teams that own the systems: write the patch PR, harden the base image, fix the IaC module, and ship the config change rather than just requesting it.
- Extend the program past where enterprise playbooks run out: BMC and device firmware, GPU drivers, host images at fleet scale, and the long tail of data center equipment.
- Run intake for pen test findings and external reports, and report exposure honestly: what's reachable, what's exploited in the wild, what's accepted and by whom.
What We're Looking ForThe below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.- You've built vulnerability management as an engineering problem: pipelines, automation, and integrations rather than spreadsheet triage.
- You write production-quality automation (Python or similar) and have wired scanners, asset systems, and ticketing into something coherent.
- You've run prioritization that survives contact with reality: KEV, EPSS, reachability, and the judgment to overrule all three.
- You've fixed vulnerabilities yourself, in someone else's codebase or infrastructure, and your pull requests got merged because they were good, not because security demanded it.
- You've driven remediation at scale through teams that don't report to you and kept SLAs credible without burning the relationships.
- You can take a technology class most programs never touch, firmware or GPU stacks or data center equipment, and stand up a defensible assessment approach instead of waiting for a vendor to sell you one.
- You've run vulnerability and exposure coverage on corporate endpoints and third-party software, including the unmanaged long tail of shadow apps, packages, and extensions.
- Bonus: External attack surface management platforms. Firmware or BMC security depth. CSPM/KSPM tooling. Exploit development or reachability validation. Endpoint management and patching tooling (MDM, EDR), software inventory, and extension and supply chain risk.
We are committed to pay equity and transparency.
