Forward Deployed Consultant / Senior Consultant

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Salesforce" then "Job Details". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content for About (the description about Salesforce and role). Could be "About the role". We have Responsibilities (multiple bullet points). We have Required Qualifications and Preferred Qualifications (these could be under Requirements/Qualifications). Also Success Metrics maybe could be under Requirements? Not a standard heading; but we could treat as "Requirements" maybe includes both required and preferred? However we have separate sections: Required Qualifications and Preferred Qualifications. The instruction says we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map Required Qualifications to

Qualifications

and Preferred Qualifications maybe also under Qualifications? But we need to preserve all substantive info; we could have two sub-sections? Not allowed to create extra headings beyond those listed? It 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 as examples. Probably we should stick to those headings. We can include "About the role", "Responsibilities", "Qualifications" (combining required and preferred), maybe "Skills" if we have specific skills list; we could extract skills from qualifications. Could also include "Benefits" (they mention benefits). Also "Pay" (they give salary range). Also maybe "Schedule" not present, so omit. We must not include boilerplate like EEO, accommodations, etc. Remove those. We need to preserve all substantive information: About Salesforce description, role description, responsibilities bullet points, required qualifications bullet points, preferred qualifications bullet points, success metrics bullet points, benefits description, pay range. We must not invent or summarize away detail. So we need to keep the bullet points as they are, maybe rephrase? Must preserve all info; we can keep them as list items. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

... (the About Salesforce paragraph plus role description). We need to include the description about Salesforce and the role summary: "The Forward Deployed Consultant / Senior Consultant sits at the intersection..." etc. We'll combine. Then

Responsibilities

• ... each bullet from Responsibilities section (there are subheadings like Roadmap & Solution Ownership etc). We need to preserve each bullet's content. The original has headings within responsibilities: "Roadmap & Solution Ownership" then bullet points under it. We could treat each heading as a list item? Better to keep as list items with the heading bold? But we cannot add extra markup beyond
• . We could embed the heading as part of the list item text. Eg:
• Roadmap & Solution Ownership Own the roadmap ...
. That's okay. Similarly for other sections. Then

Qualifications

We could split into Required and Preferred maybe as subheadings inside

or

. But we cannot create extra headings beyond allowed? Could use

for "Required Qualifications:" then list. That's fine. We need to preserve all bullet points. Then

Skills

maybe not needed if we already have qualifications. Could omit. Then

Benefits

... benefits description. Then

Pay

... salary range. We must not include sections with filler like "commensurate with experience". Not present. Now we need to strip boilerplate: The initial sentence about applying max 3 roles, Job Category Software Engineering, Job Details, etc. Also remove "Applications for this position will be accepted on an ongoing basis." That's maybe not boilerplate but could be considered meta; but it's substantive? It's about application timing; instruction says remove application instructions. That line is about application timing, could be considered application instruction. Safer to remove. Also remove "Accommodations", "Privacy Statement", "Posting Statement", EEO, etc. Also remove "Unleash Your Potential" paragraph? That's marketing fluff but still substantive? It's about benefits and resources; could be considered part of Benefits? Might be okay to keep as part of Benefits? But we already have Benefits section; we could incorporate that text there. However the instruction says preserve ALL substantive information; we should keep that text but maybe incorporate into Benefits. The "Unleash Your Potential" paragraph mentions benefits and resources, AI agents accelerate impact. Could be considered part of Benefits. We'll include it in Benefits section. Also remove "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's application instruction; remove. Now let's extract content. 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." Then role description: "The Forward Deployed Consultant / Senior Consultant sits at the intersection of customer engagement and platform innovation. This role is responsible for designing, implementing, and optimizing automated business process solutions ("Blueprints") using Agentforce platform capabilities — while also owning the roadmap and feature lifecycle for scalable process solutions that drive measurable customer value. You will partner closely with customer-facing teams, AI agents, engineering, and design to transform manual, fragmented workflows into automated solutions. You are customer-obsessed, execution-focused, and passionate about solving big problems with creative solutions at speed and quality." We'll combine into a paragraph. Now Responsibilities bullets: From text: Roadmap & Solution Ownership - Own the roadmap for process blueprints and automation solutions, balancing strategic direction with foundational execution needs - Own the feature lifecycle for specific components from discovery through launch and iteration - Identify operational inefficiencies, manual processes, and automation opportunities across customer and internal workflows Blueprint Design & Execution - Partner with customer-facing team leaders to map and analyze customer requirements for new solutions - Build solution blueprints and workflow automations using current platform features - Work directly with AI agents and prompting tools to design automated, enterprise-grade solutions - Validate, test, and iterate blueprints for accuracy, consistency, and performance Technical Specification & Delivery - Translate high-level strategic goals and customer requirements into clear Product Requirement Documents (PRDs), user stories, and technical acceptance criteria - Manage the product backlog, prioritize sprints, and drive consistent delivery using Agile methodologies - Document solution architecture, demonstrations, and implementation guidelines Customer & Market Research - Conduct user interviews and quantitative analysis to deeply understand customer pain points and identify product opportunities - Act as the voice of the customer within the development process Cross-Functional Collaboration - Partner with Engineering and Design (UX/UI) to ensure technical feasibility and intuitive user experiences - Provide structured, detailed feedback to Product Managers regarding feature gaps and enhancements needed to support scalability - Support rollout and enablement of blueprint solutions across teams and customers We'll put each bullet as

• . We'll include the heading as part of the first li maybe bold. Now Required Qualifications bullet list: - 3-8+ years of experience in Product Management, Process Automation, Business Analysis, or Solutions Consulting - Experience building external-facing products in enterprise B2B SaaS environments - Strong understanding of business workflow mapping, process modeling, and process improvement methodologies - Proven experience translating business requirements into structured automated workflows or solutions - Hands-on technical experience with automation tools, workflow builders, AI prompting, or low/no-code platforms - Excellent spoken and written communication with ability to present complex ideas clearly to both technical and non-technical audiences - Proven ability to collaborate with virtual and global cross-functional teams including engineering, design, and customer success - Rigor and consistency in managing product backlogs and executing delivery Preferred Qualifications bullet list: - Experience in SaaS, AI automation, supply chain operations, contact center operations, or customer experience technology - Experience with prompt design or agent-based automation solutions - Familiarity with the Salesforce platform ecosystem (e.g., APIs, platform services) - Experience with network effects and cold start strategies - Familiarity with feature prioritization and product feedback processes - Lean, Six Sigma, or related process improvement certification - A related technical degree - Experience within the Supply Chain or Financial Services sector highly preferred Success Metrics bullet list (maybe could be under Requirements? but we can include as a separate section? Not in allowed headings; but we could incorporate into Qualifications or Responsibilities? It's about success metrics; maybe we can add a section "Success Metrics" but not in allowed list. 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 says "Prefer a few substantive sections over many thin ones." Success Metrics is substantive; we could include as a section with heading

  Success Metrics

  though not in examples. Might be okay. But to be safe, we could incorporate under Qualifications? Not ideal. However the instruction says "include a section ONLY when the posting has real, specific content for it". Success Metrics is specific content. So we should include a section. The examples are not exhaustive. So we can add

  Success Metrics

  . Thus we will have sections: About the role, Responsibilities, Qualifications (maybe split required and preferred?), Success Metrics, Benefits, Pay. We could also have Skills but we already have qualifications covering skills; we can omit Skills. Now Benefits paragraph: from text after "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." Also earlier benefits list: "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 combine. Now Pay paragraph: "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 $117,200 - $223,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $141,200 - $246,000 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We'll put that. Now ensure we removed boilerplate: The initial lines about "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months