Technical Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications, Skills), Benefits, Pay, Schedule. Must only include sections that have real specific content. The posting includes "About The Role" content (the description). Also "Responsibilities" list. Also "Requirements" (the bullet list after "You may be a good fit if you have ..." and later "Strong candidates may also have ..."). Also "Benefits" appears later: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". Also "Pay" appears: "The annual compensation range for this role is listed below. ... Annual Salary $250,000—$365,000 USD". Also "Schedule": "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." Also travel expectation: "Travel. Expect 30 to 50%, in bursts around onsites, workshops and events." That could be schedule. Also maybe "Logistics" includes education, experience, location, visa sponsorship. Those could be part of Requirements or Qualifications. We need to avoid repeating job title heading. Use

for each section heading. We must not include boilerplate like EEO, scam warning, etc. Also remove duplicated lines. Must preserve all substantive info. We need to decide sections: About the role (maybe "About The Role" heading). Responsibilities (list). Requirements (maybe combine qualifications, skills, education, experience). Benefits (list). Pay (salary range). Schedule (hybrid policy, travel). Possibly also "Logistics" but we can incorporate into Requirements or Schedule. We must not create sections with filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. Let's extract content. About The Role paragraph: starts after "About The Role Claude Code is changing...". We'll capture that paragraph up to before "Responsibilities". It includes multiple sentences. We'll put in

. Responsibilities: bullet list after "Responsibilities". Each line starts with a bold phrase? Actually they are sentences starting with capital letters. We'll make

• each. Requirements: includes "You may be a good fit if you have 5+ years as a software engineer, solutions architect, developer advocate or similar. You still ship code and regularly teach engineering audiences. Current engineering range. You've shipped code other people depend on. You can go deep with a senior engineer anywhere in the stack. You use Claude Code or a similar agentic tool every day and have opinions about it. Big-stage presence. You've held large live audiences. You sound practiced with material you got that morning, and a broken demo doesn’t faze you. Range in one conversation. You can go from banter to a rigorous design discussion, and both feel natural. Care for people. You do right by a struggling customer, and you won't leave a confused room behind. Initiative. You build things without waiting for permission, and you say when an idea is half-formed, including your manager's. Steadiness when priorities shift, timelines are short and colleagues are under pressure. Comfort with ambiguity in a fast-moving industry and product suite. A stake in safe AI. You care that large organizations deploy AI responsibly, and you want to help them do it. You love being on the frontier. You want to work at the edge of what’s possible and help define what comes next. Strong candidates may also have Depth in enterprise identity and security review (SAML, OIDC, SCIM, SOC 2, HIPAA). Experience running Claude on Amazon Bedrock or Google Cloud Vertex AI. Time with regulated industries or with systems-integrator partners. A public record of technical teaching: talks, courses, videos or writing. An interest outside technology you can talk about with the same energy." Also 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." But we must remove boilerplate like EEO etc. The above includes some encouragement text; it's still substantive? It's more about encouraging applications; maybe we can keep as part of Requirements? It's not boilerplate but it's generic encouragement. Might be okay to keep but we could drop as it's not specific to role. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The encouragement text is not exactly boilerplate but it's generic. Might be considered application instructions? It's encouraging to apply even if not meet all qualifications. That's somewhat generic. Safer to drop that paragraph. Also the "We think AI systems..." is generic. Might drop. Thus Requirements section will include the bullet-like paragraphs (the long list). We could format as
  • each sentence? But they are not list items originally; they are separate sentences. Could wrap each in

    or

  • . The instruction: Use
    • for any list of duties/requirements/benefits. So we should treat the requirements as a list. We'll split each distinct requirement into
    • . Might be many; but okay. Similarly 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." That's a sentence with list items. We'll make
      • each. Pay: "Annual Salary $250,000—$365,000 USD". Also note about OTE for sales roles but this is not sales role? It says "For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role." This is a note; we can include as part of Pay section maybe as a

        . It's substantive. Schedule: includes location-based hybrid policy and travel expectation. We'll make

        • each. Also maybe "About Anthropic" mission statement? That's not a section heading we need; we could include as part of About the role? Actually "About Anthropic" is separate but not required heading. The instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should not include "About Anthropic" as a heading unless we have content for it. Could we include it as a paragraph under About the role? Probably not needed. The posting already shows job title; we should not repeat it. The "About Anthropic" is generic company description; could be considered boilerplate? It's not required. Might drop. Thus final HTML:

          About the role

          Claude Code is changing how engineering organizations build software, and most of them need someone to show them how. That's you. Technical Architects help customers get real work done with Claude Code, Claude Tag (Claude Code as an agent in Slack), and the enterprise admin controls that decide whether a rollout succeeds. You'll teach customers, partners and Anthropic's own field teams. Just as important, you'll train the trainers who carry that knowledge to everyone else. We're hands-on AI engineers who would rather teach than sell. You'll work alongside customer engineering organizations, teaching them about Claude Code and shepherding rollouts with advanced admin knowledge. Most weeks you're in front of an audience with Claude Desktop or a terminal open: thousands of engineers on a public webinar one day, a customer's platform team in their own conference room the next week, office hours in between. The prep material often reaches you the day before. The team is growing quickly this year, scope will grow as new products ship, and the people who join now will shape how it works.

          Responsibilities

          • Teach in every format. Take a standing rotation on Anthropic's public webinars in front of thousands of engineers at a time.
          • Lead workshops and multi-day onsites, in person and virtual, built around a customer's own codebase and questions.
          • Host office hours and multi-week cohorts where engineers, partners, and account teams bring live problems.
          • Teach the teachers. Run train-the-trainer programs for customer technologists and champions, and certify them to deliver Anthropic's material.
          • Empower admins. Educate enterprise admins on the technical requirements for a strong rollout by guiding them through single sign-on, permissions, connectors, spend controls, data-handling policy, and other advanced topics.
          • Build fast with Claude. Turn a request into a polished deck, demo repository or plugin within a day, using the tools you teach.
          • Explore new features the day they ship.
          • Pick up a teammate's material and deliver it as if you wrote it.
          • Bring field signal back to product. Tell the Claude Code, Claude Tag and Cowork teams what customers run into, specifically enough that they can fix it.
          • Be the technical voice in the room. Partner with account executives, customer success managers, Applied AI Architects, support engineers and partner leads.
          • Travel. Expect 30 to 50%, in bursts around onsites, workshops and events.

          Requirements

          • You may be a good fit if you have 5+ years as a software engineer, solutions architect, developer advocate or similar.
          • You still ship code and regularly teach engineering audiences.
          • You've shipped code other people depend on.
          • You can go deep with a senior engineer anywhere in the stack.
          • You use Claude Code or a similar agentic tool every day and have opinions about it.
          • Big-stage presence. You've held large live audiences.
          • You sound practiced with material you got that morning, and a broken demo doesn’t faze you.
          • Range in one conversation. You can go from banter to a rigorous design discussion, and both feel natural.
          • Care for people. You do right by a struggling customer, and you won't leave a confused room behind.
          • Initiative. You build things without waiting for permission, and you say when an idea is half-formed, including your manager's.
          • Steadiness when priorities shift, timelines are short and colleagues are under pressure.
          • Comfort with ambiguity in a fast-moving industry and product suite.
          • A stake in safe AI. You care that large organizations deploy AI responsibly, and you want to help them do it.