Roles we recruit
Seven practices, 27 functions. Start at the practice when you cannot yet name the title; go straight to the function when you can.
Browse all 229 roles Brief us on a seatFlat 15% of first-year base · shortlist in 10 working days
A Salesforce administrator runs the org: users and permissions, objects and fields, automation, reports and a release routine that does not break what people rely on. Certifications are easy to list, so we screen for automations they cleaned up, access they locked down and reports sales leaders still use.
A new administrator is judged on whether the org gets calmer: fewer surprises after a release, cleaner data and requests that move. Each stage below has a signal that predicts it, and we test for that signal before you meet anyone.
The ramp, and the test behind each milestone
Weeks 1 and 2
Objects, fields and record types, profiles and permission sets, flows and other automation, installed packages and integrations, license use and the open change requests.
On track looks like a written org review naming the ten riskiest items, what is unused and a license count, shared with the sales operations lead.
How we test for it before you meet them
A review exercise in our screen: a described org with a change backlog and a failing automation. We score what they check first and what they would not touch before a sandbox test.
Weeks 3 to 6
Access reviewed against roles, with permission sets in place of one-off profile edits, and duplicate rules, validation and required fields set where records go wrong.
On track looks like access limited to what each role needs, and duplicate and empty-field rates falling on a report.
How we test for it before you meet them
We ask how they set up permissions for teams with different needs and what they changed after a setting broke something.
Weeks 7 to 10
Overlapping automations merged in Flow, each one documented with an owner, a purpose and an error path, and tested in a sandbox before release.
On track looks like overlapping automations merged, with every active one owned, documented and alerting on failure.
How we test for it before you meet them
We ask for an automation that failed in production, how they found it and the safeguard they added afterwards.
Weeks 11 to 13
Sandbox testing, a change log, deployment steps, a way back and release notes that users read, with the request queue ranked by the sales leaders who asked.
On track looks like changes released on a schedule with notes, and a request queue ranked with sales leadership.
How we test for it before you meet them
A reference call with a sales leader about turnaround on their requests and whether a release ever broke a report.
After day 90
The key reports and dashboards defined with owners, adoption checked, and training for reps on the fields that matter.
On track looks like five key reports with written definitions that sales leaders use in their weekly meetings.
How we test for it before you meet them
We ask how they know users are entering data correctly. A specific answer built on validation, reports and coaching predicts an administrator who protects data quality.
Five responsibilities. If the seat also owns the roadmap, the integrations and a team of administrators, it is a CRM manager; if it mainly writes custom code, it is a developer.
Who can see and change what, through roles, permission sets and sharing rules, plus the joiner and leaver routine.
The data model, validation rules, duplicate handling and required fields that keep records usable.
Flows and approvals that move work through the org, documented and with error handling.
The reports leadership reads, with agreed definitions and a check that they are right.
Intake, sandbox testing, deployment and release notes, so changes do not break what others rely on.
Three neighboring seats absorb work people assume belongs here. Drawing the line wrong is how an administrator ends up setting strategy or debugging every integration.
That seat ownsThe CRM as a product: the roadmap, data model, integrations, release process and the administrators.
Hire it instead whenseveral teams change the CRM and nobody decides what ships.
That seat ownsPardot for teams that sell in Salesforce: programs, scoring, forms and the alignment between the two systems.
Hire it instead whenthe gap is marketing programs and scoring, not the Salesforce org itself.
That seat ownsThe syncs between CRM, marketing, billing, product and data tools: field mapping, retries and monitoring.
Hire it instead whenbookings, billing and the CRM disagree because the syncs fail.
The title stays the same; the org does not. Pick the one that matches yours.
Takes over an org that a consultant or a part-time administrator has looked after.
Looks after sales process, forecasting, territories and quotes as the team grows.
Keeps sales, service and marketing needs in one org, with sandboxes and release control.
The questions we ask in our own screen. Use them in yours; the warning signs are as useful as the answers.
Every candidate we put forward is scored on these five, and the scores travel with the shortlist, gaps included. Four out of five with a named weakness beats a clean sweep you cannot verify.
| What we score | Weak evidence | Strong evidence |
|---|---|---|
| Automation they cleaned up | Builds new flows beside the old ones. | Overlapping automations merged, documented and monitored. |
| Access and permissions | Copies profiles and adjusts them. | Roles and permission sets with a tested rollout. |
| Data quality | Makes every field required. | Validation and coaching that moved a report. |
| Release discipline | Changes things in production. | Sandbox, change log and release notes, confirmed by a sales leader. |
| Fit with your org | A different cloud or scale. | Has administered an org like yours: your clouds, users and integrations. |
Public US benchmarks, read October 2026. Salary.com’s Salesforce administrator band sits close to its CRM administrator and HubSpot administrator bands, and Built In has no page for the title. Certifications, the number of clouds and release ownership move the number most.
Each bar runs from the 25th to the 75th percentile, the middle half of reported pay.
Base salary
Salesforce Administrator
Salary.com base benchmark
$81,358 to $96,711 base
CRM Administrator
Salary.com base benchmark, neighboring seat
$82,156 to $98,743 base
HubSpot Administrator
Salary.com base benchmark, neighboring seat
$82,344 to $103,249 base
CRM Manager
Salary.com base benchmark, the next seat up
$87,622 to $111,874 base
All bars: Salary.com base salary, 25th to 75th percentile, United States, as of October 1, 2026. Public aggregates, not ZaphyrRecruit placement data.
A Salesforce administrator keeps the org working for the people who use it. They manage users, roles and permissions, shape objects and fields, build and maintain automation, create reports and dashboards, protect data quality and release changes safely through a sandbox. The measure is a CRM that sales trusts, with few surprises after a release.
Salary.com puts a Salesforce administrator at $81,358 to $96,711 base, with a median of $89,972 (October 2026). CRM administrators sit at $82,156 to $98,743 and HubSpot administrators at $82,344 to $103,249. A CRM manager sits higher, at $87,622 to $111,874. Certifications, the number of clouds and release ownership move the number. Ask for the full package, not base alone.
An administrator configures the org without code: users, permissions, objects, fields, flows, reports and releases. A developer writes custom code when configuration reaches its limits, such as complex logic, integrations and custom interfaces. Many small teams need only an administrator. If requests are about fields, reports and access, hire an administrator; if they need code, add a developer.
When reps work around Salesforce, when change requests wait weeks, or when every release breaks a report someone relies on. A first administrator also makes sense once several teams ask for changes and a consultant is doing the routine work. The signal is requests and complaints piling up with nobody owning the org.
A consultant or managed service suits an audit, a migration or a defined project. An in-house administrator pays off when the org changes every week: someone has to rank requests, protect data quality and release safely. They learn your sales process and say no to changes that do not pay back. Some teams use a consultant for the cleanup and then hire.
Describe an org with a change backlog and a flow that updates the wrong field, and ask what they would check first and what they would leave alone until a sandbox test. An hour is enough. It shows how they think about risk and ownership, which certifications hide. Then ask for an automation they cleaned up and check it with a sales leader.
Ten working days from a signed brief to a shortlist of three to five calibrated candidates, each with our org review exercise scored and past work checked with a former sales or RevOps leader. Interview speed decides the rest: good administrators rarely run one process at a time, so a decision within two weeks of the first interview keeps them.
Tell us which clouds you run, who asks for changes today and what has broken after a release. We come back within one business day with how we would run the search and what the seat pays.
We build shortlists from people doing this work now, often before a seat is advertised. Set up a job alert for operations roles, or send your CV and we will come to you when a seat opens.
The Salesforce administrator is one of ten seats in this function. If the gap sits elsewhere, start there.