Experience Design Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Salesforce, About Us, The Experience, What You'll Actually Be Doing, You're Our Person If…, Even Better If…, Unleash Your Potential, Accommodations, Posting Statement (EEO), Benefits, Salary range. We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for those headings. Probably we should map content to those headings where appropriate. However we must not repeat job title as heading. We need to include sections only when posting has real specific content. We must not include placeholder text. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Accommodations" maybe? It's not boilerplate? It's a request for accommodation; could be considered part of application instructions? Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Accommodations request form is part of application instructions? Possibly yes. Safer to remove Accommodations section. Also remove "Posting Statement" EEO boilerplate. Remove benefits link? Benefits section we can keep if there is substantive content: they list benefits and link. We should keep benefits description but maybe not the link? The link is part of benefits info; we can keep as maybe but it's okay. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep benefits description and the link. Pay: they give salary range. So we need a Pay section with that info. Schedule: not mentioned, so we should not include Schedule section. Responsibilities: we have "What You'll Actually Be Doing" which is responsibilities. So we can make a Responsibilities section with that content. Requirements/Qualifications/Skills: we have "You're Our Person If…" (requirements) and "Even Better If…" (preferred qualifications). Also "About Us" maybe qualifies as About the role? Actually "About Salesforce" is company overview; could be About the role? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing the role description). But we have "About Us" and "The Experience". Could combine into About the role? However we must not invent or summarize away detail. We could create sections: About the role (maybe using the "About Us" and "The Experience" combined). But we need to preserve all substantive information; we can't omit details. If we combine, we need to include all details from those sections. That's okay as long as we don't lose info. We could also have multiple sections: About Salesforce, About Us, The Experience. But the instruction only gave examples; not strict that we must only use those headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where applicable. So we should map content to those headings. Thus: - About the role: could include "About Salesforce", "About Us", "The Experience". But that might be too much mixing. However we can still include all details under About the role heading. - Responsibilities: "What You'll Actually Be Doing" - Requirements: "You're Our Person If…" (mandatory) - Qualifications: maybe "Even Better If…" (preferred) could be Qualifications or Skills. Could treat as Qualifications. - Skills: maybe we could extract skills from those sections, but we already have content; we could create a Skills section summarizing skills like UX writing, content design, Figma, etc. But that would be summarizing; we risk losing detail. Better to keep the original sections as Requirements and Qualifications. - Benefits: benefits description. - Pay: salary range. We must not include sections with placeholder text. All sections have real content. We must not include duplicated lines. Ensure we don't repeat. We must output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...combined text...

Responsibilities

• ... each bullet from What You'll Actually Be Doing...

Requirements

• ... each bullet from You're Our Person If…

Qualifications

• ... each bullet from Even Better If…

Benefits

... benefits description ... link

Pay

... salary range ...

We need to ensure we preserve all substantive information from those sections. Let's extract the text. 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 Us: "Our team creates AI and automation tools that make Customer Success Managers (CSMs) more effective at their jobs. By streamlining repetitive tasks and enhancing the quality of their work—right inside Slack—we free up CSMs to spend more time on customers." The Experience: "We're looking for someone who's equally at home in a product sprint and a blank slide deck — and who can tell the difference between "good enough" and actually great. You'll be the design and content standard-bearer for our team: the person who makes our work look and feel like it was made with intention, whether that's a prototype, a field-facing deck, or a Slack message that lands. The ideal background here is UX writing or content design — someone who's sat on a product team, worked in sprint cycles, and knows how to translate complex product thinking into clear, useful language. If you've also got an eye for visual design and a knack for polished storytelling, we want to talk. This isn't a strategy role — it's a craft role. You'll get your hands dirty, ship things fast, and hold a high bar for the quality of everything we put out. Please include a link to your digital portfolio (if you have one) or attach 2-3 work samples with your application." Note: The last sentence about portfolio is application instruction; we should remove application instructions. So we need to remove that sentence from The Experience. Also we should remove any other application instructions like "Please include a link to your digital portfolio...". Also later in "Even Better If…" there is no application instruction. Also "Accommodations" we decided to remove. Also "Posting Statement" EEO we remove. Thus for About the role we combine About Salesforce, About Us, The Experience (minus the portfolio instruction). Let's craft a paragraph that includes all that info. We must be careful not to lose any substantive info. Let's copy the paragraphs exactly, minus the removed sentence. About Salesforce paragraph as is. About Us paragraph as is. The Experience paragraph: we need to remove "Please include a link to your digital portfolio (if you have one) or attach 2-3 work samples with your application." So we keep everything before that. The Experience paragraph before that sentence: "We're looking for someone who's equally at home in a product sprint and a blank slide deck — and who can tell the difference between "good enough" and actually great. You'll be the design and content standard-bearer for our team: the person who makes our work look and feel like it was made with intention, whether that's a prototype, a field-facing deck, or a Slack message that lands. The ideal background here is UX writing or content design — someone who's sat on a product team, worked in sprint cycles, and knows how to translate complex product thinking into clear, useful language. If you've also got an eye for visual design and a knack for polished storytelling, we want to talk. This isn't a strategy role — it's a craft role. You'll get your hands dirty, ship things fast, and hold a high bar for the quality of everything we put out." We'll combine these three paragraphs into About the role section, maybe separated by spaces. Now Responsibilities: "What You'll Actually Be Doing" bullet list: - Partner with product leads on feature design and prototyping — contributing UX writing, IA, and content direction from early sprint stages through delivery - Translate product thinking into clear, compelling narratives for different audiences — field, ops, and leadership - Own the voice, tone, and content standards for our team's output: Skills copy, product documentation, and field-facing materials - Build and maintain lightweight design and content guidelines the team can actually use - Design and produce polished decks and communications that represent the team well at all levels — from field CSMs to exec stakeholders - Regularly audit key assets to identify and recommend updates so that the experiences being designed align with how they’re documented or delivered. We need to preserve the dash and em dashes etc. We'll keep as is. Now Requirements: "You're Our Person If…" bullet list: - You have a strong, developed POV on what "good" looks like — in copy, in design, in a slide - You're comfortable switching between sprint mode (fast, iterative, scrappy) and polish mode (deliberate, high-craft, detail-oriented) - You work well with ambiguity: you can take a half-formed brief and produce something shareable without needing all the answers first - You think in systems but can meet a deadline: you can redo the deck, then deal with updating the template later when there’s a tight turnaround. - You're a clear, confident communicator who can explain design decisions without making it feel like a lecture - You thrive in matrixed environments where the work is real but the structure isn't always neat. Now Qualifications (Even Better If…): - You have hands-on UX writing or content design experience on a product team, ideally in an agile/sprint environment - You've worked closely with engineers and product managers — you understand their constraints and know how to add value without slowing things down - You've built or contributed to a content style guide, design system, or similar standards artifact - You're comfortable in Figma (or a comparable tool) — not necessarily a pixel-perfect designer, but fluent enough to prototype and collaborate - You've raised the quality bar on team comms, decks, or branding — and have something to show for it - Experience making AI tools or technical products accessible and approachable for non-technical audiences is a major plus - You're comfortable scripting and producing short demo or explainer videos — not full production, but enough to turn a feature into a clear, watchable walkthrough. 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