Transformation & Strategic Programs, Senior Manager (Customer Success)
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, 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? Actually there is a paragraph about Salesforce (the company description). That is substantive? It's about the company, not role. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not explicitly listed to remove, but it's generic marketing fluff. However it's part of the posting; we need to preserve ALL substantive information. Is that substantive? It's about Salesforce being #1 AI CRM etc. Might be considered fluff but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." Could include an "About Salesforce" section? Not listed as allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we should incorporate that company description maybe into About the role? But About the role heading is for role description. The company description could be placed as a
before the About the role heading? The instruction: "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." It doesn't forbid other headings besides those listed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those headings. Safer to stick to those.
Thus we will output:
About the role
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.
Then Responsibilities as - each bullet.
We need to capture all responsibilities bullets from the text.
Let's extract them:
- 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
Check for duplicates: none.
Now Skills & Requirements: list from "Skills & Requirements" section.
Extract:
- 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
Now Benefits: list from "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."
Also earlier: "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." That's more generic. We'll include the specific list.
Thus Benefits
- time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program.
But each item should be separate
- . Could combine as one sentence but better separate.
Thus list:
- time off programs
- medical
- dental
- vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Now Pay: 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.
We'll put that in a
under Pay heading.
Now ensure we don't include any boilerplate like "Accommodations", "Posting Statement", etc. Remove those.
Also remove "To get the best candidate experience..." line, "Job Category Program & Project Management", "Job Details About Salesforce", the initial paragraph about Salesforce being #1 AI CRM etc. That's maybe considered boilerplate? It's not listed to remove but it's generic marketing. However we might keep it as part of About the role? But we already have About the role content. The initial Salesforce description could be omitted as it's not role-specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The Salesforce description is substantive about the company, but not about the role. However it's still part of posting. But we have limited headings; we could include a brief
before the About the role heading? The instruction says we can fold minor metadata into a short
or drop it. This is not metadata; it's marketing fluff. Might be considered boilerplate? Not sure. Safer to include it as a
before the About the role heading? But then we would have a stray paragraph not under a heading. The instruction didn't forbid that; just said use
for section headings (e.g...). It didn't say you can't have paragraphs outside headings. But typical output expects sections. I'd include a brief
with the company overview before the About the role heading, as it's substantive. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a company overview paragraph might be okay.
But we must not invent or summarize away detail. So we should keep that company description exactly as in text: "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 know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce."
We can put that as a
before the About the role heading.
Now check for duplicated lines: there may be duplicate sentences like "Unleash Your Potential..." appears later; we should not duplicate. We'll include only once.
Now ensure we removed "Accommodations", "Posting Statement", "EEO", etc.
Now produce HTML fragment.
Let's craft:
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 know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.
About the role
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.
Responsibilities
- 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,
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, 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? Actually there is a paragraph about Salesforce (the company description). That is substantive? It's about the company, not role. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not explicitly listed to remove, but it's generic marketing fluff. However it's part of the posting; we need to preserve ALL substantive information. Is that substantive? It's about Salesforce being #1 AI CRM etc. Might be considered fluff but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." Could include an "About Salesforce" section? Not listed as allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we should incorporate that company description maybe into About the role? But About the role heading is for role description. The company description could be placed as a
before the About the role heading? The instruction: "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." It doesn't forbid other headings besides those listed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those headings. Safer to stick to those.
Thus we will output:
About the role
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.
Then Responsibilities as- each bullet.
We need to capture all responsibilities bullets from the text.
Let's extract them:
- 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
Check for duplicates: none.
Now Skills & Requirements: list from "Skills & Requirements" section.
Extract:
- 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
Now Benefits: list from "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."
Also earlier: "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." That's more generic. We'll include the specific list.
Thus Benefits
- time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. But each item should be separate
- . Could combine as one sentence but better separate.
Thus list:
- time off programs
- medical
- dental
- vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Now Pay: 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.
We'll put that in a
under Pay heading. Now ensure we don't include any boilerplate like "Accommodations", "Posting Statement", etc. Remove those. Also remove "To get the best candidate experience..." line, "Job Category Program & Project Management", "Job Details About Salesforce", the initial paragraph about Salesforce being #1 AI CRM etc. That's maybe considered boilerplate? It's not listed to remove but it's generic marketing. However we might keep it as part of About the role? But we already have About the role content. The initial Salesforce description could be omitted as it's not role-specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The Salesforce description is substantive about the company, but not about the role. However it's still part of posting. But we have limited headings; we could include a brief
before the About the role heading? The instruction says we can fold minor metadata into a short
or drop it. This is not metadata; it's marketing fluff. Might be considered boilerplate? Not sure. Safer to include it as a
before the About the role heading? But then we would have a stray paragraph not under a heading. The instruction didn't forbid that; just said use
for section headings (e.g...). It didn't say you can't have paragraphs outside headings. But typical output expects sections. I'd include a brief
with the company overview before the About the role heading, as it's substantive. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a company overview paragraph might be okay. But we must not invent or summarize away detail. So we should keep that company description exactly as in text: "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 know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce." We can put that as a
before the About the role heading. Now check for duplicated lines: there may be duplicate sentences like "Unleash Your Potential..." appears later; we should not duplicate. We'll include only once. Now ensure we removed "Accommodations", "Posting Statement", "EEO", etc. Now produce HTML fragment. Let's craft:
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 know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.
About the role
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.
Responsibilities
- 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,