Salesforce Agentforce Developer Job Description

A Salesforce Agentforce Developer turns a business process into an AI agent that can act inside Salesforce. Where a general Salesforce developer writes code that runs the same way every time, this developer builds software that reads a request in plain language, decides what the person wants, and then picks from a set of approved actions to get it done. The deliverable is a working agent: a service agent that checks an order and processes a return, an employee agent that answers HR policy questions from approved articles, or a sales agent that drafts follow-ups grounded in the opportunity record.

The first job is scoping. An agent is divided into subagents, each responsible for one area such as order status, billing disputes or appointment changes. Each subagent gets instructions, a list of the actions it may call, and rules for when to hand off to a human. Poor scoping shows up quickly in testing: requests land in the wrong subagent, or one subagent tries to do everything.

The second job is logic. Salesforce's Agent Script language is the language for building agents in Agentforce Builder, and it mixes natural-language instructions for conversational tasks with programmatic expressions for business rules. In script, the developer uses expressions for if/else conditions, transitions and variables, and to select subagents and actions. That split is the core design decision in the role: what can be left to the language model's judgment, and what must run as fixed logic because it touches refunds, eligibility or compliance.

The third job is actions, the building blocks that let an agent perform tasks and work with data. Developers create them from Apex methods annotated with @InvocableMethod, from Apex REST classes, from AuraEnabled controller methods, and from named SOQL queries, alongside flows and prompt templates. A well-built action has a narrow purpose, clear input and output types, and error messages the agent can explain to the user. Lightning Types can give an action a richer interface for complex inputs and outputs.

The fourth job is grounding. In Prompt Builder, prompt templates pull CRM data in through merge fields that reference record fields, flows, related lists and Apex, so the model answers from the customer's actual account rather than general knowledge. For larger bodies of content, the developer sets up retrieval from Data 360 so the agent can cite knowledge articles and other company content.

The last job is release engineering. In Agentforce DX, agents are metadata like any other Salesforce customization, managed with Salesforce CLI commands and a VS Code extension. The Agent Script file, with the extension .agent, fully describes an agent and serves as its blueprint, so it can live in Git, go through code review, and move from scratch orgs to sandboxes to production. Day to day, the developer works with Salesforce admins, data architects, security reviewers, and the service or sales leaders who own the process the agent takes over.

The useful background is a working command of the platform: Apex, SOQL, Flow, the security model of profiles, permission sets and sharing rules, and enough Lightning Web Components to build an interface when an action needs one. A bachelor's degree in computer science, information systems or a related field is a typical starting point, and a record of shipped Salesforce work matters in interviews. As a rough guide, expect two to four years of Salesforce development before leading agent builds.

On top of that platform base sit the agent-specific skills. Prompt writing matters, but in this job it is closer to specification writing: instructions must be short, testable, and free of conflicts between subagents. The developer needs to think about failure modes the way a QA engineer does, writing test cases for ambiguous requests, missing data, and users who try to push the agent outside its scope. Comfort with data modeling helps, because retrieval quality depends on how knowledge articles and records are structured in Data 360 before an agent ever sees them.

Release discipline is the other half. Salesforce treats agents as metadata, so the developer should already be comfortable with Salesforce DX projects, scratch orgs, sandboxes, Git branching and a CI pipeline that deploys metadata. Salesforce also offers an Agentforce Python SDK for programmatic agent creation and management, which helps on teams that automate setup across many orgs.

Credentials are issued by Salesforce through Trailhead. Salesforce describes the Salesforce Certified Agentforce Specialist candidate as proficient in configuring and managing AI agents and prompt templates, and says the exam targets administrators, developers and architects who configure Prompt Builder for grounding and use Data 360 for retrieval. The exam has 60 multiple-choice questions and up to five unscored questions, allows 105 minutes, and costs $200. Salesforce Certified Platform Developer has no prerequisite certification, while Salesforce Certified Platform Developer II requires the Platform Developer credential first. Together they show the Apex depth that custom actions require.

