Forward Deployed Engineer (FDE) — Agentforce Orchestration
. Use - for lists. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Keep substantive info.
We need sections: About the role, Responsibilities? The posting includes "About The Role" and then details. Also "What You'll Actually Be Building" could be responsibilities. Also "Required Qualifications", "Preferred Qualifications". Also "Unleash Your Potential" maybe benefits? Actually benefits described later: "When you join Salesforce, you’ll be limitless..." includes benefits description. Also salary range info. Also accommodations etc but we should remove boilerplate like accommodations? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Accommodations request form maybe not boilerplate? It's a specific section but maybe considered part of application instructions? It says "If you need a reasonable accommodation during the application or the recruiting process, please submit a request via this Accommodations Request Form." That's application instruction, so remove. Also the paragraph about AI tools used by recruiters etc is legal/boilerplate, remove. Also the equal opportunity employer statement is boilerplate, remove. Also the San Francisco Fair Chance etc is legal, remove. Also the benefits description: "Salesforce offers a variety of benefits..." is substantive benefits, keep. Also salary range info is substantive, keep as Pay section. Also schedule? Not mentioned. So we may have sections: About the role (maybe combine About The Role and What You'll Actually Be Building). Responsibilities could be the bullet list of what you'll actually be building. Requirements could be Required Qualifications. Preferred Qualifications separate. Benefits section. Pay section.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting that are substantive.
Let's extract:
About Salesforce: description paragraph.
About The Role: paragraph describing role.
What You'll Actually Be Building: list of items (Workflow & Multi-Agent Orchestration, Agent Communication Protocols, Enterprise AI Grounding Systems, Enterprise Integration & API Management, AI-Assisted Engineering, Telemetry & Observability, Field-to-Product Feedback). Each with description.
Required Qualifications: list of bullet points (many). Need to keep each as
- .
Preferred Qualifications: list.
Unleash Your Potential: paragraph about benefits and resources, AI agents accelerate impact.
Benefits: paragraph describing benefits: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program. Also link.
Pay: salary range info: typical base salary range $88,970 - $287,910 annually. Different range for CA/NY etc: $97,860 - $316,750 per year. Note base salary only.
We should not include the sentence about recruiter sharing specific salary range etc? That's part of pay info, we can keep.
We should not include duplicated lines: there may be repeated sentences about recruiter sharing specific salary range appears twice; we can keep once.
We need to output only HTML fragment.
Structure:
About the role
... (including About Salesforce and About The Role? Actually About Salesforce is separate but could be part of 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 both the Salesforce description and role description.
Then Responsibilities heading with - for each building item.
Then Requirements heading (or Qualifications?) The instruction list includes Requirements, Qualifications, Skills. We have Required Qualifications and Preferred Qualifications. Could combine under Requirements? But better to have Requirements heading for Required Qualifications, and maybe Skills heading for Preferred? But they said prefer few substantive sections over many thin ones. Could have Requirements (required) and Preferred Qualifications (maybe under same heading? Could split). Let's make Requirements for Required Qualifications, and Preferred Qualifications as separate heading? Might be okay.
But we need to avoid thin sections; each has substantial list.
We'll do:
About the role
... (Salesforce description + role description)
Responsibilities
- Workflow & Multi-Agent Orchestration: Build, configure, and optimize complex operational workflows using AFO, defining agent reasoning, tool-calling logic, and conditional execution loops.
- Agent Communication Protocols: 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.
- Enterprise AI Grounding Systems: 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.
- Enterprise Integration & API Management: 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.
- AI-Assisted Engineering: 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.
- Telemetry & Observability: Model data, ship ETL/ELT pipelines, and build real-time agent performance dashboards to track execution health, fallback triggers, and business outcomes.
- Field-to-Product Feedback: 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.
Preferred 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
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.
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.
Pay
The typical base salary range for this position is $88,970 - $287,910 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We should avoid duplicated sentence about recruiter sharing specific salary range appears twice; we can keep once but it's okay to keep both? The instruction: remove duplicated lines. So we should deduplicate. Let's keep one sentence: "Your recruiter can share more about the specific salary range for the job location during the hiring process." We'll include it once.
Thus Pay paragraph: "The typical base salary range for this position is $88,970 - $287,910 annually. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
Now ensure no boilerplate: we removed accommodations, AI tools statement, EEO, fair chance, etc.
Check for any leftover boilerplate: The paragraph "Applications for this position will be accepted on an ongoing basis." is maybe application instruction? It's about process; could be considered boilerplate but it's not explicitly listed as to remove. However it's not substantive about role; it's about application timing. The instruction says remove application instructions. That line is an application instruction. So remove.
Also "Ready to level-up your career at the company leading
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Keep substantive info. We need sections: About the role, Responsibilities? The posting includes "About The Role" and then details. Also "What You'll Actually Be Building" could be responsibilities. Also "Required Qualifications", "Preferred Qualifications". Also "Unleash Your Potential" maybe benefits? Actually benefits described later: "When you join Salesforce, you’ll be limitless..." includes benefits description. Also salary range info. Also accommodations etc but we should remove boilerplate like accommodations? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Accommodations request form maybe not boilerplate? It's a specific section but maybe considered part of application instructions? It says "If you need a reasonable accommodation during the application or the recruiting process, please submit a request via this Accommodations Request Form." That's application instruction, so remove. Also the paragraph about AI tools used by recruiters etc is legal/boilerplate, remove. Also the equal opportunity employer statement is boilerplate, remove. Also the San Francisco Fair Chance etc is legal, remove. Also the benefits description: "Salesforce offers a variety of benefits..." is substantive benefits, keep. Also salary range info is substantive, keep as Pay section. Also schedule? Not mentioned. So we may have sections: About the role (maybe combine About The Role and What You'll Actually Be Building). Responsibilities could be the bullet list of what you'll actually be building. Requirements could be Required Qualifications. Preferred Qualifications separate. Benefits section. Pay section. We must not create sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting that are substantive. Let's extract: About Salesforce: description paragraph. About The Role: paragraph describing role. What You'll Actually Be Building: list of items (Workflow & Multi-Agent Orchestration, Agent Communication Protocols, Enterprise AI Grounding Systems, Enterprise Integration & API Management, AI-Assisted Engineering, Telemetry & Observability, Field-to-Product Feedback). Each with description. Required Qualifications: list of bullet points (many). Need to keep each as
About the role
... (including About Salesforce and About The Role? Actually About Salesforce is separate but could be part of 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 both the Salesforce description and role description.
Then Responsibilities heading with - for each building item.
Then Requirements heading (or Qualifications?) The instruction list includes Requirements, Qualifications, Skills. We have Required Qualifications and Preferred Qualifications. Could combine under Requirements? But better to have Requirements heading for Required Qualifications, and maybe Skills heading for Preferred? But they said prefer few substantive sections over many thin ones. Could have Requirements (required) and Preferred Qualifications (maybe under same heading? Could split). Let's make Requirements for Required Qualifications, and Preferred Qualifications as separate heading? Might be okay.
But we need to avoid thin sections; each has substantial list.
We'll do:
About the role
... (Salesforce description + role description)
Responsibilities
- Workflow & Multi-Agent Orchestration: Build, configure, and optimize complex operational workflows using AFO, defining agent reasoning, tool-calling logic, and conditional execution loops.
- Agent Communication Protocols: 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.
- Enterprise AI Grounding Systems: 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.
- Enterprise Integration & API Management: 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.
- AI-Assisted Engineering: 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.
- Telemetry & Observability: Model data, ship ETL/ELT pipelines, and build real-time agent performance dashboards to track execution health, fallback triggers, and business outcomes.
- Field-to-Product Feedback: 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.
Preferred 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
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.
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.
Pay
The typical base salary range for this position is $88,970 - $287,910 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We should avoid duplicated sentence about recruiter sharing specific salary range appears twice; we can keep once but it's okay to keep both? The instruction: remove duplicated lines. So we should deduplicate. Let's keep one sentence: "Your recruiter can share more about the specific salary range for the job location during the hiring process." We'll include it once.
Thus Pay paragraph: "The typical base salary range for this position is $88,970 - $287,910 annually. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
Now ensure no boilerplate: we removed accommodations, AI tools statement, EEO, fair chance, etc.
Check for any leftover boilerplate: The paragraph "Applications for this position will be accepted on an ongoing basis." is maybe application instruction? It's about process; could be considered boilerplate but it's not explicitly listed as to remove. However it's not substantive about role; it's about application timing. The instruction says remove application instructions. That line is an application instruction. So remove.
Also "Ready to level-up your career at the company leading
About the role
... (Salesforce description + role description)
Responsibilities
- Workflow & Multi-Agent Orchestration: Build, configure, and optimize complex operational workflows using AFO, defining agent reasoning, tool-calling logic, and conditional execution loops.
- Agent Communication Protocols: 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.
- Enterprise AI Grounding Systems: 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.
- Enterprise Integration & API Management: 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.
- AI-Assisted Engineering: 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.
- Telemetry & Observability: Model data, ship ETL/ELT pipelines, and build real-time agent performance dashboards to track execution health, fallback triggers, and business outcomes.
- Field-to-Product Feedback: 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.
Preferred 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
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.
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.
Pay
The typical base salary range for this position is $88,970 - $287,910 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We should avoid duplicated sentence about recruiter sharing specific salary range appears twice; we can keep once but it's okay to keep both? The instruction: remove duplicated lines. So we should deduplicate. Let's keep one sentence: "Your recruiter can share more about the specific salary range for the job location during the hiring process." We'll include it once. Thus Pay paragraph: "The typical base salary range for this position is $88,970 - $287,910 annually. There is a different range applicable to specific work locations. 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 in those locations is $97,860 - $316,750 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." Now ensure no boilerplate: we removed accommodations, AI tools statement, EEO, fair chance, etc. Check for any leftover boilerplate: The paragraph "Applications for this position will be accepted on an ongoing basis." is maybe application instruction? It's about process; could be considered boilerplate but it's not explicitly listed as to remove. However it's not substantive about role; it's about application timing. The instruction says remove application instructions. That line is an application instruction. So remove. Also "Ready to level-up your career at the company leading