Solution Consultant/Senior Solution Consultant

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About Salesforce (intro) maybe "About the role"? Actually "About Salesforce" is company description. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We have: - Role Description (some paragraphs). Could be "About the role". We'll put that under

About the role

with paragraphs. - Your Impact Responsibilities: Actually there is a heading "Your Impact Responsibilities". Then bullet list of responsibilities. We'll put under

Responsibilities

with

• items. - Minimum Requirements: list of bullet-like sentences. Could be under

  Requirements

  (or Qualifications?). The instruction includes both Requirements and Qualifications. We need to decide where to put content. Minimum Requirements likely go under Requirements. Preferred Requirements maybe under Qualifications or Skills? Preferred Requirements includes Bachelor's degree, etc. Could be Qualifications. - There's also "Strong presentation skills; ..." under Minimum Requirements (list). Then "Preferred Requirements" list. - There's also "Travel is an integral part of this role, and will be based on individual customer needs. 25% travel." That could be under Requirements or maybe Schedule? Travel is not schedule but maybe part of Requirements. We'll keep as a paragraph under Requirements. - Benefits: The posting includes a paragraph about benefits: "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 link. So we can create

  Benefits

  with
  • items. - Pay: The posting includes typical base salary range: "$80,900 - $150,300 annually." So we can create

    Pay

    with paragraph. - Schedule: Not mentioned besides travel 25% maybe but not schedule like full-time/part-time. No explicit schedule. So we should not create Schedule section. - Skills: Not explicitly listed as a separate section; we have presentation skills, communication skills, etc. Could be under Skills but we already have Requirements covering those. Might combine. But instruction: prefer few substantive sections over many thin ones. We could omit Skills if content covered elsewhere. However we have "Strong presentation skills; able to successfully present a point of view..." etc. Those are under Minimum Requirements. Could be considered Skills. But we already have Requirements. Might be okay to not create Skills. - Qualifications: Could be Preferred Requirements (Bachelor's degree, certifications). We'll put under

    Qualifications

    . Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check for any other content: "Unleash Your Potential" paragraph about benefits and resources, but we already captured benefits. Also "Accommodations", "Posting Statement", etc are boilerplate to remove. We must preserve all substantive information: need to keep details like "Serve as a trusted advisor to the client", etc. Must not lose any. We need to format responsibilities as list items. Let's extract responsibilities list from the text: From "Your Impact Responsibilities" paragraph: "Salesforce Professional Services is looking for a Senior Solution Consultant. You will be serving as a Salesforce product and platform guide to the company’s largest, most complex enterprise customers. Here are some salient responsibilities the role entails:" Then list: - Serve as a trusted advisor to the client - Participate as a part of a team working on internal critical initiatives to grow the consulting practice; serving as an active contributor to the community’s overall knowledge base and expertise - Guide customers and colleagues in rationalizing and deploying new technologies that drive increased business value - Work collaboratively and having very strong communications skills, especially in guiding complex concepts, and creative, prescriptive thinking - Identify and proactively handle risk areas and commit to seeing an issue through to complete resolution - Handle customer expectations; negotiate solutions to sophisticated problems with both the customer and third-party partners - Review and correct key artifacts to keep projects on track and solutions extendable and maintainable going forward - Work closely with Delivery Managers, Solution Architects, Technical Architects, and directly with clients to design technology solutions to meet client needs - Contribute to the creation of a program vision/case creation and justification, and be responsible for the monitoring and delivery of these elements throughout the program's lifecycle while advising and articulating program/project strategies on enabling technologies including the Salesforce Platform We need to keep each as
  • . Now Minimum Requirements list: - Strong presentation skills; able to successfully present a point of view and clearly articulate the rationale to a variety of collaborators - Meticulous individual with the ability to rapidly learn and take advantage of new concepts, business models, and technologies - Strong communication skills, both written and verbal; able to effectively develop materials that are appropriate for the audience - A great listener with the ability to connect with people in diverse roles - Consistent track record to analyze, design, and optimize business processes via technology and integration - Resourceful and high-reaching thinker who can work through and solve problems - Travel is an integral part of this role, and will be based on individual customer needs. 25% travel. We'll put these under Requirements as
    • . Preferred Requirements list: - Bachelor’s degree in a Technology, Engineering (any field) or a related quantitative subject area. Equivalent validated work experience in lieu of a degree will be considered - Confirmed results translating business user stories into technical requirements documents - Confirmed results leading customer and/or partner success - Relevant Salesforce certifications and consulting experience are strongly recommended We'll put under Qualifications as
      • . Benefits list: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. We'll put as
        • . Pay: paragraph with salary range. Now About the role: we have the initial paragraphs: "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." Then "Role Description The Senior Solution Consultant supports a work stream in sophisticated enterprise customer engagements, partnering with key collaborators to achieve the vision while completing key deliverables. They serve as hands-on advisors, using strong social skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client’s business to deliver customer return on investment. Senior Solution Consultants are strong presenters that are able to obtain customer acceptance by demonstrating solutions and an understanding of the client's vision. They can identify key risks or issues and are confident in handling difficult conversations with their team and customer to address them. They interact with customer product owners, business process owners and technical resources to understand capabilities and requirements, analyze information, and craft comprehensive solutions. They also show a strong understanding of typical business challenges faced by customers and common objectives. They supply thought leadership and standard processes, both internally in their Community and externally in the marketplace." We can combine these into About the role section. We must not repeat job title. Already not. We must not include boilerplate like "To get the best candidate experience..." etc. Remove that first sentence. Also remove "Job Category Customer Success Job Details". Also remove "Accommodations", "Posting Statement", etc. Now produce HTML fragment. We'll output:

          About the role

          ... paragraphs ...

          Responsibilities

          • ...
          ...

          Requirements

          ...

          Qualifications

          ...

          Benefits

          ...

          Pay

          The typical base salary range for this position is $80,900 - $150,300 annually.

          Make sure no extra whitespace? It's fine. Check that we didn't include Schedule or Skills. Now ensure we preserved all substantive info: Did we miss any? Let's scan original text for any other substantive info not covered. - "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." This is a instruction to candidate, maybe considered boilerplate? It's not about job; it's application advice. Likely considered boilerplate to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is an application instruction, so remove. - "Job Category Customer Success Job Details" - remove. - "About Salesforce" we used. - "Role Description" we used. - "Your Impact Responsibilities" we used. - "Minimum Requirements" we used. - "Preferred Requirements" we used. - "Unleash Your Potential" paragraph: "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." This is marketing fluff but still substantive? It's about benefits and resources, but we already captured benefits. The "Apply today..." is application instruction, remove. The rest maybe could be kept but it's vague. Might be considered boilerplate? It's not specific details. Safer to remove as it's not specific benefit details. We already have benefits list. - "Accommodations" section: remove. - "Please note that Salesforce uses artificial intelligence (AI) tools..." remove. - "Please see our Candidate Privacy Statement..." remove. - "Posting Statement" etc remove. - "At Salesforce, we believe in equitable compensation practices..." we already captured salary range; the rest is boilerplate. - "More details about company benefits can be found at the following link: https://www.salesforcebenefits.com." This is a link to benefits details; we could keep as part of Benefits section maybe as a link. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference for more details. Could include as a

          with link. But we already have benefits list; we could add a

          with link. However the instruction says prefer few substantive sections over many thin ones. Adding a link is fine. We could include after benefits list:

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

          But is that considered boilerplate? It's a link to benefits page; it's specific