Value Acceleration Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "To get the best candidate experience..." line (application advice). Also remove "Accommodations" etc? That's legal/EEO? It's about accommodations request form, maybe considered legal boilerplate; we should remove. Also remove "Posting Statement" etc. Also remove "Salesforce is an equal opportunity employer..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "At Salesforce, we believe in equitable compensation practices..."? That's part of compensation description; we need to keep pay info. The posting includes salary range details. So we need to keep that under Pay section. We need to extract sections: - About the role: The overview paragraphs after "Overview Of The Role". Should include description of role, mission, etc. Must preserve all substantive info, not summarizing away detail. So we need to copy the text exactly? Probably we can keep paragraphs as is, but we must not include boilerplate. The "Overview Of The Role" section includes: "Global supply chains still rely on slow, manual processes - email, spreadsheets, and fragmented data. The economy moves fast but supply chains don’t, creating an inefficiency that affects the $13T of goods shipped annually and is one of the largest untapped opportunities in modern enterprise. Agentforce for Supply Chain is reimagining the supply chain with an AI-powered platform for designing, automating, and running end-to-end business processes. Customers are clamoring for more, rapidly expanding their use cases as we enter an exhilarating growth phase. We are looking for an early-career, highly driven Value Acceleration Engineer to join us for a unique, high-impact "tour of duty." In this forward-deployed role, you will be on the front lines of our post-sales engine, embedding directly with our enterprise customers and Customer Success teams to bring AI concepts to life and compress their time-to-value. You will be the technical muscle that unblocks implementations, designs agentic workflows, and helps gets 1-2 critical business processes live in production during an intensive 90-day window. This role is designed as a rotational "Field Residency." After spending your first 6-12 months mastering production edge cases, developing deep customer empathy, and learning the real-world complexities our customers face, you will rotate back into a core AFO product and engineering pod. You will bring those invaluable frontline insights with you to help us build the paved pathways of our future platform." We need to keep that as prose in

tags. - Responsibilities: The bullet list under Responsibilities includes Day-to-Day & Project Execution and Long-Term Goals & Strategic Impact and Experience Gained & Impact Made? Actually those are subheadings within Responsibilities? The posting shows: Responsibilities Day-to-Day & Project Execution - Work hands-on with strategic customers to design and build "Day 1" agentic workflows and blueprints. - Participate in 90-day Value Acceleration programs, acting as the technical builder to get 1-2 primary use cases live in production. - Quickly troubleshoot bugs, unblock implementation hurdles, and solve usability or security asks to drastically reduce Time-to-First-Value (TTFV). - Facilitate working sessions with customers and deployment strategists, bridging the gap between business needs and technical feasibility. - Enable and support implementation partners to take over ongoing build work post-engagement. Long-Term Goals & Strategic Impact - Document design decisions and build patterns from your bespoke customer engagements to feed our use case library and core product roadmap. - Serve as the feedback loop between the customer edge and mainline engineering, translating real-world friction into scalable product features. - Successfully graduate from your forward-deployed rotation, transitioning your hands-on deployment expertise into a permanent builder role within the core product pods. Experience Gained & Impact Made Experience Gained: You will receive a masterclass in real-world software deployment. Through our Value Acceleration Residency curriculum, you will move rapidly from shadowing senior team members to independently owning end-to-end customer projects. You will learn how large enterprise supply chains operate on the ground, master customer empathy, and build a unique techno-functional skillset. Impact Made: Your work will directly accelerate time-to-value for our most strategic accounts, clearing onboarding blockers, and setting the stage for massive account expansion. You will be the critical link that turns a signed deal into a highly successful, live deployment. We need to treat these as list items under Responsibilities? The instruction: Use

• for any list of duties/requirements/benefits. So we should convert each bullet point to
• . The subheadings like "Day-to-Day & Project Execution" could be maybe a

  or we could treat as heading inside responsibilities? But we only have

  for section headings. Inside a section we can have

  prose and

  . The subheadings could be

  bold? But we cannot add arbitrary tags besides those specified? The instruction only says use

  for section headings,

  • for any list,

    for prose. It doesn't forbid other tags, but to be safe we can just treat subheadings as prose

    (maybe with strong?). But we should preserve the text. Could embed them as

    Day-to-Day & Project Execution

    then list. However strong tag not specified but maybe okay. Safer to just put them as

    plain text. Thus Responsibilities section will have

    prose for subheadings and then

    for each bullet list. But we also have "Experience Gained & Impact Made" which is prose not list. We'll treat as

    . - Requirements / Qualifications: The posting has "Required Qualifications" and "Preferred Qualifications". We need to include a section for Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We can choose "Requirements" for required qualifications, and maybe "Preferred Qualifications" could be under Skills? But better to have a "Qualifications" section that includes both required and preferred? However we must not invent sections with filler. We have real content for required qualifications and preferred qualifications. We could make two subsections: maybe under Qualifications we have required and preferred as

    or

    . But we need to follow instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate headings for Requirements and Qualifications? That seems redundant. Probably we should have one "Qualifications" section containing both required and preferred. But we have also "Skills" maybe separate. The posting includes "Required Qualifications" list and "Preferred Qualifications" list. We could treat required as

    under Qualifications, and preferred as another
    maybe under Skills? But the instruction says we can have Skills section for skills. The posting includes skills like "Experience with modern programming languages (e.g., Go, Python, JavaScript) and a proven ability to pick up new technologies quickly." etc. Those are more like preferred qualifications. Could treat them as Skills. Thus we can have: -

    Requirements

    with required qualifications list. -

    Skills

    with preferred qualifications list (or maybe also include some skills from required like builder's spirit etc). But we need to preserve all info. Better: Have Requirements for required qualifications, Skills for preferred qualifications (including technical skills, experience). Then Benefits, Pay, Schedule. Check if posting includes Benefits: It mentions benefits 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 earlier: "Unleash Your Potential 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." That's generic but we have specific list. So we should include Benefits section with that list. Pay: The posting includes salary range details: "The typical base salary range for this position is $117,200 - $223,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $141,200 - $246,000 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." Also earlier mention "At Salesforce, we believe in equitable compensation practices..." but we keep the salary range. Schedule: Not mentioned explicitly. No schedule info. So we should NOT create a Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not include empty sections. Now we need to strip boilerplate: Remove lines like "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." Also remove "Job Category Software Engineering". Also remove "Job Details". Also remove "About Salesforce" maybe? Actually "About Salesforce" is part of the overview? The posting starts with "About Salesforce Salesforce is the #1 AI CRM..." That's generic company description; could be considered boilerplate? It's not about the role. Might be considered part of "About the role"? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Salesforce" paragraph is generic but still part of posting. Should we keep? It's not about the role but it's still content. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's company overview. Might be okay to keep. But the "About Salesforce" is not specific to the role; still it's part of posting. I'd keep it as part of About the role? However we already have an "Overview Of The Role" section. The "About Salesforce" could be placed before that as part of About the role? The instruction says use

    for section headings (e.g. About the role, Responsibilities...). So we could have an About the role section that includes the company overview plus overview of role. But we must not repeat job title as heading. So we can put the company overview as prose under About the role. Thus About the role section will contain: - The "About Salesforce" paragraph(s). - Then the "Overview Of The Role" paragraph(s). We need to ensure we don't duplicate lines. There's also "Overview Of The Role" heading; we should not repeat that as a heading inside the section (since we already have About the role heading). We'll just include the prose. Now let's extract the exact text. From posting: "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." -> remove. "Job Category Software Engineering" -> remove. "Job Details" -> remove. "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