Staff+ Software Engineer, Enterprise AI Products

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, remove boilerplate: About Anthropic (mission) is maybe not needed? The instruction: "Prefer a few substantive sections over many thin ones." We need to include sections only when posting has real specific content. The posting includes "About The Role" (description), "What you'll do" (responsibilities), "You may be a good fit if you" (requirements/qualifications/skills), "Strong candidates may also have" (additional qualifications), "The annual compensation range for this role is listed below." (Pay), "Logistics" includes Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship, etc. Also "We encourage you to apply..." etc is boilerplate (EEO). Also "How We're Different" etc is maybe not needed. Also "Come work with us! Anthropic is a public benefit corporation..." includes benefits description: "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. We need to extract substantive content. Let's list sections: - About the role: The paragraph after "About The Role": "Anthropic's Enterprise AI Products team builds what makes Claude a daily-use tool for enterprise customers across industries. We focus on organizational context and workflows (plugins, skills, connectors, webhook-triggered processes / agents). In other words, we focus on products that form the connective tissue that lets Claude operate across an organization. A big part of this work is understanding what's blocking adoption and building the capabilities that close those gaps. Much of this is being built 0→1 right now: you'll be shaping the product and the architecture in a market where no one has done this well yet. You'll be a technical leader who thinks holistically about the end-to-end customer experience, partners directly with research to push model capabilities into production, and carries real ownership over what we ship next." That's substantive. - Responsibilities: "What you'll do" bullet list (actually sentences). We need to put each as

under

. The bullet points: Own technical design and delivery for enterprise-facing core products, end-to-end across the stack Partner with product, design, and go-to-market to turn enterprise customer workflows into shipped product, not just execute against a spec Set technical direction and standards for your team: architecture, code quality, and how the team builds Work directly with enterprise customers and sales during key conversations, translating what you learn into engineering priorities Work closely with research to make the models better in your domain: shaping evals, surfacing failure modes, and feeding customer learnings back into model development Mentor other engineers and raise the technical bar across the team, working with influence rather than authority Build multi-player, asynchronous agents: department-level processes that are goal-oriented, many-step, and triggered by a webhook, a form, or an email rather than a person typing That's responsibilities. - Requirements / Qualifications / Skills: The "You may be a good fit if you" list: Have 8+ years of software engineering experience, ideally with 2+ years at a Staff or equivalent technical leadership level Have led the design and delivery of complex enterprise or B2B products across the full stack Have built AI products and know what it takes to turn model capabilities into applications people actually use Are comfortable working directly with enterprise customers and translating what you learn into technical decisions Have built products from 0 to 1 in fast-moving environments, and can set technical direction with limited precedent to lean on Drive cross-team alignment to ship impactful work, with influence over authority Then "Strong candidates may also have" list: Experience working with research to improve domain-specific model capabilities, including evaluation frameworks Experience building extensibility surfaces (plugins, integrations, agent tooling) that third parties or internal teams build on Exposure to both product-led growth and direct enterprise sales These could be considered qualifications/skills. We could combine into one "Requirements" section or separate "Qualifications" and "Skills". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can decide to have Requirements (core) and Qualifications (additional) maybe. But we should avoid thin sections. Perhaps combine all into one "Requirements" section (or "Qualifications") and not create separate Skills if not needed. However we have both core and "strong candidates may also have". Could treat core as Requirements, additional as Qualifications. That seems reasonable. - Pay: The posting includes "Annual Salary $405,000—$485,000 USD". Also note about OTE for sales roles but this is not sales. So we have Pay section with that range. - Benefits: The "Come work with us! Anthropic is a public benefit corporation..." includes: "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. Also maybe "competitive compensation and benefits" is vague but we have specific items: optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. That's substantive. - Schedule: The posting includes 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/hybrid expectation. Also maybe visa sponsorship is not schedule. So we can include Schedule section with that. - Also there is Minimum education, Required field of study, Minimum years of experience under Logistics. Those could be part of Requirements/Qualifications. But we already have experience requirement (8+ years). The logistics includes Minimum education: Bachelor’s degree or equivalent; 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. That's somewhat generic. Might be considered boilerplate. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly boilerplate but it's generic HR. Might be considered minor metadata; we could fold into a short p or drop. Since we already have experience requirement (8+ years) and we have education implied (Bachelor's). Could include a short p under Requirements maybe. But we need to avoid filler like "commensurate with experience". The logistics lines are not filler but generic. However we could incorporate them into Requirements as additional points. But we need to decide: The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Education/Field/Experience into Requirements section as bullet points. Thus Requirements section could include: - Bachelor’s degree or an equivalent combination of education, training, and/or experience - Field relevant to the role as demonstrated through coursework, training, or professional experience - 8+ years of software engineering experience, ideally with 2+ years at a Staff or equivalent technical leadership level - Have led the design and delivery of complex enterprise or B2B products across the full stack - Have built AI products and know what it takes to turn model capabilities into applications people actually use - Are comfortable working directly with enterprise customers and translating what you learn into technical decisions - Have built products from 0 to 1 in fast-moving environments, and can set technical direction with limited precedent to lean on - Drive cross-team alignment to ship impactful work, with influence over authority Then Qualifications section (strong candidates may also have) includes: - Experience working with research to improve domain-specific model capabilities, including evaluation frameworks - Experience building extensibility surfaces (plugins, integrations, agent tooling) that third parties or internal teams build on - Exposure to both product-led growth and direct enterprise sales Alternatively we could merge them into one Requirements section and not have Qualifications. But we have headings list includes Qualifications; we can use if we have content. The strong candidates list is substantive, so we can make Qualifications. Now Benefits: we have bullet list: optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. Also "competitive compensation and benefits" is vague; we can ignore. Pay: Annual Salary $405,000—$485,000 USD. Schedule: Location-based hybrid policy: expect staff to be in one of our offices at least 25% of the time; some roles may require more time in offices. We should not include visa sponsorship etc as it's not schedule; maybe we could include under Benefits? But visa sponsorship is not a benefit per se but could be considered. However we already have benefits; we could add visa sponsorship as a benefit point. The instruction: include section only when posting has real specific content. 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. Could be part of Benefits or maybe a separate section like "Immigration". But not in headings list. Could fold into Benefits as a point. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. Visa sponsorship could be considered a benefit. So we can add a bullet under Benefits: "Visa sponsorship available (reasonable efforts to secure visa, immigration lawyer support)". That seems okay. Now we need to output HTML fragment only, no markdown fences. We'll produce:

About the role

... paragraph ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Pay

Annual Salary $405,000—$485,000 USD

Schedule

Location‑based hybrid policy: staff expected to be in one of our offices at least 25% of the time; some roles may require more office time.

We need to ensure we preserve all substantive information. Let's verify we didn't miss any. From About the role: we captured the paragraph. From What you'll do: captured all bullet points. From You may be a good fit if you: captured all bullet points. From Strong candidates may also have: captured. From Logistics: we captured education, field, experience (though experience also in requirements). We might duplicate experience; but we already have 8+ years experience in requirements. The logistics Minimum years of experience: "Years of experience required will correlate with the internal job level requirements for the position." That's vague; we can skip as it's not specific. The education and field we added. We didn't include "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" and "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience". We added those as bullet points under Requirements. We didn't include "Visa sponsorship" but we added under Benefits. We didn't include "We encourage you to apply..." etc (boilerplate). We didn't include "How We're Different" etc (maybe not needed). We didn't include "Come work with us! Anthropic is a public benefit corporation..." we used for benefits. We