Expert Agent Builder, Forward Deployed Engineering
Salesforce · San Francisco, CA · 1 mo ago
HybridSales$89k–$288k/yrFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Remove boilerplate etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not emit heading followed by filler/placeholder text like "commensurate with experience", etc. Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range info (Pay). It also includes benefits info (Benefits). It does not include schedule info (no mention of schedule). So we should not include Schedule heading. Also we need sections: About the role (we have About The Role content). Responsibilities: we have "Your Impact" bullet list (list of duties). Requirements: we have Required Qualifications. Qualifications: we have Preferred Qualifications. Skills: maybe we can combine? The instruction says use headings for those categories if content exists. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements heading, Preferred Qualifications to Qualifications heading. Skills maybe not explicitly separate; we could omit Skills heading if no specific skills list beyond qualifications. But we have many skill mentions inside qualifications; but we could still create Skills heading if we want to list skills extracted? However instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Requirements and Qualifications. We'll not create Skills unless there is explicit skills list. There's no separate skills list. So omit Skills.
Benefits: we have benefits description. Pay: we have salary range. Schedule: none.
We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Remove boilerplate etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not emit heading followed by filler/placeholder text like "commensurate with experience", etc. Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range info (Pay). It also includes benefits info (Benefits). It does not include schedule info (no mention of schedule). So we should not include Schedule heading. Also we need sections: About the role (we have About The Role content). Responsibilities: we have "Your Impact" bullet list (list of duties). Requirements: we have Required Qualifications. Qualifications: we have Preferred Qualifications. Skills: maybe we can combine? The instruction says use headings for those categories if content exists. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements heading, Preferred Qualifications to Qualifications heading. Skills maybe not explicitly separate; we could omit Skills heading if no specific skills list beyond qualifications. But we have many skill mentions inside qualifications; but we could still create Skills heading if we want to list skills extracted? However instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Requirements and Qualifications. We'll not create Skills unless there is explicit skills list. There's no separate skills list. So omit Skills.
Benefits: we have benefits description. Pay: we have salary range. Schedule: none.
We need to use - for any list of duties/requirements/benefits. For prose use
. For headings use
. Must not repeat job title as heading. Must not include metadata like Job Category etc. Must drop cookie/navigation/legal/EEO etc. Also drop "To get the best candidate experience..." etc. Also drop "Accommodations", "Posting Statement", etc? Those are boilerplate/legal; we should remove them. However we need to preserve ALL substantive information; but accommodations statement maybe considered boilerplate? It's about accommodations request; could be considered part of application instructions? The instruction says remove application instructions. Accommodations request form is part of application process; likely remove. Also the statement about AI tools usage 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 link maybe we can keep benefits description but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits description includes a link to benefits page; that's not boilerplate? It's a reference; but might be considered navigation? It's a URL; maybe we keep the description but drop the link? Safer to keep the description text but maybe drop the URL as it's navigation. However the instruction says remove navigation; the link is navigation. So we can omit the URL. Keep the benefits description text.
We need to preserve all substantive information: that includes the salary range details, benefits description, role description, responsibilities, required qualifications, preferred qualifications.
We must not invent or summarize away detail. So we need to keep the bullet points exactly as given? We can rephrase? Probably we should keep the substance but can rephrase slightly? Safer to keep the original phrasing but maybe wrap in
- . We'll extract the bullet points from "Your Impact" and from Required Qualifications and Preferred Qualifications.
Let's parse:
Your Impact bullet points (each starts with a bold phrase? Actually they are sentences starting with a capitalized phrase and colon? Eg:
Define Agentic Architecture: Design, architect, and hands-on develop the most difficult and bespoke agentic AI solutions that leverage the full power of the Agentforce platform and integrate with complex enterprise systems to solve critical customer challenges.
Build and Deploy Agent Systems: Apply extensive hands-on experience to integrate Large Language Models (LLMs) and expertly utilize agent-building and orchestration frameworks (e.g., Agentforce, LangChain, LlamaIndex) to implement and deploy complex agent-based solutions.
Lead Engineering Best Practices: Master our development process, culture, and code base, then define, improve, and enforce engineering best practices for code quality, scalability, and security across all deployed agentic solutions.
Drive Platform Customization: Utilize significant direct experience with the Salesforce platform to perform advanced configuration, customization, and complex development necessary to support and integrate agentic solutions.
Develop Data & Integration Solutions: Design strategic data models and build efficient processing pipelines to ensure data is ready, optimized, and secure for advanced AI applications.
Proactively Remove Technical Blockers: Identify, analyze, and directly resolve the most complex technical challenges during all phases of solution delivery, serving as the ultimate go-to expert for advanced agent orchestration and intricate data integration issues.
Drive Agentforce Innovation: Become the foremost expert in our innovative Agentforce platform, leading the development of custom intelligent agents and influencing future product enhancements based on deep field insights.
Undertake Continuous Learning: Maintain expertise in the latest AI advancements, both within the company and the wider industry, and proactively seek opportunities to integrate this knowledge for product and process innovation.
We'll keep each as
- .
Required Qualifications list: It's a paragraph with many items separated by periods. We need to turn into
- for any list of duties/requirements/benefits. So we should split into items. The required qualifications text:
"8+ years of experience in a hands-on, end-to-end delivery role for high-quality, scalable production solutions. Strong background in Computer Science or a related engineering discipline.Expert-level proficiency in one or more programming languages (e.g., Java, Apex, JavaScript, Python). Deep knowledge of object-oriented programming and databases.Experience building applications with modern web component frameworks like React, Angular, or LWC.Extensive hands-on experience building and deploying solutions with AI/LLM technologies, including:Integrating LLMs and applying advanced AI orchestration frameworks (e.g., LangChain, LlamaIndex).Developing custom agentic frameworks and systems.Deep understanding of machine learning and natural language processing.Expertise in prompt engineering, advanced RAG (Retrieval-Augmented Generation) strategies, and defining/automating rigorous evaluation and testing frameworks for LLM outputs and agentic workflows.Deep expertise in data modeling, processing, integration, and analytics, with demonstrable proficiency in enterprise data platforms (e.g., Salesforce Data Cloud, Snowflake, Databricks, BigQuery).Proven experience in automated testing, including unit and functional testing, and the ability to develop test strategies and design automation frameworks.Excellent interpersonal skills with the ability to collaborate effectively with people from various backgrounds and levels of expertise.Track record of innovation and problem solving to find creative technical solutions to new and unforeseen business problems.Ability to travel 30% of the time, as needed to customer sites."
We need to split each sentence into
- . Note there are some sentences that contain colon and sublist like "Extensive hands-on experience building and deploying solutions with AI/LLM technologies, including:" then subitems. We could keep as one
- with the colon and then maybe a nested
? The instruction: use - for any list of duties/requirements/benefits. It doesn't forbid nested lists. We could keep the main item and then a nested list for the subitems. But to keep simple, we could treat each bullet as separate
- and include the subitems as part of the same
- text. That's acceptable.
Similarly Preferred Qualifications list:
"Significant direct experience with the Salesforce platform, including advanced configuration, customization, and complex development.Experience contributing to open-source AI frameworks or libraries.Advanced Salesforce platform certifications (e.g., Platform Developer II, Application Architect, System Architect).Expert-level experience with Apex, Javascript, and/or Python coding languages in a professional setting.Experience with voice systems preferably in an agentic setting, but including text-to-speech and speech-to-text APIs.Appreciation for high quality user experiences that go beyond accomplishing the bare minimum."
We'll split sentences.
Benefits description: "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."
We need to keep the benefits description but drop the link (navigation). So we keep the sentence before the link. Could keep "More details about company benefits can be found at the following link." but that's navigation; maybe drop that sentence entirely. Keep the benefits list.
Pay: we have salary range info: "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."
We need to keep this as prose under Pay heading. Should we include the sentence about recruiter sharing more? That's substantive. Keep.
We must not create Schedule heading.
Now About the role: we have the paragraph after "About The Role". It includes multiple sentences. We'll put that in
under
About the role
.
Now we need to ensure we don't duplicate content. Also we need to remove any duplicated lines (like repeated "About Salesforce" etc). We'll ignore those.
Now produce HTML fragment:
About the role
... (the paragraph)
Responsibilities
- Define Agentic Architecture: Design, architect, and hands-on develop the most difficult and bespoke agentic AI solutions that leverage the full power of the Agentforce platform and integrate with complex enterprise systems to solve critical customer challenges.
- Build and Deploy Agent Systems: Apply extensive hands-on experience to integrate Large Language Models (LLMs) and expertly utilize agent-building and orchestration frameworks (e.g., Agentforce, LangChain, LlamaIndex) to implement and deploy complex agent-based solutions.
- Lead Engineering Best Practices: Master our development process, culture, and code base, then define, improve, and enforce engineering best practices for code quality, scalability, and security across all deployed agentic solutions.
- Drive Platform Customization: Utilize significant direct experience with the Salesforce platform to perform advanced configuration, customization, and complex development necessary to support and integrate agentic solutions.
- Develop Data & Integration Solutions: Design strategic data models and build efficient processing pipelines to ensure data is ready, optimized, and secure for advanced AI applications.
- Proactively Remove Technical Blockers: Identify, analyze, and directly resolve the most complex technical challenges during all phases of solution delivery, serving as the ultimate go-to expert for advanced agent orchestration and intricate data integration issues.
- Drive Agentforce Innovation: Become the foremost expert in our innovative Agentforce platform, leading the development of custom intelligent agents and influencing future product enhancements based on deep field insights.
- Undertake Continuous Learning: Maintain expertise in the latest AI advancements, both within the company and the wider industry, and proactively seek opportunities to integrate this knowledge for product and process innovation.
Requirements
. For headings use
. Must not repeat job title as heading. Must not include metadata like Job Category etc. Must drop cookie/navigation/legal/EEO etc. Also drop "To get the best candidate experience..." etc. Also drop "Accommodations", "Posting Statement", etc? Those are boilerplate/legal; we should remove them. However we need to preserve ALL substantive information; but accommodations statement maybe considered boilerplate? It's about accommodations request; could be considered part of application instructions? The instruction says remove application instructions. Accommodations request form is part of application process; likely remove. Also the statement about AI tools usage 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 link maybe we can keep benefits description but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits description includes a link to benefits page; that's not boilerplate? It's a reference; but might be considered navigation? It's a URL; maybe we keep the description but drop the link? Safer to keep the description text but maybe drop the URL as it's navigation. However the instruction says remove navigation; the link is navigation. So we can omit the URL. Keep the benefits description text. We need to preserve all substantive information: that includes the salary range details, benefits description, role description, responsibilities, required qualifications, preferred qualifications. We must not invent or summarize away detail. So we need to keep the bullet points exactly as given? We can rephrase? Probably we should keep the substance but can rephrase slightly? Safer to keep the original phrasing but maybe wrap in
- for any list of duties/requirements/benefits. So we should split into items. The required qualifications text: "8+ years of experience in a hands-on, end-to-end delivery role for high-quality, scalable production solutions. Strong background in Computer Science or a related engineering discipline.Expert-level proficiency in one or more programming languages (e.g., Java, Apex, JavaScript, Python). Deep knowledge of object-oriented programming and databases.Experience building applications with modern web component frameworks like React, Angular, or LWC.Extensive hands-on experience building and deploying solutions with AI/LLM technologies, including:Integrating LLMs and applying advanced AI orchestration frameworks (e.g., LangChain, LlamaIndex).Developing custom agentic frameworks and systems.Deep understanding of machine learning and natural language processing.Expertise in prompt engineering, advanced RAG (Retrieval-Augmented Generation) strategies, and defining/automating rigorous evaluation and testing frameworks for LLM outputs and agentic workflows.Deep expertise in data modeling, processing, integration, and analytics, with demonstrable proficiency in enterprise data platforms (e.g., Salesforce Data Cloud, Snowflake, Databricks, BigQuery).Proven experience in automated testing, including unit and functional testing, and the ability to develop test strategies and design automation frameworks.Excellent interpersonal skills with the ability to collaborate effectively with people from various backgrounds and levels of expertise.Track record of innovation and problem solving to find creative technical solutions to new and unforeseen business problems.Ability to travel 30% of the time, as needed to customer sites." We need to split each sentence into
- . Note there are some sentences that contain colon and sublist like "Extensive hands-on experience building and deploying solutions with AI/LLM technologies, including:" then subitems. We could keep as one
- with the colon and then maybe a nested
- ? The instruction: use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We could keep the main item and then a nested list for the subitems. But to keep simple, we could treat each bullet as separate
- and include the subitems as part of the same
- text. That's acceptable.
Similarly Preferred Qualifications list:
"Significant direct experience with the Salesforce platform, including advanced configuration, customization, and complex development.Experience contributing to open-source AI frameworks or libraries.Advanced Salesforce platform certifications (e.g., Platform Developer II, Application Architect, System Architect).Expert-level experience with Apex, Javascript, and/or Python coding languages in a professional setting.Experience with voice systems preferably in an agentic setting, but including text-to-speech and speech-to-text APIs.Appreciation for high quality user experiences that go beyond accomplishing the bare minimum."
We'll split sentences.
Benefits description: "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."
We need to keep the benefits description but drop the link (navigation). So we keep the sentence before the link. Could keep "More details about company benefits can be found at the following link." but that's navigation; maybe drop that sentence entirely. Keep the benefits list.
Pay: we have salary range info: "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."
We need to keep this as prose under Pay heading. Should we include the sentence about recruiter sharing more? That's substantive. Keep.
We must not create Schedule heading.
Now About the role: we have the paragraph after "About The Role". It includes multiple sentences. We'll put that in
under
About the role
. Now we need to ensure we don't duplicate content. Also we need to remove any duplicated lines (like repeated "About Salesforce" etc). We'll ignore those. Now produce HTML fragment:About the role
... (the paragraph)
Responsibilities
- Define Agentic Architecture: Design, architect, and hands-on develop the most difficult and bespoke agentic AI solutions that leverage the full power of the Agentforce platform and integrate with complex enterprise systems to solve critical customer challenges.
- Build and Deploy Agent Systems: Apply extensive hands-on experience to integrate Large Language Models (LLMs) and expertly utilize agent-building and orchestration frameworks (e.g., Agentforce, LangChain, LlamaIndex) to implement and deploy complex agent-based solutions.
- Lead Engineering Best Practices: Master our development process, culture, and code base, then define, improve, and enforce engineering best practices for code quality, scalability, and security across all deployed agentic solutions.
- Drive Platform Customization: Utilize significant direct experience with the Salesforce platform to perform advanced configuration, customization, and complex development necessary to support and integrate agentic solutions.
- Develop Data & Integration Solutions: Design strategic data models and build efficient processing pipelines to ensure data is ready, optimized, and secure for advanced AI applications.
- Proactively Remove Technical Blockers: Identify, analyze, and directly resolve the most complex technical challenges during all phases of solution delivery, serving as the ultimate go-to expert for advanced agent orchestration and intricate data integration issues.
- Drive Agentforce Innovation: Become the foremost expert in our innovative Agentforce platform, leading the development of custom intelligent agents and influencing future product enhancements based on deep field insights.
- Undertake Continuous Learning: Maintain expertise in the latest AI advancements, both within the company and the wider industry, and proactively seek opportunities to integrate this knowledge for product and process innovation.
Requirements