US Public Sector Compliance, Security GRC

About Anthropic 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. About the team Anthropic's Security Governance, Risk, and Compliance (GRC) team is the connective tissue that holds the company accountable to its security commitments. We translate regulatory, customer, and voluntary obligations into controls that teams act on, and give leadership a bird's-eye view of how well we're meeting them. We're building toward a fundamentally different kind of GRC: one that directs Claude, with the right humans in the loop, to challenge and evidence the performance of controls continuously rather than through periodic audits. Within Security GRC, Compliance and Audit Programs (CAP) runs the integrated audit across our frameworks and maintains the Common Control Framework the program hangs off. This role sits in Compliance & Audit Programs and works one regime family, US public sector, from requirements through authorization and ongoing compliance, working alongside the public sector engineering pods rather than downstream of them. About the role You'll help drive the compliance programs that keep Anthropic's US government authorizations current: federal civilian (FedRAMP, including FedRAMP 20x for Claude Enterprise), Department of War (DoD impact levels, CMMC, NIST SP 800-171), and state and local (StateRAMP, TX-RAMP and agency requirements). You'll own the recurring cycles those authorizations run on (continuous monitoring, POA&M, annual assessments, significant changes), help build new authorizations as we add them, and keep every frontier model's authorizations current. You'll turn government requirements into specific, testable requirements that engineering teams build against, review the evidence that comes back, and say so when a launch is not ready for a government boundary. You'll map US government requirements onto our Common Control Framework so the public sector view and the integrated audit view of the same control stay one framework. Building with Claude is a normal part of the job: mapping, evidence collection and reporting, with you deciding where human judgment stays in the loop. This is an individual contributor role, working closely with a peer on US public sector compliance, for someone who works well independently, writes clearly, and gets satisfaction from a government authorization that holds up as the product changes underneath it. Key responsibilities Run the recurring compliance cycles for our US government authorizations (continuous monitoring, POA&M, annual assessments, SSP updates, significant changes and incident notifications), starting with C4G on Palantir FedStart and the NIST SP 800-171 assessment with Schellman Co-own FedRAMP 20x work for Claude Enterprise, and help build new authorizations (first-party FedRAMP High, DoW impact levels, StateRAMP and TX-RAMP) with requirements and evidence work Support model authorizations in GovCloud and Vertex for every model launch, as the GRC member of the Inference and model delivery pod Translate government obligations into partner team requirements, for example vulnerability SLAs in our internal vulnerability reporting platform, and review the evidence Answer public sector customer and deal questions (what a boundary allows, CUI, IRS Publication 1075, CJIS, ITAR), and handle questionnaires and RFIs until they move to Customer Trust Map US government requirements onto the Common Control Framework with the Controls Assurance Lead and keep one source of truth for status Build with Claude: automate mapping, evidence collection and reporting, and verify machine-drafted language before it becomes the record Minimum qualifications Several years in security compliance or IT audit with hands-on US government compliance for a cloud service (FedRAMP, DoD impact levels, CMMC or NIST SP 800-171, or StateRAMP), including the ongoing compliance cycle after authorization Working command of the NIST SP 800-53 Moderate baseline and the mechanics of authorization: boundary definition, control implementation statements, assessment, continuous monitoring, POA&M and significant change Experience writing requirements for engineering teams from a control baseline and reviewing the evidence that came back Working knowledge of how a GovCloud or Vertex style government region differs from commercial, and what changes when a model, feature or region is added to an authorized boundary Enough technical fluency to read a runbook, configuration or pipeline definition and judge whether it enforces the written control Clear writing, because implementation statements and status reports are what assessors, engineers and leadership work from Ability to get partner teams to prio