AI Builder Partner Solutions

Overview

This role engages before the buying decision, building working solutions against real customer challenges alongside the partners who will deliver them. You are a builder with a voice, shipping working things and explaining them in a way that makes other people more confident, more capable, and more willing to bet on the platform. You may come from forward‑deployed engineering, applied AI engineering, solutions engineering, technical consulting, partner engineering, technical founding, or hands‑on Salesforce engineering.

• Build inside the Sales Cycle – implement working Agentforce/Salesforce solution artifacts for partner teams to use with the customer during qualification, shaping, and decision phases; build with a production‑mindset for implementations that handle enterprise requirements such as identity, permissions, governed actions, observability, retrieval quality, and evaluation coverage.
• Create reusable accelerators that travel beyond the engagement – packaged metadata, deployment scripts, install guides, sample data, and test cases.
• Pair with partner engineers and customer technical teams to debug, refactor, and harden the implementation in proof‑of‑concepts & pilots.
• Produce clear walkthrough artifacts that increase Agentforce credibility and reuse – READMEs, partner delivery kits, technical posts, and recorded implementation walkthroughs.
• Present working implementations to experienced engineering audiences and translate fluently between technical and business stakeholders.
• Deliver live technical sessions or co‑builds with partner engineering teams that produce reusable artifacts or change their implementation approach.
• Build reusable assets before the meeting starts – published implementations, technical posts, Git Hub repos, accelerators, and field‑ready walkthroughs.
• Represent Salesforce engineering credibility in partner forums, technical sessions, and enablement moments where working proof matters.
• Turn repeatable field patterns into accelerators, solution assets, and Partner FDE Network resources.
• Surface product friction, missing capabilities, and field‑proven workarounds back to Agentforce, Data Cloud, Mule Soft, and Slack product and engineering teams.

Within 90 days, you have:

• Shipped at least one working Agentforce implementation inside an active sales cycle that visibly increased partner or customer confidence in Salesforce.
• Built or contributed to a reusable accelerator, repo, or solution kit that another team is already using or extending.
• Created a written or recorded explainer of a real implementation that other builders are reusing.
• Earned trust with at least one strong partner technical team through visible hands‑on work.
• Delivered at least one live technical session or co‑build with a partner engineering team that produced a reusable artifact or changed their implementation approach.

Within 6 months, you have:

• Influenced at least one strategic partner technical team's belief about Salesforce in the AI and data lane.
• Shipped a body of working implementations, reusable assets, and technical content that compounds across multiple engagements.
• Produced evidence of impact through partner reuse, reduced implementation time, active production agents, or measurable contribution to qualified opportunity progression.

• Hands‑on experience building on the Salesforce platform:
  Agentforce, Flow, Apex, Lightning Web Components, APIs, permissions, metadata, packaging, and deployment patterns.
• Practical experience building LLM‑powered applications: prompt design, context engineering, retrieval and RAG, tool calling and actions, evaluation, and debugging agent behavior.
• Hands‑on experience with agentic coding tools as a core part of your daily engineering workflow:
  Claude Code, Cursor, Git Hub Copilot, Windsurf, Codex, or equivalent.
• Comfortable building from day 1 in new environments; experience integrating enterprise systems through APIs, middleware, Mule Soft, Data Cloud, Slack, or equivalent technologies.
• Comfortable with at least one of Python, Type Script, JavaScript, Apex, or Java, and with Git Hub‑based development workflows.
• Low‑ego,…