Salesforce Administrator Job Description Template 2026

Last updated: August 20, 2026

By Gregg Flecke, Senior Talent Acquisition Partner, KORE1

A Salesforce administrator job description should name the org’s size, the automation the admin will own, whether the seat is solo or on a team, the current credential names, and a 2026 base band of $85,000 to $135,000.

Most of the templates you will find for this role were written before the job changed. They still ask for a “Salesforce Certified Administrator.” That credential was renamed in the fall of 2025. They still list Workflow Rules and Process Builder as core duties, and Salesforce ended support for Workflow Rules on December 31, 2025. A posting built from one of those templates reads, to a good admin, like a company that has not opened Setup in three years. They keep scrolling.

I have spent close to thirty years placing technical people, most of it inside financial services, insurance, HR outsourcing, and healthcare. Those are the industries where Salesforce quietly became the system of record for revenue, and where a weak admin hire shows up six months later as a data-quality problem nobody can trace. Six months. Sometimes longer. I write our compensation and hiring guides for KORE1’s IT staffing services practice, so I read a lot of these postings. Most of them describe a job that no longer exists.

Fair warning about my angle here. KORE1 runs a Salesforce staffing desk and we only get paid when somebody actually hires. You can lift the template below, post it yourself, never call us, and I will have done my job. Plenty of readers do exactly that. Genuinely fine by me. There are also two places further down where I tell you to spend less money than you were planning to, and I left both in.

The Certification on Your Job Description Was Renamed

Salesforce renamed 35 credentials in fall 2025. The admin badge you are asking for now reads Salesforce Certified Platform Administrator. What everyone still calls Advanced Administrator is Platform Administrator II.

Sounds cosmetic. It really isn’t.

Every certified admin in the market watched that rename happen, sat through the maintenance module, and updated their LinkedIn. Whole ecosystem. Same quarter. When your posting asks for a credential under its retired name, you have told them the posting is old, or copied, or both. Candidates in mature ecosystems read that signal instantly. Salesforce people especially. The whole culture of that community runs on badges and release names, and getting the badge name wrong is the tell.

The rename is the surface. Salesforce also rebuilt the exam under it, and the rebuild is the part worth your attention.

The updated Platform Administrator exam went live on December 15, 2025. Configuration and Setup dropped from 20% of the exam to 15%. Object Manager and Lightning App Builder dropped the same way, 20% down to 15%. Data and Analytics Management climbed from 14% to 17% and is now the single heaviest section on the test. Automation held its ground at 15%. And Agentforce AI showed up as a brand-new topic worth 8%, per Salesforce Ben’s breakdown of the blueprint.

Read that as a market signal. Not a testing decision. Salesforce spent a decade defining a competent admin as somebody who could find the right screen in Setup, and then in one exam revision moved that definition toward owning the data layer and governing what an AI agent is permitted to do inside the org. Your job description should have moved with it. Most haven’t.

One caveat before you rewrite your requirements section around that table. A certification is a floor, not a forecast. I have placed admins with no badge at all who had rebuilt a sharing model under audit pressure, and I have interviewed triple-certified candidates who had never once been the person on the phone at 6 a.m. when a data load went sideways. Both exist. Neither is rare. Ask for the credential. Screen for the scar tissue.

Three Admin Seats Wear the Same Title

Salesforce administrator postings usually describe one of three jobs: the solo admin who owns a whole org alone, the team admin who owns a slice of a platform group, or the admin-analyst who splits time between configuration and requirements.

Pick one before you write anything. Just one. Across those three bands you are looking at roughly $55,000 of spread, and a posting that straddles two of them pulls candidates who are wrong for both. Wrong for both. Worth sitting with.

The solo admin is the one companies underestimate. Badly, usually. One person holds the security model, the release calendar, the integrations, the reports the CFO reads on Monday, and every ticket from a sales team that does not care whose queue it lands in. There is nobody to peer-review a permission set change, which matters more than it sounds like it should, because the single most expensive incident I have watched a client work through started with one well-intentioned profile edit made on a Friday afternoon by a person with nobody to check it. When that person leaves, and they do leave, the org’s institutional memory walks out with them in a two-week window. We charge that premium into the band on purpose, because the risk being priced is not the difficulty of the work so much as the concentration of it in one head that can hand in a resignation letter on any given Tuesday. It is partly skill and partly hazard pay, and if you have ever inherited an undocumented org from a departed solo admin you already know which part is bigger. You know.

Team admins are different animals. Narrower scope, more depth, real code review, an architect above them to escalate to. They tend to specialize fast, and the good ones get expensive in a specific direction rather than a general one. Depth over breadth.

Then the admin-analyst. Half the postings I read are secretly hiring this person and do not say so. Half. Not an exaggeration. The seat writes user stories, runs discovery with the sales ops team, builds the thing, and then trains the people who asked for it. It’s a genuinely different skill profile from either of the other two, and it competes for candidates with the business analyst market rather than the platform market. If that’s your seat, say business analyst somewhere in the posting or you will spend six weeks screening people who want to live in Setup.

