Senior, Specialist SE

We need to output HTML fragment with sections: About the role? Actually we have Overview, Responsibilities, Required Qualifications, Preferred Qualifications, How We Work, Unleash Your Potential (maybe Benefits?), Pay (salary range), Schedule (Hybrid). Also location info. We must not repeat job title. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "To get the best candidate experience..." line. Also remove "Job Category Sales". Also remove "Job Details". Also remove "Accommodations" maybe? It's not boilerplate but maybe keep? It's about accommodations request form; might be considered application instructions? It's not exactly application instructions but could be considered part of process. The instruction says remove application instructions. Accommodations request form is part of application process; likely remove. Also remove "Posting Statement" etc. Also remove "Please note that Salesforce uses artificial intelligence..." etc. Also remove "Salesforce is an equal opportunity employer..." etc. Also remove "Know your rights..." etc. Also remove "More details about company benefits can be found at the following link:" maybe keep benefits? We have benefits described 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." That's substantive benefits. Also we have salary range info. Also schedule: Hybrid, based near a Salesforce office on the East Coast — Atlanta, DC, Boston, Austin, Chicago, or New York. Preference for Central and Eastern time zones. Also "How We Work" section includes bullet points: Builder mentality, Customer obsession, Peer teaching, Flexibility: hybrid, based near an East Coast office, with a preference for Central/Eastern time zone coverage. That's somewhat overlapping with location/schedule. We'll keep How We Work as a section with bullet list. We need to preserve all substantive information. So include Overview (maybe as About the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if they match content? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. We have Overview (like About the role). We'll map Overview to About the role. Responsibilities as Responsibilities. Required Qualifications as Requirements or Qualifications? We have Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But instruction: prefer a few substantive sections over many thin ones. Could have Requirements (including required and preferred) but we need to preserve both. Could have Required Qualifications and Preferred Qualifications as separate sections under Qualifications? Might be okay to have two sections: Required Qualifications and Preferred Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. So we can use Required Qualifications and Preferred Qualifications as headings. We also have "How We Work" which could be Skills? Not exactly. Could be "How We Work" as a section heading (maybe not in list but allowed). The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. How We Work could be considered Skills? Not really. Could be omitted? But it's substantive. Could be placed under Skills? Not ideal. Maybe we can create a section "How We Work" as heading; it's not prohibited. The instruction says use

  for section headings (e.g. ...). It doesn't say only those. So we can use How We Work. Similarly "Unleash Your Potential" could be Benefits? Actually it's about benefits and resources. Could be Benefits section. We'll map Unleash Your Potential to Benefits. Pay: we have salary range. Schedule: we have Hybrid info. Location: we could include in Schedule or maybe a separate section? Not required but we can include location in Schedule section. We must not include filler like "commensurate with experience". Not present. Now we need to strip boilerplate: remove lines like "To get the best candidate experience...", "Job Category Sales", "Job Details", "Accommodations", "Please note that Salesforce uses artificial intelligence...", "Please see our Candidate Privacy Statement...", "Posting Statement", "Salesforce is an equal opportunity employer...", all that EEO stuff, also "Know your rights...", "Recruiting, hiring, and promotion decisions...", "In the United States, compensation offered will be determined..." maybe keep salary range but remove explanatory text? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range specifics but can we remove explanatory sentences? Those are substantive? They explain that range is base salary only, etc. That's substantive. We should keep them. However they might be considered boilerplate? Not exactly. We'll keep. Similarly benefits description: keep. Now we need to format. Structure:

  About the role

  Overview text (the paragraph starting "Do you want to be part of an outstanding team...") maybe also include the earlier marketing fluff about Salesforce being #1 AI CRM etc. That's part of About the role? The "About Salesforce" paragraph is generic marketing; could be considered part of About the role. We'll include it. Then

  Responsibilities

  • each responsibility line. We need to extract responsibilities from the block after "Responsibilities". The block is a long sentence with many items separated by line breaks? Actually it's a paragraph with many phrases separated by line breaks? Let's parse: "Play a pivotal role in aligning innovative solutions to technology challenges within complex CBS accounts, partnering with clients and collaborating with internal team members to drive consensus on multi-product technology solutions across Salesforce's product lines, with a primary focus on the Analytics portfolioHandle business development, operations strategy, and product demonstrations as a trusted advisor for innovative solutionsBusiness Problem Solving: Define ambiguous business problems through research and assessment, drive innovative ideas, and recommend practical next stepsInnovation Management: Focus client decision-making by evaluating solutions and driving stakeholder consensus; help build decision frameworks that deliver ongoing valueConnect Experiences: Demonstrate connected, data-driven experiences through software demos and rapid prototyping with Salesforce and Tableau, bringing genuine energy and enthusiasm to every customer presentationBuild customized solutions and demonstrations for multiple personas, showing how platforms accelerate strategy and deliver valueUnderstand and advise on customer data and analytics architecture as it relates to Salesforce and Tableau solutions, including modern data warehouse/lakehouse environments (e.g., Snowflake, Databricks)Participate in all appropriate product, sales, and procedural training and certifications to maintain the knowledge needed to be effective in the role" We need to split into list items. Likely each sentence or clause separated by line breaks in original but got merged. We'll split by capital letters after a period? We'll approximate: - Play a pivotal role in aligning innovative solutions to technology challenges within complex CBS accounts, partnering with clients and collaborating with internal team members to drive consensus on multi-product technology solutions across Salesforce's product lines, with a primary focus on the Analytics portfolio. - Handle business development, operations strategy, and product demonstrations as a trusted advisor for innovative solutions. - Business Problem Solving: Define ambiguous business problems through research and assessment, drive innovative ideas, and recommend practical next steps. - Innovation Management: Focus client decision-making by evaluating solutions and driving stakeholder consensus; help build decision frameworks that deliver ongoing value. - Connect Experiences: Demonstrate connected, data-driven experiences through software demos and rapid prototyping with Salesforce and Tableau, bringing genuine energy and enthusiasm to every customer presentation. - Build customized solutions and demonstrations for multiple personas, showing how platforms accelerate strategy and deliver value. - Understand and advise on customer data and analytics architecture as it relates to Salesforce and Tableau solutions, including modern data warehouse/lakehouse environments (e.g., Snowflake, Databricks). - Participate in all appropriate product, sales, and procedural training and certifications to maintain the knowledge needed to be effective in the role. That seems fine. Next

    Required Qualifications

    • each bullet. List: - B.S. in Computer Science, Software Engineering, MIS, Data Science, or equivalent relevant experience (experience evaluated on core competencies — extracurricular leadership, military experience, volunteer roles, work experience, etc.) - Approximately 3–5 years of relevant SE, consulting, or analytics/BI experience - Hands-on experience across multiple Tableau products (not just Tableau Desktop), or equivalent breadth with a comparable BI platform (e.g., Power BI); familiarity with data visualization, dash boarding, and self-service analytics best practices - Experience with modern cloud data platforms such as Snowflake or Databricks - Solid oral, written, presentation, collaboration, and interpersonal communication skills — and the charisma and passion to bring genuine excitement to customer-facing presentations - Ability to work as part of a team to solve technical problems in varied organizational and political environments - Strategic and creative problem solver comfortable engaging technical, business, and executive audiences - Willingness and ability to travel occasionally for customer engagements and team events Next

      Preferred Qualifications

      • each bullet. List: - Previous experience as a solution/sales engineer/consultant for a CRM, analytics, or BI company, or in a similar customer-facing technical role - Experience building with AI tools (Claude, Cursor, ChatGPT, etc.) as these are an expanding portion of our demo toolkit - Salesforce Certifications (including Tableau Certifications) - Familiarity with AI/ML fundamentals and how analytics platforms surface AI-driven insights (e.g., Einstein, agentic AI, predictive analytics) - Experience with SQL and data modelling across structured and semi-structured data - Basic programming/scripting experience (Python, HTML, JavaScript, or similar) - Experience with design thinking, persona-based discovery, or workshop facilitation techniques Next

        How We Work

        • each bullet. List: - Builder mentality: we show up with working demos and real solutions — not just slides - Customer obsession: we go deep on customer problems before prescribing solutions - Peer teaching: we share what we learn — internally, with customers, and at industry events - Flexibility: hybrid, based near an East Coast office, with a preference for Central/Eastern time zone coverage Note: Flexibility duplicates location/schedule; we may also have separate Schedule section. But we can keep it here and also maybe Schedule section just repeats? To avoid duplication, we could put location/schedule in Schedule section and not repeat in How We Work. But How We Work includes Flexibility bullet; we could keep it as part of How We Work. Then Schedule section maybe not needed. However instruction: include a section ONLY when posting has real, specific content for it. We have schedule info (Hybrid, based near a Salesforce office on the East Coast — Atlanta, DC, Boston, Austin, Chicago, or New York. Preference for Central and Eastern time zones.) That's specific. So we should have a Schedule section with that info. The How We Work Flexibility bullet overlaps; we could keep both but risk duplication. Better to keep How We Work without the Flexibility bullet, and put schedule info in Schedule section. Let's adjust How We Work bullets to exclude Flexibility. Thus How We Work: - Builder mentality: we show up with working demos and real solutions — not just slides - Customer obsession: we go deep on customer problems before prescribing solutions - Peer teaching: we share what we learn — internally, with