Finance & Strategy, Deal Velocity

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements (maybe Minimum Qualifications, Preferred Qualifications), Benefits, Pay, Schedule, Skills? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. Do not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Also remove "About Anthropic" maybe? It's not a section heading but we can keep as prose? It's about the company; maybe we can keep as a paragraph under a heading? There's no heading for About Anthropic in list; but we could include as a

before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can start with maybe a

about Anthropic? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings not in list, but they gave examples. Probably we should stick to those headings only if content exists. We need to extract substantive content: - About The Role: description paragraph: "You will play a critical role in scaling our revenue by managing complex deals and developing standardized processes that balance speed with control. You'll work at the intersection of finance, sales, legal, and compliance teams to ensure our products reach customers to support Anthropic's rapid growth. Day-to-day, you'll quarterback complex deals through CPQ, contract management, and internal approvals. Over time, you'll also identify and drive improvements to the systems and workflows you operate in — embedding approved deal structures into Salesforce, improving CPQ configurations, and helping build the operational infrastructure that lets a lean team support enterprise deal volume at scale." That's the About the role content. - Key Responsibilities: list bullet points. List them: - Quarterback deals through internal processes — CPQ quote-building, approval routing, contract execution — ensuring accurate, timely completion - Own Anthropic’s deal-making execution processes, ensuring that all commercial workflows can seamlessly navigate internal processes - Build AI-native tooling with internal teams to meaningfully scale our commercial processes - Optimize operational workflows that reduce friction in the sales cycle and accelerate time-to-close - Act as the bridge between Sales and supporting teams, maintaining contract and compliance management systems and ensuring agreement terms align with company standards - Maintain visibility on high-priority deals, providing appropriate escalation paths when commercial terms require executive input - Collaborate with Legal teams to validate that agreements reflect the correct commercial intent and approvals - Track and analyze deal patterns to identify bottlenecks and propose data-driven improvements to our sales operations - Maintain and improve deal documentation: approval policies, pricing guidelines, SKU guidance, and process playbooks These are responsibilities. - Minimum Qualifications: list bullet points. List: - Are comfortable both executing within existing systems (CPQ, SFDC, contract platforms) and improving those systems as you go - Bring a detail-oriented, process-improvement mindset: you notice when something is manual or error-prone and you want to fix it - Have excellent communication and stakeholder management abilities, with proven success coordinating across multiple departments - Strong project management skills with experience juggling multiple critical initiatives - Bias toward action and comfort operating in ambiguity - Have experience with CRM systems, CPQ tools, and contract management platforms - Have a collaborative mindset and enjoy solving complex problems through cross-functional partnership - Preferred Qualifications: list bullet points. List: - Have 3+ years of experience in deal desk, sales strategy, commercial operations, or related roles, preferably in a high-growth technology environment - Experience with Salesforce, CPQ tools (Nue, Apttus, Steelbrick), or contract management platforms (Ironclad, Docusign CLM) - Background in project management, sales strategy, or commercial operations, where you’ve balanced operational excellence with building scaled systems - Experience with deal operations at companies with subscription and/or consumption-based business models - Knowledge of enterprise software contract terms and industry-standard commercial practices - Understanding of AI business models and the unique commercial considerations - Pay: "Annual Salary $190,000—$240,000 USD". Also note OTE includes base + commission. So we can put Pay section with that. - Benefits: The posting mentions: "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." Also earlier: "Anthropic is a public benefit corporation headquartered in San Francisco. 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." So we can extract benefits: competitive compensation and benefits (but that's vague), optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. Also maybe "We think AI systems..." not benefit. We'll include those. - Schedule: Not explicitly stated besides 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. So we can include Schedule section with that. - Skills: Not explicitly a separate list; but we could combine into Requirements? The instruction says use headings like Skills if content exists. There's no explicit skills list separate from qualifications. Might skip Skills. - Requirements: Could be Minimum Qualifications + Preferred Qualifications combined? But we have separate headings for Minimum Qualifications and Preferred Qualifications; they said we can use Requirements, Qualifications. Probably better to have a Qualifications section with Minimum and Preferred sub-sections? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Qualifications heading and inside we can have

