Applied AI Architect, Strategic Enterprise Tech

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications, Skills), Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - About the role: there is a paragraph starting "About The Role". We'll put that as

About the role

then

with content. - Responsibilities: there is a "Responsibilities" heading then a long paragraph with many sentences separated by periods. We need to convert to list items? The instruction: Use

• for any list of duties/requirements/benefits. The responsibilities are a list of duties; we can split each sentence into
• . Must preserve all substantive info. We'll extract each duty sentence. - Requirements/Qualifications/Skills: There's a "You May Be a Good Fit If You Have" block with bullet-like sentences. We'll treat as Requirements (or Qualifications). We'll put

  Requirements

  and list each bullet as
• . Also there is "Minimum education: Bachelor’s degree..." etc under Logistics. That's also requirements. We'll include those as list items too. - Pay: There's "The annual compensation range for this role is listed below... Annual Salary $240,000—$315,000 USD". That's specific pay. So we include Pay section with

  containing that. - Benefits: There's a paragraph at end: "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. So include Benefits section with

  • items. - 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 section with

    . We must not include sections like About Anthropic (company description) as it's not a section heading per rules? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "About Anthropic" is not one of those; we should omit it. Also remove boilerplate like EEO, scam warning, etc. Also remove "How We're Different", "Guidance on Candidates' AI Usage", etc. We must preserve all substantive information from the posting that falls under those sections. Ensure we don't lose any details. Let's extract content. About The Role paragraph: "As an Applied AI team member at Anthropic, you will be a Pre-Sales architect focused on becoming a trusted technical advisor helping large enterprises understand the value of Claude and paint the vision on how they can successfully integrate and deploy Claude into their technology stack. You'll combine your deep technical expertise with customer-facing skills to architect innovative LLM solutions that address complex business challenges while maintaining our high standards for safety and reliability. You will focus on a short list of strategic accounts within our Enterprise Technology business. For each one you will co-own the account plan with the account executive, build executive technical champions, and drive a multi-quarter adoption roadmap. You will have breadth and depth, reproducing customer environments and problems, building working solutions with them, and develop deep relationships with our engineering and product teams, all in service of each account's strategic roadmap Working closely with our Sales, Product, and Engineering teams, you'll guide customers from initial technical discovery through successful deployment. You'll leverage your expertise to help customers understand Claude's capabilities, develop evals, and design scalable architectures that maximize the value of our AI systems." Note there is a missing period before "Working". We'll keep as is. Now Responsibilities list: The text after "Responsibilities" is a long sentence with many clauses separated by periods? Let's copy: "Partner with account executives to deeply understand customer requirements and translate them into technical solutions, ensuring alignment between business objectives and technical implementationServe as the primary technical advisor to enterprise customers throughout their Claude adoption journey, from discovery to initial evaluation through deployment. You will need to coordinate internally across multiple teams & stakeholders to drive customer successWork with your customers on their overall AI adoption strategies, including use case scoping, architecture reviews, technical champion building, adoption workshops, and use case execution Support customers building with both the Claude API and Claude for EnterpriseCreate and deliver compelling technical content tailored to different audiences. You will need to be able to spread the gamut from technical deep dives for engineering & development teams up to business value focused conversations with executivesReproduce customer environments and problems in your own builds. Use them to prove the path to productionBuild deep relationships with Anthropic engineering and product teams. Carry customer needs into the product roadmap and bring product direction back to your accountsGuide technical architecture decisions and help customers integrate Claude effectively into their existing technology stackHelp customers develop evaluation frameworks to measure Claude's performance for their specific use casesIdentify common integration patterns and contribute insights back to our Product and Engineering teamsTravel occasionally to customer sites for workshops, technical deep dives, and relationship buildingMaintain strong knowledge of the latest developments in LLM capabilities and implementation patterns" We need to split into sensible bullet items. Each clause seems to start with a verb. We'll split at periods. Let's identify sentences: 1. Partner with account executives to deeply understand customer requirements and translate them into technical solutions, ensuring alignment between business objectives and technical implementation 2. Serve as the primary technical advisor to enterprise customers throughout their Claude adoption journey, from discovery to initial evaluation through deployment. 3. You will need to coordinate internally across multiple teams & stakeholders to drive customer success 4. Work with your customers on their overall AI adoption strategies, including use case scoping, architecture reviews, technical champion building, adoption workshops, and use case execution 5. Support customers building with both the Claude API and Claude for Enterprise 6. Create and deliver compelling technical content tailored to different audiences. 7. You will need to be able to spread the gamut from technical deep dives for engineering & development teams up to business value focused conversations with executives 8. Reproduce customer environments and problems in your own builds. 9. Use them to prove the path to production 10. Build deep relationships with Anthropic engineering and product teams. 11. Carry customer needs into the product roadmap and bring product direction back to your accounts 12. Guide technical architecture decisions and help customers integrate Claude effectively into their existing technology stack 13. Help customers develop evaluation frameworks to measure Claude's performance for their specific use cases 14. Identify common integration patterns and contribute insights back to our Product and Engineering teams 15. Travel occasionally to customer sites for workshops, technical deep dives, and relationship building 16. Maintain strong knowledge of the latest developments in LLM capabilities and implementation patterns Check for missing spaces: some sentences concatenated without space after period (e.g., "implementationServe"). We'll fix by adding space. Now Requirements/Qualifications/Skills: The block "You May Be a Good Fit If You Have" includes many bullet-like sentences. Let's extract each line: - 8+ years of experience in roles such as Field CTO, Solutions Architect, Sales Engineer, or Product Manager, with hands-on building experience - Experience working with enterprise customers, navigating complex buying cycles involving multiple stakeholders - Experience owning named or strategic enterprise accounts through long, multi-stakeholder buying cycles - Exceptional ability to build relationships with and communicate technical concepts to diverse stakeholders to include C-suite executives, engineering & IT teams, and more - Strong technical communication skills with the ability to translate customer requirements between technical and business stakeholders - Experience designing scalable cloud architectures and integrating with enterprise systems - Comfortable with python - Familiarity with common LLM frameworks and tools or a background in machine learning or data science - Excitement for engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities - A love of teaching, mentoring, and helping others succeed - Excellent communication and interpersonal skills, able to convey complicated topics in easily understandable terms to a diverse set of external and internal stakeholders. - You enjoy engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities (duplicate? Actually appears twice; we should keep both? It's duplicate; we should not invent but we can keep as is; but maybe we should deduplicate? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplicate lines are part of posting; we should keep them? It says remove duplicated lines. Yes: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to eliminate duplicate "You enjoy engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities". Also there is earlier "Excitement for engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities". That's similar but not identical; one is "Excitement for engaging..." the other is "You enjoy engaging...". They are not exact duplicates but similar. We'll keep both as they are not identical strings. However the duplicate line is exactly same as earlier? Let's check: earlier we have "Excitement for engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities". Later we have "You enjoy engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities". Not identical, so keep both. - Passion for thinking creatively about how to use technology in a way that is safe and beneficial, and ultimately furthers the goal of advancing safe AI systems - Excellent communication and interpersonal skills, able to convey complicated topics in easily understandable terms to a diverse set of external and internal stakeholders. (This appears again? Actually we already have that line earlier; there is duplicate: "Excellent communication and interpersonal skills, able to convey complicated topics in easily understandable terms to a diverse set of external and internal stakeholders." appears twice? Let's see: earlier we had "Strong technical communication skills with the ability to translate customer requirements between technical and business stakeholders". Then later we have "Excellent communication and interpersonal skills, able to convey complicated topics in easily understandable terms to a diverse set of external and internal stakeholders." Then later again: "Excellent communication and interpersonal skills, able to convey complicated topics in easily understandable terms to a diverse set of external and internal stakeholders." Indeed appears twice. We need to remove duplicated lines. So keep one instance. - You enjoy engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities (we already have similar but not duplicate; keep) - Passion for thinking creatively about how to use technology in a way that is safe and beneficial, and ultimately furthers the goal of advancing safe AI systems (maybe duplicate? we have earlier "Passion for thinking creatively about how to use technology in a way that is safe and beneficial, and ultimately furthers the goal of advancing safe AI systems". It appears only once? Actually appears at end of block; we have also earlier? Not sure. We'll keep one. Now also under 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.", "We encourage you to apply even if you do not believe you meet every single qualification. Not all strong candidates will meet every single qualification as listed. Research shows that people who identify as being from underrepresented groups are more prone to experiencing imposter syndrome and doubting the strength of their candidacy, so we urge you not to exclude yourself