Lead Member of Technical Staff - AI Research

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "To get the best candidate experience..." line (application advice). Also remove "Accommodations" maybe? That's not a required heading but could be considered boilerplate? It's about accommodations request form; might be considered legal/EEO? Probably remove. Also remove "Posting Statement" etc. Also remove "Salesforce is an equal opportunity employer..." etc. Also remove "Know your rights..." etc. Also remove "In the United States, compensation offered will be determined..." etc. But we need to keep Pay section if salary range is given. The posting includes salary range: typical base salary range $172,500 - $260,100 annually; in select cities within SF and NYC metro area, base salary range $207,800 - $285,800 annually. So we should include Pay section with that info. Benefits: The posting mentions 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 to benefits page. So we can include Benefits section with that list. Schedule: Not mentioned explicitly. No schedule info. So we should not include Schedule section. About the role: There's a paragraph about Salesforce, Agentforce, etc. We need to extract substantive content about the role. The posting includes "About Salesforce" description, then "Agentforce is the future of AI, and you are the future of Salesforce." Then description of responsibilities: "ware engineers, product managers and solution engineers closely to design, implement and iterate agentic AI systems with customers." There's a typo "ware engineers" maybe meant "Work with engineers". We'll keep as is but it's substantive. Also "With your strong technical competence, strategic thinking and customer engagement, you will innovate at the frontier of the field, having the opportunity to create new solutions and define new categories of product with meaningful impact to Salesforce customers and beyond." Also list of desired qualifications: "We are looking for candidates who Has exceptional engineering skills.Has deep ML knowledge with meaningful implementation track records. Prioritize deep and strategic thinking.Has dedication, patience and resilience to build exceptional product experience. Collaborative and win with teams.Proactive and bias to action, comfortable in fast-pacing environment. Competitive coding winner (ACM-ICPC, etc). Startup founders in agentic AI, LLM, area (e.g., YC backed startup)" Then sections: Programming & Systems, Agentic / LLM Systems, Machine Learning & AI, Infrastructure & Deployment, etc. Those are requirements/skills. We need to structure into sections: About the role (maybe a brief paragraph summarizing role), Responsibilities (list of duties), Requirements (maybe qualifications), Skills (maybe technical skills), Benefits, Pay. We must not invent or summarize away detail; preserve all substantive information. So we need to include all the bullet points from the posting as list items under appropriate sections. We need to decide categorization: The posting has sections: "Programming & Systems:", "Agentic / LLM Systems", "Machine Learning & AI", "Infrastructure & Deployment". Also earlier bullet list of personal attributes. Could treat those as Requirements or Skills. We'll create: - About the role: paragraph describing the role and mission. - Responsibilities: list of duties: design, implement and iterate agentic AI systems with customers; innovate at frontier; create new solutions; define new categories of product; contribute to building/maintaining shared system context; critically evaluate code (Human or AI-generated) for correctness, quality, security, performance; build and ship high-quality production-grade software using modern engineering practices, with AI as core part of development workflow; design and orchestrate complex systems where AI agents integrate seamlessly into human workflows; etc. We need to extract all responsibilities from the text. Let's parse the posting: "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. ware engineers, product managers and solution engineers closely to design, implement and iterate agentic AI systems with customers. With your strong technical competence, strategic thinking and customer engagement, you will innovate at the frontier of the field, having the opportunity to create new solutions and define new categories of product with meaningful impact to Salesforce customers and beyond. We are looking for candidates who Has exceptional engineering skills.Has deep ML knowledge with meaningful implementation track records. Prioritize deep and strategic thinking.Has dedication, patience and resilience to build exceptional product experience. Collaborative and win with teams.Proactive and bias to action, comfortable in fast-pacing environment. Competitive coding winner (ACM-ICPC, etc). Startup founders in agentic AI, LLM, area (e.g., YC backed startup)Programming & Systems:Strong proficiency in Python; solid experience with C++ and/or JavaBuild and ship high-quality, production-grade software using modern engineering practices, with AI as a core part of your development workflow by pushing the boundaries of AI development tools to deliver secure, optimized, and high-quality code.Design and orchestrate complex systems where AI agents integrate seamlessly into human workflows, driving efficiency and innovation at scale.Contribute to building and maintaining the shared system context, an explicit repository of system designs, constraints, and standards that enables AI to operate accurately and reliably.Critically evaluate code (Human or AI-generated) for correctness, quality, security, and performanceStrong software engineering fundamentals (data structures, algorithms, system design)Experience building production-quality systems Agentic / LLM SystemsPractical experience with LLMs and agentic workflows (tool use, planning, memory, multi-step reasoning)Experience building end-to-end AI agents or complex AI-driven applicationsFamiliarity with prompting, orchestration, and evaluation for LLM-based systemsMachine Learning & AIHands-on experience with deep learning frameworks Strong understanding of ML fundamentalsExperience implementing and debugging model training, evaluation, and inference pipelinesInfrastructure & DeploymentExperience deploying ML systems using Docker and cloud platforms (AWS, GCP, or Azure)Familiarity with distributed training or inference and performance optimizationA demonstrated, genuine AI-first approach to engineering. Using AI to move faster, build fluency across the stack, and contribute well beyond your core specialty.Experience using AI tools (e.g., Claude Code, GitHub Copilot, Codex, Cursor, etc.) in development workflowsAdvanced prompt engineering skills and the ability to write precise, structured prompts and cultivate the system context that makes AI outputs reliable, secure, and production-ready." We need to separate responsibilities vs requirements. Responsibilities likely: design, implement and iterate agentic AI systems with customers; innovate at frontier; create new solutions; define new categories of product; build and ship high-quality production-grade software using modern engineering practices, with AI as core part of development workflow; design and orchestrate complex systems where AI agents integrate seamlessly into human workflows; contribute to building and maintaining shared system context; critically evaluate code (Human or AI-generated) for correctness, quality, security, performance. Also maybe "With your strong technical competence, strategic thinking and customer engagement, you will innovate at the frontier of the field..." that's more expectation. We'll list responsibilities as bullet list. Requirements/Skills: The bullet list of personal attributes: exceptional engineering skills, deep ML knowledge with meaningful implementation track records, prioritize deep and strategic thinking, dedication, patience and resilience to build exceptional product experience, collaborative and win with teams, proactive and bias to action, comfortable in fast-pacing environment, competitive coding winner (ACM-ICPC, etc), startup founders in agentic AI, LLM, area (e.g., YC backed startup). Then technical skills grouped under headings. We could combine Requirements and Skills sections: maybe Requirements for qualifications (education/experience) and Skills for technical abilities. But the posting doesn't separate clearly; we can put all under Requirements or Skills. The instruction says use sections only when posting has real specific content. We can have both Requirements and Skills if we can differentiate. We could treat "Requirements" as the personal attributes and baseline qualifications (like exceptional engineering skills, deep ML knowledge, etc.) and "Skills" as the technical proficiencies (Programming & Systems, Agentic/LLM Systems, ML/AI, Infrastructure & Deployment). That seems reasonable. Thus: - About the role: paragraph(s) describing role and mission. - Responsibilities: bullet list of duties. - Requirements: bullet list of personal/behavioral requirements. - Skills: bullet list of technical skills grouped maybe under subheadings? But we must use

