AI Deployment Specialist, Beneficial Deployments

We need to output only HTML fragment with sections for headings that have real content. The posting includes sections: About Anthropic (maybe not needed? It's about the company, but we can include as a section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says we should not repeat the job title as a heading. It doesn't forbid "About Anthropic" but likely we should include sections that have real content: About the role, Responsibilities, Requirements (maybe "You May Be a Good Fit If You Have" is qualifications), Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections where posting has real specific content. Let's parse the posting: - "About Anthropic" paragraph: description of mission. Could be considered "About the company" but not in list. Probably we can include as a section? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should stick to those typical sections. However "About Anthropic" is not one of the listed examples but could be considered "About the role"? Actually there is "About The Role" heading later. So we should include "About The Role" as a section. Thus sections: - About The Role (the paragraph after "About The Role") - Responsibilities (list of duties) - Requirements / Qualifications (the "You May Be a Good Fit If You Have" bullet list) - Skills? Might be covered within qualifications. Could separate but we can combine. - Benefits? Not explicitly listed; there is mention of compensation range but it's weird: "Annual Salary $1—$2 USD" obviously placeholder nonsense; we should not include Pay section because it's not real specific content (it's nonsense). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state "Annual Salary $1—$2 USD" but that's obviously placeholder; but it's still stating a range, albeit unrealistic. However it's likely not real specific content; but we must decide. The instruction says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The salary range "$1—$2 USD" is placeholder/filler. So we should not include Pay section. - Benefits: Not mentioned besides generic "We offer competitive compensation and benefits..." later in "How We're Different" paragraph. That's generic, not specific. So we should not include Benefits. - Schedule: Not mentioned besides hybrid policy: "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time." That's specific enough? It states a schedule expectation. Could be considered Schedule section. The instruction: include a section ONLY when posting has real, specific content for it. This is specific: at least 25% time in office. So we could include Schedule. - Education requirements: "Education requirements: We require at least a Bachelor's degree in a related field or equivalent experience." That's qualifications. - Also there is "Logistics" repeated. Thus we will create sections:

About The Role

with paragraph(s) from that section.

Responsibilities

with

• items from responsibilities list.

  Qualifications

  (or Requirements) with the bullet list from "You May Be a Good Fit If You Have". Could also include education requirement. We could also have

  Skills

  but maybe not needed. We'll also include

  Schedule

  with the hybrid policy paragraph. We must not include boilerplate like EEO, scam warning, etc. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to extract the exact text for each section. Let's copy the relevant parts. About The Role: "As a Deployment Manager on the Beneficial Deployments team, you will guide customers from a signed contract into a live, governed, and adopted deployment so that customers achieve tangible impact rather than simply incremental improvement with Claude. You'll guide organizations from contract signature to production deployment across Claude for Enterprise, Claude Code, and our API products, fundamentally changing how they work and deliver on their missions. You'll be the technical hands that switch Claude on. Before any organization can drive adoption, before any champion can ship their first workflow, someone has to connect Claude to the customer's identity provider, get the right people provisioned into the right workspaces, and walk their CISO through how it all comes together. That's your work. You turn "we've signed the contract" into "our employees can log in, with the right access, under the right policies, the way our security team expects." This is a high-leverage role where you'll pioneer scalable activation methodologies that enable hundreds of nonprofit customers to unlock transformative use cases and realize measurable outcomes at unprecedented speed. You won't just follow playbooks. You'll design the frameworks and repeatable processes that can be deployed consistently across diverse customer environments, and you'll shape them into programs that reach customers we could never serve one at a time. You'll operate at the intersection of technical deployment, enablement, and program design. Some days you'll be in the weeds with a customer's IT team debugging a SAML assertion; other days you'll be stepping back to ask how the last ten deployments should change the next hundred. Your systems-thinking approach will directly shape how we activate customers, and your strategic management will ensure every customer achieves meaningful outcomes within their first 90 days. By identifying patterns across activations, you'll build replicable approaches to organizational change while maintaining the agility to customize solutions for each customer's unique transformation journey." That's the whole About The Role paragraph(s). We'll put inside

  . Responsibilities: The bullet list after "Responsibilities". Let's extract each line: - Own the complete activation journey from contract signature to production deployment, orchestrating cross-functional resources and customer teams to ensure rapid time-to-value across Claude for Enterprise, Claude Code, and API products. - Deploy Claude inside customer environments. - Configure and troubleshoot SSO (SAML), SCIM and JIT provisioning, MCP connectors, admin policy templates, and seat-assignment logic across Okta, Entra ID, Ping, and Google Workspace. - Deliver informative transitions to Support for deeper issues that require investigation or engineering support. - Act as a trusted advisor to customer CISOs and CTOs on governance and enterprise setup. - Bring a clear point of view on best practices, help security and IT leadership make the design decisions that determine whether a deployment holds up over time - Light up the capabilities that make Claude valuable. Enable and govern MCP connectors to the customer's systems, ensure Skills, Projects, and other capabilities are turned on and configured for their use cases, and work with their IT team on the approvals and OAuth consent this requires, so that day one feels ready - Design and scale activation frameworks by identifying patterns across deployments and building templated playbooks that balance standardization with customization for breakthrough outcomes. - Turn playbooks into programs. Package what works into repeatable, increasingly self-serve motions (deployment checklists, admin enablement sessions, onboarding cohorts, Claude-powered guidance) so that activation quality no longer depends on you being in the room. - Drive organizational transformation by developing change management strategies, rollout plans, and Train-the-Trainer programs that build internal AI champions and catalyze adoption across customer organizations. - Define and track success metrics across activation rate, time-to-value, customer satisfaction, and operational efficiency, using data to continuously optimize the motion. - Channel customer insights back to Product, Support, and Security teams, serving as voice of the customer so that repeat deployment blockers get solved once. We need to keep each as

