Forward Deployed Consultant / Senior Consultant

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Salesforce" and then description. 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. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract sections: About (maybe "About Salesforce" or "About the role"? The posting has "About Salesforce" then description. Could treat as "About the role" or "About Salesforce". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have: - About Salesforce: description of company, mission, etc. That's substantive. Could be "About the role"? Actually "About Salesforce" is about company. But we can still use heading "About the role"? Might be okay. The instruction says use those headings as examples, not strict list. We can use "About the role" for the introductory paragraph about the role and company. Or we could use "About Salesforce". Safer to use "About the role" as heading and include the company description plus role overview. - Responsibilities: list of bullet points under "Responsibilities" heading with subheadings? The posting has sections: Roadmap & Solution Ownership, Blueprint Design & Execution, Technical Specification & Delivery, Customer & Market Research, Cross-Functional Collaboration. Those are sub-responsibilities. We can combine them under a single

• list, each bullet containing the description. Or we could keep subheadings but not required. We'll output a
  with each responsibility as
  • . Ensure we preserve all details. - Required Qualifications: list of bullet points. We'll output under heading "Qualifications" (or "Required Qualifications"? The instruction says use headings like Qualifications. We'll use "Qualifications". Could also separate Required and Preferred but instruction says prefer few substantive sections. Could combine Required and Preferred under Qualifications? But they are distinct. However we could have "Qualifications" heading and then separate
    for required and maybe another for preferred? Might be thin. Better to have two sections: "Required Qualifications" and "Preferred Qualifications". Both are substantive. Use headings "Required Qualifications" and "Preferred Qualifications". That's okay. - Success Metrics: could be under "Skills"? Not exactly. Could be under "Skills" or maybe we omit if not matching headings. The instruction says include a section ONLY when posting has real, specific content for it. Success Metrics is substantive. Could map to "Skills"? Not ideal. Could create a custom heading? The instruction gave examples but not strict; we can use other headings if needed. But they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should stick to those headings. Success Metrics could be considered part of "Skills"? Not really. Could be omitted? But we must preserve ALL substantive information. If we omit Success Metrics, we lose info. So we need a section for it. Perhaps we can treat it as "Skills"? Not accurate. Could treat as "Requirements"? Not exactly. Could treat as "Qualifications"? Not exactly. Could create a custom heading like "Success Metrics". The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive list. So we can use other headings as needed. We'll include a heading "Success Metrics". - Benefits: The posting includes benefits description 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 mentions link. So we should include a Benefits section. - Pay: The posting includes salary range: "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." That's substantive. So include Pay section. - Schedule: Not mentioned. So omit. - Requirements: Could be same as Qualifications? The instruction includes Requirements as a possible heading. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to "Requirements" and Preferred to "Qualifications"? But we already have Qualifications heading. Might be confusing. Better to follow the posting: have "Required Qualifications" and "Preferred Qualifications". Use headings as such. We must remove boilerplate: the initial line 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 application instruction? It's not exactly instruction to apply but could be considered metadata. Might be okay to keep? The instruction says remove application instructions. That line is about application timing; could be considered instruction. Safer to remove. Also remove "Accommodations", "Please note that Salesforce uses artificial intelligence (AI) tools..." etc. That's legal/EEO boilerplate. Remove. Also remove "Posting Statement" etc. Also remove "More details about company benefits can be found at the following link: https://www.salesforcebenefits.com." That's maybe okay to keep as part of Benefits? Could keep but it's a link. Might be okay. We need to preserve all substantive information: company description, role description, responsibilities, required qualifications, preferred qualifications, success metrics, benefits, pay. We must not repeat job title as heading. The job title is "Forward Deployed Consultant / Senior Consultant". Not to be used as heading. We must not include Job ID/requisition numbers. Now craft HTML. Structure:

    About the role

    ... (company description + role overview)

    Responsibilities

    • 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

    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

    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

    Success Metrics

    • Efficiency improvements and measurable reduction in manual work for customers
    • Blueprint adoption, usage outcomes, and tangible business value delivered (e.g., cost savings)
    • Quality and clarity of roadmap feedback influencing platform improvements
    • Time-to-value and scalability of solution deployments
    • Customer satisfaction and depth of engagement with deployed solutions

    Benefits

    • Time off programs
    • Medical, dental, vision
    • Mental health support
    • Paid parental leave
    • Life and disability insurance
    • 401(k)
    • Employee stock purchasing program

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

    Pay

    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 need to ensure we didn't include any boilerplate like "Applications for this position will be accepted on an ongoing basis." Removed. Check for any leftover boilerplate: The initial line about "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; remove. "Job Category Software Engineering Job Details" remove. "About Salesforce" we incorporated into About the role paragraph. We need to include the company description paragraph: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets