Product Design Lead

We need to output HTML fragment with sections: headings

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. 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 not needed as heading? Could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings for those sections if content exists. We have "About The Role" section: includes description of AI Labs, role description. That's "About the role". We'll put that under

About the role

with

content. Then "What You'll Do" is responsibilities. So

Responsibilities

with

• items. Then "What We're Looking For" includes requirements/qualifications/skills. We need to split maybe into Requirements, Qualifications, Skills. The posting lists: 7+ years product design experience, track record leading design programs, experience in fast-moving environments, ability to align cross-functional leaders, hands-on prototyping in code, experience designing AI/ML-powered products, comprehensive portfolio, experience mentoring designers, experience partnering with engineering, related technical degree required. Then "Nice To Have" items: prompt design, conversational UX, agent-based product design, integrating acquired products, background in human-AI interaction research, experience contributing to design system. We could put Requirements as the mandatory items, Qualifications maybe overlapping, Skills maybe the nice-to-have? But we need to follow instruction: use headings only when posting has real specific content. We can create sections: Requirements, Qualifications, Skills. But we need to decide what goes where. Could treat Requirements as the mandatory list, Qualifications as education/degree, Skills as nice-to-have. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements" covering both mandatory and nice-to-have? But they ask to use headings like Requirements, Qualifications, Skills. We could include all three if we have content. Let's extract: Mandatory (What We're Looking For): - 7+ years of product design (or equivalent) experience, including shipping complex, high-craft products at scale. - A track record of leading design programs across multiple teams or product areas with autonomy and minimal direction. - Experience working in fast-moving environments, whether at a start-up, in an incubator, or on a zero-to-one team inside a larger enterprise. - Demonstrated ability to align cross-functional and senior leaders around priorities and tradeoffs. - Hands-on experience prototyping in code, with examples of using prototypes to accelerate decisions and iteration. - Experience designing AI/ML-powered or data-intensive products, and a strong understanding of generative AI UX challenges (uncertainty, latency, hallucinations, feedback loops). - A comprehensive portfolio showcasing systems thinking, interaction design, and high visual craft. - Experience mentoring designers and elevating team quality through constructive critique (formal people management is not required). - Experience partnering closely with engineering on technical implementation. - A related technical degree required. Nice To Have: - Experience with prompt design, conversational UX, or agent-based product design. - Experience integrating acquired or independently built products into a shared platform and unified design language. - Background in human-AI interaction research or responsible AI and ethics-in-design practices. - Experience contributing to or building a design system from scratch. We could map: Requirements: the mandatory list. Qualifications: maybe the technical degree requirement? But that's already in mandatory. Could treat Qualifications as education/degree: "A related technical degree required." But that's already part of mandatory. Could still separate but might be thin. Better to combine into Requirements and maybe Skills for nice-to-have. But instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have two sections: Responsibilities and Requirements (including qualifications and skills). However they gave examples of headings but not mandatory to use all. So we can omit sections lacking content. Thus we will have:

  About the role

  ... (content from About The Role)

  Responsibilities

  • ... each bullet from What You'll Do

  Requirements

  • ... mandatory items

  Skills

  • ... nice-to-have items
  We could also include Benefits if present: The posting mentions benefits 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 mentions salary range. So we have Benefits and Pay sections. Thus we should include:

  Benefits

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

  Pay

  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.

  Schedule: not mentioned, so omit. We must not include boilerplate like accommodations, EEO, etc. Also need to include the initial intro about Salesforce? Could be part of About the role? The "About Salesforce" paragraph is generic company description. Might be considered part of About the role? But we already have About the role section from "About The Role". The initial "About Salesforce" could be omitted as it's not specific to role. However we could include it under About the role as additional context. But 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." The About Salesforce intro is not metadata; it's company description. Could be included in About the role section as a paragraph. But we already have About The Role content; we could prepend that intro. Let's craft About the role paragraph: combine the intro about Salesforce and the description of AI Labs team. Thus:

  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. AI Labs is a new Salesforce team that builds AI-native products with the agility of a start-up, backed by the full scale and trust of the Salesforce platform. Our team brings together products including Agentforce Operations (powered by Regrello). We're hiring a Product Design Lead to shape the design vision and craft for this next generation of AI-powered products. You will partner with senior leadership and cross-functional leaders in product management, research, and engineering to turn new AI capabilities into experiences that are clear, trustworthy, ready to ship, and deliver real outcomes for customers. You will help shape direction at the product level. This is a self-directed role in a fast-moving, zero-to-one environment. You will often start with an ambiguous problem, no defined path, and competing priorities. We are looking for someone who can frame the problem, align partners on what matters most, and move quickly from idea to working prototype to a shipped experience.

  That seems good. Now Responsibilities: list each bullet from "What You'll Do". Let's extract: - Lead multiple large-scale, cross-functional design programs across AI Labs product areas, from early concept through launch and iteration. - Frame ambiguous problem spaces, define the right problem to solve, and drive alignment with senior and cross-functional leaders on top priorities and tradeoffs. - Influence product-level decisions, direction, and roadmaps. - Prototype in code (e.g., HTML/CSS/JS, React, or AI-assisted coding tools) to test ideas, demonstrate interaction models, and iterate quickly with users and partners. - Define patterns and interaction models for novel AI and agentic experiences, including generative UI, conversational interfaces, and human-in-the-loop workflows, with trust, transparency, and explainability built in. - Help build a coherent experience across AI Labs products and connect it to the broader Salesforce and Agentforce platform. - Create system-level artifacts, such as experience maps and relationship models, that show how users, agents, data, and products connect across journeys. - Use research, usability testing, data, and experimentation to ground design decisions and uncover strategic opportunities. - Mentor fellow designers, lead design critiques, and contribute to design systems and guidelines for AI experiences. - Present design rationale and strategy clearly to cross-functional leaders and senior stakeholders. Now Requirements (mandatory): - 7+ years of product design (or equivalent) experience, including shipping complex, high-craft products at scale. - A track record of leading design programs across multiple teams or product areas with autonomy and minimal direction. - Experience working in fast-moving environments, whether at a start-up, in an incubator, or on a zero-to-one team inside a larger enterprise. - Demonstrated ability to align cross-functional and senior leaders around priorities and tradeoffs. - Hands-on experience prototyping in code, with examples of using prototypes to accelerate decisions and iteration. - Experience designing AI/ML-powered or data-intensive products, and a strong understanding of generative AI UX challenges (uncertainty, latency, hallucinations, feedback loops). - A comprehensive portfolio showcasing systems thinking, interaction design, and high visual craft. - Experience mentoring designers and elevating team quality through constructive critique (formal people management is not required). - Experience partnering closely with engineering on technical implementation. - A related technical degree required. Now Skills (nice-to-have): - Experience with prompt design, conversational UX, or agent-based product design. - Experience integrating acquired or independently built products into a shared platform and unified design language. - Background in human-AI interaction research or responsible AI and ethics-in-design practices. - Experience contributing to or building a design system from scratch. Now Benefits: - 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 $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. We should not include "The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." That's extra detail but still substantive. Could include as part of Pay paragraph. Thus Pay paragraph: "The typical base salary range for this position is $172,500 - $26