Salesforce Developer, Partnerships

Anthropic · San Francisco, CA · 1 mo ago

HybridInformation Technology$270k–$345k/yrFull-time

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Minimum Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule. Must only include sections if posting has real specific content. We need to extract content: - About the role: The paragraph after "About The Role". It's a description: "As a Salesforce Developer at Anthropic, you will design, build, and maintain the Salesforce platform that powers our Partnerships business: deal registration, partner attribution, co-sell, and cloud marketplace operations. You'll work both autonomously and collaboratively across Revenue Operations, Partnerships, and Finance to translate partner-channel requirements into scalable Apex, Flow, and integration solutions. We are an AI-first systems team, and you'll be expected to use Claude and our in-house AI development tooling as a core part of how you write, review, and ship code, always against our house standards for flexibility, maintainability, and scale." We can put that in

. - Responsibilities: list under "Key Responsibilities". Items: bullet list. We'll create

each. - Requirements: combine Minimum Qualifications and Preferred Qualifications? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose appropriate headings. Likely we need a "Requirements" section that includes Minimum Qualifications (maybe also Preferred). Could split into Minimum Qualifications and Preferred Qualifications but they said prefer few substantive sections over many thin ones. So we can combine into Requirements (including both minimum and preferred). But we must preserve all substantive info. We'll list bullet points for each qualification. We need to avoid repeating job title as heading. No Job ID. - 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 have benefits content. - Pay: The posting includes "Annual Salary $270,000—$345,000 USD". Also mention 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". This role is Salesforce Developer, not sales, but they still give range. We'll include Pay section with that range. - 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." Also maybe "flexible working hours" mentioned under benefits. But schedule: we have hybrid policy. We'll include Schedule section with that. We must not include sections with filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the "How We're Different", "Guidance on Candidates' AI Usage", "We think AI systems..." etc. Also the "Not all strong candidates..." etc. Also the "Your safety matters..." etc. Also the "We encourage you to apply..." etc. Also the "We believe that the highest-impact AI research..." etc. Also the "Come work with us!" etc. Also the "Guidance on Candidates' AI Usage:" etc. Also the "We think AI systems..." etc. Also the "We believe that the highest-impact AI research..." etc. Also the "We're an extremely collaborative group..." etc. Also the "The easiest way to understand our research directions..." etc. Also the "Guidance on Candidates' AI Usage:" etc. Also the "We think AI systems..." etc. Also the "We believe that the highest-impact AI research..." etc. Also the "We view AI research as an empirical science..." etc. Also the "As such, we greatly value communication skills." etc. Also the "The easiest way to understand our research directions is to read our recent research." etc. Also the "This research continues many of the directions our team worked on prior to Anthropic, including: ..." etc. Also the "Come work with us!" etc. Also the "Anthropic is a public benefit corporation..." etc (but we used part of that for benefits). However we need to avoid duplication; we can keep the benefits sentence but not the rest. We must ensure we don't include any application instructions like "We encourage you to apply even if you do not believe you meet every single qualification." That's application instruction; we should remove. Also "Not all strong candidates..." etc. Also "We encourage you to apply..." etc. Also "We think AI systems..." etc. Also "Your safety matters..." etc. Also "We believe that the highest-impact AI research..." etc. Also "Guidance on Candidates' AI Usage:" etc. Thus we will keep only: - About the role paragraph. - Responsibilities list. - Requirements (minimum and preferred qualifications) maybe as bullet list. - Benefits paragraph. - Pay paragraph. - Schedule paragraph. We need to use
for each section heading. Let's extract responsibilities bullet points exactly: From "Key Responsibilities": - Design and build Partnerships infrastructure in Salesforce, including deal registration workflows, channel-conflict detection, partner attribution, and partner account hierarchy - Develop and maintain Apex (triggers, services, selectors, batch/queueable), Lightning Web Components, and Flow automation following our house Apex standards and trigger framework - Build and own integrations between Salesforce and partner-ecosystem systems such as cloud marketplaces (AWS, GCP, Azure), PRM tools, and middleware - Configure partner-facing portals with appropriate sharing, visibility, and license-model design - Use Claude and our internal AI development tooling as a first-class part of your build and code-review workflow - Partner with Revenue Operations analysts to ensure data-model decisions support downstream partner performance reporting - Partner with DevOps on release management for your work: sandbox strategy, source control, peer review, and deployment via SFDX/metadata tooling - Ensure appropriate controls, test coverage, and documentation are in place for an effective control environment - Operate with ambiguity in a rapidly changing business, resolve problems independently, and propose solutions that scale We'll put each as
. Now Requirements: Minimum Qualifications bullet list: - Hands-on Salesforce development experience (Apex, SOQL, LWC, Flow) in a production org - Experience building or maintaining partner/channel functionality in Salesforce: deal registration, partner portals, attribution models, or co-sell opportunity management - Experience integrating Salesforce with external platforms via REST/Bulk APIs, middleware (Workato, Mulesoft, or similar), or direct callouts - Fluency with SFDX, source-controlled metadata, and a sandbox-to-prod release process with peer review - Active use of AI-assisted development tools (Claude, Copilot, Cursor, or similar) as part of how you write and review code, and the ability to speak to how you steer and verify their output - Basic SQL skills and comfort working alongside a data warehouse - Effective communication with sales, partnerships, finance, and engineering stakeholders Preferred Qualifications bullet list: - Salesforce Platform Developer I and II certifications - Advanced Administrator or Application/System Architect certification - Deep understanding of Salesforce platform constraints: governor limits, bulkification, sharing and visibility, recursion control - Cloud-marketplace integration experience (AWS, GCP, Azure) - Familiarity with partner-specific integration platforms such as Workspan - Proven experience scaling Salesforce in a high-growth GTM environment We'll combine them maybe under Requirements with subheadings? But we cannot add extra headings besides the allowed ones? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings, but says prefer few substantive sections over many thin ones. Could we include both Minimum Qualifications and Preferred Qualifications as subheadings (
?) Not allowed? It didn't forbid other headings, but to be safe we could just list all qualifications under Requirements as a single list, maybe grouping with comments? But we need to preserve all substantive info; we can just list them all as bullet points without distinguishing minimum vs preferred. That would lose the distinction but still preserve the content (the qualifications themselves). The distinction is not essential for the job; but maybe they want to keep it. However we can include a note like "Minimum Qualifications:" and "Preferred Qualifications:" as plain text inside
before the list. That's okay; not a heading. We'll do that. Thus Requirements section:
Requirements
then a
Minimum Qualifications:
then

Salesforce Developer, Partnerships

Requirements

About the role

Responsibilities

Similar jobs