Senior Director, Product Design - Ecosystem
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions, accommodations, etc. Keep substantive info.
We need to parse the posting.
Key sections:
- About Salesforce (intro) maybe "About the role"? Actually there is "About Salesforce" and "About Slack & The Role". Could combine into "About the role". Use About the role
with paragraphs.
- Responsibilities: list under "Key Responsibilities". Use - .
- Minimum Qualifications: list. Could be "Requirements" or "Qualifications". Use
Minimum Qualifications
maybe as Requirements.
- Preferred Qualifications: could be "Preferred Qualifications" maybe as Skills? But we have Skills section. Could treat as "Preferred Qualifications" under Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: combine About Salesforce and About Slack & The Role.
- Responsibilities: Key Responsibilities.
- Requirements: Minimum Qualifications.
- Qualifications: maybe Preferred Qualifications? Or we could treat Preferred Qualifications as Skills? Actually Skills could be derived from qualifications. But we have both Minimum and Preferred; we could put Minimum under Requirements, Preferred under Qualifications.
- Skills: maybe not separate; we could omit if no specific skills list beyond qualifications. But we could include "Skills" heading with bullet list of skills from qualifications? However we must not create sections with filler. If we don't have explicit skills list, better to omit Skills section.
- Benefits: The posting mentions benefits: "Our benefits and resources support you to find balance and be your best..." plus 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." Also link. So we have specific benefits list. So include Benefits section with .
- Pay: The posting includes salary range: "The typical base salary range for this position is $218,400 - $365,200 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $263,200 - $401,400 annually." So we have Pay section.
- Schedule: Not mentioned. So omit Schedule.
Also we may have "What Makes This Role Different" etc. Could be part of About the role or Responsibilities? Might be extra but we can include as part of About the role paragraph.
We must not include boilerplate like accommodations, AI tools statement, equal opportunity, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase into HTML? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Likely we should keep the same sentences, maybe copy them.
We need to output only HTML fragment, no markdown fences.
Let's craft:
About the role
... combine About Salesforce and About Slack & The Role paragraphs, plus maybe "What Makes This Role Different" and "Unleash Your Potential"? The latter is more about benefits; maybe keep in About the role? But "Unleash Your Potential" is generic marketing; could be considered boilerplate? It's not EEO but still promotional. Might be okay to keep as part of About the role. However we need to avoid fluff? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Unleash Your Potential" is not those; it's marketing but substantive? It's vague. Might be considered filler? It says "When you join Salesforce, you’ll be limitless..." It's generic. Could be considered boilerplate? Not sure. Safer to omit generic marketing fluff. Keep only concrete details about role, responsibilities, qualifications, benefits, pay.
Thus About the role: include the description of Salesforce, Slack, the role, the opportunity, the open questions. That's substantive.
Let's extract:
About Salesforce paragraph: "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 Slack & The Role: "Slack is at an inflection point. We're evolving from the world's most beloved team communication tool into an AI operating system for work, where humans and agents get things done together. The developer platform is how that future comes to life: it's the ecosystem that lets builders at every scale extend Slack with agents and apps, creating them, managing them, and distributing them through the Slack Marketplace. As Senior Director, Product Design - Ecosystem, you'll hold and continuously refine the design vision for the developer experience across Slack's platform, partnering closely with product and engineering leadership. This is a player-coach role: you'll build and grow a small team of designers while staying hands-on in the design work yourself. You'll report to the Vice President, Product Design. The Opportunity: Defining How the World Builds on Slack You'll own design across the platform's full arc: what agents do inside Slack, how they're built, how they're managed and discovered, and how partners bring theirs to the ecosystem. As AI redefines both how software gets built and how work gets done, you'll shape what that developer experience becomes. The open questions you'll answer: The Agent Experience: What should agents do inside Slack, and how do people build them now that AI has changed what "building" means?Management: How do developers and admins run a growing ecosystem of agents with confidence?Discovery: How do people find and trust the right agents in the marketplace?Partners: How do we host partners like OpenAI, Anthropic, Cognition, and GitHub so their agents feel native to Slack?"
We can keep that as paragraphs.
Now Responsibilities: list from "Key Responsibilities". Items:
- Design Vision: Hold and continuously refine the long-range design vision for the platform, in close partnership with product and engineering leadership
- End-to-End Platform Design: Drive design across the full developer lifecycle: defining what agents do in Slack, agent creation, install and management, and marketplace discovery
- Partner Experience: Shape how partners building on Slack (OpenAI, Anthropic, Cognition, GitHub, and more) bring their agents into the ecosystem
- Hands-On Craft: Contribute directly to the design work as a player-coach, setting the craft bar for the team
- Team Leadership: Grow and develop the platform design team, owning staffing and career development for the designers on it
We'll output as
- each.
Minimum Qualifications: list:
- 10+ years of product design experience, including work on developer-facing or highly technical products
- Experience managing and growing design teams
- Hands-on experience with AI and vibe-coding tools, and a solid understanding of developer workflows
- A track record of partnering with product and engineering leadership to define and refine product direction through design
Preferred Qualifications:
- Experience designing marketplace or agent-discovery experiences
- Experience bringing third-party agentic experiences into a product
- Experience designing multiplayer or collaborative use cases
- Deep familiarity with Slack's platform surfaces and how its ecosystem works
We could put Minimum Qualifications under Requirements heading, Preferred Qualifications under Qualifications heading.
Benefits: list:
- time off programs
- medical
- dental
- vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Also mention "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 prose; could be a
before list.
Pay: include the salary ranges as prose.
We must not include "Apply today..." etc. Also remove "Accommodations", "Posting Statement", etc.
Now craft HTML.
We need to ensure no extra whitespace? It's fine.
Let's produce:
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.
Slack is at an inflection point. We're evolving from the world's most beloved team communication tool into an AI operating system for work, where humans and agents get things done together. The developer platform is how that future comes to life: it's the ecosystem that lets builders at every scale extend Slack with agents and apps, creating them, managing them, and distributing them through the Slack Marketplace. As Senior Director, Product Design - Ecosystem, you'll hold and continuously refine the design vision for the developer experience across Slack's platform, partnering closely with product and engineering leadership. This is a player-coach role: you'll build and grow a small team of designers while staying hands-on in the design work yourself. You'll report to the Vice President, Product Design. The Opportunity: Defining How the World Builds on Slack You'll own design across the platform's full arc: what agents do inside Slack, how they're built, how they're managed and discovered, and how partners bring theirs to the ecosystem. As AI redefines both how software gets built and how work gets done, you'll shape what that developer experience becomes. The open questions you'll answer: The Agent Experience: What should agents do inside Slack, and how do people build them now that AI has changed what "building" means?Management: How do developers and admins run a growing ecosystem of agents with confidence?Discovery: How do people find and trust the right agents in the marketplace?Partners: How do we host partners like OpenAI, Anthropic, Cognition, and GitHub so their agents feel native to Slack?
Responsibilities
- Design Vision: Hold and continuously refine the long-range design vision for the platform, in close partnership with product and engineering leadership
- End-to-End Platform Design: Drive design across the full developer lifecycle: defining what agents do in Slack, agent creation, install and management, and marketplace discovery
- Partner Experience: Shape how partners building on Slack (OpenAI, Anthropic, Cognition, GitHub, and more) bring their agents into the ecosystem
- Hands-On Craft: Contribute directly to the design work as a player-coach, setting the craft bar for the team
- Team Leadership: Grow and develop the platform design
Minimum Qualifications
maybe as Requirements. - Preferred Qualifications: could be "Preferred Qualifications" maybe as Skills? But we have Skills section. Could treat as "Preferred Qualifications" under Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: combine About Salesforce and About Slack & The Role. - Responsibilities: Key Responsibilities. - Requirements: Minimum Qualifications. - Qualifications: maybe Preferred Qualifications? Or we could treat Preferred Qualifications as Skills? Actually Skills could be derived from qualifications. But we have both Minimum and Preferred; we could put Minimum under Requirements, Preferred under Qualifications. - Skills: maybe not separate; we could omit if no specific skills list beyond qualifications. But we could include "Skills" heading with bullet list of skills from qualifications? However we must not create sections with filler. If we don't have explicit skills list, better to omit Skills section. - Benefits: The posting mentions benefits: "Our benefits and resources support you to find balance and be your best..." plus 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." Also link. So we have specific benefits list. So include Benefits section with- .
- Pay: The posting includes salary range: "The typical base salary range for this position is $218,400 - $365,200 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $263,200 - $401,400 annually." So we have Pay section.
- Schedule: Not mentioned. So omit Schedule.
Also we may have "What Makes This Role Different" etc. Could be part of About the role or Responsibilities? Might be extra but we can include as part of About the role paragraph.
We must not include boilerplate like accommodations, AI tools statement, equal opportunity, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase into HTML? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Likely we should keep the same sentences, maybe copy them.
We need to output only HTML fragment, no markdown fences.
Let's craft:
- each.
Minimum Qualifications: list:
- 10+ years of product design experience, including work on developer-facing or highly technical products
- Experience managing and growing design teams
- Hands-on experience with AI and vibe-coding tools, and a solid understanding of developer workflows
- A track record of partnering with product and engineering leadership to define and refine product direction through design
Preferred Qualifications:
- Experience designing marketplace or agent-discovery experiences
- Experience bringing third-party agentic experiences into a product
- Experience designing multiplayer or collaborative use cases
- Deep familiarity with Slack's platform surfaces and how its ecosystem works
We could put Minimum Qualifications under Requirements heading, Preferred Qualifications under Qualifications heading.
Benefits: list:
- time off programs
- medical
- dental
- vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Also mention "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 prose; could be a
before list. Pay: include the salary ranges as prose. We must not include "Apply today..." etc. Also remove "Accommodations", "Posting Statement", etc. Now craft HTML. We need to ensure no extra whitespace? It's fine. Let's produce:
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.
Slack is at an inflection point. We're evolving from the world's most beloved team communication tool into an AI operating system for work, where humans and agents get things done together. The developer platform is how that future comes to life: it's the ecosystem that lets builders at every scale extend Slack with agents and apps, creating them, managing them, and distributing them through the Slack Marketplace. As Senior Director, Product Design - Ecosystem, you'll hold and continuously refine the design vision for the developer experience across Slack's platform, partnering closely with product and engineering leadership. This is a player-coach role: you'll build and grow a small team of designers while staying hands-on in the design work yourself. You'll report to the Vice President, Product Design. The Opportunity: Defining How the World Builds on Slack You'll own design across the platform's full arc: what agents do inside Slack, how they're built, how they're managed and discovered, and how partners bring theirs to the ecosystem. As AI redefines both how software gets built and how work gets done, you'll shape what that developer experience becomes. The open questions you'll answer: The Agent Experience: What should agents do inside Slack, and how do people build them now that AI has changed what "building" means?Management: How do developers and admins run a growing ecosystem of agents with confidence?Discovery: How do people find and trust the right agents in the marketplace?Partners: How do we host partners like OpenAI, Anthropic, Cognition, and GitHub so their agents feel native to Slack?
Responsibilities
- Design Vision: Hold and continuously refine the long-range design vision for the platform, in close partnership with product and engineering leadership
- End-to-End Platform Design: Drive design across the full developer lifecycle: defining what agents do in Slack, agent creation, install and management, and marketplace discovery
- Partner Experience: Shape how partners building on Slack (OpenAI, Anthropic, Cognition, GitHub, and more) bring their agents into the ecosystem
- Hands-On Craft: Contribute directly to the design work as a player-coach, setting the craft bar for the team
- Team Leadership: Grow and develop the platform design
About the role
... combine About Salesforce and About Slack & The Role paragraphs, plus maybe "What Makes This Role Different" and "Unleash Your Potential"? The latter is more about benefits; maybe keep in About the role? But "Unleash Your Potential" is generic marketing; could be considered boilerplate? It's not EEO but still promotional. Might be okay to keep as part of About the role. However we need to avoid fluff? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Unleash Your Potential" is not those; it's marketing but substantive? It's vague. Might be considered filler? It says "When you join Salesforce, you’ll be limitless..." It's generic. Could be considered boilerplate? Not sure. Safer to omit generic marketing fluff. Keep only concrete details about role, responsibilities, qualifications, benefits, pay. Thus About the role: include the description of Salesforce, Slack, the role, the opportunity, the open questions. That's substantive. Let's extract: About Salesforce paragraph: "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 Slack & The Role: "Slack is at an inflection point. We're evolving from the world's most beloved team communication tool into an AI operating system for work, where humans and agents get things done together. The developer platform is how that future comes to life: it's the ecosystem that lets builders at every scale extend Slack with agents and apps, creating them, managing them, and distributing them through the Slack Marketplace. As Senior Director, Product Design - Ecosystem, you'll hold and continuously refine the design vision for the developer experience across Slack's platform, partnering closely with product and engineering leadership. This is a player-coach role: you'll build and grow a small team of designers while staying hands-on in the design work yourself. You'll report to the Vice President, Product Design. The Opportunity: Defining How the World Builds on Slack You'll own design across the platform's full arc: what agents do inside Slack, how they're built, how they're managed and discovered, and how partners bring theirs to the ecosystem. As AI redefines both how software gets built and how work gets done, you'll shape what that developer experience becomes. The open questions you'll answer: The Agent Experience: What should agents do inside Slack, and how do people build them now that AI has changed what "building" means?Management: How do developers and admins run a growing ecosystem of agents with confidence?Discovery: How do people find and trust the right agents in the marketplace?Partners: How do we host partners like OpenAI, Anthropic, Cognition, and GitHub so their agents feel native to Slack?" We can keep that as paragraphs. Now Responsibilities: list from "Key Responsibilities". Items: - Design Vision: Hold and continuously refine the long-range design vision for the platform, in close partnership with product and engineering leadership - End-to-End Platform Design: Drive design across the full developer lifecycle: defining what agents do in Slack, agent creation, install and management, and marketplace discovery - Partner Experience: Shape how partners building on Slack (OpenAI, Anthropic, Cognition, GitHub, and more) bring their agents into the ecosystem - Hands-On Craft: Contribute directly to the design work as a player-coach, setting the craft bar for the team - Team Leadership: Grow and develop the platform design team, owning staffing and career development for the designers on it We'll output as