Forward Deployed Consultant / Senior Consultant

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "To get the best candidate experience..." line (that's instruction). Also remove "Applications for this position will be accepted on an ongoing basis." maybe considered boilerplate? It's not EEO but maybe still generic; but it's not a section heading. We can keep as prose if relevant? It's about application timing; maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is an application instruction? It says "Applications for this position will be accepted on an ongoing basis." That's about application process, maybe considered instruction. Safer to remove. We need sections: About the role? The posting has "About Salesforce" then description. Could treat as About the role? There's a paragraph about Salesforce and Agentforce. Could be "About the role" or "About Salesforce". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present. We have: - About Salesforce (description) -> could be About the role. - Responsibilities: list bullet points under "Responsibilities" heading. - Required Qualifications: list. - Preferred Qualifications: list. - Success Metrics: list. - Benefits: there is a paragraph about benefits after "Unleash Your Potential". Also 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." Also link. - Pay: salary range info: "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." - Schedule: not mentioned. - Skills: maybe not explicit; could be derived from qualifications but we should not invent. So we skip Skills if no explicit. - Requirements: maybe same as Qualifications? The instruction includes Requirements as possible heading. We have Required Qualifications and Preferred Qualifications. Could combine into Requirements? But better to have Qualifications section with subheadings? The instruction says use headings for those categories; we can have Required Qualifications and Preferred Qualifications as separate headings? They are not in the list but we can still use them? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those examples. So we need to map content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We don't have Skills or Schedule. We need to decide what goes under Requirements vs Qualifications. Usually Requirements are mandatory, Qualifications could be preferred. But we have Required Qualifications and Preferred Qualifications. Could treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications (or maybe Skills). But we have no separate Skills. Could put Preferred Qualifications under Qualifications. Thus:

About the role

with paragraph about Salesforce and Agentforce.

Responsibilities

with

• items from Responsibilities section.

  Requirements

  with
  • items from Required Qualifications.

    Qualifications

    with
    • items from Preferred Qualifications.

      Benefits

      with
      • items from benefits paragraph.

        Pay

        with

        containing salary range info. We must not include fluff like "commensurate with experience". Not present. We must preserve all substantive information. Ensure we don't lose any details. Let's extract details. 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." We need to keep that as prose. Responsibilities bullet points: From text: "Roadmap & Solution Ownership Own the roadmap for process blueprints and automation solutions, balancing strategic direction with foundational execution needsOwn the feature lifecycle for specific components from discovery through launch and iterationIdentify operational inefficiencies, manual processes, and automation opportunities across customer and internal workflows" It seems missing punctuation; but we need to split into separate bullet points. The original had line breaks? It appears as a run-on. We need to parse likely three bullet points: - 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 Next: "Blueprint Design & Execution Partner with customer-facing team leaders to map and analyze customer requirements for new solutionsBuild solution blueprints and workflow automations using current platform featuresWork directly with AI agents and prompting tools to design automated, enterprise-grade solutionsValidate, test, and iterate blueprints for accuracy, consistency, and performance" Bullet points: - 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 Next: "Technical Specification & Delivery Translate high-level strategic goals and customer requirements into clear Product Requirement Documents (PRDs), user stories, and technical acceptance criteriaManage the product backlog, prioritize sprints, and drive consistent delivery using Agile methodologiesDocument solution architecture, demonstrations, and implementation guidelines" Bullet points: - 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 Next: "Customer & Market Research Conduct user interviews and quantitative analysis to deeply understand customer pain points and identify product opportunitiesAct as the voice of the customer within the development process" Bullet points: - 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 Next: "Cross-Functional Collaboration Partner with Engineering and Design (UX/UI) to ensure technical feasibility and intuitive user experiencesProvide structured, detailed feedback to Product Managers regarding feature gaps and enhancements needed to support scalabilitySupport rollout and enablement of blueprint solutions across teams and customers" Bullet points: - 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 Now Required Qualifications bullet points: "3-8+ years of experience in Product Management, Process Automation, Business Analysis, or Solutions ConsultingExperience building external-facing products in enterprise B2B SaaS environmentsStrong understanding of business workflow mapping, process modeling, and process improvement methodologiesProven experience translating business requirements into structured automated workflows or solutionsHands-on technical experience with automation tools, workflow builders, AI prompting, or low/no-code platformsExcellent spoken and written communication with ability to present complex ideas clearly to both technical and non-technical audiencesProven ability to collaborate with virtual and global cross-functional teams including engineering, design, and customer successRigor and consistency in managing product backlogs and executing delivery" We need to split into sensible bullet points: - 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 points: "Experience in SaaS, AI automation, supply chain operations, contact center operations, or customer experience technologyExperience with prompt design or agent-based automation solutionsFamiliarity with the Salesforce platform ecosystem (e.g., APIs, platform services)Experience with network effects and cold start strategiesFamiliarity with feature prioritization and product feedback processesLean, Six Sigma, or related process improvement certificationA related technical degreeExperience within the Supply Chain or Financial Services sector highly preferred" Split: - 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 points maybe could go under Requirements? But we have no heading for Success Metrics; we could incorporate into Qualifications? But instruction says only include sections when posting has real specific content. Success Metrics is a section with bullet points. Should we create a heading? Not in the examples but could be okay. However 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 "use

        for section headings (e.g ...)". It implies we should use those headings for those categories; but we could also add other headings if needed? Safer to stick to given categories. Success Metrics could be placed under Requirements or Qualifications? It's about metrics for success; maybe treat as part of Responsibilities? Not exactly. Could be considered part of "Requirements"? Not ideal. Could create a section "Success Metrics" as

        though not listed; risk of deviating. The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add Success Metrics as a heading if appropriate. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include Success Metrics. Thus we add

        Success Metrics

        with bullet points. Success Metrics bullet points: "Efficiency improvements and measurable reduction in manual work for customersBlueprint adoption, usage outcomes, and tangible business value delivered (e.g., cost savings)Quality and clarity of roadmap