Security Technology Deployment Specialist

for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to extract sections: About the role (the paragraph after "About The Role"), Responsibilities (list), Requirements (maybe "You May Be a Good Fit If You Have" and "Strong Candidates May Have" etc). Also "Minimum education", "Required field of study", "Minimum years of experience", "Location-based hybrid policy", "Visa sponsorship", "We encourage you to apply..." etc. Those are requirements/qualifications. Also "Skills" maybe from bullet list of technologies? Could be part of requirements. Benefits: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". Also "We think AI systems..." not benefit. Pay: "Annual Salary $180,000—$230,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." Also maybe travel: "Are comfortable with 25% travel for site deployments". That's schedule? Could be part of schedule. We must not include sections with filler. So we will include:

About the role

Responsibilities

• each bullet from responsibilities list.

  Requirements

  combine "You May Be a Good Fit If You Have" list and "Strong Candidates May Have" list plus education, field of study, years of experience, location-based hybrid policy, visa sponsorship maybe? But visa sponsorship is more like a note; could be included as a paragraph. Also "We encourage you to apply..." is more encouragement not requirement; maybe we can drop as it's not a requirement. But we need to preserve ALL substantive information; we cannot drop encouragement? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However we can fold minor metadata into a short

  or drop it. The encouragement is not metadata? It's more like a note. Might be considered boilerplate? It's not legal/EEO but it's encouraging underrepresented groups. Might be considered substantive? It's about diversity encouragement. Could be included as a paragraph under Requirements or maybe a separate section? There's no specific heading for that. Could be included as a paragraph under Requirements. Also "We think AI systems..." etc is more about mission; maybe not needed. We also have "Guidance on Candidates' AI Usage:" which is maybe not needed. We must not include sections like "How We're Different" etc unless we map to a heading? Not required. But we need to preserve ALL substantive information; but we can maybe include that as a paragraph under About the role? Not exactly. The instruction says we should reformat job posting into clean, well-structured semantic HTML using those headings. It doesn't forbid adding other headings, but says use those headings for section headings. It doesn't say we cannot add other headings, but likely they expect only those headings. However they say "include a section ONLY when the posting has real, specific content for it". So we could add a section like "About Anthropic" maybe? But they didn't list that as allowed heading. They gave a list of headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. Any other content should be folded into those sections if appropriate, or dropped if it's boilerplate. The "About Anthropic" paragraph at start could be considered "About the role"? No, it's about the company. Could be placed under "About the role"? Not really. Could be omitted as it's not required? But they said preserve ALL substantive information. However the "About Anthropic" is substantive but not about the role. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say we must include company description. But they said preserve ALL substantive information; but maybe they consider that as part of the job posting and we need to keep it somewhere. Could we put it under "About the role"? Might be a stretch but maybe acceptable as it's still about the role context. However they said "About the role" heading for section headings (e.g. About the role, Responsibilities...). So likely they expect the "About the role" section to contain the description of the role, not the company overview. The company overview could be considered boilerplate? It's not legal/EEO but it's about the company mission. Might be considered substantive but not required to keep? The instruction ambiguous. I'd err on keeping it as a paragraph under About the role, maybe as an introductory paragraph before responsibilities. That would preserve it. Similarly, "We think AI systems..." etc could be considered part of "About the role" or maybe omitted. But to be safe, include it as a paragraph under About the role. Now Benefits: we have "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." That's benefits. Pay: Annual Salary $180,000—$230,000 USD. Schedule: Location-based hybrid policy: at least 25% time in office. Also travel 25% for site deployments. Could combine. Now Skills: maybe list of specific technology experience: Genetec Security Center, Axis cameras, Wavelynx, Commend Symphony Cloud, Alcatraz.ai, Ambient.ai, SureView, Envoy; also experience with OSDP, modern credential technologies, encryption protocols; scripting or automation (Python, PowerShell); health monitoring and observability platforms; knowledge of SOC 2 compliance, GDPR, physical security compliance frameworks; change management, configuration control, version-controlled infrastructure documentation. Also IP networking, VLANs, PoE, infrastructure requirements. Also broad technology experience across access control, video management, intercoms, visitor management, AI/analytics, alarm monitoring platforms. Also strong technical communicator, etc. Those could be under Skills. Requirements: the "You May Be a Good Fit If You Have" list (5+ years experience, deployed across 50+ sites, built standardized processes, worked across InfoSec/IT/Networking/Identity Management, supported SSO integration, InfoSec reviews, enterprise application onboarding, broad technology experience across platforms, strong technical communicator, experience with IP networking, VLANs, PoE, infrastructure requirements, comfortable with 25% travel). Also "Strong Candidates May Have" list (previous experience at hyper-growth tech company, experience with specific tech stack, certifications, experience with OSDP etc, scripting, health monitoring, SOC2/GDPR, change management). Also Minimum education: Bachelor’s degree or equivalent. 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 (that's vague). Could be omitted as filler? It's not specific; maybe we drop as it's not specific. Location-based hybrid policy: we already have under Schedule. Visa sponsorship: we could include under Requirements as a note. We must not create sections with filler like "commensurate with experience". We have no such. Now we need to output HTML fragment. Structure:

  About the role

  ... (combined paragraphs)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  Maybe also include a

  for education etc. But we need to decide what goes into Requirements vs Skills. The instruction says use

  • for any list of duties/requirements/benefits. So we can put requirements as list. Skills also as list. We have many items; we can split: Requirements: experience, education, etc. Skills: technical skills, certifications, etc. Let's extract. About the role paragraph(s): From "About The Role": "As part of Anthropic’s Global Safety, Intelligence, and Security (GSIS) team, the Security Technology Deployment Engineer will own the validation, standardization, and deployment of physical security technology across Anthropic’s rapidly expanding global office portfolio. This role bridges the gap between technology selection and production-ready operation — ensuring that every security platform deployed is rigorously tested, properly integrated with enterprise infrastructure, fully documented, and built for scale. You’ll define the installation standards, configuration baselines, and deployment processes that the broader team executes against — from access control migrations and intercom replacements to AI analytics onboarding and new application integrations. You’ll work across InfoSec, IT, Networking, and Identity Management to ensure every security application passes review, integrates with SSO, and is supported within Anthropic’s infrastructure before going live. Your work will directly determine whether Anthropic’s security technology stack scales reliably as the company grows from dozens of locations to a global enterprise footprint." Also earlier "About Anthropic" paragraph: "Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems." And later "We think AI systems like the ones we're building have enormous social and ethical implications. We think this makes representation even more important, and we strive to include a range of diverse perspectives on our team." plus "We believe that the highest-impact AI research will be big science..." etc. That's more about company. Could be included but maybe not needed. To preserve all substantive info, we could include a paragraph after About the role that includes the mission and diversity statements. But that might be better as a separate section? Not in allowed headings. Could fold into About the role as introductory context. Thus About the role will have multiple

    elements. Now Responsibilities list: copy each bullet from responsibilities section. Let's list them: - Validate and deploy new and replacement security technology platforms including access control systems, intercom solutions, video management,