Those bands blend public salary data with what KORE1 has placed across the 30-plus U.S. metros where we run technical searches. Base only. No bonus, no equity, no on-call differential.

The Salesforce Administrator Job Description Template

Copy the block. Replace every bracket with something true about your org, delete the italic notes, and post it. It is written for a mid-to-senior seat. If you are hiring an associate admin, cut the governance language and lower the years; if you are hiring a lead, add roadmap authority and raise the band.

What the Seat Actually Pays in 2026

Salesforce administrators in the United States average roughly $99,000 in base pay in 2026, with the middle of the market running about $80,000 to $125,000 and senior admins who own automation, security, and an AI rollout clearing $130,000.

The public trackers disagree. The disagreement is informative rather than sloppy. Each one samples a different crowd doing a different flavor of the work.

The Bureau of Labor Statistics does not track “Salesforce administrator” as its own occupation, so computer systems analysts is the honest federal stand-in. That category projects 9% growth from 2024 to 2034 and about 34,200 openings a year, roughly triple the average across all occupations. Treat it as a directional read on demand, not a comp benchmark for your specific posting. Demand signal only.

Here is the first place I tell you to spend less. If your org is under 100 users, runs Sales Cloud only, and has no integrations worth the name, you do not need a $130,000 admin. You need a solid mid-level person at $90,000 and a documented escalation path to a partner for the two weeks a year something hard happens. Paying architect money for a maintenance seat is the most common budget mistake I see, and the person you overpay gets bored and leaves in eighteen months anyway. Everybody loses.

For the full breakdown by experience level, city, and contract rate, our Salesforce administrator salary guide goes deeper than this section can. If you want to pressure-test a band against live market data before it goes in the posting, the salary benchmark assistant does that in about a minute.

Lines That Quietly Shrink Your Applicant Pool

Five keep resurfacing. I pulled every one of them off a live req in the past year. In three of those five the hiring manager had no idea the line was costing anything; the posting had been forwarded around so long nobody remembered writing it.

“Salesforce Certified Administrator required.” Wrong name since fall 2025. Two-second fix, and fixing it signals that somebody in the building still keeps up.

Then there’s the Workflow Rules line. Salesforce ended support for Workflow Rules on December 31, 2025. Existing rules keep running and you can still edit them, but bugs will not get fixed and the whole ecosystem has been pointed at Flow for years now. Asking for Workflow Rules experience as a requirement tells a candidate they are inheriting debt. Asking them to migrate off Workflow Rules tells them they are inheriting a project with a finish line. Same technical reality underneath. Completely different posting.

Eighteen bullets in the responsibilities section is the next one. I counted one at nineteen last month. Not a typo. Nobody reads past the sixth, and the six you keep should name real systems, which has the side benefit of making your intake call about twenty minutes shorter.

“Must be a self-starter who wears many hats.” Translated: no documentation, no backup, no plan. Experienced admins have been burned by that exact phrasing and they filter on it now. If the seat genuinely is a solo-admin role, say solo admin and pay the premium. Honest and expensive beats vague and cheap. Every time.

The last one costs the most. No salary band. Colorado, California, New York, Washington, and a growing list of others require one anyway, so for a lot of you this is already settled. Compliance aside, the band is the fastest screening tool you own. Publishing $95,000 to $125,000 means the $150,000 people never apply, and the $70,000 people rule themselves out before anybody wastes a screen on either side. You just saved your team forty resume reviews. Maybe more.

Name the Stack, Not the Category

A Salesforce administrator posting should name specific clouds, packages, and integration tools rather than generic categories, because admins search and filter by product names, not by phrases like “CRM platform experience.”

Generic postings lose twice. Search, then credibility. They rank badly against candidate searches, and they read as though nobody technical reviewed them.

Write Sales Cloud, Service Cloud, Experience Cloud, Financial Services Cloud, or Health Cloud. Write CPQ if you run CPQ, and say whether it is Salesforce CPQ or Revenue Cloud, because those are not the same migration story. Name the managed packages, because an admin who has fought with DocuSign for Salesforce or Conga or Certinia knows something an admin who has not does not. Name your integration layer: MuleSoft, Workato, Boomi, or the homegrown middleware your last architect built and did not document.

If Data Cloud is in play, say it. One word. That one word moves your posting into a much smaller and much better-paid candidate pool, and it is worth knowing before you set the band whether the person you want is actually in that pool.

Same goes for Agentforce. Say it only if it’s real. A posting that names Agentforce when the company has no AI roadmap gets a round of excited applicants who churn out within a year once they discover the truth, and the recruiting community talks. I would rather you write “Agentforce is on our roadmap for late 2026 and this person will own the rollout” than pretend it’s live. Candidates respect the honest version. They also remember the other kind.

What Hiring Managers Bring to Intake Calls

How many years should I actually ask for?

Three years covers most mid-level Salesforce administrator seats. Five-plus is honest only if the role owns the security model, release management, and platform governance rather than day-to-day configuration and support tickets.

