Senior Experience Architect

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. No Job ID etc. Remove boilerplate like application instructions, EEO, etc. Keep substantive info. We need to parse the posting. Key sections: - About Salesforce (maybe "About the role"? Actually there is "About Salesforce" paragraph describing company. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have: - Overview Of The Role (description). Could go under "About the role". Should include description of Senior Experience Architects. - Responsibilities: list of bullet points. - Minimum Requirements: list of bullet points (requirements). Could be under "Requirements". Also "Preferred Qualifications": could be under "Qualifications" or "Skills"? The instruction includes Qualifications and Skills separate. We could put Preferred Qualifications under "Qualifications". Minimum Requirements maybe under "Requirements". Skills maybe we could extract from requirements? But we can also combine. - Benefits: there is a paragraph about benefits: "Unleash Your Potential When you join Salesforce, you’ll be limitless..." plus later "Salesforce offers a variety of benefits..." and link. Also mention typical base salary range: that is Pay. So we have Pay: "$172,500 - $260,100 annually". Also mention benefits details. - Schedule: not mentioned explicitly. There's "A willingness to travel when required (up to 50% of the time)". That's not schedule. No schedule info. So we should not create Schedule section. - Skills: maybe we can extract from requirements: "Strong proficiency with AI tools", "Advanced skills in human-centered design", etc. Could be a Skills section. But we have Requirements and Qualifications already. The instruction says prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. But we have separate headings allowed. Might be better to have Requirements (minimum), Qualifications (preferred), Benefits, Pay. Possibly also About the role and Responsibilities. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info, not invent or summarize away detail. Must keep details like bullet points. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to strip boilerplate: the initial "To get the best candidate experience..." line, also "Applications will be accepted until 10/16/2026." maybe keep? It's substantive? It's a date. Might be considered metadata but not job ID. Could be kept as a short paragraph maybe under About the role? But instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. The date is minor metadata; we could fold into a short p. But we might drop it as not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The date is substantive? It's about application deadline. Might be considered relevant. However they said to remove application instructions. The date is not exactly instruction but could be considered part of posting. I'd keep it as a short p under About the role maybe. Also "Department Overview" paragraph could be part of About the role. We need to avoid repeating job title. Let's extract content. 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." Department Overview: "Salesforce Professional Services focuses on delivering strategic engagements that define transformational opportunities and articulate clear plans for execution of change programs. We rely on our team's expertise and specialisms to engage with executive-level customers to agree on specific business goals and actions to ignite the full value of Salesforce. Our approach considers people, process, and technology — and a successful engagement includes recommendations to the business for change to support deeper, more relevant use of the Salesforce platform." Overview Of The Role: description of Senior Experience Architects. We can combine About Salesforce + Department Overview + Overview Of The Role into About the role section. Responsibilities: list bullet points (starting with "Lead and manage design teams..." etc). Need to keep each as

• . Minimum Requirements: list bullet points (starting with "10+ years of experience..." etc). We'll put under Requirements. Preferred Qualifications: list bullet points (starting with "Experience across various industries..." etc). We'll put under Qualifications. Benefits: paragraph about "Unleash Your Potential..." plus later benefits list. We'll combine into Benefits section with

  prose and maybe a

  for list of benefits? The benefits list includes: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program. Also link. We'll make a
  for those. Pay: typical base salary range: "$172,500 - $260,100 annually". Also note base salary only, etc. We'll put in

  . Schedule: none. We must not include boilerplate like Accommodations, AI tools statement, Candidate Privacy Statement, Posting Statement, EEO, etc. Remove those. Also remove "Apply today to not only shape the future..." maybe that's promotional but could be considered part of Benefits? It's more like call to action. Might be considered boilerplate? It's not a legal statement but it's a marketing line. Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Apply today..." is not exactly application instruction but could be considered promotional. I'd keep it maybe as part of Benefits or a separate call to action? Safer to keep it as part of Benefits? It's not a benefit. Might be considered fluff. I'd drop it to keep only substantive. Also "Unleash Your Potential When you join Salesforce..." is part of benefits description, keep. Now produce HTML. Structure:

  About the role

  ... (combined paragraphs)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  ... (Unleash Your Potential paragraph)

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

  More details about company benefits can be found at the following link: https://www.salesforcebenefits.com

  Pay

  The typical base salary range for this position is $172,500 - $260,100 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.

  We need to ensure we didn't include any heading with empty content. Check for duplication: we have not repeated job title. Check for any leftover boilerplate: we removed Accommodations, AI tools statement, Candidate Privacy Statement, Posting Statement, EEO, etc. Check for "Applications will be accepted until 10/16/2026." We omitted; maybe we should include as minor metadata under About the role? The instruction says fold minor metadata into a short

  or drop it. It's minor metadata; we could drop it. I'd drop to keep concise. Now verify we kept all substantive info: About Salesforce, Department Overview, Overview Of The Role, Responsibilities list, Minimum Requirements list, Preferred Qualifications list, Benefits description and list, Pay range. Yes. Now produce HTML fragment only. Let's craft the About the role paragraph: combine three paragraphs into maybe two

  elements? Could be one

  with multiple sentences. But we can split for readability. We'll do:

  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.

  Salesforce Professional Services focuses on delivering strategic engagements that define transformational opportunities and articulate clear plans for execution of change programs. We rely on our team's expertise and specialisms to engage with executive-level customers to agree on specific business goals and actions to ignite the full value of Salesforce. Our approach considers people, process, and technology — and a successful engagement includes recommendations to the business for change to support deeper, more relevant use of the Salesforce platform.

  Our Senior Experience Architects serve as design team captains, creative project directors, strategic advisors, and problem solvers. They ensure teams are aligned and serve as a guide toward impactful design outcomes in engagements. They provide leadership throughout all stages of an engagement, establish and maintain the highest quality of execution across all design work, provide a strong point of view, build strong partnerships, and foster collaboration with the customer. Senior Experience Architects work to understand the business and end-user's needs in order to translate those needs into intuitive, transformational experiences. These experiences are primarily driven by a focus on research, interaction design, and technical feasibility. They excel at working cross-functionally, effectively partnering with other competencies to demonstrate a valuable vision. We believe the best Senior Experience Architects are those who obsess over the creation of customer and business value. They have a customer-centric and collaborative mentality, a willingness to commit to the customer, and the drive to break down barriers to ensure customer success. Are you passionate about Customer Success and want to work at the forefront of Digital Innovation at one of the fastest-growing CRM companies? This is the job for you!

  That preserves all. Now Responsibilities list: need to copy each bullet exactly as in posting. Responsibilities bullet list from posting: - Lead and manage design teams to drive key design activities and deliverables throughout project lifecycles - Develop project scope, timelines, and strategic roadmaps that prioritize investments and support business objectives - Build and maintain close relationships with customers, key stakeholders, and cross-functional collaborators - Lead customer discovery activities, stakeholder interviews, workshops, and collaborative design sessions - Apply design-thinking and