Soft skills are concrete here. The developer has to interview the people who do a process today, such as support agents or HR coordinators, and turn their judgment calls into instructions and escalation rules. They also have to explain to a business owner why an agent should refuse certain requests, and document what each action is allowed to change in the org so security reviewers can sign off.

BLS does not count Agentforce developers as an occupation, and no federal projection exists for the title. The work is filed under software developers, a group BLS counted at 1,687,890 workers nationally in May 2025. The computer systems design and related services industry employed 515,410 of them, with a median wage of $132,050. Those figures describe the broad occupation; they say nothing specific about how many people build agents on Salesforce.

The platform underneath the job keeps changing its vocabulary. Beginning in April 2026, Salesforce's documentation started calling agent topics subagents, with no change in how they work, and its guides now mix the new and previous terms during the transition. A developer in this role should expect to relearn names, metadata types and recommended patterns on Salesforce's release schedule, which makes reading release notes part of the job rather than a side task.

Cost is a design constraint, not only a licensing question. Salesforce's Flex Credits rate card, updated Nov. 18, 2025, says customers consume Flex Credits at a multiplier rate based on usage type, and Agentforce actions are a usage type consumed by all product types. That ties a developer's choices, such as how many actions an agent chains per conversation, directly to what the company pays. Developers who can show a business owner both resolution quality and consumption per conversation give the company a clearer case for expanding an agent.

The agents these developers build are already changing other jobs, and the shift is visible inside Salesforce itself. In September 2025, CNBC reported that Salesforce had cut 4,000 customer support roles, with its chief executive saying support headcount went from 9,000 to about 5,000 while discussing how AI had helped reduce headcount. For a developer, that shows the business case an agent project can carry: absorbing routine requests, judged on whether escalations, error rates and customer outcomes hold up after launch.

Career paths branch in three directions. Some developers move toward Salesforce technical architecture, owning the data model, integration patterns and security review for every agent in an org. Others become delivery leads at consulting partners, running agent rollouts for several clients at once. A third group moves into broader AI engineering roles, carrying their experience with evaluation, grounding and action design to platforms outside Salesforce. In each case, a portfolio of agents that reached production, with tests and measured results, gives a hiring manager something concrete to review.

The main risk for the title is that it narrows to one vendor. Skills tied to Agent Script and Salesforce metadata are specific to Salesforce, so developers who also keep general software skills, such as API design, testing practice and data engineering, keep more options open if a company changes platforms.

Dear Hiring Manager,

I am applying for the Salesforce Agentforce Developer position on your customer platform team. For the past three years I have built on Salesforce for a regional home services company, and for the last year my main assignment has been our first service agent, which now handles appointment changes and warranty questions for homeowners.

That project taught me where agent work is hard. The first version tried to answer everything, and it routed billing disputes into the scheduling flow. I rebuilt it with four narrow subagents, moved the warranty eligibility rules out of the instructions and into scripted conditions, and wrote two Apex invocable actions that check coverage dates and open a case with the right queue. I added a test suite of about one hundred conversations, including vague requests and customers who ask for refunds the agent is not allowed to grant, and we run it before every deployment.

I also care about the parts of the job that happen after launch. Each week I read a sample of transcripts with our support lead, mark the conversations that should have gone to a person sooner, and adjust the handoff rules. I keep every agent change in Git and deploy through our pipeline, so we can roll back an instruction change as easily as an Apex change.

Your posting mentions grounding agents in knowledge articles. I have spent time cleaning up our article library so retrieval returns one clear answer instead of three conflicting ones, and I would bring that same attention to your content.

I hold the Salesforce Certified Platform Developer credential and am preparing for the Agentforce Specialist exam. I would welcome the chance to talk about the agents on your roadmap.

Sincerely, Jordan Ellis