Salesforce administrator job description templates for small teams: 6 role variants with duties, certifications, pay bands, and overtime notes. Free DOCX.
6 free templates for companies hiring their first or next admin without a systems team: standard, junior, solo, admin and business analyst, Service Cloud, and fractional. Download as DOCX.
Most Salesforce administrator job descriptions on the internet were written for a company with a systems team. They assume a technical hiring manager who can read a build, a senior administrator to escalate to, and a budget band wide enough that nobody has to choose between configuration skill and coding skill. If you have thirty employees and one increasingly fragile org, none of that describes you.
The pattern I see most often at small companies is a posting assembled from every skill anyone wished the last person had: flows and Apex and integrations and data architecture and reporting, at a mid-level salary. It attracts nobody. The declarative administrators read it as a developer role and pass, and the developers read the pay band and pass.
At FirstHR we build hiring templates for the companies doing this without an HR department. The six below cover a standard administrator, a junior, a solo first hire, an admin and business analyst hybrid, a Service Cloud specialist, and a fractional arrangement, each with the classification and access notes the generic versions leave out.
TL;DR
A Salesforce administrator job description should state licensed user count, which clouds you run, whether the first project is a cleanup, and where the code boundary sits. Classification is the trap: the computer employee exemption needs a systems analysis or programming duty plus $684 weekly, which configuration and support work often fails. Six templates below, downloadable as DOCX.
What a Salesforce Administrator Actually Owns
A Salesforce administrator owns configuration, data, access, and reporting, and does that work declaratively rather than in code. That one sentence settles most of the arguments a small company has with itself while writing the posting.
The distinction matters because it sets the pay band and the candidate pool. Configuration skill and development skill are different markets with different certifications, and a posting that blurs them narrows your applicant list to the small overlap who can command far more than you budgeted.
Declarative configuration
The core of the job
Objects, fields, page layouts, record types, flows, validation rules, and the permission model. Built through configuration rather than code. This is what a Salesforce Administrator credential actually certifies, and it is where most of the week goes.
Data and reporting
The part that gets noticed
Deduplication, imports, mass updates, field standardization, and the reports leadership reads on a Monday. When this slips, everyone notices at once, and the administrator gets blamed for a data problem the process created.
Users, access, and support
The invisible workload
Provisioning, deactivation, permission sets, sharing rules, license true-ups, and the internal support queue. It never appears in the job description and it consumes real hours, so put an estimated share of time on it.
Apex and custom code
A different hire
Triggers, Lightning Web Components, and integration engineering belong to a developer, not an administrator. Asking for both in one posting is how a search stalls for four months. Scope it out explicitly or budget for a senior hybrid.
Write the Code Boundary as One Explicit Sentence
Put a line in the posting that says where configuration ends. Something as plain as: this role is declarative; Apex, Lightning Web Components, and integration engineering are handled by an outside partner. Candidates read that sentence and self-select correctly in about four seconds. Leaving it out is the single most reliable way to stall a search, because every applicant guesses differently about what you meant and the strong ones guess conservatively and move on.
What Belongs in the Posting
A job description for this role does four jobs at once: it describes the org honestly, it filters applicants, it protects you legally, and it closes the candidate. Most postings only attempt the second, which is why they generate volume without fit.
The facts that set expectations
Licensed user count and how long the org has run
Which clouds you use, stated by name
Whether this is a cleanup or a steady-state role
Who the administrator reports to
The parts that filter applicants
Certification marked required, preferred, or not required
Code versus configuration boundary drawn explicitly
Integrations and packages listed, not implied
Support queue volume and response expectation
The parts that protect you
FLSA classification decided on duties, not title
Confidentiality and data export acknowledgment
Essential functions written plainly
Equal opportunity statement
The parts that win the hire
Salary or a good-faith range
Certification and study budget
Autonomy over the roadmap and the standards
A named person and a real decision timeline
The omission that costs small companies most is the org description itself. Five licensed users and two hundred licensed users are different jobs with different pay, and a candidate cannot infer which one you are from the company name. Our guide to job posting requirements covers what has to appear on the ad itself, and the general structure is in our guide to writing a job description.
6 Salesforce Administrator Job Description Templates to Download
Download all six as one file or copy them individually. Each follows the same structure: company and org overview, position summary, key responsibilities, required qualifications, a classification note, an access and confidentiality clause, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you change.
Download All 6 Salesforce Administrator Job Description Templates
Standard, junior, solo first hire, admin and business analyst hybrid, Service Cloud, and fractional. All in one download.
Standard Administrator
Established org, one owner
The general role for a company with a running org and enough users to need a dedicated administrator on configuration, data, and access.
Junior / Associate
Supervised, defined scope
For a second pair of hands under a senior administrator: user administration, support queue, hygiene, and reports, with schema changes escalated.
Solo / First Admin Hire
No systems team
For a small business inheriting an org nobody has owned. Includes a first ninety days audit plan and an explicit line around custom code.
Admin / Business Analyst
Design then build
For the hybrid that gathers requirements, documents process, configures the solution, and measures whether the change worked.
Service Cloud Administrator
Support operations
For case management specifically: intake channels, routing and escalation, entitlements, knowledge, and support metrics reporting.
Part-Time / Fractional
Capped monthly scope
For companies that need a few reliable hours a month, with an explicit scope, an exclusions list, and a blunt contractor classification warning.
Template 1: Salesforce Administrator (Standard)
The general role for a company with a running org and enough licensed users to justify a dedicated owner for configuration, data quality, access, and reporting.
For a second pair of hands under a senior administrator, with user administration, the support queue, and hygiene in scope and schema changes escalated rather than built.
Template 3: Solo / First Salesforce Administrator at a Small Business
For a company inheriting an org nobody has properly owned. Includes a first ninety days audit plan and an explicit line separating configuration from custom development.
Solo / First Salesforce Administrator, Small Business Job Description
SOLO SALESFORCE ADMINISTRATOR JOB DESCRIPTION (FIRST ADMIN HIRE)
Company: __ ([City, State])
Reports to: [Owner / COO / Head of Sales]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] has [number] employees and no dedicated systems team. Salesforce
has been administered part-time by [the sales manager / an outside consultant /
nobody] for [number] years, and it shows. You would be the first person whose
actual job is the org, with a mandate to fix what is broken and then keep it
that way.
POSITION SUMMARY
The Salesforce Administrator is the single owner of our Salesforce org: access,
configuration, data quality, reporting, integrations, and the internal support
queue. You will set the standards because there are none yet.
FIRST NINETY DAYS
•Audit the org: unused fields, broken automation, duplicate records, orphaned
permissions, and licenses we pay for and do not use
•Deliver a written cleanup plan with a sequence and an estimate
•Rebuild [the pipeline stages / the reporting pack] with [sales leadership]
•Document the data model and the naming standard so the next person inherits
something readable
ONGOING RESPONSIBILITIES
•Own users, profiles, permission sets, and the sharing model
•Build and maintain flows, validation rules, layouts, and record types
•Run data hygiene on a schedule rather than in a panic before board meetings
•Build the reports leadership actually reads, and retire the ones nobody opens
•Manage the [integrations and AppExchange packages] we depend on
•Prepare and test for the [three] platform releases each year
•Handle the license true-up and tell us honestly when we are over-bought
•Train new hires during onboarding on the process behind the fields
REQUIRED QUALIFICATIONS
•[Number] years as the primary administrator of an org, ideally at a company
•Comfort working without a technical peer to check your build
•Judgment about what to fix first, and the ability to defend that order
•Willingness to explain a no to a founder who wants a new field today
WHAT THIS ROLE IS NOT
This is not an Apex development role. Custom code, Lightning Web Components, and
complex integration engineering go to [an outside partner / a developer we
contract]. If the build needs code, your job is to scope it and manage it.
CLASSIFICATION NOTE
Classification turns on duties, not on being the only person in the function.
The computer employee exemption requires a primary duty of systems analysis or
program design plus at least $684 per week salaried or $27.63 hourly. The
administrative exemption requires office work directly related to management or
general business operations, with a primary duty involving independent judgment
on matters of significance. A solo administrator setting standards may fit the
second one; a solo administrator whose week is tickets and imports may fit
neither. Decide honestly and document the reasoning. This is general
information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [certification budget],
[conference or community budget]
To apply, email __ with your resume and one paragraph on an
org you inherited and what you changed first.
Template 4: Salesforce Administrator / Business Analyst Hybrid
For the variant that gathers requirements, documents the process before building it, configures the solution, and then measures whether the change moved anything. If the analysis half dominates, compare it against the business analyst templates.
Salesforce Administrator / Business Analyst Hybrid Job Description
SALESFORCE ADMINISTRATOR / BUSINESS ANALYST JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Head of Revenue Operations / COO]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] needs someone who can sit with [sales, support, finance], work
out what the process should be, and then build it in Salesforce. Half the job is
listening and writing; half is configuration. If you only want to build tickets
handed to you, this is not the role.
POSITION SUMMARY
The Salesforce Administrator and Business Analyst gathers requirements from
stakeholders, designs the process before touching the platform, configures the
solution declaratively, and measures whether the change worked.
KEY RESPONSIBILITIES
•Run discovery sessions with [sales, support, finance, leadership]
•Document current-state process and proposed changes in writing before building
•Translate requirements into configuration: objects, fields, flows, validation
•Maintain a prioritized backlog with business impact stated for each item
•Build the reporting that shows whether a process change moved the number
•Own user acceptance testing and release notes for each change
•Manage users, permissions, and the sharing model
•Prepare for the [three] platform releases each year and communicate impact
•Train users and write the internal documentation they will actually read
REQUIRED QUALIFICATIONS
•[Number] years combining Salesforce administration with requirements work
•Demonstrated process documentation and stakeholder facilitation ability
•Strong writing; this role produces documents other people rely on
•Comfort pushing back on a requested feature that solves the wrong problem
PREFERRED QUALIFICATIONS
•Advanced Administrator, Platform App Builder, or Business Analyst credential
•Experience in [our industry] or with [our sales motion]
•Familiarity with [our integrations]
CLASSIFICATION NOTE
This is the variant most likely to qualify as exempt, and it still requires
analysis. The administrative exemption covers office work directly related to
management or general business operations where the primary duty includes the
exercise of discretion and independent judgment on matters of significance.
Requirements gathering, process design, and prioritization decisions point that
way. Ticket work and data entry do not. Base the decision on how the week
actually splits. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [certification budget]
To apply, email __ with your resume and a writing sample:
any requirements document you have authored, redacted as needed.
Template 5: Service Cloud Salesforce Administrator
For case management specifically: intake channels, assignment and escalation rules, queues, entitlements, knowledge, and the support metrics a support manager is measured on.
Service Cloud Salesforce Administrator Job Description
SERVICE CLOUD SALESFORCE ADMINISTRATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Head of Customer Support / Operations Director]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
Support team size: [number] agents across [channels]
ABOUT THIS ROLE
[Company Name] runs customer support for [number] customers on Service Cloud
across [email, web, phone, chat]. We are hiring an administrator who understands
support operations specifically: case routing, queues, entitlements, and the
metrics a support manager is measured on.
POSITION SUMMARY
The Service Cloud Administrator configures and maintains the case management
environment: intake channels, assignment and escalation rules, queues, macros,
knowledge, and the reporting that shows how the support team is performing.
KEY RESPONSIBILITIES
•Configure case intake across [email-to-case, web-to-case, chat, phone]
•Build and tune assignment rules, escalation rules, queues, and omni-channel
routing so cases reach the right agent the first time
•Maintain [entitlements and milestones / service level targets] and the alerts
that fire before a target is missed
•Own the knowledge base structure, article types, and publishing workflow
•Build macros, quick actions, and console layouts that cut handling time
•Report on [first response time, resolution time, backlog, CSAT] for leadership
•Manage agent users, permission sets, and console access
•Test each platform release against the support console before it lands
•Partner with the sales-side administrator on the shared account and contact
data model so the two clouds do not drift apart
REQUIRED QUALIFICATIONS
•[Number] years administering Service Cloud in a live support environment
•[Salesforce Certified Administrator required; Service Cloud Consultant
credential preferred]
•Working knowledge of support metrics and what drives each one
•Experience configuring routing for a team of [size]
CLASSIFICATION NOTE
Support platform administration is often closer to configuration and user
support than to systems analysis, so the computer employee exemption frequently
does not apply. Evaluate the administrative exemption separately and, if the
role is non-exempt, track hours carefully: support platform work concentrates in
outages and release weekends, which is exactly when overtime accrues. This is
general information, not legal advice.
ACCESS AND CONFIDENTIALITY
Case records contain customer communications and may contain regulated personal
information. Access is provisioned at [permission level], export activity is
logged, and a signed confidentiality acknowledgment is required before
credentials are issued.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [benefits summary], [certification budget]
To apply, email __ with your resume and a note on a routing
•Experience maintaining orgs for small companies without a systems team
•Reliable availability during [agreed window] and a stated response time
•Willingness to write down what you did, so we are never stranded
CLASSIFICATION NOTE (the important one)
Choose the engagement type deliberately. If you set the schedule, the method,
the tools, and the order of work, you are likely directing an employee, and
labeling that person a contractor is one of the most common and most expensive
misclassification mistakes small companies make. A genuine contractor runs their
own business, serves other clients, controls how the work gets done, and invoices
against a scope. A part-time employee is fine: part-time simply means fewer
hours, and a part-time employee is still non-exempt unless an exemption clearly
applies. Decide before the first invoice, not after an audit. This is general
information, not legal advice.
ACCESS AND OFFBOARDING
Access is provisioned at [permission level] under a signed confidentiality and
acceptable use agreement. On engagement end, credentials are deactivated the
same day, connected app tokens are revoked, and any exported data is certified
as destroyed.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per [hour / month retainer], [scope review cadence]
To apply, email __ with your resume, your availability, and
your rate.
Overtime and Why Administrator Rarely Means Exempt
Do not assume this role is exempt from overtime. The exemption most employers reach for is the computer employee exemption, and a configuration-and-support administrator frequently fails its duties test, which makes the mistake compound quietly across every unpaid hour of the employment.
The federal regulation on computer employees requires at least $684 per week on a salary basis or $27.63 an hour, plus a primary duty of systems analysis, the design and testing of systems or programs, or programming related to machine operating systems. The Department of Labor is explicit in Fact Sheet 17E that employees whose work is highly dependent on computers, but who do not meet the duties tests, are not exempt under that provision.
The computer exemption is narrower than the title suggests
The federal regulation on computer employees sets a duties test built around systems analysis, the design and testing of systems or programs, and programming related to machine operating systems, on top of a pay floor of $684 per week on a salary basis or $27.63 per hour. Clicking together a flow, adjusting a page layout, and running a deduplication pass is skilled work, and it is not what that regulation describes. The Department of Labor states the point directly in its computer employee fact sheet: employees whose work is highly dependent on computers but who do not meet the duties tests are not exempt under that provision. Job titles in this field change faster than the regulations do, so the exempt status has to be tested against actual duties. This is general information, not legal advice.
The administrative exemption is the one worth analyzing
If an exemption applies to a Salesforce administrator, it is usually the administrative one. That test requires office or non-manual work directly related to the management or general business operations of the employer, with a primary duty that includes the exercise of discretion and independent judgment on matters of significance, plus the same $684 weekly salary floor. An administrator who decides how the sales process is modeled, sets the data standards, prioritizes a backlog against business impact, and tells leadership no has a real argument. An administrator who executes a queue of requests written by someone else does not. The same job title lands on both sides depending on the company. Write the decision down with the reasoning attached. This is general information, not legal advice.
Non-exempt is a normal answer, not a demotion
Small companies often reach for exempt status because it feels like a signal of seniority, then discover that platform work concentrates in exactly the hours overtime accrues: release weekends, a data load run at night to avoid disrupting users, an outage, the end of quarter. Classifying honestly as non-exempt and paying the overtime is cheaper than a back-pay calculation across the length of employment, and it is not an insult to the person. Track hours, state the classification on the posting so candidates are not surprised at offer stage, and plan the release calendar so predictable spikes are staffed rather than absorbed. This is general information, not legal advice.
Contractor status is a separate question with its own trap
Fractional administrators are common at small companies and are a frequent source of reclassification exposure. The label on the invoice does not decide it. A genuine independent contractor runs their own business, serves other clients, controls how the work gets done, and delivers against a scope. If you set the schedule, the tools, the method, and the order of work, and the person is functionally a member of the team, that is an employee regardless of how they bill. Part-time employment is a perfectly good answer for a company that needs eight hours a week, and a part-time employee is still non-exempt unless an exemption clearly applies. Run the analysis before the first invoice. This is general information, not legal advice.
The more promising analysis for this role is the administrative exemption, which turns on discretion and independent judgment about matters of significance rather than on technical skill. Anyone outside an exemption needs hours tracked and overtime paid past forty in a week. If you are unsure which side a role falls on, our breakdown of exempt versus non-exempt classification works through the tests in order.
The second question is whether the person is an employee at all. Fractional administration is common at this company size and is a frequent source of reclassification exposure, so run the analysis in our guide to employee versus contractor status before the first invoice rather than after the first audit.
Certifications and What They Actually Prove
The Salesforce Certified Administrator credential verifies a known body of platform knowledge, and it proves familiarity rather than judgment. Require it when nobody at your company can evaluate an org build, and mark it preferred when someone can.
Whichever way you decide, say so explicitly in the posting. Ambiguity costs you in both directions: credentialed candidates skip postings that appear to discount the exam, and strong self-taught administrators skip postings that appear to demand it.
Requirement
How to state it in the posting
Administrator credential
Mark it required, preferred, or not required, and add a study and exam budget either way
Advanced credentials
Name the specific one you want rather than asking for certifications generally
Flow and automation skill
Describe the build you need, not the tool: routing, approvals, validation, notifications
Permission model
State the user count and whether the sharing model is simple or role-heavy
Data work
Say whether the first project is a cleanup, a migration, or steady-state hygiene
Reporting depth
Name who reads the reports and how often, since that sets the real bar
Integrations
List the connected systems and whether the seams exist already or need building
Code boundary
Draw it explicitly; it changes the pay band, the candidate pool, and the time to hire
Two screening moves are worth more than any credential filter. Give a short practical exercise in a developer sandbox, because configuration skill and naming discipline show within fifteen minutes. Then take a reference from a sales or support leader who depended on the candidate's reports, not only from a technical manager who reviewed the build.
What to Pay a Salesforce Administrator
There is no dedicated federal occupation code for Salesforce administrator, so benchmark against the nearest classifications and adjust for scope. The spread between those proxies is wide enough that choosing the right one matters far more than fine-tuning inside it.
Nearest Federal Classifications, National Medians
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), median annual wages were $61,860 for computer user support specialists, $83,050 for business operations specialists not classified elsewhere, $99,130 for network and computer systems administrators, $104,620 for database administrators, and $105,850 for computer systems analysts. The systems administrator ladder runs from $62,640 at the tenth percentile to $155,050 at the ninetieth, and computer systems analysts from $67,340 to $167,710 (U.S. Bureau of Labor Statistics, OEWS national estimates).
Nearest classification
National median (BLS OEWS, May 2025)
When to use it as your benchmark
Computer user support specialists
$61,860 per year
Associate administrator whose week is the support queue and data hygiene
Business operations specialists, all other
$83,050 per year
Revenue operations flavored administrator sitting close to the sales process
Network and computer systems administrators
$99,130 per year
Full org owner carrying configuration, access, releases, and integrations
Database administrators
$104,620 per year
When data modeling, migration, and integration work dominate the role
Computer systems analysts
$105,850 per year
Admin and business analyst hybrid doing requirements gathering and process design
Computer occupations, all other
$116,580 per year
Residual category; treat as a ceiling reference rather than a target
Two adjustments matter at a small company. Scope the band down honestly for a hybrid role, because paying a full org owner rate for half an org owner job attracts candidates who leave once they meet the other half. Publish a good-faith range where pay transparency laws apply, and fund the certification budget: study time is inexpensive compensation that strong operators genuinely value.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Three recurring obligations sit inside this job and almost never appear in the posting: release readiness, sandbox and documentation discipline, and access governance. Leaving them unstated does not remove the work, it just leaves it unassigned.
Three platform releases a year
Salesforce ships major seasonal releases on a fixed calendar, and every org receives them whether or not anyone prepared. Someone has to read the release notes, test the changes in a sandbox against your configuration, retire what is being deprecated, and tell users what will look different on Monday. If your posting does not name release readiness as a duty, you have quietly assigned it to nobody.
Sandbox discipline and change records
Building directly in production is the habit that turns a healthy org into a fragile one. Write the expectation into the job description: changes are built and tested in a sandbox, each change carries a written record of what and why, and the naming standard is documented. Small companies skip this because there is only one administrator, which is exactly the situation where the documentation matters most, since the whole system lives in one person's head.
Access, licenses, and offboarding
This role can export your entire customer database, so treat access as part of the job description rather than an afterthought. State the permission level, the export rules, and the confidentiality acknowledgment required before credentials are issued. The annual license true-up belongs here too: an administrator who tells you honestly that you are paying for seats nobody uses often covers a meaningful share of their own salary.
Access governance deserves a line in the job description rather than a footnote in onboarding. Contact and case records are personal information under a growing set of state privacy statutes, and laws of that kind give residents rights to know, delete, and correct the data a business holds about them, with statutory deadlines to respond. In practice those requests get executed by whoever administers the platform, so name that duty explicitly instead of discovering it during the first request.
Offboarding a Systems Owner Is Not a Normal Offboarding
When an administrator leaves, deactivating the user account is roughly a third of the job. Connected app tokens, API credentials, integration user accounts, scheduled exports, and any personal sandbox all need revoking, and someone has to confirm that documentation exists before the last day rather than hoping it does. Build the checklist while you are hiring, not while you are losing them. Our offboarding checklist covers the general sequence; the credential revocation list is the part you add for this role.
Hiring a Salesforce Administrator Without an HR Department
Small company searches for this role fail in three predictable places: the posting describes a developer, the org history is hidden, and the access-heavy onboarding lands all at once. Each has a fix that costs nothing but honesty.
The posting asks for an administrator and describes a developer
The most common failure in a small company Salesforce search is a job description assembled from every skill anyone wished the last person had: declarative configuration, Apex triggers, Lightning Web Components, integration engineering, data architecture, and reporting, at an administrator salary. Candidates who can do all of that exist and cost far more than the band on the posting, so the strong declarative administrators self-select out because the ad reads as a developer role, and the developers pass because the pay does not match. Decide which one you are hiring, write the code boundary into the posting in one sentence, and route the rest to an outside partner. A clear, narrower posting fills faster than a broad one.
Nobody has decided who owns the org, so the answer is everyone and nobody
Before the first hire, the org has usually been maintained by a sales manager on a Friday afternoon, an outside consultant billing by the hour, and whoever last had admin rights and did not give them back. That history is the real starting condition of the job, and hiding it produces a bad first ninety days. Say it plainly in the posting: how long the org has run, how many licensed users it carries, who has been administering it, and whether the first project is a cleanup or steady-state maintenance. Strong candidates are not scared off by a messy org. They are scared off by discovering the mess after they accept, which is how a first-year departure happens.
System access, paperwork, and training all land in the first week and nothing is centralized
A systems hire has a heavier onboarding load than most roles, because access is the job. Signed offer, confidentiality and acceptable use acknowledgment, security and data handling training, credential provisioning at a defined permission level, documented handover from whoever held the keys, plus every standard new-hire form. FirstHR was built for that sequence. The onboarding wizard runs the same steps for every hire, e-signature handles the offer and the acceptable use acknowledgment, document management stores the certifications and clearances against the employee profile with renewal dates attached, and training modules cover security and data handling before credentials are issued. Applicant tracking is coming soon to FirstHR. Note that FirstHR is an onboarding and HR platform, not a payroll provider.
Once the offer is signed, the work becomes a repeatable onboarding checklist with the credential provisioning sequence attached to it. Applicant tracking is coming soon to FirstHR, which will close the gap between the posting and that first day.
If you are still deciding whether this role should be Salesforce-specific at all, the broader CRM administrator templates cover the platform-neutral version. The rest of our job description library sits in hiring templates.
Key Takeaways
A Salesforce administrator owns configuration, data quality, user access, and reporting declaratively, while Apex, Lightning Web Components, and integration engineering belong to a developer.
State licensed user count, the clouds you run, how long the org has existed, and whether the first project is a cleanup, because those facts define the job more than the title does.
The computer employee exemption needs a systems analysis or programming primary duty plus $684 per week salaried or $27.63 per hour, which a configuration-and-support administrator often fails.
The administrative exemption is the analysis worth running, and non-exempt is a normal answer for a ticket-driven role rather than a demotion.
There is no federal occupation code for this title; nearest classifications (BLS OEWS, May 2025) run from $61,860 for user support specialists to $105,850 for computer systems analysts.
Name release readiness, sandbox discipline, and access governance in the posting, because unstated duties do not disappear, they simply end up unassigned.
A systems hire carries a heavier first week than most roles, because access is the job. FirstHR runs the same onboarding sequence every time, with e-signature for the offer and the acceptable use acknowledgment, document storage for certifications and clearances, training modules delivered before credentials are issued, and renewal dates tracked so nothing expires quietly. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does a Salesforce administrator do?
A Salesforce administrator owns the configuration, data quality, user access, and reporting of a company’s Salesforce org, working through declarative tools rather than code. The week splits across four areas: building and maintaining objects, fields, page layouts, flows, and validation rules; managing users, profiles, permission sets, and sharing rules; keeping data clean through deduplication, imports, and standardization; and producing the reports and dashboards leadership reads. On top of that sits an internal support queue and readiness testing for the platform releases that ship on a fixed calendar each year. What the role does not include is custom code. Apex triggers, Lightning Web Components, and integration engineering belong to a developer, and a posting that asks for both at administrator pay tends to stall.
What should a Salesforce administrator job description include?
Seven things, and most postings miss at least three. State the licensed user count and how long the org has run, because a five-user org and a two-hundred-user org are different jobs. Name the clouds you use. Say whether the first project is a cleanup or steady-state maintenance. Draw the code versus configuration boundary in one explicit sentence. Mark the Administrator certification as required, preferred, or not required rather than leaving candidates to guess. List the integrations and packages you depend on instead of implying them. State the FLSA classification and the pay or a good-faith range. Add the confidentiality and data export acknowledgment, the equal opportunity statement, a named person to apply to, and a real decision timeline. The six templates on this page follow that structure.
Is a Salesforce administrator exempt from overtime?
Not automatically, and the assumption is expensive. The federal computer employee exemption requires a primary duty of systems analysis, the design and testing of systems or programs, or programming, plus at least $684 per week on a salary basis or $27.63 per hour. An administrator whose week is configuration, user support, data hygiene, and reporting frequently does not meet that duties test, and the Department of Labor states plainly that employees whose work is highly dependent on computers but who do not meet the duties tests fall outside the provision. The administrative exemption is a separate analysis: it needs office work directly related to management or general business operations with a primary duty involving discretion and independent judgment on matters of significance. A senior administrator setting standards and prioritizing a backlog may qualify; a ticket-driven administrator likely does not. Classify on duties, document the reasoning, and track hours for anyone non-exempt. This is general information, not legal advice.
How much does a Salesforce administrator make?
There is no dedicated federal occupation code for Salesforce administrator, so benchmark against the nearest classifications rather than inventing a figure. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), national median annual wages were $61,860 for computer user support specialists, $83,050 for business operations specialists not classified elsewhere, $99,130 for network and computer systems administrators, $104,620 for database administrators, and $105,850 for computer systems analysts. The systems administrator percentile ladder runs from $62,640 at the tenth percentile to $155,050 at the ninetieth, and computer systems analysts run from $67,340 to $167,710, which shows how much scope drives the number. Pick the proxy that matches the actual job: support-queue-heavy junior roles sit near the bottom, full system owners near the middle, and requirements-and-design hybrids near the top. Publish a good-faith range where pay transparency rules apply, and add a certification budget.
Should I require the Salesforce Certified Administrator credential?
It depends on whether you can evaluate the work yourself. If nobody at your company can assess an org build, the credential is a reasonable floor because it verifies a known body of knowledge and shortens the screening you cannot do. If you have someone who can review a build, treat it as preferred and weight demonstrated work higher, because the certification proves familiarity with the platform rather than judgment about your business. Whichever you choose, write it into the posting explicitly as required, preferred, or not required. Leaving it ambiguous costs you both directions: credentialed candidates skip postings that seem to discount the exam, and strong self-taught administrators skip postings that seem to demand it. Add a study and exam budget either way, since maintenance releases require ongoing credential upkeep and study time is inexpensive compensation that operators value.
What is the difference between a Salesforce administrator and a Salesforce developer?
The boundary is code. An administrator works declaratively through configuration: objects, fields, flows, validation rules, layouts, permissions, reports, and data. A developer writes Apex, builds Lightning Web Components, and engineers integrations that configuration cannot reach. The two roles carry different certifications, different pay bands, and different candidate pools, which is why a single posting asking for both at administrator pay usually attracts neither group. Most small companies need an administrator and occasional developer help, not a full-time developer. The practical pattern is to hire the administrator, give them authority to scope code work, and contract a developer or partner for the pieces that genuinely need it. If you truly need both in one person, the honest description is a senior hybrid role and the budget has to reflect that.
Can a small business hire a part-time Salesforce administrator?
Yes, and for a small org it is often the right call. A company with a handful of licensed users usually needs reliable maintenance rather than forty hours a week: user provisioning, a scheduled data hygiene pass, report upkeep, release readiness testing, and a capped support queue. Write it as a part-time employee role with a defined monthly scope and an explicit exclusions list so expectations do not drift. The trap is classification. If you set the schedule, the tools, the method, and the order of work, that is an employee, and labeling the person a contractor is one of the most common misclassification mistakes small companies make. Part-time employment is a perfectly good answer, and a part-time employee remains non-exempt unless an exemption clearly applies. Decide before the first invoice rather than after an audit.
