Senior Director, Product Design - Ecosystem

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Job title: Senior Director, Product Design - Ecosystem (but we don't repeat as heading). We need to extract: - About the role: likely the "About Slack & The Role" paragraph and maybe "The Opportunity: Defining How the World Builds on Slack". Also "About Salesforce" maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: About Salesforce (intro) maybe not needed as "About the role"? Could be considered about the role? The posting includes "About Salesforce" and "About Slack & The Role". The "About the role" likely includes description of role and opportunity. We have responsibilities listed under "Key Responsibilities" with bullet points (Design Vision, End-to-End Platform Design, Partner Experience, Hands-On Craft, Team Leadership). Those are responsibilities. Minimum Qualifications and Preferred Qualifications: these could go under Requirements or Qualifications. The instruction: Use headings Requirements, Qualifications, Skills. We need to decide where to put qualifications. Probably "Minimum Qualifications" and "Preferred Qualifications" go under Requirements or Qualifications. Since they are qualifications, we can put them under

Qualifications

with subpoints? But we need to use

• for any list of duties/requirements/benefits. So we can list each qualification as li. Skills: maybe we can extract from qualifications: "Experience managing and growing design teams", "Hands-on experience with AI and vibe-coding tools", etc. But we could also put them under Skills if we want. However we should avoid thin sections. Probably combine qualifications and skills into one Qualifications section. Benefits: The posting mentions benefits: "Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact..." 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 we can include Benefits section with ul. 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. No schedule info. So we should not include Schedule heading. Also we might include "About the role" section with prose about role and opportunity. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the "To get the best candidate experience..." line at start. Also remove "Accommodations", "Posting Statement", etc. We need to preserve all substantive information. Let's extract substantive content: 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 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?" Key Responsibilities bullet list: - 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 Minimum Qualifications: - 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 What Makes This Role Different: maybe could be included under About the role or separate? It's substantive but not a standard heading. Could be included under About the role as additional prose. 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." This is more marketing; but we might keep as part of About the role? However we already have benefits section. Accommodations etc removed. Benefits list: "time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Pay: salary ranges. We need to output HTML fragment only. Structure:

  About the role

  ... combined prose from About Salesforce and About Slack & The Role and maybe What Makes This Role Different and Unleash Your Potential? But we should avoid too much fluff. However we need to preserve all substantive information; we can include them as prose. We'll combine: Paragraph 1: About Salesforce description. Paragraph 2: About Slack & The Role description. Paragraph 3: The Opportunity: Defining How the World Builds on Slack (including open questions). Paragraph 4: What Makes This Role Different. Paragraph 5: Unleash Your Potential (maybe optional but it's substantive about benefits and impact; but we have Benefits section separate; still we can keep as prose about impact.) But we must not repeat info that will be in Benefits section. The Unleash Your Potential mentions benefits and resources, AI agents accelerate impact. That's somewhat overlapping with Benefits section but still substantive. We could keep it as part of About the role. Better to keep About the role focusing on role description, not benefits. Benefits separate. Thus we can put About the role as description of role and opportunity, maybe include What Makes This Role Different. We'll keep Unleash Your Potential as part of Benefits? Not exactly. It's more about potential; we could omit to avoid duplication. But instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that text somewhere. Could put it under About the role as a paragraph. Ok. Now Responsibilities section:

  Responsibilities

  • ... each.
  Qualifications section: combine Minimum and Preferred Qualifications. Could separate into two subheadings? But only allowed headings are the listed ones; we could still have

  Qualifications

  and then within that we could have

  Minimum qualifications:

  ... and

  Preferred qualifications:

  ... That's acceptable. Skills section: maybe we could extract skills from qualifications: "Experience managing and growing design teams", "Hands-on experience with AI and vibe-coding tools", "solid understanding of developer workflows", "track record of partnering with product and engineering leadership", "Experience designing marketplace or agent-discovery experiences", etc. But we already have them in Qualifications; we could omit Skills to avoid thin section. The instruction: Prefer a few substantive sections over many thin ones. So we can skip Skills if not needed. Benefits section:

  Benefits

  • time off programs
  • medical
  • dental
  • vision
  • mental health support
  • paid parental leave
  • life and disability insurance
  • 401(k)
  • employee stock purchasing program
  Pay section:

  Pay

  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 not include Schedule. Now ensure we don't include any boilerplate like "To get the best candidate experience..." etc. Let's craft the HTML. We need to output only HTML fragment, no markdown fences. Let's write:

  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.