Experience Design Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use headings only when posting has real specific content.
We need to decide which sections map to those headings. The posting includes: About Salesforce (company overview), About Us (team description), The Experience (what they're looking for), What You'll Actually Be Doing (responsibilities), You're Our Person If… (requirements/qualifications), Even Better If… (preferred qualifications), Unleash Your Potential (benefits/culture). Also there is salary range info (Pay). So we can create sections: About the company (maybe About Salesforce), About the team (About Us), The Experience (maybe Qualifications?), Responsibilities (What You'll Actually Be Doing), Requirements (You're Our Person If…), Preferred Qualifications (Even Better If…), Benefits (Unleash Your Potential + benefits mention), Pay (salary range). Also maybe Schedule not present.
We must not create sections with filler text. Ensure each heading has substantive content.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, benefits we should list items.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details as given, but we can format as list items.
We must not repeat the job title as heading. No job title given explicitly; but we can ignore.
We must not include markdown fences.
We need to output only HTML fragment.
Let's extract content.
First, About Salesforce paragraph:
"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."
We can keep as
.
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 that as per instruction to remove application instructions. So drop "Please include a link to your digital portfolio (if you have one) or attach 2-3 work samples with your application."
What You'll Actually Be Doing: list of duties.
Let's extract bullet-like sentences:
- 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'll make
- for each.
You're Our Person If…: list of requirements.
Extract:
- 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.
Even Better If…: list of preferred qualifications.
Extract:
- 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.
Unleash Your Potential: paragraph about benefits and resources.
"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."
The last sentence about Apply today is application instruction; we should remove that. So drop "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world."
Also earlier there is a benefits list later in posting statement: "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 should include benefits section with that list. Also there is salary range info: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $143,400 - $216,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $172,200 - $236,700 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
We need Pay section with that info.
We must not create sections with filler text like "commensurate with experience". Not present.
We need to decide headings: About Salesforce (maybe About the company), About Us (maybe About the team), The Experience (maybe Qualifications?), Responsibilities (What You'll Actually Be Doing), Requirements (You're Our Person If…), Preferred Qualifications (Even Better If…), Benefits (benefits list), Pay (salary range). Could also combine About Salesforce and About Us into About the role? But instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: could combine About Salesforce and About Us and The Experience? But better to have separate sections if content distinct. However we should not create headings that are not in the list unless we have real content. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings exactly. So we need to decide which content goes under which heading.
We could put:
About the role
containing About Salesforce, About Us, The Experience (maybe summarizing role). But we must not invent or summarize away detail; we can keep the paragraphs as is under that heading.
Responsibilities
for What You'll Actually Be Doing.
Requirements
for You're Our Person If…
Qualifications
for Even Better If… (or maybe Skills). But Qualifications could be for preferred qualifications. Skills could be for specific skills like Figma, etc. But we have both.
We could do:
- About the role: About Salesforce + About Us + The Experience
- Responsibilities: What You'll Actually Be Doing
- Requirements: You're Our Person If…
- Qualifications: Even Better If…
- Benefits: benefits list + Unleash Your Potential (maybe)
- Pay: salary range
We should not create Skills section unless we have specific skills list; we could embed skills in Qualifications.
We must not create Schedule section.
Now we need to format lists.
Let's craft HTML.
We'll start with About the role
then containing About Salesforce paragraph, then
About Us paragraph, then
The Experience paragraph (without portfolio instruction). Ensure we keep all sentences.
Then
Responsibilities
then - each
. 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 that as per instruction to remove application instructions. So drop "Please include a link to your digital portfolio (if you have one) or attach 2-3 work samples with your application." What You'll Actually Be Doing: list of duties. Let's extract bullet-like sentences: - 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'll make
- for each.
You're Our Person If…: list of requirements.
Extract:
- 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.
Even Better If…: list of preferred qualifications.
Extract:
- 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.
Unleash Your Potential: paragraph about benefits and resources.
"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."
The last sentence about Apply today is application instruction; we should remove that. So drop "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world."
Also earlier there is a benefits list later in posting statement: "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 should include benefits section with that list. Also there is salary range info: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $143,400 - $216,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $172,200 - $236,700 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
We need Pay section with that info.
We must not create sections with filler text like "commensurate with experience". Not present.
We need to decide headings: About Salesforce (maybe About the company), About Us (maybe About the team), The Experience (maybe Qualifications?), Responsibilities (What You'll Actually Be Doing), Requirements (You're Our Person If…), Preferred Qualifications (Even Better If…), Benefits (benefits list), Pay (salary range). Could also combine About Salesforce and About Us into About the role? But instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: could combine About Salesforce and About Us and The Experience? But better to have separate sections if content distinct. However we should not create headings that are not in the list unless we have real content. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings exactly. So we need to decide which content goes under which heading.
We could put:
About the role
containing About Salesforce, About Us, The Experience (maybe summarizing role). But we must not invent or summarize away detail; we can keep the paragraphs as is under that heading.Responsibilities
for What You'll Actually Be Doing.Requirements
for You're Our Person If…Qualifications
for Even Better If… (or maybe Skills). But Qualifications could be for preferred qualifications. Skills could be for specific skills like Figma, etc. But we have both. We could do: - About the role: About Salesforce + About Us + The Experience - Responsibilities: What You'll Actually Be Doing - Requirements: You're Our Person If… - Qualifications: Even Better If… - Benefits: benefits list + Unleash Your Potential (maybe) - Pay: salary range We should not create Skills section unless we have specific skills list; we could embed skills in Qualifications. We must not create Schedule section. Now we need to format lists. Let's craft HTML. We'll start withAbout the role
thencontaining About Salesforce paragraph, then
About Us paragraph, then
The Experience paragraph (without portfolio instruction). Ensure we keep all sentences. Then
Responsibilities
then- each