or

for both minimum and preferred? But they said prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into one Qualifications section with two sublists? But we need to use

for section headings only; subheadings not specified. Could just have Qualifications heading and then two

paragraphs describing minimum and preferred. But we risk losing detail. Better to have separate sections: Minimum Qualifications and Preferred Qualifications as separate headings? They didn't list those exactly but they are under Qualifications umbrella. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use Requirements or Qualifications. I'd choose Qualifications and inside include both minimum and preferred as separate

with maybe a

label. That's acceptable. Thus sections: - About the role (

About the role

) with

content. - Responsibilities (

Responsibilities

) with
• ... - Qualifications (

  Qualifications

  ) with maybe two

  headings? Could use Minimum Qualifications and Preferred Qualifications inside. Or we could just list all qualifications in one list but that loses distinction. Better to include headings inside using

  Minimum Qualifications:

  then
  ..., then

  Preferred Qualifications:

  then
  ... - Benefits (

  Benefits

  ) with
  ... - Pay (

  Pay

  ) with

  ... - Schedule (

  Schedule

  ) with

  ... We must not include boilerplate like "About Anthropic", "How We're Different", "Guidance on Candidates' AI Usage", "We think AI systems...", "Your safety matters to us.", etc. Also remove "Logistics" maybe? That's metadata like Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship, etc. Some of that is relevant to Schedule (location-based hybrid policy) and maybe Requirements (minimum education). But we already have Schedule covering hybrid policy. Minimum education, required field of study, minimum years of experience could be part of Qualifications. However they are under "Logistics" heading. We should incorporate them if they are substantive. The posting includes: "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 should include Minimum education, Required field of study, Minimum years of experience as part of Qualifications (maybe as bullet points). Visa sponsorship is maybe not a benefit but could be mentioned under Benefits? It's not a standard benefit but could be included. However the instruction says to remove duplicated lines and boilerplate; visa sponsorship is not boilerplate but it's a specific policy. Could include under Benefits as "Visa sponsorship available". But we need to see if it's substantive. It's a specific statement. I'd include it under Benefits. Minimum years of experience: "Years of experience required will correlate with the internal job level requirements for the position." That's vague; maybe we can drop as it's not specific. 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. That's somewhat generic but still substantive. We'll include as bullet under Qualifications maybe. We also have "We encourage you to apply even if you do not believe you meet every single qualification..." that's boilerplate/application instruction; remove. Also "We think AI systems like the ones we're building have enormous social and ethical implications..." that's boilerplate; remove. Also "Come work with us!" etc maybe keep as part of Benefits? It's more marketing; but we already have Benefits paragraph. Could keep as part of Benefits but it's fluff. Might be okay to keep as part of Benefits but it's not specific benefit. The instruction: prefer a few substantive sections over many thin ones. So maybe we keep Benefits as we have. Now compile HTML. We must not include or . Just fragment. Let's craft:

  About the role

  You will play a critical role in scaling our revenue by managing complex deals and developing standardized processes that balance speed with control. You'll work at the intersection of finance, sales, legal, and compliance teams to ensure our products reach customers to support Anthropic's rapid growth. Day-to-day, you'll quarterback complex deals through CPQ, contract management, and internal approvals. Over time, you'll also identify and drive improvements to the systems and workflows you operate in — embedding approved deal structures into Salesforce, improving CPQ configurations, and helping build the operational infrastructure that lets a lean team support enterprise deal volume at scale.

  Responsibilities

  • Quarterback deals through internal processes — CPQ quote-building, approval routing, contract execution — ensuring accurate, timely completion
  • Own Anthropic’s deal-making execution processes, ensuring that all commercial workflows can seamlessly navigate internal processes
  • Build AI-native tooling with