• for any list. We could have nested lists? Probably just flat list. But we could keep headings inside
• ? Not ideal. Better to keep separate sections for each skill category? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add custom headings like "Programming & Systems". So we need to flatten all skills into a single list under Skills section. That's okay; we just list each skill as a bullet. Thus Skills section will contain all technical proficiencies: Strong proficiency in Python; solid experience with C++ and/or Java; Build and ship high-quality, production-grade software using modern engineering practices, with AI as a core part of your development workflow by pushing the boundaries of AI development tools to deliver secure, optimized, and high-quality code; Design and orchestrate complex systems where AI agents integrate seamlessly into human workflows, driving efficiency and innovation at scale; Contribute to building and maintaining the shared system context, an explicit repository of system designs, constraints, and standards that enables AI to operate accurately and reliably; Critically evaluate code (Human or AI-generated) for correctness, quality, security, and performance; Strong software engineering fundamentals (data structures, algorithms, system design); Experience building production-quality systems; Practical experience with LLMs and agentic workflows (tool use, planning, memory, multi-step reasoning); Experience building end-to-end AI agents or complex AI-driven applications; Familiarity with prompting, orchestration, and evaluation for LLM-based systems; Hands-on experience with deep learning frameworks; Strong understanding of ML fundamentals; Experience implementing and debugging model training, evaluation, and inference pipelines; Experience deploying ML systems using Docker and cloud platforms (AWS, GCP, or Azure); Familiarity with distributed training or inference and performance optimization; A demonstrated, genuine AI-first approach to engineering. Using AI to move faster, build fluency across the stack, and contribute well beyond your core specialty.; Experience using AI tools (e.g., Claude Code, GitHub Copilot, Codex, Cursor, etc.) in development workflows; Advanced prompt engineering skills and the ability to write precise, structured prompts and cultivate the system context that makes AI outputs reliable, secure, and production-ready. But note some of these overlap with responsibilities; we might duplicate. To avoid duplication, we should separate: responsibilities are actions you will do; skills are abilities/experience you need. Some items like "Build and ship high-quality, production-grade software..." could be both responsibility and skill. We need to decide. Better to treat responsibilities as the tasks you will perform: design, implement and iterate agentic AI systems with customers; innovate at frontier; create new solutions; define new categories of product; contribute to building/maintaining shared system context; critically evaluate code; etc. Skills as the technical proficiencies: proficiency in Python, C++/Java; experience with LLMs, agentic workflow