Partner Engagements Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Salesforce, About The Team, Role Overview, Responsibilities, Skills/Experience, Benefits (maybe), Pay (salary range). Also maybe Schedule? Not present. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About Salesforce (company description) could go under "About the role"? Actually "About the role" is typical heading for role overview. But we have "Role Overview". Could map to "About the role". Or we could have separate sections: "About the team" maybe not a standard heading but we could incorporate into "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. We should not invent headings not in list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those exact headings when applicable. So we need to map content to those headings. We have content: - About Salesforce (company description) maybe fits under "About the role"? Not exactly. Could be "About the role" includes role overview and maybe company context. We'll put company description under "About the role". Or we could have "About the role" includes role overview and maybe team description. - About The Team could be part of "About the role" as well. - Role Overview: could be part of "About the role". - Responsibilities: we have a detailed list. - Skills/Experience: we have skills/experience list; could map to "Skills" or "Qualifications". The list includes both skills and qualifications (education). We could split: "Skills" for skills, "Qualifications" for education and experience. But we have to avoid thin sections. Maybe combine into "Skills" and include experience/education there. - Benefits: we have benefits description. - Pay: we have salary range. - Schedule: not present (flexible schedule mentioned under Skills/Experience: "Flexibility & Travel: Flexible schedule to accommodate global time zones, with the ability to travel to event locations globally 20–40%." That's schedule/travel info. Could be considered schedule. But we should only include Schedule if posting actually states them. It does mention flexible schedule and travel. So we could include a Schedule section with that info. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the accommodations, AI notice, privacy statement, equal opportunity statement, etc. Also remove "To get the best candidate experience..." line at start. Also remove "Job Category Operations Job Details". Also remove "Unleash Your Potential" maybe considered boilerplate? It's more marketing but could be considered part of benefits? It's generic; maybe we keep as part of benefits? It's not specific benefits; it's fluff. Probably remove as boilerplate. Also remove "Accommodations" etc. Also remove "Posting Statement" etc. Also remove "Salesforce is an equal opportunity employer..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "At Salesforce, we believe in equitable compensation practices..." maybe part of pay? It's generic; we could keep pay range but not the fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the equal opportunity statement, accommodations, AI notice, privacy statement, etc. Keep the pay range specifics. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the responsibilities list exactly as given (maybe rephrase? No, preserve). Keep skills/experience list exactly. Keep benefits list (time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program). Keep pay range specifics. We need to format as HTML fragment with

headings and

• for lists,

  for prose. We must not output markdown code fences. Let's craft sections: 1.

  About the role

  - include company description, team description, role overview. Could be multiple paragraphs. We need to preserve all substantive info: About Salesforce paragraph, About The Team paragraph, Role Overview paragraph(s). We'll combine them into maybe two

  elements. 2.

  Responsibilities

  - we have bullet points under Logistics & Program Execution, Content Coordination & Management, Stakeholder Leadership & Operations. We need to turn each bullet into
• . The original has headings within responsibilities (Logistics & Program Execution, Content Coordination & Management, Stakeholder Leadership & Operations). Should we keep those as headings inside? The instruction: use
  • for any list of duties/requirements/benefits. It didn't forbid subheadings inside list? Probably better to keep as plain list items; we could incorporate the heading as part of the li text. But we could also keep subheadings as

    ? Not allowed? Only specified headings are h3 for section headings. Could use other headings but not required. Safer to just make list items, preserving the content exactly as given (including the heading text as part of the item). We'll produce list items like: - Logistics & Program Execution Own the operational strategy and execution roadmap for partner-facing programs, both virtual and in-person.Direct event logistics including registration setup, venue contracts, back-end virtual platform setup, entertainment, meeting space planning, timelines, onsite event execution, budget ownership, debrief collection, and survey distribution. But note there is missing period after first sentence; we keep as is. Similarly for Content Coordination & Management: multiple sentences. Stakeholder Leadership & Operations: multiple sentences. We'll keep each as separate

    . 3.

    Skills

    - we have skills/experience list. Could split into Skills and Qualifications but we have only Skills heading allowed. We'll put all under Skills. The list includes: - 8+ years of program leadership, event strategy, content direction, or communications leadership experience. - Experience leading partner programs or working within a B2B technology environment preferred. - Content & Communication Skills: Strong writing, editorial judgment, and presentation strategy skills, with a high degree of proficiency in Google Slides and Google Docs. - Program Leadership & Decision-Making: Exceptional program leadership skills—highly organized, detail-oriented, and able to own complex timelines and make sound decisions in a fast-paced environment. - Cross-Functional Leadership: Strong leader with the ability to direct and influence global cross-functional teams and build lasting stakeholder relationships. - Service-Focused: Proactive and outcomes-oriented mindset with a strong commitment to internal stakeholders and partner success. - Technical Proficiency: High aptitude for learning new tools and software. Proficient in Google Workspace, Slack, and Salesforce platforms. - Flexibility & Travel: Flexible schedule to accommodate global time zones, with the ability to travel to event locations globally 20–40%. - Education: Bachelor's degree or equivalent experience required. We'll make each as

    . 4.

    Benefits

    - list of benefits: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program. We'll make

    • . 5.

      Pay

      - paragraph with salary range details: "The typical base salary range for this position is $117,400 - $177,600 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $140,900 - $193,700 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." Also maybe include the line about equitable compensation practices? That's fluff; we can omit as boilerplate? It's not legal boilerplate but it's generic statement; maybe keep as part of Pay? It's not specific detail; but it's not boilerplate like EEO. It's still somewhat generic. Safer to keep only the specific range sentences. We'll keep those two sentences. 6.

      Schedule

      - we have flexible schedule and travel info already included under Skills; but we could also create Schedule section with that info. However we already used that info under Skills; duplicating would be repeating content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it under Skills, we already preserved it. Adding a Schedule section would duplicate content (the same sentence). That's not prohibited but could be considered duplication. Better to keep it only once. Since we already placed it under Skills, we can omit Schedule section. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having content appear under multiple headings, but that would be duplication. We'll avoid duplication. Thus we have sections: About the role, Responsibilities, Skills, Benefits, Pay. Check if any other sections like Qualifications needed? We have education under Skills; that's fine. Now we need to strip out boilerplate lines: The initial line "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." Remove. "Job Category Operations Job Details" remove. "About Salesforce" paragraph keep. "About The Team" paragraph keep. "Role Overview" paragraph(s) keep. Responsibilities block keep. Skills/Experience block keep. "Unleash Your Potential" paragraph maybe remove as marketing fluff; it's not specific benefit. Remove. "Accommodations" etc remove. "Please note that Salesforce uses artificial intelligence..." remove. "Please see our Candidate Privacy Statement..." remove. "Posting Statement" etc remove. All equal opportunity etc remove. "Pursuant to the San Francisco Fair Chance Ordinance..." remove. "At Salesforce, we believe in equitable compensation practices..." remove (maybe part of pay but it's generic; we already have pay specifics; we can drop). Now ensure we keep the benefits paragraph: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com." The link maybe considered boilerplate? It's a link to benefits details; it's substantive? It's a reference; we could keep it as part of benefits. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not boilerplate; it's a benefits link. We'll keep it. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft:

      About the role

      About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we