Applied AI Architect, Strategic Enterprise Tech
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role, Responsibilities, Requirements (maybe combine Requirements/Qualifications/Skills), Benefits, Pay, Schedule.
We need to decide what content belongs where.
"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.
That's the role description. So we can put that under About the role
as prose (
). Next "Responsibilities": list bullet points after "Responsibilities". Let's extract bullet list: - Partner with account executives to deeply understand customer requirements and translate them into technical solutions, ensuring alignment between business objectives and technical implementation - Serve 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 success - 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 - Support customers building with both the Claude API and Claude for Enterprise - Create 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 executives - Reproduce customer environments and problems in your own builds. Use them to prove the path to production - Build deep relationships with Anthropic engineering and product teams. Carry customer needs into the product roadmap and bring product direction back to your accounts - Guide technical architecture decisions and help customers integrate Claude effectively into their existing technology stack - Help customers develop evaluation frameworks to measure Claude's performance for their specific use cases - Identify common integration patterns and contribute insights back to our Product and Engineering teams - Travel occasionally to customer sites for workshops, technical deep dives, and relationship building - Maintain strong knowledge of the latest developments in LLM capabilities and implementation patterns We need to put these in
- .
Next "You May Be a Good Fit If You Have": list of qualifications/skills. This could be Requirements/Qualifications/Skills. Let's extract bullet list (though it's in paragraph with "If You Have" and then list separated by line breaks). Items:
- 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 not duplicate lines. We need to remove duplicated lines. The second occurrence is duplicate of earlier "Excitement for engaging...". We'll keep one.)
- 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
Also there is "The annual compensation range for this role is listed below." Then Pay: Annual Salary $240,000—$315,000 USD
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 prematurely and to submit an application if you're interested in this work. 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. Your safety matters to us. To protect yourself from potential scams, remember that Anthropic recruiters only contact you from @anthropic.com email addresses. In some cases, we may partner with vetted recruiting agencies who will identify themselves as working on behalf of Anthropic. Be cautious of emails from other domains. Legitimate Anthropic recruiters will never ask for money, fees, or banking information before your first day. If you're ever unsure about a communication, don't click any links—visit anthropic.com/careers directly for confirmed position openings. How We're Different ... etc. Also benefits: "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 need Benefits section if posting actually states them. It does: "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 section: we have salary range.
Schedule: location-based hybrid policy: at least 25% time in office. That's schedule info.
We should not include boilerplate like EEO, scam warnings, etc. Also remove "How We're Different" etc if not needed? It's not a required section; but we could include as part of About the role? Probably not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "How We're Different" is not boilerplate but maybe considered extra info not required; but we should preserve ALL substantive information; does it count as substantive? It's about company culture; could be considered part of About the role? Might be okay to include as a paragraph under About the role? But the instruction says prefer a few substantive sections over many thin ones. We could incorporate that info into About the role paragraph. However we must not invent or summarize away detail. We could add a separate section like "About Anthropic" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit everything into those.
Thus we can put the "About Anthropic" mission and team description maybe under About the role as introductory paragraph? But About the role should be about the role, not company. However we could include a brief About Anthropic as part of About the role? Might be okay.
But we need to preserve all substantive information: The mission statement, team description, etc. Could be placed under About the role as a preamble? Might be okay.
Alternatively we could create a section "About the role" that includes both the role description and some company context. That seems acceptable.
We must not include duplicated lines: we saw duplicate "You enjoy engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities". We'll keep one.
Also duplicate "Excitement for engaging in cross-organizational collaboration, working through trade-offs, and balancing competing priorities" appears earlier; we have that as one item. The duplicate later we will drop.
Now we need to decide on Requirements/Qualifications/Skills section. Could combine into one
Requirements
with list. We have Minimum education, Required field of study, Minimum years of experience (though vague). Also list of qualifications from "You May Be a Good Fit If You Have". Those are more like skills/qualifications. We could split: Requirements (education, experience) and Skills (the list). But we have limited headings; we could use Requirements for education/experience, and Skills for the list. Or combine. Given instruction: prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section that includes both education/experience and skills list. But we need to avoid filler like "not specified". All content is specific. Thus:About the role
... (including Anthropic mission? maybe separate paragraph). We'll include the role description plus maybe a brief about Anthropic mission as separate paragraph but still under same heading? Could be two
under same heading. Better: Under About the role, we can have two paragraphs: first about Anthropic mission and team (from "About Anthropic"), second about the role specifics. But the heading is About the role, not About Anthropic. However it's okay to include company info as context. Now Responsibilities
- .
Requirements
- for any list). We'll use
- .
We need to include Minimum education, Required field of study, Minimum years of experience, plus the list of qualifications.
We could format each as
- items.
Pay:
Pay
Annual Salary $240,000—$315,000 USD
Schedule:Schedule
Location‑based hybrid policy: expected to be in one of our offices at least 25% of the time (some roles may require more office time).
Benefits:Benefits
We offer competitive compensation and benefits, optional equity donation matching
- items.
Pay:
- (or
- ? but spec says
- for any list). We'll use