AI Operations Engineer, Partnerships

<div class="content-intro"><h2><strong>About Anthropic</strong></h2> <p>Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems.</p></div><h2 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="4:1-4:18;143-160">About the role</h2> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="6:1-6:384;162-545">Our Partner Experience team is building an AI-native operating model. We already run a growing set of partner-facing systems: a partner portal, CRM workflows, enablement and certification platforms, and the trackers that connect them. The systems lead on our team owns that foundation — the portal, the data model, and the integrations that keep partner records accurate and flowing.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="8:1-8:459;547-1005">This role is the other half of that build. As our AI Operations Engineer, you'll design, build, and run the agentic workflows that sit on top of those systems: Claude-powered agents and automations that triage partner applications, draft and send partner communications, sync data across tools, surface deal and enablement signals, and take routine operational work off the team entirely. Where the systems lead builds the rails, you build what runs on them.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="10:1-10:180;1007-1186">This is a builder role, not an analyst role. You'll ship working automations weekly, own them in production, and continuously expand what the team can do without adding headcount.</p> <h2 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="12:1-12:24;1188-1211">Key responsibilities</h2> <ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1" data-sourcepos="14:1-19:186;1213-2419"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="14:1-14:253;1213-1465">Design and build agentic workflows (using Claude, MCP connectors, and API integrations) that automate core partner experience operations: application triage, onboarding, deal registration, certification tracking, partner communications, and reporting</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="15:1-15:247;1466-1712">Partner closely with our systems lead to integrate these workflows with the partner portal, CRM, enablement stack, finance systems, and database systems — consuming and writing back to the systems of record rather than creating shadow processes</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="16:1-16:228;1713-1940">Turn recurring manual work into reliable, monitored automations: define the workflow, build it, test it against real cases, add guardrails and human-in-the-loop checkpoints where decisions carry risk, and document how it runs</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="17:1-17:137;1941-2077">Own the operational health of what you ship: error handling, edge cases, escalation paths, and iteration when partner processes change</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="18:1-18:156;2078-2233">Prototype fast with the team: sit with partner managers, find the highest-friction workflows, and get a working v1 in front of them in days, not quarters</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="19:1-19:186;2234-2419">Establish reusable patterns (skills, prompts, connectors, playbooks) so each new workflow is faster to build than the last, and teach the broader team to self-serve on the simple ones</li> </ul> <h2 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="21:1-21:26;2421-2446">Minimum qualifications</h2> <ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1" data-sourcepos="23:1-27:75;2448-3252"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="23:1-23:191;2448-2638">Hands-on experience building with LLMs and agentic tooling: prompt and workflow design, tool/function calling, MCP or comparable integration frameworks, and evaluating agent output quality</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="24:1-24:235;2639-2873">Experience working across APIs and business systems — CRMs (e.g., Salesforce), PRM/partner portals, LMS/certification platforms, spreadsheet-based tools, Slack, and email — and scripting the glue between them in Python or JavaScript</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="25:1-25:158;2874-3031">Strong judgment about automation risk: knowing which steps an agent can own outright, which need a human checkpoint, and how to design for graceful failure</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="26:1-26:146;3032-3177">Process instincts: ability to look at a messy manual workflow, find the actual bottleneck, and redesign it rather than just automating it as-is</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="27:1-27:75;3178-3252">Clear written communication; documents what you build so it outlives you</li> </ul> <h2 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="29:1-29:28;3254-3281">Preferred qualifications</h2> <ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1" data-sourcepos="31:1-34:107;3283-3815"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="31:1-31:188;3283-3470">5+ years in operations engineering, solutions engineering, business systems, RevOps, or a similar build-heavy role, ideally supporting a partner, sales, or customer success organization</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="32:1-32:140;3471-3610">Experience in partner/channel operations specifically (deal registration, MDF/co-sell programs, partner tiering, certification pipelines)</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="33:1-33:98;3611-3708">Experience shipping internal AI tools or automations that are still running in production today</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="34:1-34:107;3709-3815">Familiarity with the Claude API, Claude Code, or agent frameworks; building custom MCP servers is a plus</li> </ul><div class="content-pay-transparency"><div class="pay-input"><div class="description"><p>The annual compensation range for this role is listed below. </p> <p>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.</p></div><div class="title">Annual Salary:</div><div class="pay-range"><span>$215,000</span><span class="divider">—</span><span>$300,000 USD</span></div></div></div><div class="content-conclusion"><h2><strong>Logistics</strong></h2> <p><strong>Minimum education: </strong>Bachelor’s degree or an equivalent combination of education, training, and/or experience</p> <p><strong>Required field of study: </strong>A field relevant to the role as demonstrated through coursework, training, or professional experience</p> <p><strong>Minimum years of experience: </strong>Years of experience required will correlate with the internal job level requirements for the position</p> <p><strong>Location-based hybrid policy:</strong> 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.</p> <p><strong data-stringify-type="bold">Visa sponsorship:</strong> 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 w