Staff / Senior Data Center Security Engineer

About the role

Claude is trained and served on hardware in data centers Anthropic operates and in sites partners build and run for us. DCSE secures that footprint: the sites, the hardware moving through them, and the people and vendors who touch it. You'll be the engineer for one or more security domains end to end: design the controls, build the systems that enforce and verify them, and set the technical standard the rest of the team and our partners build to.

The engineering is in the controls and the tooling that proves them. The goal is security that runs itself: requirements kept as code and checked automatically, evidence, chain of custody and access continuously verified, and tools and agents in place of manual reviews. We favor simple, standard controls and tools that can be verified over elaborate ones. We use Claude throughout our engineering workflow and expect you to as well.

This is a foundational role: you'll shape how our security engineering is built and scaled. The team's physical security systems engineers design and test the site security systems themselves; this role engineers the controls around them and across the domains beyond the facility itself: hardware custody, media, personnel and vendors. You'll work with the rest of DCSE, Anthropic's compute, data center operations, legal, compliance and procurement teams, and directly with data center operators, hardware vendors and logistics providers.

The role involves regular travel to data center sites, which are critical infrastructure, and may include on-call for security events at them.

Key responsibilities

• Security domains, end to end: own one or more of physical security at partner-operated and Anthropic-operated sites, hardware supply chain and chain of custody, media protection and sanitization, personnel security and site access, third-party and vendor security assessment, and maintenance and contingency controls
• Tools, automation and AI agents: build the internal tools, automation and agents the team runs on: evidence collection, access reviews, asset and custody tracking, partner intake. When a process keeps costing people time, you build the tool that retires it
• Security review for new sites, leases and vendors: find the gaps in the design, the contract and the operator's procedures, write the security terms and exhibits, and verify the fixes after signing
• Requirements and procedures as code: write requirements and procedures that a partner can build to and an assessor can test, kept as code in a version-controlled repository
• Site and supplier assessment: assess sites and suppliers against those requirements, on site and from evidence; document deviations and engineer the compensating control where a requirement can't be met as written
• Continuous compliance evidence: tie controls to the compliance frameworks we and our partners are assessed against, with evidence always current so an assessment pulls from it directly
• Security event response: respond to security events at sites (intrusion alarms, custody breaks, access violations) with operations teams and site operators; write up what happened and fix the control that allowed it

Minimum qualifications

• Have engineered a security control domain end to end: designed the controls, built or integrated the systems that enforce them, and verified they work
• Read and review code, design the data systems behind security tooling, and build automation (often with AI coding agents) using Git and code review
• Have done security work hands-on for data centers, critical infrastructure or a large hardware fleet, in at least one of the domains under Key responsibilities
• Have applied a control framework such as NIST SP 800-53, ISO 27001 or SOC 2 to real systems and produced the evidence for it
• Write requirements a third party can build to and an assessor can test: each states what must be true, how it is verified and what evidence shows it

Preferred qualifications

• Experience across several of the domains above rather than one
• Experience at sites you did not fully control: cloud, colocation or GPU cloud operators
• Experience with federal assessment regimes based on NIST SP 800-53, including supply chain (NIST SP 800-161) and media sanitization (NIST SP 800-88) guidance; have produced evidence an assessor accepted
• Have built governance, risk and compliance (GRC) or evidence automation: automated control checks, asset or custody tracking, questionnaire and assessment pipelines, docs-as-code workflows
• Have run incident response at physical sites: alarms, investigations, after-action fixes
• Have worked in live data halls and on active construction sites, and can follow a method of procedure
• Experience redlining contract security language with legal and procurement counterparts
• Experience with international sites: per-country personnel screening and staffing restrictions, data residency, and export controls on hardware
• Have built AI agents or automation that replaced recurring manual security work