• . Qualifications: The "You May Be a Good Fit If You Have" list. Let's extract each bullet: - 5+ years in customer-facing technical roles such as implementation management, technical account management, technical onboarding, solutions consulting, or customer success, with a track record of running multiple concurrent enterprise deployments with documented handoffs. - Experience serving nonprofits or mission-driven organizations. You've worked with (or inside) them and you understand how they differ from commercial enterprises. - Hands-on, sustained ownership of enterprise identity integration work. SAML, OIDC, SCIM v2, and JIT provisioning across at least two major identity providers (Okta, Entra ID, Ping, Google Workspace). You can debug a broken SAML assertion or a misconfigured SCIM attribute map without escalating, and you know when a Support handoff is the right call. - Experience advising CISOs, CTOs, or IT leadership on enterprise governance and setup for a SaaS or AI platform, with an informed point of view on org topology, access models, RBAC, and OAuth. - Working knowledge of security and compliance frameworks (SOC 2, ISO 27001, HIPAA, GDPR) sufficient to anticipate what a customer's security review will ask, and to know when to bring in our AI Security Specialist. - You've designed, shipped, and measured programs that serve many customers at once: onboarding cohorts, enablement series, admin academies, lifecycle or engagement motions. You naturally ask "how might we scale this?", turn 1:1 moments into 1:many programs, and instrument what you build so you know what's working. - Hands-on fluency with AI in your own workflow. You've prototyped, generated content, analyzed accounts, or replaced internal processes with LLMs, and you can talk concretely about what worked, what didn't, and what's next. You don't wait for AI tooling to arrive; you build it. - Organizational change and enablement experience including developing rollout strategies, navigating stakeholder resistance, building internal champions, and designing programs that drive adoption at scale. - Comfort building in ambiguity. This is a new role on the team, and what you build becomes the template. You'll thrive creating structure where none exists, adapting quickly as the business evolves, and learning continuously. - Data-driven and metrics-oriented. Experience setting and tracking success metrics from day one, using data to optimize approaches, and demonstrating impact to diverse stakeholders. Also education requirements: "Education requirements: We require at least a Bachelor's degree in a related field or equivalent experience." Could be included in Qualifications. Also "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" repeated. We'll include education as part of Qualifications. Schedule: The hybrid policy paragraph: "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." We'll put that in

  under Schedule. We should not include other duplicated logistics like visa sponsorship etc because that's generic but maybe considered substantive? It's about visa sponsorship. The instruction: include a section ONLY when posting has real, specific content for it. Visa sponsorship is specific: "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." That's specific content. Should we include a section for Visa? Not in the typical list but we could include as a section maybe "Visa Sponsorship". However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those are typical. It might be okay to add Visa Sponsorship as a section, but the instruction says "Prefer a few substantive sections over many thin ones." Adding Visa might be thin but still substantive. However we already have several sections; adding another may be okay. But we need to decide if we should include it. The posting also includes "We encourage