Lead, Data Center Security Delivery (Construction to Operations)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate etc. We need to parse the posting. Key sections: - About Anthropic (mission) - maybe not needed? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About the role" corresponds to "About The Role" paragraph. So we put that under

About the role

with

content. - Responsibilities: list under "Key Responsibilities". Use

• . - Requirements: "Minimum Qualifications". Use
  • . - Qualifications: "Preferred Qualifications". Use
    • . - Skills: Not explicitly listed; maybe we can infer from qualifications? But we should only include if posting has real specific content. There's no separate skills section. So we omit Skills. - Benefits: The posting mentions "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". That's benefits. Also earlier: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". So we can include Benefits section with those items as list. - Pay: "The annual compensation range for this role is listed below. Annual Salary $290,000—$365,000 USD". So Pay section with that info. - Schedule: There's "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule/hybrid policy. Also maybe "Logistics" includes Minimum education, field of study, years of experience, location-based hybrid policy, visa sponsorship. Those could be considered under Requirements? But we already have Minimum Qualifications. The "Logistics" section includes education, field of study, years of experience, location-based hybrid policy, visa sponsorship. Those are more like qualifications/requirements. However we already captured Minimum Qualifications (which are bullet points). The logistics includes additional specifics: Minimum education: Bachelor’s degree or equivalent; Required field of study: A field relevant to the role; Minimum years of experience: Years of experience required will correlate with internal job level; Location-based hybrid policy: expect staff to be in office at least 25% of time; Visa sponsorship: we sponsor visas but not guaranteed. Those are substantive. Should we put them under Requirements or Qualifications? They are more like baseline requirements. Could create a separate section "Requirements" already used for Minimum Qualifications. Could add those as additional list items under Requirements. But we must not invent sections; we can add to Requirements. We must not repeat job title as heading. No Job ID etc. We must not include boilerplate like EEO, scam warning, etc. Remove those. We must not include duplicated lines. We must preserve all substantive information. Thus we need to extract: About the role: The paragraph under "About The Role". Let's copy that exactly? It's long. We'll include as

      . Responsibilities: bullet list under "Key Responsibilities". We'll extract each bullet. Requirements: combine Minimum Qualifications bullet list plus logistics items (education, field of study, years experience, hybrid policy, visa sponsorship). Also maybe "Minimum education: Bachelor’s degree or an equivalent combination..." etc. Qualifications: Preferred Qualifications bullet list. Benefits: list from "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". Also maybe "We think AI systems..." not benefit. So just those. Pay: annual salary range. Schedule: location-based hybrid policy (already in requirements). But schedule section maybe just that policy. However we already used hybrid policy in requirements; but we could still have schedule section with that policy. The instruction: prefer a few substantive sections over many thin ones. If we already put hybrid policy in Requirements, we might not need separate Schedule. But we need to decide if schedule content exists separate from requirements. The posting includes "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule/hybrid. Could be placed under Schedule. But we also have education etc under Requirements. Might be okay to have both Requirements and Schedule sections. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid policy, so we can have Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Skills. Now format. We need to ensure we don't include any markdown fences. Just raw HTML. Let's craft.

      About the role

      Anthropic is building data center campuses at a pace where several are under construction at once, each moving through design, construction, commissioning, and turnover to an operating partner. Security scope on those projects (the physical protections, the systems that enforce them, and the operational readiness of the company that will run the site) has to be delivered as deliberately as the buildings themselves. As Lead for Data Center Security Delivery, you will own security through that entire arc for every campus under construction: from groundbreaking, through construction-phase security, through commissioning and milestone acceptance, to a clean handover into full operation. You are the single point of accountability for "the site's security is actually ready", and you will verify that the operating partner has its people, processes, systems, and contractual security obligations genuinely in place before a site goes live. This is a delivery role, not a watch-the-dashboard role. You'll absorb the day-to-day noise of active construction sites (schedule slips, design changes, vendor coordination, escalations) so the rest of DCSE can stay focused on steady-state operations and systems. And where DCSE's requirements or processes don't survive contact with a real construction schedule, you will have the authority, and the expectation, to rewrite them. Role boundaries. This seat is distinct from DCSE's regional security operations leads and from the team's systems-engineering roles. The operations leads own steady-state regional programs (vendors, guard force, incident response) once a site is running; the systems roles build platforms and tooling. This role owns the delivery arc: every site's security scope from construction start through commissioning, acceptance, and handover, after which accountability transfers to operations.

      Responsibilities

      • Own the security delivery program across every Anthropic campus under construction: concurrently, from groundbreaking to handover.
      • Construction-phase security delivery: temporary site security, contractor vetting and access, protection of installed equipment, and coordination with general contractors and site teams on every active build.
      • Milestone and commissioning acceptance: define and maintain the security acceptance criteria at each construction milestone and commissioning gate; run or attend acceptance events (FAT/SAT, punch lists); issue or withhold the security sign-off.
      • Operator readiness verification: build and run a structured, evidence-based readiness process proving the operating company is genuinely ready before handover: staffing and guard force in place, SOPs adopted, security systems commissioned and monitored, contractual security obligations demonstrably met.
      • Clean handover to operations: own the turnover package (as-builts, test records, credentials, punch-list closure, residual-risk register) and the defined transition from construction-phase to operational security ownership.
      • Requirements and process authority: rewrite DCSE's construction-security requirements, delivery processes, and acceptance frameworks where they fail in the field, and codify what works, so each build is cleaner than the last.
      • Representation and escalation: represent security in design reviews, owner-architect-contractor (OAC) meetings, and change management; coordinate integrators, general contractors, and operator counterparts on security system installation, testing, and commissioning; surface schedule and readiness risks early, with options, to DCSE leadership and cross-functional partners.

      Requirements

      • Have personally delivered the physical security scope on new-build data center (or comparable critical-infrastructure) construction projects (design reviews through construction, commissioning, and turnover to operations) and can name the sites and your role on them.
      • Have run milestone- or commissioning-acceptance processes: FAT/SAT, punch lists, turnover documentation, formal sign-off.
      • Have held an operator, landlord, or vendor accountable to contractual security obligations, with evidence rather than assurances.
      • Are comfortable being the person who says "not ready", and can do it in a way that produces a plan rather than a standoff.
      • Can absorb the operational noise of multiple concurrent construction sites and still drive each one toward its handover date.
      • Can author requirements, standards, and process documents that get adopted, and are willing to rewrite your own when they fail in the field.
      • Work through influence with general contractors, integrators, operators, and internal partners; you shape decisions rather than block them.
      • Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience.
      • Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience.
      • Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position.
      • Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.
      • Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this.

      Qualifications

      • CPP (Certified Protection Professional) or PSP (Physical Security Professional) certification, or commissioning credentials.
      • Hyperscaler or major colocation new-build delivery experience.
      • Experience on both sides of an operator/tenant relationship.
      • Construction management or owner's-representative background.
      • Experience in regulated or high-assurance environments.

      Benefits

      • Competitive compensation and benefits
      • Optional equity donation matching
      • Generous vacation and parental leave
      • Flexible working hours
      • Lovely office space for collaboration

      Pay

      Annual Salary $290,000—$365,000 USD

      Schedule

      Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.

      Check duplication: We already included hybrid policy in Requirements list; now also in Schedule. That duplicates content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It didn't say we cannot duplicate, but we should avoid unnecessary duplication. Better to keep hybrid policy only in Schedule, and remove from Requirements list. However Requirements list also had education, field of study, years experience, visa sponsorship. Those are not duplicated elsewhere. So we should move hybrid policy to Schedule and remove from Requirements. Thus adjust Requirements list to exclude hybrid policy item. Let's rewrite Requirements list without hybrid