The number gets inflated more than any other line in these postings. I have seen “7+ years” on a req that was, in practice, user provisioning and report building for 180 people. That posting sat open for four months. Four. We rewrote it at three years, kept every technical requirement, and it closed in twenty-two days with a stronger candidate than the original spec would have allowed through.

Do I need to require a certification at all?

Wrong question, slightly. Requiring the Platform Administrator credential is reasonable and cheap to verify. Requiring Platform Administrator II for a mid-level seat is not, and it cuts your pool by more than half.

Certification correlates with baseline competence and with nothing else. Somebody who passed the exam knows the vocabulary. That is the whole claim. Whether they have ever unwound a sharing model that a well-meaning predecessor built on public read-write is a completely separate question, and the only way to find out is to ask them about a specific mess they inherited. Our Salesforce admin interview questions cover the ones that actually separate people.

One admin or two, and when does that change?

Most orgs add a second administrator somewhere between 300 and 500 licensed users, or earlier if they run more than two clouds, a managed package like CPQ, or integrations that break in ways only one person understands.

User count is the wrong trigger on its own. Complexity is the real one. A 200-user shop running two clouds, a managed package, an integration layer somebody babysits, and a half-finished Data Cloud migration will bury one admin. Meanwhile the 600-user org next door, clean Sales Cloud, a dozen Flows, nothing custom, hums along fine on one person and a decent backlog process. Licenses are the easy number to count, which is exactly why everybody counts them instead of counting the work. Count integrations and clouds before you count seats.

Should the posting name Agentforce if we have not turned it on?

Only with a date attached. Naming Agentforce as a future project you will own attracts strong candidates. Naming it as a current responsibility when nothing is deployed produces an angry admin by month three.

Admins talk to each other constantly. Trailblazer community, local user groups, Slack. Word travels. A company that oversold an AI mandate gets a reputation faster than you would believe, and it costs you the next three searches too.

Contract, contract-to-hire, or direct hire for this seat?

Direct hire for the permanent org owner. Contract for a defined project like a Workflow Rules migration, a data cleanup, or a Lightning transition. Contract-to-hire when you need coverage now and clarity later.

The pattern I recommend most often is the third one, and specifically for solo-admin seats where the hiring manager is not a Salesforce person and cannot evaluate depth in a 45-minute interview. Ninety days of watching somebody actually run your org tells you more than any loop will. Far more. Contract staffing also covers the gap when a departing admin gives two weeks and takes the only working knowledge of your integrations with them. Which happens. Regularly.

Our admin will also do business analysis. Which title goes on the posting?

Put the dominant function in the title and the secondary one in the first paragraph. If more than half the week is stakeholder discovery and requirements, that seat is a business analyst who administers Salesforce.

Titles are search terms. Treat them that way. An admin-analyst hybrid posted as “Salesforce Administrator” gets configuration-first candidates, and the ones who love requirements work never see it. Split the difference in the body copy, not in the title.

Is publishing the band actually worth it?

$95,000 to $125,000 on the posting will do more screening work than your first two interview rounds combined. Several states require pay transparency regardless, and candidates in the others have started treating a missing band as a red flag.

The objection I hear is that current employees will see it, and that the admin who has been running the org for four years at $88,000 will read the new posting, do the arithmetic, and walk into their manager’s office the same afternoon with a printout and a question that has no comfortable answer. They will. Count on it. If your published band for a new hire embarrasses you next to what you pay your existing admin, the band is not the problem.

Realistically, how fast can this close?

Three to six weeks for a well-scoped mid-level Salesforce administrator search with a published band. KORE1 averages 17 days to hire across our IT desk, though admin searches with industry-cloud requirements run longer than that.

The variable that moves the timeline most is not sourcing. It’s your interview loop. Two rounds inside a week beats four rounds over a month, and in a market where good admins hold multiple conversations at once, the slower process loses candidates it already won.

When It Makes Sense to Call Us

You can run this search yourself. The template above is the same one we hand to clients who tell us they want to try internally first, and a decent number of them never call back because it worked. Good. That is a win too.

We earn the fee in four situations. Industry cloud work, Financial Services Cloud or Health Cloud. Solo-admin seats where the hiring manager cannot evaluate platform depth in a 45-minute conversation and knows it. Replacement searches where the incumbent already left, taking the only working knowledge of the integrations with them and leaving a wiki page last edited in 2023. And tight bands, where how the role gets positioned decides whether the best candidate picks up at all. KORE1 has been placing technical talent since 2005, we run searches across 30-plus U.S. metros, and our placements hold a 92% twelve-month retention rate. Our recruiters average 15-plus years each. Mostly that means they have seen the failure modes before.

If you want a second read on a posting before it goes live, or a shortlist against a band you have already set, talk to a KORE1 recruiter and we will tell you honestly whether you need us. Our Salesforce recruiters handle admin, developer, and architect searches, and if you are hiring on the build side instead, the Salesforce developer job description template covers that seat. Still deciding whether to hire at all? Start with how to hire a Salesforce administrator.