Senior Product Manager, Project & Program Management, Emerging Technology
About the role
then...
. - Responsibilities: list of duties from "What You'll Be Doing". Use- each bullet.
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? Could separate into Requirements (required) and Qualifications (preferred) but guidelines say we can have sections Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to put where. The posting has Required Qualifications (list) and Preferred Qualifications (list). Could map Required Qualifications to Requirements section, Preferred Qualifications to Qualifications section. Skills maybe not explicitly listed; we could omit Skills if no specific skill list beyond what's in qualifications. Could include Skills from Required Qualifications like "Fluency in Agile methodologies", "AI fluency", "Hands-on experience with modern project management tools". But better to keep Skills section only if there is explicit skill list; we could treat those as skills. However guidelines: Prefer a few substantive sections over many thin ones. Could combine Required and Preferred into Requirements and Qualifications. Benefits: we have benefits description. Pay: salary range. Schedule: not mentioned; omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: accommodations, EEO, etc. Also remove "To get the best candidate experience..." line at start. Also remove "Job Category Product". Also remove "About Salesforce" maybe? That's introductory but could be considered part of About the role? Actually "About Salesforce" is generic company description; could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The "About Salesforce" paragraph is substantive but not role-specific; still it's about the company. Could we include it under About the role? Might be okay but we already have About the role heading; we could include that paragraph there. However the "About Salesforce" is separate from "About The Role". Might be better to include a short paragraph about Salesforce under About the role heading as context. 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. So we can include the About Salesforce paragraph as part of About the role section. Thus About the role section: combine the About Salesforce paragraph and the About The Role paragraph. Let's extract text: 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 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: "Emerging Technology is Salesforce's 0-to-1 engine — the team that discovers, builds, and proves out new capabilities as Customer Zero before handing them off to scale. As Senior Product Manager for Project & Program Management, you'll be the person who helps product owners cut through the noise. You won't own a product portfolio; instead, you'll embed directly with PMs, engineers, designers, and cross-functional partners to bring structure to ambiguity, clear blockers, and help the team execute at the pace this work demands." We can combine into one
maybe two paragraphs. Responsibilities: list from "What You'll Be Doing": each bullet: - Partner with product owners: Work side-by-side with PMs to plan, sequence, and execute their projects. Help break big problems into shippable milestones and hold the line on scope and timelines - Drive cross-functional coordination: Own the coordination layer across engineering, design, data, security, and partner teams. Proactively identify dependencies and get ahead of blockers before they stall progress - Navigate partner team complexity: ET projects almost always touch other orgs — help PMs understand and manage the nuance of cross-org work so nothing falls through the cracks - Run project cadences: Stand up and facilitate the right rituals for each project — standups, milestone check-ins, sprint reviews, and stakeholder syncs. Keep them lightweight and useful, never ceremonial - Create clarity on status and risk: Maintain honest, clear project health updates that give leadership visibility without creating overhead for the PMs doing the work. Surface risks early and facilitate trade-off decisions - Enable PM effectiveness: Help product owners level up their execution skills — coach them on communicating status, running effective meetings, and navigating the organizational dynamics that come with 0-to-1 work inside a large company - Drive continuous improvement: Run retrospectives, identify what's slowing the team down, and iterate on how projects are managed so the team keeps getting faster We need to ensure each bullet is a
- .
Requirements: Required Qualifications list:
- 5–8 years of experience in program management, technical program management, or project-oriented product management within enterprise technology
- Proven track record of driving complex, cross-functional projects to completion across multiple teams and orgs simultaneously, managing dependencies and competing priorities without losing momentum
- Deep comfort operating in ambiguity — you move fast, cut scope when needed, and optimize for outcomes over process without waiting for perfect information
- Strong communication and interpersonal skills: you can translate messy project dynamics into clear, honest updates for executives and individual contributors alike, and build trust quickly with PMs, engineers, designers, and business partners
- Fluency in Agile methodologies (Scrum, Kanban) with the judgment to adapt frameworks to what the team actually needs
- AI fluency: comfortable using AI tools to accelerate work, remove bottlenecks, and help teams ship faster
- Hands-on experience with modern project management tools like Linear, with a perspective on how tooling can improve team velocity and visibility
Qualifications: Preferred Qualifications list:
- Experience working within or alongside internal platform or infrastructure teams at a large technology company
- Familiarity with Salesforce's product and engineering org structure
- Background in 0-to-1 product development or innovation programs
- Experience coaching or mentoring product managers on execution practices
- A related technical degree
Benefits: from "What's In It For You" and later benefits list:
What's In It For You: "This is an opportunity to work at the center of one of Salesforce's most exploratory and fast-moving team — influencing how cutting-edge capabilities are built and delivered across the company. You'll have direct impact on how the Emerging Technology team operates, with room to shape the function itself. The team moves with startup speed inside one of the world's most trusted technology companies. 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."
Then later: "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."
We can combine into a Benefits section with a paragraph summarizing and then a list of specific benefits.
Pay: Salary range: "The typical base salary range for this position is $172,500 - $260,100 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $207,800 - $285,800 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 Pay section.
Schedule: not present, omit.
We must not include any boilerplate like Accommodations, Posting Statement, EEO, etc.
Now produce HTML fragment: use
for each section heading. Use
- for lists. Use
for prose. We need to ensure we don't include empty sections. Let's craft:
About the role
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.
Emerging Technology is Salesforce's 0-to-1 engine — the team that discovers, builds, and proves out new capabilities as Customer Zero before handing them off to scale. As Senior Product Manager for Project & Program Management, you'll be the person who helps product owners cut through the noise. You won't own a product portfolio; instead, you'll embed directly with PMs, engineers, designers, and cross-functional partners to bring structure to ambiguity, clear blockers, and help the team execute at the pace this work demands.
Responsibilities
- Partner with product owners: Work side-by-side with PMs to plan, sequence, and execute their projects. Help break big problems into shippable milestones and hold the line on scope and timelines
- Drive cross-functional coordination: Own the coordination layer across engineering, design, data, security, and partner teams. Proactively identify dependencies and get ahead of blockers before they stall progress
- Navigate partner team complexity: ET projects almost always touch other orgs — help PMs understand and manage the nuance of cross-org work so nothing falls through the cracks
- Run project cadences: Stand up and facilitate the right rituals for each project — standups, milestone check-ins, sprint reviews, and stakeholder syncs. Keep them lightweight and useful, never ceremonial
- Create clarity on status and risk: Maintain honest, clear project health updates that give leadership visibility without creating overhead for the PMs doing the work. Surface risks early and facilitate trade-off decisions
- Enable PM effectiveness: Help product owners level up their execution skills — coach them on communicating status, running effective meetings, and navigating the organizational dynamics that come with 0-to-1 work inside a large company
- Drive continuous improvement: Run retrospectives, identify what's slowing the team down, and iterate on how projects are managed so the team keeps getting faster
Requirements
- for lists. Use