Forward Deployed Engineer (FDE) (Mid/Senior Level)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About Salesforce (company description) maybe not needed? The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have "About The Role" section: includes description of role, builder mindset, etc. That's likely "About the role". So we put that under About the role
with paragraphs.
Then responsibilities: bullet list of duties: "What You'll Actually Be Building" includes list of tasks. Also earlier bullet points about working with Deployment Strategist etc. So we can put responsibilities as a - .
Requirements: maybe "You're Our Forward Deployed Engineer If…" list of requirements. That's requirements.
Qualifications: maybe degree, experience etc overlapped. Could combine but we need separate sections if content. The posting includes "You have 3+ years..." etc. That's qualifications/requirements. Could treat as Requirements. Qualifications maybe education: degree in CS. Could separate.
Skills: maybe technical skills: fluent in Python etc, LLMs, data modeling, APIs, etc. Could be separate.
Benefits: The posting mentions benefits later: "Unleash Your Potential When you join Salesforce, you’ll be limitless..." then mentions benefits and resources, AI agents accelerate impact. 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. So we have benefits content.
Pay: The posting includes salary range: "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." So we have pay info.
Schedule: maybe travel ~25% of the time. Also maybe ongoing basis. Not explicit schedule like full-time. Could infer full-time. But we should only include schedule if posting actually states them. It mentions "You're excited to travel ~25% of the time, working directly alongside customers." That's schedule/travel expectation. Could treat as Schedule section.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. Remove accommodations, equal opportunity, etc. Also remove "Applications for this position will be accepted on an ongoing basis." maybe not needed but it's not boilerplate? It's about application instructions; we should remove application instructions. So drop that.
Also remove "Accommodations" etc.
Now craft HTML.
Structure:
About the role
... paragraphs from About The Role section (maybe two paragraphs).
Responsibilities
- ... each bullet from "What You'll Actually Be Building" and maybe earlier collaborative delivery etc.
Requirements
- ... from "You're Our Forward Deployed Engineer If…" list.
Qualifications
- Degree in Computer Science or related field.
Skills
- Fluent in at least one of Python, JavaScript/TypeScript, Java, or Apex.
- Hands‑on experience with LLMs and prompt engineering.
- Understanding of data modeling, APIs, and integration patterns.
- Ability to work with sales teams and customer architects.
- Experience shipping quality code and evaluating AI outputs with engineering rigor.
- Curiosity about evolving AI/data landscape, experimenting with new tools/models.
Benefits
- Time off programs
- Medical, dental, vision
- Mental health support
- Paid parental leave
- Life and disability insurance
- 401(k)
- Employee stock purchasing program
Pay
The typical base salary range for this position is $88,970 – $287,910 annually. In California, New York, and select cities in the metro areas of Boston, Chicago, Seattle, and Washington DC, the base pay range is $97,860 – $316,750 per year. (Base salary only; bonus, incentive, equity, or benefits not included.)
Schedule
Expect to travel approximately 25% of the time to work directly alongside customers.
We need to ensure we didn't repeat job title. No headings for Job ID.
Check for any duplicated content: we used bullet lists.
Make sure we didn't include any boilerplate like "Applications for this position will be accepted on an ongoing basis." Not included.
Check that we preserved all substantive info: The "About Salesforce" description at top maybe not needed; but it's substantive about company. However instruction: use headings for sections like About the role etc. Not required to include company description. Could we include it under About the role? Might be okay to include a brief paragraph about Salesforce as part of About the role? But the "About The Role" section already starts after company description. The company description could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the company description too. Where to put it? Could be a preceding paragraph before About the role heading, as a general intro. Since we cannot add extra headings not listed, we can just put a before the first heading. That's allowed. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can have leading
describing Salesforce.
Thus we will start with a paragraph summarizing the company description: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together..." etc. Keep it.
Let's extract that paragraph: The posting starts: "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. Job Category Sales Job Details 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 remove the first sentence about applying max 3 roles (that's application instruction). Also "Job Category Sales Job Details" maybe metadata; we can drop. Keep the substantive description about Salesforce.
Thus we will have a
with that description (starting from "Salesforce is the #1 AI CRM...").
Now after that, we put headings.
Let's craft final HTML.
Check for any leftover boilerplate: "Applications for this position will be accepted on an ongoing basis." removed. "Accommodations" removed. "Please note that Salesforce uses artificial intelligence (AI) tools..." removed. "Please see our Candidate Privacy Statement..." removed. "Posting Statement" etc removed. All EEO etc removed.
Now ensure we didn't miss any substantive content like "Builder Experience AI-Powered Development: Ship real customer solutions..." That's part of About the role; we can include in About the role paragraph.
Also "The Builder Experience AI-Powered Development: Ship real customer solutions, supported by best-in-class AI tools — Cursor, Claude, and Salesforce coding products like Vibes — embedded into your day-to-day workflow." etc.
We'll incorporate those into About the role paragraph(s).
Let's draft About the role paragraph(s):
We can combine multiple sentences into one or two paragraphs.
Paragraph 1: "Production experience required. Builder mindset non-negotiable. Salesforce is hiring Forward Deployed Engineers — experienced Technical Builders who design, build, and deploy agentic AI solutions directly inside enterprise customer environments. You'll work as part of a delivery team, partnering closely with a Deployment Strategist (Strategic Builder - a customer-facing advisor who shapes AI strategy and drives adoption) to co-build solutions that go live in production environments from day one. Engagements range from a single large strategic customer to multiple accounts simultaneously. The common thread is real code, real environments, and measurable business impact. This work spans configuration, customization, and full-stack deployment — shipping solutions customers depend on."
Paragraph 2: "The Builder Experience AI-Powered Development: Ship real customer solutions, supported by best-in-class AI tools — Cursor, Claude, and Salesforce coding products like Vibes — embedded into your day-to-day workflow. Collaborative Delivery: You'll work alongside Senior Forward Deployed Engineers and a Deployment Strategist. You'll own real components, benefit from structured mentorship from people who've shipped agentic systems at scale, and have a clear path to leading complex deliveries yourself. Frontier Access: Our agentic AI platform is evolving in real time. You'll work on capabilities most engineers won't touch for months — spanning Agentforce, data, platform, and headless architectures and your field insight will feed directly to the product teams building them. Continuous Innovation: You'll be expected to stay at the forefront, experimenting with emerging AI tools, models, and frameworks, and sharing what you learn with your team and customers."
Paragraph 3: "What You'll Actually Be Building Develop AI agents and experiences that take real actions for real organizations. Our solutions are in production at some of the largest enterprises on the planet. The work matters because the customers depend on it. Design agent intelligence: prompts, reasoning, tool calls, and integration with customer systems, leveraging our Agentic AI platform and current LLM techniques. Own technical components end-to-end: from architecture choice to deployed, validated, and observable in production. Build and integrate data pipelines on Salesforce Data 360, Snowflake, Databricks, and customer data platforms. Model the data, ship the pipeline, validate the output. Build and maintain agent performance dashboards and customer KPI reporting to track deployment health and business outcomes. Contribute to proofs-of-concept and MVPs that move from sketch to deployable in days, not months. Co-build alongside customers and partners, sharing best practices and enablement as you go. Leaving teams more capable after each engagement than before. Surface platform gaps, edge cases, and field insights to senior Engineers and the product team. Your real-world experience is the product feedback loop. Partner with the Deployment Strategist in your pod to translate customer business challenges into agentic solutions that actually ship."
That covers responsibilities as well; but we already have responsibilities section separate. To avoid duplication, we could put the detailed bullet list under Responsibilities and keep About the role more high-level. However we must preserve all substantive info; we can split.
Thus About the role could be the initial description up to "The Builder Experience..." maybe. Then Responsibilities list the "What You'll Actually Be Building" bullet points.
Let's do that.
Now Requirements: list from "You're Our
About the role
... paragraphs from About The Role section (maybe two paragraphs).
Responsibilities
- ... each bullet from "What You'll Actually Be Building" and maybe earlier collaborative delivery etc.
Requirements
- ... from "You're Our Forward Deployed Engineer If…" list.
Qualifications
- Degree in Computer Science or related field.
Skills
- Fluent in at least one of Python, JavaScript/TypeScript, Java, or Apex.
- Hands‑on experience with LLMs and prompt engineering.
- Understanding of data modeling, APIs, and integration patterns.
- Ability to work with sales teams and customer architects.
- Experience shipping quality code and evaluating AI outputs with engineering rigor.
- Curiosity about evolving AI/data landscape, experimenting with new tools/models.
Benefits
- Time off programs
- Medical, dental, vision
- Mental health support
- Paid parental leave
- Life and disability insurance
- 401(k)
- Employee stock purchasing program
Pay
The typical base salary range for this position is $88,970 – $287,910 annually. In California, New York, and select cities in the metro areas of Boston, Chicago, Seattle, and Washington DC, the base pay range is $97,860 – $316,750 per year. (Base salary only; bonus, incentive, equity, or benefits not included.)
Schedule
Expect to travel approximately 25% of the time to work directly alongside customers.
We need to ensure we didn't repeat job title. No headings for Job ID. Check for any duplicated content: we used bullet lists. Make sure we didn't include any boilerplate like "Applications for this position will be accepted on an ongoing basis." Not included. Check that we preserved all substantive info: The "About Salesforce" description at top maybe not needed; but it's substantive about company. However instruction: use headings for sections like About the role etc. Not required to include company description. Could we include it under About the role? Might be okay to include a brief paragraph about Salesforce as part of About the role? But the "About The Role" section already starts after company description. The company description could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the company description too. Where to put it? Could be a preceding paragraph before About the role heading, as a general intro. Since we cannot add extra headings not listed, we can just put abefore the first heading. That's allowed. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can have leading
describing Salesforce. Thus we will start with a paragraph summarizing the company description: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together..." etc. Keep it. Let's extract that paragraph: The posting starts: "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. Job Category Sales Job Details 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 remove the first sentence about applying max 3 roles (that's application instruction). Also "Job Category Sales Job Details" maybe metadata; we can drop. Keep the substantive description about Salesforce. Thus we will have a
with that description (starting from "Salesforce is the #1 AI CRM..."). Now after that, we put headings. Let's craft final HTML. Check for any leftover boilerplate: "Applications for this position will be accepted on an ongoing basis." removed. "Accommodations" removed. "Please note that Salesforce uses artificial intelligence (AI) tools..." removed. "Please see our Candidate Privacy Statement..." removed. "Posting Statement" etc removed. All EEO etc removed. Now ensure we didn't miss any substantive content like "Builder Experience AI-Powered Development: Ship real customer solutions..." That's part of About the role; we can include in About the role paragraph. Also "The Builder Experience AI-Powered Development: Ship real customer solutions, supported by best-in-class AI tools — Cursor, Claude, and Salesforce coding products like Vibes — embedded into your day-to-day workflow." etc. We'll incorporate those into About the role paragraph(s). Let's draft About the role paragraph(s): We can combine multiple sentences into one or two paragraphs. Paragraph 1: "Production experience required. Builder mindset non-negotiable. Salesforce is hiring Forward Deployed Engineers — experienced Technical Builders who design, build, and deploy agentic AI solutions directly inside enterprise customer environments. You'll work as part of a delivery team, partnering closely with a Deployment Strategist (Strategic Builder - a customer-facing advisor who shapes AI strategy and drives adoption) to co-build solutions that go live in production environments from day one. Engagements range from a single large strategic customer to multiple accounts simultaneously. The common thread is real code, real environments, and measurable business impact. This work spans configuration, customization, and full-stack deployment — shipping solutions customers depend on." Paragraph 2: "The Builder Experience AI-Powered Development: Ship real customer solutions, supported by best-in-class AI tools — Cursor, Claude, and Salesforce coding products like Vibes — embedded into your day-to-day workflow. Collaborative Delivery: You'll work alongside Senior Forward Deployed Engineers and a Deployment Strategist. You'll own real components, benefit from structured mentorship from people who've shipped agentic systems at scale, and have a clear path to leading complex deliveries yourself. Frontier Access: Our agentic AI platform is evolving in real time. You'll work on capabilities most engineers won't touch for months — spanning Agentforce, data, platform, and headless architectures and your field insight will feed directly to the product teams building them. Continuous Innovation: You'll be expected to stay at the forefront, experimenting with emerging AI tools, models, and frameworks, and sharing what you learn with your team and customers." Paragraph 3: "What You'll Actually Be Building Develop AI agents and experiences that take real actions for real organizations. Our solutions are in production at some of the largest enterprises on the planet. The work matters because the customers depend on it. Design agent intelligence: prompts, reasoning, tool calls, and integration with customer systems, leveraging our Agentic AI platform and current LLM techniques. Own technical components end-to-end: from architecture choice to deployed, validated, and observable in production. Build and integrate data pipelines on Salesforce Data 360, Snowflake, Databricks, and customer data platforms. Model the data, ship the pipeline, validate the output. Build and maintain agent performance dashboards and customer KPI reporting to track deployment health and business outcomes. Contribute to proofs-of-concept and MVPs that move from sketch to deployable in days, not months. Co-build alongside customers and partners, sharing best practices and enablement as you go. Leaving teams more capable after each engagement than before. Surface platform gaps, edge cases, and field insights to senior Engineers and the product team. Your real-world experience is the product feedback loop. Partner with the Deployment Strategist in your pod to translate customer business challenges into agentic solutions that actually ship." That covers responsibilities as well; but we already have responsibilities section separate. To avoid duplication, we could put the detailed bullet list under Responsibilities and keep About the role more high-level. However we must preserve all substantive info; we can split. Thus About the role could be the initial description up to "The Builder Experience..." maybe. Then Responsibilities list the "What You'll Actually Be Building" bullet points. Let's do that. Now Requirements: list from "You're Our