Forward Deployed Engineer (FDE) — Agentforce Orchestration

We need to output HTML fragment with sections: About the role (maybe heading "About the role"), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About The Role (description). Then "What You'll Actually Be Building" which is responsibilities. Then "Required Qualifications" and "Preferred Qualifications". Also benefits and pay info later. No schedule info. So we need sections: About the role (maybe we can call it About the role), Responsibilities (from "What You'll Actually Be Building"), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe list of technical skills from required?), Benefits (list of benefits), Pay (salary range). We must not repeat job title. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: the initial "To get the best candidate experience..." etc, Job Category Sales, etc. Also remove accommodations, AI tools note, privacy statement, equal opportunity, etc. Also remove application instructions (Apply today...). Also remove "Accommodations" etc. Also remove "Posting Statement" etc. Keep only substantive content: About Salesforce description? That's part of "About Salesforce" maybe not needed as a section? The instruction: include a section ONLY when posting has real specific content for it. The "About Salesforce" paragraph is descriptive but not a standard section heading; we could treat it as part of "About the role"? Actually there is a separate "About Salesforce" paragraph before "About The Role". Could be considered company overview; not required to include as a section unless we have a heading like "About Salesforce". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Salesforce". So we likely omit that paragraph or incorporate into About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings not in list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we need to map content to those headings. Thus: - About the role: include the paragraph "About The Role As a Forward Deployed Engineer (FDE) focusing on Agentforce Operations, you are a hands-on Technical Builder ..." plus maybe the preceding "About Salesforce" is not needed. We'll include the role description. - Responsibilities: the "What You'll Actually Be Building" bullet list (multiple items). We'll turn each into

  . - Requirements: maybe combine Required Qualifications and Preferred Qualifications? But we have separate sections Requirements and Qualifications. Could put Required Qualifications under Requirements, Preferred Qualifications under Qualifications. Or we could put all under Requirements and leave Qualifications empty (but we shouldn't emit empty sections). So we need both sections with content. Thus:

  Requirements

  with

  of required qualifications items.

  Qualifications

  with
  of preferred qualifications items. Skills: maybe we could extract technical skills from required qualifications (languages, tools) but we already have them in Required Qualifications; we could still create a Skills section summarizing specific skills like Python, JavaScript/TypeScript, Java, Apex, LLM orchestration, RAG, vector databases, MCP, API design, MuleSoft, data modeling, etc. But that would be duplicating content; we should not invent or summarize away detail, but we can list them as skills if they appear explicitly. The posting includes many specific skills; we could put them under Skills. However we already have Required Qualifications which includes those. To avoid duplication, maybe we skip Skills section because the content is already covered in Requirements. But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required Qualifications and Skills into one Requirements section. But we have separate headings allowed; we can choose to omit Skills if not needed. Benefits: list of benefits from later paragraph: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program. Also maybe mention "AI agents accelerate your impact". We'll list those. Pay: salary range info: typical base salary range $88,970 - $287,910 annually; also location-specific range $97,860 - $316,750 for certain locations. We'll include both. Schedule: no info, so omit. We must not include boilerplate like "Applications for this position will be accepted on an ongoing basis." That's application instruction? Might be considered minor metadata; we can drop. Also drop "Unleash Your Potential" etc as it's fluff; but it's part of benefits? It's more marketing; we could drop as not substantive? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "Unleash Your Potential" paragraph is somewhat generic but still part of posting; but it's not specific detail like benefits. Might be considered boilerplate? It's not navigation/legal/EEO. It's more marketing; but we could keep as part of Benefits? Not sure. Safer to omit as it's not a concrete benefit. The benefits paragraph after that is concrete. Thus produce HTML:

  About the role

  As a Forward Deployed Engineer (FDE) focusing on Agentforce Operations, you are a hands-on Technical Builder who designs, constructs, and deploys enterprise-grade agentic AI solutions directly inside customer environments. AFO powers the multi-agent orchestration layer, transforming messy operational workflows, unstructured data (emails, PDFs, spec sheets), and legacy ERP logs into autonomous execution engines with humans in the loop. Operating in an agile deployment pod alongside a Deployment Strategist and Specialized AI Engineers, you will serve as the crucial link connecting advanced AI agents to the broader enterprise technology landscape. You will write production code, architect real-time data grounding systems, perform prompt engineering, manage multi-agent communication protocols, and deploy automated supply chain and back-office workflows into production from day one.

  Responsibilities

  • Build, configure, and optimize complex operational workflows using AFO, defining agent reasoning, tool-calling logic, and conditional execution loops.
  • Implement modern agent-to-agent communication standards and the Model Context Protocol (MCP) to govern context sharing, task hand-offs, and tool execution across specialized AI agents.
  • Architect, build, and maintain real-time data grounding infrastructure using RAG (Retrieval-Augmented Generation), vector databases, search indexes, and knowledge bases to supply agents with accurate enterprise context.
  • Develop and maintain custom APIs (REST, GraphQL, webhooks) and integration pipelines connecting AFO/Agentforce to Salesforce Data Cloud (Data 360), cloud warehouses (Snowflake, Databricks), and core ERPs (SAP, Oracle, NetSuite) via MuleSoft or custom middleware.
  • Leverage modern AI tools (Cursor, Claude, Vibes) embedded directly into your daily developer workflow to move from architecture sketch to deployable code in days, not months.
  • Model data, ship ETL/ELT pipelines, and build real-time agent performance dashboards to track execution health, fallback triggers, and business outcomes.
  • Serve as the direct connective bridge between frontline customer deployments and core Salesforce product/engineering teams to feed edge cases and gaps back into platform feature roadmaps.

  Requirements

  • 3+ years of software engineering or technical delivery experience, with at least one production AI, data engineering, or enterprise integration system deployed to production.
  • High proficiency in at least one modern language: Python, JavaScript/TypeScript, Java, or Apex.
  • Hands-on AI & Grounding Expertise: Deep experience with LLM orchestration, prompt tuning, and building RAG pipelines, vector search indexes, and knowledge base retrievers for enterprise data.
  • Multi-Agent Systems & API Mastery: Practical experience with API design (REST/SOAP/webhooks) and modern agent protocols (e.g., MCP, tool calling, or event-driven messaging architectures).
  • Expertise in process orchestration and API-led connectivity using tools like MuleSoft or custom middleware to bridge AI agents with legacy ERP systems.
  • Solid understanding of data modeling, schema design, and asynchronous message integration patterns.
  • Strong executive presence - ability to whiteboard architecture with enterprise CTOs and VPs while writing production code alongside lead architects.
  • Familiarity with automation platforms (Pega, UiPath, Automation Anywhere, ServiceNow, Appian, Microsoft Power Platform) and competing enterprise AI and agent platforms (Microsoft Copilot Studio, Google Vertex AI, AWS Bedrock, IBM watsonx, Palantir AIP, ServiceNow AI Agents).
  • Experience with integrated enterprise applications (Workday, Coupa, Jira, Slack, major warehouse or transportation management systems) and deployment infrastructure (Kafka, AWS EventBridge, Azure Service Bus, GitHub, Docker, Kubernetes, Terraform).
  • Knowledge of data governance and master data systems (Informatica, Collibra, SAP MDG, Reltio) and operational execution platforms (Manhattan Associates, Blue Yonder, Kinaxis, Oracle transportation management).
  • Understanding of enterprise security and governance: Identity and access management, OAuth, data privacy, audit logging, permissioning, and secure tool execution.
  • Willingness to travel 25-30% for on-site deployment with key enterprise accounts.

  Qualifications

  • Specific domain expertise in Supply Chain, Manufacturing, or Logistics Execution.
  • Experience within the Salesforce Ecosystem (Agentforce Specialist, Data Cloud, Apex, Flow, or Headless architectures).
  • Hands-on experience with cloud data platforms (Snowflake, Databricks, BigQuery).
  • Proven ability to create reusable accelerators, reference architectures, connectors, and implementation playbooks from customer deployments.

  Benefits

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

  Pay

  The typical base salary range for this position is $88,970 - $287,910 annually. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role is $97,860 - $316,750 per year. The range represents base salary only and does not include bonus, incentive, equity, or benefits.

  We must ensure no extra text outside HTML. No markdown fences. Provide just the HTML. Check for any leftover boilerplate: we omitted "Applications for this position will be accepted on an ongoing basis." Good. Also omitted "Unleash Your Potential" etc. Also omitted accommodations, AI tools note, privacy statement, equal opportunity, etc. Good. Check that we didn't repeat job title. No. All good.