Transformation & Strategic Programs, Senior Manager (Customer Success)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Skills & Requirements), Benefits, Pay (if present). Also maybe "About Salesforce" is not a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings for sections that have content. We must not repeat job title as heading. Do not put Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "To get the best candidate experience..." line, "Job Category Program & Project Management", "Job Details About Salesforce" maybe part of About Salesforce? The "About Salesforce" paragraph is descriptive about company; maybe we can include as part of "About the role"? Actually there is a separate "About Salesforce" paragraph before "About The Role". The instruction: include a section ONLY when the posting has real, specific content for it. The "About Salesforce" is generic company description; could be considered boilerplate? It's not a standard heading like About the role, Responsibilities, etc. It might be considered fluff; but it's substantive about company. However the instruction says to use headings like About the role, Responsibilities, etc. Not "About Salesforce". So we likely should not create a heading for About Salesforce; we could incorporate that paragraph into maybe a

under About the role? But the instruction says do not repeat job title as heading; but we can have other headings not listed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should not create other headings like About Salesforce. So we should omit that paragraph or maybe incorporate into a

without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid stray paragraphs without heading. But they said "Prefer a few substantive sections over many thin ones." So we could include a

for the About Salesforce description as part of the fragment, maybe before the About the role heading. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have a

without heading; that's okay. But we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the About Salesforce paragraph content. We also need to keep "Accommodations" etc? That's boilerplate/legal; remove. We need to keep "Posting Statement" etc? That's EEO boilerplate; remove. We need to keep benefits description and salary range. We need to keep "Skills & Requirements" content. We need to keep responsibilities list. We need to keep "About The Role" paragraph. We need to keep "Unleash Your Potential" maybe part of benefits? It's more marketing; could be considered boilerplate? It's about benefits and resources; but we already have Benefits section. Might be considered fluff; but it's substantive about benefits and resources. However we already have Benefits section with details; we could incorporate that paragraph into Benefits section as a

before list. But we must not create filler. It's okay. We need to ensure we don't include duplicated lines. Let's extract sections: - About The Role: paragraph(s) after "About The Role". The text: "The Senior Program Manager plays a meaningful role leading both large-scale, cross-functional initiatives as well as new product launches within our Customer Success organization. PMs are responsible for programs from beginning to end, ensuring cross team collaboration, flawless execution and effective communication. They work closely with executives, strategy leaders, technology partners and many more to drive critical programs and activities across the company. PMs do this by understanding the business strategy, the customer experience necessary to realize the strategy, and the impact of the technology and process changes to our people." That's the content. - Responsibilities: bullet list after "Responsibilities". Let's capture each line: Drives the strategic development of large scale, cross organizational programs Understands and contributes to the overarching business strategy; bridges the gap between cross functional teams to realize the program vision Builds cross functional relationships and proactively drives alignment across a diverse set of stakeholder groups Partners with Experience teams to influence technology and process building that align to Customer Success strategies Collaborate with Product Architects, Support Engineers and Success Managers to design Delivery models that best suit the customer experience Ability to adapt communication style and content to necessary audiences ranging from executive leadership to cross functional working groups Develops program approach and leads the charge to successful delivery Drives program plan and all related launch activities tied to the Product, Offer and/or Experience launch through our formal stage gate process Partner with Business Technology and other shared services teams to appropriately staff, prioritize and capacity plan across all programs through the use of agile methodologies Lead weekly and/or daily team calls to drive program alignment as well as monthly Steerco calls to gain executive buy-in Successfully bridges the gap between strategy, capacity, content, technology, engineering, support delivery & global enablement Anticipates problems, identifies mitigation plans and escalates gaps with leaders Fosters cross team collaboration and, as needed, leads the team through fearless decision making Develops and governs PMO best practices across the organization Define, implement and continuously improve the program launch process to increase efficiency, reduce risk and improve quality Serve as product owner to sprint planning processes for shared services teams Train and enable cross functional teams on program management disciplines We need to put each as

inside

. - Skills & Requirements: after "Skills & Requirements". The list: 10+ years of Program Management and/or Product Launch experience in a highly matrixed environment Outstanding organizational, communication (verbal/presentation/written), and interpersonal skills Strong understanding of Salesforce products, in how they connect to offer a comprehensive solution to our prospects and customers Proven experience working with global teams across multiple cultures, time zones, departments and functions Ability to establish credibility and rapport with senior executives, technical and non-technical team members alike Flexibility in shifting direction quickly when priorities change; excellent multi-tasking skills Demonstrate strong problem solving skills, process-driven mindset, and resourcefulness Analytical thinker that is willing to make decisions cross functionally in a fast paced, dynamic environment Self starter; willing to dig in and get the job done with minimal guidance Ideal: Scrum master certification (CSM), PMI or PrMI certification We need to output as
• . Could also treat as Requirements section. - Benefits: after "Unleash Your Potential" paragraph? Actually there is a paragraph: "Unleash Your Potential When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love. Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's marketing fluff; but we might keep as part of Benefits? However there is later a detailed benefits list: "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." Also there is compensation range: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $143,400 - $216,900 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." Thus we need Benefits section with 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). Also maybe include link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include the link as well? It's a URL; we could include as maybe. But they didn't forbid links. We'll include as

  with link. Pay section: we need to include Pay heading with the salary range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we have Pay: we should create

  Pay

  and include the salary range paragraph. Schedule: not present, so omit. We also need to include maybe "About Salesforce" paragraph as a

  before About the role heading? Could be considered boilerplate but it's descriptive about company; but we already have About the role heading; we could include it as a

  under About the role? However the About the role heading already has its own paragraph; we could add another

  after it? But that would be duplicate heading? Not exactly. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having multiple

  under a heading. So we could put the About Salesforce description as a

  under About the role heading? But that would mix company description with role description; maybe better to have a separate heading like "About Salesforce" but not allowed. Could we omit it? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The About Salesforce paragraph is substantive about company; if we omit it, we lose info. So we need to include it somewhere. Since we cannot create a heading for it (not in allowed list), we could just put it as a

  before the first heading. That's acceptable. Similarly, the "Unleash Your Potential" paragraph could be placed under Benefits heading as a

  before the list. Now we need to remove boilerplate: lines like "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. Also "Job Category Program & Project Management" remove. Also "Job Details About Salesforce" maybe part of the About Salesforce paragraph? Actually the line "Job Details About Salesforce" is a heading? It appears as "Job Details About Salesforce". That's likely a label; we can treat as part of the About Salesforce paragraph? But it's just a label; we could drop it as it's not substantive. The paragraph after that starts with "Salesforce is the #1 AI CRM..." So we can drop "Job Details About Salesforce". Also remove "Accommodations" etc. Remove "Posting Statement" etc. Remove "Please note that Salesforce uses artificial intelligence..." etc. Remove "Humans will always make any candidate selection..." etc. Remove "Please see our Candidate Privacy Statement..." etc. Remove "Posting Statement" and all EEO boilerplate. Remove "Recruiting, hiring, and promotion decisions..." etc. Remove "In the United States, compensation offered will be determined..." Actually that's part of compensation description; we might keep some of it? The paragraph about compensation includes: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $143,400 - $216,900 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." That's substantive; we keep that as Pay section