Senior Director, Product Design - Ecosystem

We need to produce HTML fragment with sections: About the role? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the initial line about applying max 3 roles etc. Also remove "Accommodations" etc? That's likely boilerplate/legal; we should remove. 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..." etc. Also remove "The typical base salary range..."? That is pay info, we need to keep Pay section if present. The posting includes salary range details. So we should include a Pay section with that info. Also Benefits: there is a paragraph about benefits: "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 mention link. So we can include Benefits section with that list. Schedule: Not mentioned; no schedule info. So we should not include Schedule section. Skills: Not explicitly listed; maybe we can infer from qualifications but better not to create unless explicit. The posting includes Minimum Qualifications, Preferred Qualifications, and "What Makes This Role Different". There's no explicit Skills section. We could treat Requirements as Minimum Qualifications? Or Requirements could be combined with Minimum Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have "About Slack & The Role" which is about the role. Could be About the role section. Also there is "About Salesforce" intro but that's company description; maybe we can include in About the role? The instruction: do not repeat job title as heading; we can have About the role heading and include the descriptive paragraphs about the role and company. Responsibilities: we have "Key Responsibilities" bullet list. Requirements: could be Minimum Qualifications. Qualifications: could be Preferred Qualifications. Skills: maybe not present; we could omit. Benefits: we have benefits paragraph. Pay: we have salary range. Schedule: none. We must not create sections with filler like "commensurate with experience". So only include sections with real content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can reformat into HTML lists and paragraphs. We must not include duplicated lines. Ensure we don't repeat same sentences. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, About the role: combine the paragraphs after "About Slack & The Role" and maybe the earlier "About Salesforce" paragraph? The "About Salesforce" paragraph is generic company description; could be considered part of About the role? It's about the company, not the role. But we could still include it under About the role as context. However we must preserve all substantive information; if we omit it, we lose info. So we should include it. Perhaps we can have About the role section containing both the company description and role description. Let's copy the relevant 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." Then "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 need to keep that as prose. Now Responsibilities: list under "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 need to put each as

inside

. Now Requirements: 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 Now Qualifications: Preferred Qualifications list: - 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 Now 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." We could turn the list into
• for each benefit? The instruction: Use
  • for any list of duties/requirements/benefits. So we should list benefits as list items. Thus 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 note the link; we can include as a

    after list maybe. Now Pay: we have salary range info: "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. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We should keep that as prose under Pay heading. Now Schedule: none, so omit. Now we must ensure we don't include any boilerplate like "Accommodations", "Please note that Salesforce uses artificial intelligence (AI) tools..." etc. Also remove "Posting Statement", "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..." etc. Also remove 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." Also remove "Job Category User Experience Job Details". Also remove "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's like a call to action; maybe considered application instruction? It's not exactly instruction to apply but promotional; but it's likely considered boilerplate? The instruction says remove application instructions. This line is a call to apply; could be considered application instruction. Safer to remove. Also remove "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." That's also promotional; maybe keep? It's not substantive info about role; it's fluff. Might be considered boilerplate. Safer to remove. We need to preserve all substantive information; fluff may be considered non-substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can remove fluff that doesn't add substantive detail about role, responsibilities, qualifications, benefits, pay. The "Unleash Your Potential" paragraph is generic marketing; not substantive. So we can remove. Now we need to output HTML fragment with sections in order maybe: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must use

    for section headings. Let's craft. About the role: combine the two paragraphs (About Salesforce and About Slack & The Role) into maybe two

    elements. We need to ensure we don't lose any sentences. Let's copy exactly the text (but we can adjust punctuation? Must preserve info; we can keep same wording. 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 paragraph: "Slack is at an inflection point. We're evolving from the world's most beloved team communication tool into an AI operating system