Technical Deployment Lead
for 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. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "About Anthropic", "How We're Different", "Guidance on Candidates' AI Usage", etc. Also remove "You May Be a Good Fit If You Have ..."? That's part of qualifications/requirements. We need to parse content. Let's extract sections: - About the role: The paragraph after "About The Role". Contains description of role. Should be in
. - Responsibilities: List of bullet points under "Responsibilities". Should be
- .
- Requirements/Qualifications/Skills: The "You May Be a Good Fit If You Have ..." list. Also "Logistics Minimum education: ..." etc. Also "Minimum education: Bachelor’s degree or an equivalent combination..." etc. Also "Required field of study: ..." etc. Also "Minimum years of experience: ..." etc. Also "Location-based hybrid policy: ..." etc. Also "Visa sponsorship: ..." etc. Also "We encourage you to apply even if you do not believe you meet every single qualification." etc. Also "We think AI systems..." etc. Also "Your safety matters..." etc. Also "We believe that the highest-impact AI research..." etc. Also "Come work with us! Anthropic is a public benefit corporation..." etc. Many of these are boilerplate/EEO etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Your safety matters..." is scam-warning boilerplate, should be removed. The "We think AI systems..." is maybe part of mission but could be considered boilerplate? It's about representation, maybe EEO. Likely remove. The "Come work with us! Anthropic is a public benefit corporation..." is benefits description? It mentions competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. That's benefits info. So we should include Benefits section with that content. Also "Guidance on Candidates' AI Usage:" is application instructions? Might be considered boilerplate; remove.
Pay: The posting includes "Annual Salary $275,000—$380,000 USD". That's pay. So include Pay section.
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 info. So include Schedule.
Also "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." This could be considered part of logistics but not specifically required heading; maybe we can fold into a short p under Requirements or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Visa sponsorship is minor metadata; could be placed in a short p maybe under Requirements or separate? But we have limited headings; we could include it in a paragraph under Requirements or maybe under a generic "Logistics" but we don't have that heading. Probably fold into Requirements as a short p. Also "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" etc. That's qualifications. Also "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience" Also "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position" Also "Location-based hybrid policy: ..." (schedule) Also "Visa sponsorship: ..." (maybe minor metadata) Also "We encourage you to apply even if you do not believe you meet every single qualification." That's encouraging but maybe not needed; could be considered boilerplate; remove. Also "Not all strong candidates will meet every single qualification as listed." etc. Remove. Also "Research shows that people who identify as being from underrepresented groups are more prone to experiencing imposter syndrome..." Remove as EEO. Also "We think AI systems like the ones we're building have enormous social and ethical implications..." Remove. Also "Your safety matters to us..." Remove (scam-warning). Also "How We're Different" etc. Remove. Also "Come work with us! Anthropic is a public benefit corporation headquartered in San Francisco. 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. Thus sections: - About the role (p) - Responsibilities (ul) - Requirements/Qualifications/Skills (maybe combine into one section? The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements, Qualifications, Skills into one section titled "Requirements" or "Qualifications". We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with real content. We have content for About the role, Responsibilities, Requirements (education, experience, field of study, etc.), Qualifications (the "You May Be a Good Fit If You Have ..." list), Skills (maybe overlapping with qualifications; but we could treat the list as Skills). However we might combine Requirements and Qualifications into one to avoid thin sections. But we must follow headings: if we include a heading, we must have real specific content under it. We could include Requirements and Qualifications and Skills each with content, but they'd be thin. Better to combine into one heading, maybe "Requirements" and put all relevant info there, and omit Qualifications and Skills headings. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check if we have content for Benefits: yes. Pay: yes. Schedule: yes. Now we need to extract the precise content. About the role paragraph: Let's copy exactly the paragraph after "About The Role". It starts: "As a Technical Deployment Lead on the Claude Agentic Solutions team, you will lead the delivery of custom AI agent solutions for enterprise customers in highly regulated industries." Continue until end of that paragraph before "Responsibilities". Let's capture: "As a Technical Deployment Lead on the Claude Agentic Solutions team, you will lead the delivery of custom AI agent solutions for enterprise customers in highly regulated industries. You'll own high-value engagements where we collaborate directly with customers to build and deploy agents into their most critical business processes. This is a founding team: you will help us to build technical playbooks and define the processes and repeatable patterns needed for us to scale this emerging motion. You will champion our mission in the field, ensure world class delivery, and bring insights back to our product and research teams on a regular basis. You'll own engagements end-to-end, from SOW through production deployment. You'll work alongside Forward Deployed Engineers who build the technical solution, while you own product scoping, stakeholder management, value measurement, and the organizational complexity that comes with deploying AI agents in enterprise environments. You need to be technical enough to hold architecture conversations with engineering stakeholders and polished enough to run executive briefings with C-suite sponsors." That's the paragraph. Now Responsibilities bullet list: Under "Responsibilities" there are many bullet points each starting with a verb. Let's extract them as list items. List: - Own the technical delivery plan for each engagement. - Structure SOWs with clear scope, milestones, dependencies, success criteria, and value hypotheses. - Translate customer business objectives into a sequenced roadmap that FDEs execute against. - Lead technical discovery. Map customer workflows, identify constraints, define MVP scope, and shape the solution architecture for custom agent deployments. - Run day-to-day engineering execution. Drive delivery across Anthropic and customer teams. Keep progress unblocked and sequenced. Make real-time trade-offs on scope and priority to protect the critical path. - Own product scoping for field engagements. Define the MVP, author requirements documentation, prioritize the engineering backlog, and manage scope against success criteria as requirements evolve. - Own the customer relationship throughout delivery. Lead executive briefings, manage stakeholder communications across technical leads and procurement, and represent Anthropic's technical credibility with senior business and engineering leaders. - Own value measurement and ROI. Define impact hypotheses, set baselines and KPIs, run pre- and post-deployment measurement, and report outcomes to executive sponsors. - Codify reusable delivery assets. Build solution patterns, evaluation frameworks, and technical playbooks. Extract what works across engagements and feed field signals back to Product and Research to improve our platform and models. - Navigate enterprise and regulatory complexity. Security reviews, legal approvals, procurement processes, compliance requirements, and organizational dynamics. - Manage scope and change. Handle evolving requirements, set expectations, negotiate contract modifications, identify risks early, and escalate with clear context when needed. - Run delivery operations. Sprint ceremonies, milestone reviews, and progress reporting. - Travel to customer sites. Build relationships, unblock delivery, and accelerate adoption. (25–50% expected). We need to keep each as
- . Ensure we keep the content exactly.
Now Requirements section: combine education, field of study, years of experience, location-based hybrid policy? Actually schedule separate. Also visa sponsorship maybe minor metadata; we could include as a short p under Requirements? But we have separate Schedule heading for location-based hybrid policy. Visa sponsorship maybe not needed; we could drop as minor metadata. The instruction: fold minor metadata into a short
or drop it. We could drop visa sponsorship. Also "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" etc. Also "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience". Also "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position". Also maybe "Logistics Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" appears duplicated? Actually there is a "Logistics" section earlier: "Logistics 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." So we need to extract those. Thus Requirements content: combine: - 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 We could also include "Location-based hybrid policy" under Schedule, not Requirements. Now Benefits section: from "Come work with us! Anthropic is a public benefit corporation headquartered in San Francisco. 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." We should keep that as a paragraph.