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". We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. We must not repeat job title. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Keep substantive info. We need to parse content: - Intro: "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." That's application instruction? Possibly remove as it's advice. Might be considered boilerplate? It's not EEO but it's a suggestion. Probably remove. - "Job Category Software Engineering" - minor metadata, fold into short p or drop. Probably drop. - "Job Details About Salesforce" then paragraph about Salesforce. That's about the company, could be "About the role"? Actually "About Salesforce" is about company. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and company? The posting includes "About Salesforce" describing company mission. We'll put that under About the role. - Then "Applications for this position will be accepted on an ongoing basis." That's application instruction; remove. - Then description of role: "The Forward Deployed Consultant / Senior Consultant sits at the intersection..." That's role description. Include under About the role. - Then "Responsibilities" heading with bullet list items. We'll create

Responsibilities

then

• each. - Then "Required Qualifications" heading with bullet list. That's qualifications. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications headings. We need to decide: maybe "Requirements" for required qualifications, "Qualifications" for preferred qualifications. We'll map Required Qualifications to

  Requirements

  . Preferred Qualifications to

  Qualifications

  . - Then "Success Metrics" maybe could be under Skills? Not exactly. Could be omitted if not matching headings. But we need to include only sections with real content. Success Metrics could be considered "Skills"? Not really. Might be better to omit or include under "Skills"? The instruction says use those headings only if posting has real specific content. Success Metrics is not one of the listed headings, so we should not create a heading for it. We could incorporate its content into maybe "Responsibilities" or "Qualifications"? But better to drop if not fitting. However we must preserve ALL substantive information; we cannot drop Success Metrics if it's substantive. But we can embed it under an existing heading like "Responsibilities" or "Qualifications"? The instruction: "Prefer a few substantive sections over many thin ones." We could add a section "Success Metrics" but not in allowed list? The list is examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should map Success Metrics to maybe "Skills" or "Requirements"? Might be considered part of "Requirements"? Not exactly. Could be considered "Skills"? Not really. Could be considered "Qualifications"? Might be okay to put under "Qualifications" as part of preferred? But it's about metrics of success for the role, not qualifications. Could be placed under "Responsibilities" as part of what you'll be measured on. Might be okay to add a bullet under Responsibilities about measuring success. But the original text is a separate section; we could incorporate its bullet points as sub-bullets under Responsibilities? Might be okay. Better: create a section "Skills" and put success metrics there? Not ideal. Alternatively, we could create a custom heading but risk violating instruction. The instruction says use those headings (e.g.) - maybe they are examples, not strict. But to be safe, we should stick to those headings. We can embed Success Metrics content under "Responsibilities" as additional bullet points about measuring outcomes. Now "Unleash Your Potential" paragraph about benefits and resources. That's benefits. So we can create

  Benefits

  with paragraph. Then "Accommodations" etc - that's legal/EEO boilerplate, remove. Then "Posting Statement" includes EEO etc, remove. Then "Recruiting, hiring, and promotion decisions..." remove. Then "In the United States, compensation offered will be determined..." then salary range. That's Pay. So we create

  Pay

  with paragraph containing salary range. Also mention "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." Keep that. No schedule info present, so we omit Schedule section. Now we need to ensure we don't include duplicated lines. Also remove "Job Category Software Engineering". Also remove "Applications for this position will be accepted on an ongoing basis." Also remove "Accommodations" etc. Now construct HTML:

  About the role

  ... combine About Salesforce paragraph and role description.

  We need to preserve all substantive info: 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." 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." Combine into one

  maybe two paragraphs. Then Responsibilities: list each bullet. We need to extract bullet points from Responsibilities section: - 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 flatten into

  • each bullet. Then Requirements (Required Qualifications): - 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 Then Qualifications (Preferred Qualifications): - 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 Then Benefits: from "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." Also maybe mention benefits list later? Actually later there is a benefits list in EEO section: "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 in the EEO boilerplate but it's substantive benefits info. However that paragraph is within the EEO/legal section which we were told to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The benefits list appears in that EEO section. Should we keep it? The instruction says remove EEO/equal-opportunity boilerplate. The benefits list is part of that EEO section, but it's substantive about benefits. However it's within the EEO boilerplate; we might need to remove the whole block. But we already have a benefits paragraph from "Unleash Your Potential". That may be enough. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO block entirely, even if it contains benefits info. However we already have a benefits paragraph earlier; we can keep that. If we remove the EEO block, we lose the detailed benefits list, but we still have a generic benefits statement. That may be acceptable. Thus Benefits section: use the paragraph from "Unleash Your Potential". Could also add "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's more call to action, maybe remove as application instruction? It's not exactly instruction but could be considered promotional. Might keep as part of benefits? Safer