IT administrator job description templates for small teams: sole IT, co-managed, Microsoft 365, network hybrid, remote-first, with pay and overtime notes.
6 templates for the generalist IT hire: standard in-house, sole IT owner, co-managed with a provider, Microsoft 365 estate, network and systems hybrid, and remote-first. Download as DOCX.
The first IT administrator job description I ever wrote was three pages long and listed eleven platforms. We ran four of them. The two people who applied were both wrong for the job, and the reason was obvious in hindsight: I had written down every technology frustration of the previous two years instead of describing a role someone could actually hold.
That is the standard failure mode at a company hiring its first or second IT person. The title is broad on purpose, the scope is genuinely undefined, and the posting ends up describing a department rather than a person. Meanwhile the strong generalists, the ones who can run an environment alone, read it and move on.
At FirstHR we write hiring templates for employers without an HR department, and this page is the hub for the IT administrator title. Six templates below cover the standard in-house role, the sole IT owner at a small business, the co-managed setup, a Microsoft estate, a multi-site network and systems hybrid, and a remote-first team.
TL;DR
An IT administrator owns servers, network, identity, endpoints, and backups as a generalist rather than a specialist. There is no BLS occupation by that name: the nearest is network and computer systems administrators, national median $99,130 (BLS OEWS, May 2025). Many of these roles fail the FLSA computer employee duties test and are non-exempt. Six templates below, downloadable as DOCX.
IT Administrator, System Administrator, or IT Specialist?
These four titles describe overlapping jobs, and at a company under about two hundred people they frequently describe the same job. The distinction is emphasis rather than a defined boundary, which is why picking one matters more for candidate search behavior than for the work itself.
The practical rule is to name the title after the majority of the week. If most of it is servers and platforms, post a system administrator role. If most of it is user support and devices, post an IT specialist role instead.
IT administrator
The generalist infrastructure role
The broadest of the administrator titles. Servers, network, identity, endpoints, and whatever else keeps the company working. Small employers use it because it does not promise a specialty they cannot staff.
System administrator
Systems first, network second
Usually signals server and operating system depth: builds, patching, virtualization, storage, directory services. In a company of thirty people the daily work overlaps almost completely with an IT administrator.
Network administrator
Connectivity is the specialty
Switching, routing, wireless, firewalls, and circuits. A real specialty at multi-site companies and a title that will confuse candidates if what you actually need is broad systems ownership.
IT specialist
Support-weighted generalist
Broad like an administrator but tilted toward user support rather than infrastructure ownership. Use it when most of the week is people and devices rather than servers and access control.
Title
What it signals to candidates
Post it when
IT administrator
Broad infrastructure ownership without a declared specialty
One person runs everything and you cannot name a single focus
System administrator
Server, operating system, virtualization, and storage depth
The week is dominated by platform and server work
Network administrator
Switching, routing, wireless, firewalls, and circuits
Connectivity across sites is the hardest part of the job
IT specialist
Broad but support-weighted, closer to the user than the rack
Most of the week is people, devices, and tickets
IT support or help desk
First-line ticket resolution under an escalation path
You need volume absorbed below an existing administrator
IT manager
Leads the function, the budget, and the people
You are hiring headcount and spend rather than hands
One title to avoid entirely for this role is plain administrator. In hiring language that word means an office and administrative role, and posting it for an infrastructure job draws a candidate pool that barely overlaps with the one you want. If the volume of routine tickets is the real problem, the help desk templates and the IT support templates cover the tier that should absorb it.
What Belongs in an IT Administrator Posting
An IT administrator posting does four jobs at once: it describes the environment honestly, it filters people who cannot work at your level of autonomy, it protects you on classification and access, and it closes the candidate. Most small-company postings do only the first, and they do it as a platform list.
The parts candidates read first
Company size, industry, and how many people the role supports
The actual platform list, limited to what you run
Who the role reports to and who else is in IT
Onsite, hybrid, or remote, stated exactly
The parts that filter applicants
Years of experience as a band, not a floor
Certifications marked required, preferred, or funded
On-call rotation, change windows, and travel
Background check notice for a privileged-access role
The parts that protect you
FLSA classification stated on the posting
Essential functions written plainly
Equal opportunity statement
Change control and access approval expectations
The parts that win the hire
Salary or a good-faith range
Training budget and certification funding
What is broken today and what you want fixed first
A named person and a real decision timeline
The most valuable line in the whole posting is the one naming what is broken today. Generalists choose jobs by the problem they get to fix, not by the benefits page. Our guide to writing a job description covers the general structure, and the templates below apply it to this role.
Name the Escalation Structure, Not Just the Stack
Candidates evaluating an IT administrator posting want one answer above all others: when something breaks at 2 a.m., who is on the other end of the phone. Being the last line at a forty-person company is a completely different job from being the internal owner with a provider behind you, and the two attract different people. State it in the posting. Say whether there is a help desk below the role, whether an outside provider handles after-hours, how long the on-call rotation runs, and how it is paid. Silence on this point is read as bad news, because it usually is.
6 IT Administrator Job Description Templates to Download
Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities, required qualifications, a classification and compliance note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change, and the rest of the hiring templates library covers the roles around this one.
Download All 6 IT Administrator Job Description Templates
Standard in-house, sole IT small business, co-managed with a provider, Microsoft 365 estate, network and systems hybrid, and remote-first. All in one download.
Standard, In-House
The default posting
The general administrator role inside an existing technical standard: servers, identity, network, endpoints, and second-line escalation.
Sole IT, Small Business
Your first IT hire
For the company with no IT function yet. Everything from a password reset to the backup strategy, with the honest note about after-hours coverage.
Co-Managed With an MSP
Split duties, in writing
For companies keeping an outside provider. The posting states what stays in-house, what the provider owns, and what the two share.
Microsoft 365 Estate
Tenant, identity, endpoints
For a Microsoft-centered environment: tenant administration, conditional access, endpoint policy, licensing, and Windows servers.
Network and Systems Hybrid
Multi-site, hands-on
For companies where connectivity is as critical as the servers, with travel, change windows, and carrier coordination written in.
Remote-First
No office to walk into
For distributed teams: cloud identity, MDM, device logistics, same-day offboarding, and the multi-state employment question.
Template 1: Standard In-House IT Administrator
The default posting for a company that already has a technical standard and needs someone to operate inside it: servers, identity, network, endpoints, backups, and second-line escalation.
IT Administrator Job Description (Standard, In-House)
IT ADMINISTRATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Operations Lead / Owner]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
Work model: [Onsite / Hybrid, ___ days onsite / Remote]
ABOUT [COMPANY NAME]
[Company Name] is a [industry] company in [City, State] with [number] employees
across [number] locations. We run [number] servers or cloud tenants, [number]
managed endpoints, and [name the two or three platforms that matter most]. We
are hiring an IT Administrator to keep that environment running and to own the
day-to-day systems work end to end.
POSITION SUMMARY
The IT Administrator operates and maintains our servers, network, identity
directory, and endpoints. The role owns provisioning, patching, backups,
monitoring, and second-line escalation, and works within an existing technical
standard rather than setting that standard alone.
KEY RESPONSIBILITIES
•Administer [Windows Server / Linux / cloud] systems: builds, patching,
updates, and capacity checks
•Manage identity and access in [Active Directory / Entra ID / Google
Workspace]: accounts, groups, permissions, and access reviews
•Own the backup and recovery program, including scheduled restore tests
•Provision, image, and manage endpoints through [MDM or endpoint management
tool]
•Handle escalated tickets from [help desk / first line] and close the loop
•Keep runbooks, network diagrams, and asset records current
•Support onboarding and offboarding: accounts, hardware, and access removal
on the employee's last day
•Coordinate with vendors and [managed service provider, if applicable] on
incidents and renewals
•Follow change control for anything that touches production
REQUIRED QUALIFICATIONS
•[2 to 5] years administering business systems in a comparable environment
•Hands-on depth in [name the two platforms you actually run]
•Demonstrated backup and restore experience, including restores you personally
performed
•Working knowledge of networking fundamentals: [TCP/IP, VLANs, VPN, DNS]
•Clear written documentation habits
•[Certification] required or preferred: [state which]
•Must clear a background check, since this role holds privileged access
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
The FLSA computer employee exemption is not automatic for systems
administration work. It requires both a pay test (at least $684 per week on a
salary basis, or at least $27.63 per hour) and a duties test centered on
systems analysis, program or system design, and development or modification. A
role that is mostly installing, configuring, maintaining, and supporting
hardware and software may not meet the duties test even when the pay test is
met. Classify on the actual duties, and where the role is non-exempt, track
hours and pay overtime past forty in a week. 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], [on-call rate if any]
On-call: [rotation length, expected response time, how it is compensated]
To apply, email __ with your resume.
Template 2: Sole IT Administrator, Small Business
For the company with no IT function yet. Everything from a password reset to the backup strategy sits with one person, and the posting says so plainly instead of discovering it in month two.
Sole IT Administrator Job Description (Small Business, First IT Hire)
IT ADMINISTRATOR JOB DESCRIPTION (SOLE IT, SMALL BUSINESS)
Company: __ ([City, State])
Reports to: [Owner / COO / Finance Lead]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
Work model: [Onsite / Hybrid, ___ days onsite]
ABOUT THIS ROLE
[Company Name] has [number] employees and no internal IT function today.
Technology has been handled by [an office manager / a founder / an outside
provider], and it has outgrown that arrangement. You would be our first
dedicated IT hire, responsible for everything from a password reset to the
backup strategy. This is a broad generalist role, not a specialist one.
POSITION SUMMARY
The IT Administrator owns all company technology: user support, devices,
accounts, network, servers or cloud services, security basics, vendor
relationships, and documentation. You will inherit an environment that is
partly undocumented and your first months will be spent finding out what we
actually have.
KEY RESPONSIBILITIES
•Provide first and second line support to every employee
•Own accounts and access in [Google Workspace / Microsoft 365], including
onboarding, offboarding, and periodic access reviews
•Manage endpoints: procurement, imaging, MDM enrollment, repair, and disposal
•Run backups and prove they restore, on a written schedule
•Maintain the network: [firewall, wireless, VPN, ISP relationships]
•Administer [line-of-business application] and coordinate with its vendor
•Build and maintain an asset inventory and a written systems map
For companies keeping an outside provider. The responsibilities section is split three ways: retained in-house, owned by the provider, and shared. That split is the single most useful thing you can publish about this kind of role.
Co-Managed IT Administrator Job Description (Works With an MSP)
IT ADMINISTRATOR JOB DESCRIPTION (CO-MANAGED IT)
Company: __ ([City, State])
Reports to: [Operations Lead / Owner / IT Manager]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] works with an outside managed service provider that handles
[after-hours monitoring / server patching / security operations / the service
desk]. We are hiring an internal IT Administrator to own the parts that need
someone in the building and to manage the relationship with that provider. This
is a co-managed model, so the split of duties is written down and enforced.
POSITION SUMMARY
The IT Administrator is the internal owner of our technology, working alongside
our managed service provider. You handle onsite work, user-facing support,
access management, and anything specific to our business, and you hold the
provider to its contract on everything else.
KEY RESPONSIBILITIES
RETAINED IN-HOUSE (yours)
•Onsite support, hardware, and anything physical
•Identity and access: joiners, movers, leavers, and access reviews
•Administration of [line-of-business application] the provider does not touch
•Asset inventory, license tracking, and IT spend
•Employee-facing training and communication
•First triage: decide what stays here and what goes to the provider
OWNED BY THE PROVIDER (theirs)
•[After-hours monitoring and alerting]
•[Server and network patching]
•[Backup infrastructure and offsite copies]
•[Security operations and threat response]
SHARED
•Ticket flow, escalation, and root cause review
•Change control, with a written approval path for production changes
•Quarterly service review: performance against the agreement, spend, roadmap
REQUIRED QUALIFICATIONS
•[3 to 6] years in an internal IT role
•Experience working with an outside provider, ideally in a co-managed model
•Ability to read a service agreement and hold a vendor to it without drama
•Hands-on skill in [name the platforms you retain in-house]
•Documentation discipline, because two organizations share this environment
•Must clear a background check, since this role holds privileged access
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
Apply the FLSA computer employee tests to the duties you retain in-house, not
to the combined scope of the environment. A co-managed role weighted toward
support, hardware, and coordination is frequently non-exempt. State the
classification on the posting and track hours where the role is non-exempt.
Separately, confirm that the provider's staff are correctly engaged under your
vendor contract and are not treated as your employees in practice. 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]
Provider relationship: [name the scope of the agreement in one sentence]
To apply, email __ with your resume.
Template 4: Microsoft 365 and Windows Estate
For a Microsoft-centered environment: tenant administration, conditional access, endpoint policy, licensing discipline, and the Windows servers still sitting behind all of it.
IT Administrator Job Description (Microsoft 365 and Windows Estate)
IT ADMINISTRATOR JOB DESCRIPTION (MICROSOFT 365 AND WINDOWS)
Company: __ ([City, State])
Reports to: [IT Manager / Operations Lead / Owner]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] runs a Microsoft-centered environment: [Microsoft 365 tenant,
Entra ID, Intune, Windows endpoints, and ___ on-premises servers]. We are
hiring an IT Administrator to own that estate day to day, from tenant
configuration through the laptop on a new hire's desk.
POSITION SUMMARY
The IT Administrator administers our Microsoft 365 tenant, identity directory,
device management, and Windows infrastructure. The role covers licensing,
security configuration, endpoint policy, and the user-facing work that follows
from all three.
KEY RESPONSIBILITIES
•Administer the Microsoft 365 tenant: users, groups, licenses, mail flow, and
shared resources
•Manage identity in [Entra ID / Active Directory], including conditional
•Administer file and collaboration services: [SharePoint, Teams, OneDrive]
structure, sharing rules, and retention
•Maintain [number] Windows servers: patching, monitoring, and capacity
•Run backup and recovery for [servers, endpoints, and tenant data], with
documented restore tests
•Review security posture reports and close the findings that matter
•Handle escalations from [help desk / first line] and improve what recurs
•Track licensing so we pay for what we use and no more
•Document tenant configuration and every non-default setting, with the reason
REQUIRED QUALIFICATIONS
•[3 to 6] years administering a Microsoft 365 tenant in a business environment
•Hands-on experience with [Entra ID / Active Directory] and endpoint
management tooling
•Windows Server administration, including patching and backup
•Understanding that tenant-level data needs a backup plan of its own
•[Certification] required or preferred: [state which]
•Must clear a background check, since this role holds privileged access
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
Tenant administration does not automatically satisfy the FLSA computer employee
duties test. The test asks about systems analysis, design, development, and
modification, not about configuring and maintaining a vendor platform. Evaluate
the duties honestly, state exempt or non-exempt on the posting, and track hours
where non-exempt. 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]
To apply, email __ with your resume.
Template 5: Network and Systems Hybrid
For multi-site companies where connectivity matters as much as the servers, with travel, change windows, and carrier coordination written into the posting. If connectivity is genuinely the whole job, use the network administrator templates instead.
IT Administrator Job Description (Network and Systems Hybrid)
IT ADMINISTRATOR JOB DESCRIPTION (NETWORK AND SYSTEMS)
Company: __ ([City, State])
Reports to: [IT Manager / Operations Lead]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt] (see classification note)
retail] connectivity that has to stay up during business hours. We are hiring
an IT Administrator who covers both sides of the environment: the network that
connects our locations and the systems that run on it.
POSITION SUMMARY
The IT Administrator maintains network infrastructure across our sites and the
server and endpoint systems that depend on it. The role is hands-on with
switching, wireless, firewalls, and VPN, and equally hands-on with servers,
directory services, and backups.
KEY RESPONSIBILITIES
NETWORK
•Maintain switching, wireless, and firewall configuration across [number] sites
•Manage VPN and site-to-site connectivity, and the ISP relationships behind it
•Own IP addressing, VLAN design within our standard, DNS, and DHCP
•Monitor circuits and respond to outages, including coordinating carrier
tickets
•Keep network diagrams and cabling records accurate
SYSTEMS
•Administer [Windows Server / Linux] hosts and [virtualization platform]
•Manage identity, group policy, and access reviews
•Run backups with tested restores and a written recovery objective
•Patch servers and endpoints on a documented cadence
•Support [line-of-business or operational technology systems], including
[scanners, printers, time clocks, sensors]
REQUIRED QUALIFICATIONS
•[3 to 6] years covering both network and systems work
•Practical routing and switching knowledge, not only theoretical
•Firewall rule management and VPN troubleshooting
•Server administration and virtualization experience
•Valid driver's license and willingness to travel between sites
•Ability to work [after hours / weekends] for change windows, [compensated as
stated below]
•Must clear a background check, since this role holds privileged access
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
Multi-site roles generate real overtime through travel, change windows, and
outage response. If the role is non-exempt under the FLSA computer employee
duties test, all of that time is hours worked and is owed at the overtime rate
past forty in a week, and travel between sites during business hours counts.
Decide the classification before you post, not after the first invoice-sized
timesheet. 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]
Change windows and on-call: [state the schedule and how it is paid]
To apply, email __ with your resume.
Template 6: Remote-First IT Administrator
For distributed teams with no office to walk into: cloud identity, device management, hardware logistics, same-day offboarding, and the multi-state employment question that comes with hiring anywhere.
Remote-First IT Administrator Job Description (Distributed Team)
IT ADMINISTRATOR JOB DESCRIPTION (REMOTE-FIRST COMPANY)
Reports to: [Operations Lead / Owner / IT Manager]
Employment type: Full-time, remote
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
Coverage hours: [time zone and hours you expect to be reachable]
ABOUT THIS ROLE
[Company Name] has [number] employees across [number] states and no central
office to walk into. Every device is shipped, every account is cloud-based, and
every support conversation happens over chat or video. We are hiring an IT
Administrator who has run technology this way before.
POSITION SUMMARY
The IT Administrator owns cloud identity, device management, and remote support
for a distributed workforce, along with the logistics of getting hardware to
people and back again.
KEY RESPONSIBILITIES
•Administer cloud identity in [Google Workspace / Microsoft 365 / Okta],
including SSO, MFA, and group-based access
•Manage devices remotely through [MDM platform] across [macOS / Windows /
both], including enrollment, policy, encryption, and patching
•Run hardware logistics: procurement, drop-shipping to new hires, returns,
repairs, and secure disposal
•Own SaaS administration: provisioning, deprovisioning, license counts, and
renewal calendar
•Support employees remotely with clear written communication and recorded
fixes
•Maintain security baselines for a workforce with no network perimeter
•Run onboarding day one: accounts, device, access, and a working setup before
the first meeting
•Run offboarding same day: access revoked, device recovered, data retained per
policy
•Keep documentation good enough that employees self-serve the routine things
REQUIRED QUALIFICATIONS
•[3 to 6] years in IT administration, including remote or distributed support
•MDM experience on the platforms we run
•Cloud identity administration and SSO configuration
•Strong written communication, since most support is asynchronous
•Organized approach to shipping, tracking, and recovering hardware
•Must clear a background check, since this role holds privileged access
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
Remote roles carry two extra compliance questions. First, classification: apply
the FLSA computer employee duties test and, where the role is non-exempt, use a
timekeeping system that captures work performed outside scheduled hours.
Second, location: an employee working from another state generally creates
payroll registration, tax withholding, and employment law obligations in that
state. Confirm where the hire will actually sit before you make the offer. 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], [home office stipend]
Eligible locations: [list the states where you can employ]
To apply, email __ with your resume.
Which Level You Actually Need
The level you post determines the pay band, the supervision required, and whether the hire can be trusted alone with production access. Get it wrong in either direction and the hire fails: a junior left unsupervised breaks things, and a senior given ticket work leaves within a year.
Use the boundary test. Ask what the person is allowed to change without asking anyone. If the honest answer is nothing without approval, you are hiring a junior IT administrator. If the answer is anything within an existing standard, that is the mid-level role this page describes.
Level
Authority boundary
What the posting emphasizes
Where it fits
Junior IT administrator
Acts within a written task boundary, escalates the rest
The boundary itself, supervision, and the growth path
You have an existing admin who needs volume absorbed
IT administrator
Operates independently inside an existing standard
The environment, the platforms, and what is broken today
Most small and mid-size companies most of the time
Senior IT administrator
Sets the standard, owns recovery objectives and vendors
Ownership, design decisions, and the last escalation
You need judgment rather than throughput
IT manager
Owns budget, roadmap, and people
Headcount, spend, and vendor strategy
Technical work is delegated rather than performed
If your posting reads like the senior row but pays like the middle row, the search stalls. Our senior IT administrator templates cover the ownership language, and the IT manager templates cover the point where the job becomes management rather than administration.
In-House Administrator or Managed Service Provider?
Answer this before writing the posting, because it changes the job description more than any technology on the list. The decision is not about cost alone. It is about presence, coverage, institutional knowledge, and how fast an access decision has to be made.
Hire in-house
When presence and context win
Hire when you need someone physically present, when your line-of-business application is unusual enough that an outside team will never learn it properly, when access decisions have to be made in minutes rather than through a ticket, or when the volume of small requests is already high enough to fill a week. Institutional knowledge is the real asset here, and it is the one thing a provider cannot hold for you.
Use a provider
When coverage and depth win
A provider is the better answer when you need coverage across nights and weekends that one person cannot supply, when you need specialist depth occasionally rather than constantly, or when the environment is small enough that a full-time administrator would spend half the week idle. You are buying a bench and a rota, not a colleague.
Run both
The common small-company answer
Co-managed IT is what most growing companies land on: an internal administrator who owns access, devices, and anything specific to the business, with a provider covering monitoring, after-hours response, and the platforms nobody internally has time to master. It only works when the split is written down, because an unwritten split becomes an argument during an outage.
Most companies I talk to arrive at the third answer without ever deciding to. A provider was hired years ago, an internal person was added later, and nobody wrote down the split. Then an outage happens and both sides assume the other was monitoring. Template 3 above exists to prevent exactly that, by publishing the split in the job description itself.
Whichever model you choose, the security baseline is yours to own. The federal Cybersecurity and Infrastructure Security Agency guidance for small businesses sets out the practices a small environment should have in place regardless of who runs it: multifactor authentication, patching, backups that are tested, and a plan for removing access quickly.
Overtime and the Computer Employee Exemption
A salaried IT administrator is not automatically exempt from overtime. The FLSA computer employee exemption has a pay test and a duties test, both must be met, and a large share of small-company administrator roles fail the duties test.
The rule is set out in the federal regulation on computer employees as exempt professionals, which requires at least $684 per week on a salary basis or at least $27.63 an hour, plus a primary duty of systems analysis, systems or program design and development, or operating system modification. Our breakdown of exempt versus non-exempt classification works through the tests in general terms.
The computer exemption has two tests, and the duties test is the hard one
The federal computer employee regulation requires a pay test and a duties test, and both must be satisfied. The pay test is straightforward: at least $684 per week on a salary basis, or at least $27.63 an hour for an hourly computer employee, which is the one exemption in the white-collar family that allows an hourly rate. The duties test is where most administrator roles fail. It asks whether the primary duty is systems analysis, the design or development of systems or programs, the design or modification of operating system programs, or a combination requiring the same skill level. Keeping an environment running is not on that list. This is general information, not legal advice.
Maintaining hardware and software is called out as not qualifying
The regulation is unusually explicit for a reason: employers kept assuming that anyone who touches computers is exempt. Work that consists of manufacturing, repairing, or maintaining computer hardware and related equipment does not qualify, and neither does being a highly skilled user of software rather than someone who designs or modifies it. Read those two sentences with an honest picture of the week you are hiring for. If the week is provisioning, patching, ticket resolution, hardware, and vendor calls, the safer classification is non-exempt. This is general information, not legal advice.
Non-exempt is not a demotion, and it needs timekeeping
Classifying an IT administrator as non-exempt does not reduce the seniority of the role or the salary you pay. It means hours are tracked and overtime is paid past forty in a workweek, which for this job means the 2 a.m. outage, the Saturday migration, and the phone call during dinner all count as hours worked. Small companies get into trouble here by paying a good salary, calling it exempt, and then relying on after-hours availability that was never budgeted. Decide the classification before you post, put it in the offer, and give the person a way to record time that does not depend on their memory.
State rules can be stricter than the federal floor
Several states set their own computer professional exemption with a higher pay threshold, a narrower duties definition, or both, and a few apply daily overtime rules that the federal standard does not. The federal floor is exactly that, a floor. Check your state labor department before you finalize the classification, especially if you are hiring remotely into a state where you have no other employees, because the rule that applies is generally the one where the work is performed rather than where your headquarters sits. This is general information, not legal advice.
The practical consequence for a small employer is a budgeting one. If the role is non-exempt, after-hours incident response and weekend change windows are hours worked, and overtime is owed past forty in a week. Price that into the offer rather than discovering it in the third month.
What to Pay an IT Administrator
There is no Bureau of Labor Statistics occupation called IT administrator. Federal wage data classifies by occupation rather than by job title, so the honest benchmark is the percentile ladder of the nearest classification, which is network and computer systems administrators.
The Nearest BLS Classification and Its Percentile Ladder
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), network and computer systems administrators (SOC 15-1244) had a national median annual wage of $99,130, equal to $47.66 per hour. The ladder ran $62,640 at the 10th percentile, $78,010 at the 25th, $126,640 at the 75th, and $155,050 at the 90th (U.S. Bureau of Labor Statistics, OEWS).
A generalist IT administrator at a small company usually lands between the 25th percentile and the median of that classification. Support-weighted versions of the role benchmark lower, and roles carrying sole ownership of an environment benchmark higher than their headcount would suggest, because there is nobody to escalate to.
Benchmark classification
25th percentile
Median
75th percentile
When to use it
Network and computer systems administrators
$78,010
$99,130
$126,640
The closest match for an infrastructure-owning administrator
Computer network support specialists
$58,240
$76,220
$98,750
Support-weighted roles that also touch network duties
Computer user support specialists
$49,000
$61,860
$79,040
Roles where the week is mostly tickets and devices
Information security analysts
$97,810
$129,180
$163,500
Reference when the posting carries a real security program
Computer and information systems managers
$138,060
$175,140
$220,730
Reference when the role is drifting into management
Two adjustments before you publish a number. Metro differentials on this occupation are wide enough that a national median is a starting point rather than an answer. And the occupation is not growing: the Bureau of Labor Statistics Occupational Outlook Handbook projects employment to decline 4 percent from 2024 to 2034 while still expecting about 14,300 openings a year from replacement need, which means experienced administrators keep circulating even as the headline shrinks. Publish a good-faith range where pay transparency laws apply.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Hiring the first IT administrator fails in three predictable places: the posting becomes a wish list, one person quietly accumulates every key in the building, and the employee lifecycle work lands on IT with no process behind it. Each has a fix that costs an afternoon.
The posting turns into a wish list because nobody has decided what the job is
The first IT administrator posting at a small company is usually written by an owner or an operations lead who is describing every technology annoyance of the past two years rather than a job. Fourteen platforms appear, five certifications appear, and the experience floor lands at seven years for a salary that supports three. Strong candidates read that as a company that has not decided what it needs, and they skip it. The fix takes an afternoon: list what actually breaks, sort it into what a person must own in month one and what can wait until month six, then write the posting from the first list only. The second list becomes the growth section, which is the part that closes candidates anyway.
One person holds every key and there is no plan for the day they leave
A sole IT administrator accumulates administrator rights, vendor logins, license portals, firewall passwords, and the only real knowledge of how the environment fits together. That is not a character risk, it is a structural one, and it is worst at exactly the companies least able to absorb it. Build the countermeasure into the role from the first week: a documented systems map, credentials in a shared vault the owner can reach, an access register that says who has what and why, and a written escalation path to a provider for the week the administrator is on vacation. Ask about documentation habits in the interview, and treat a candidate who volunteers a runbook as evidence rather than as a nice extra.
The employee lifecycle work lands on IT with no process behind it
Every new hire needs an account, a device, group access, and a working setup before their first meeting, and every departure needs all of it removed the same day. At a small company that sequence lives in somebody's head, which is how a former employee keeps mailbox access for four months. This is exactly the seam FirstHR was built for. The onboarding wizard runs the same sequence for every hire, task workflows hand IT its steps with owners and due dates, employee profiles and the HRIS hold the record of who has what, e-signature covers the acceptable use and device policies, and training modules deliver security awareness before day one. 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 shifts to a repeatable onboarding checklist. For this role specifically, the account and device sequence matters in both directions, and our guide to IT onboarding covers the day-one setup that your new administrator will be running for everyone else.
Key Takeaways
IT administrator is the generalist infrastructure title: servers, network, identity, endpoints, and backups owned by one person rather than split across specialists.
At a company under about two hundred people, IT administrator and system administrator describe the same job, so choose the title by what the majority of the week looks like.
Post the level deliberately: junior works inside a written task boundary, mid-level operates independently within an existing standard, senior sets the standard and owns recovery objectives.
Decide in-house versus managed provider before writing the posting, and if you run both, publish the split of duties in the job description rather than discovering it during an outage.
The FLSA computer employee exemption needs both a pay test ($684 per week or $27.63 an hour) and a duties test that maintaining and supporting systems does not satisfy, so many of these roles are non-exempt.
There is no BLS occupation for the title: network and computer systems administrators had a median of $99,130 with a 25th percentile of $78,010 (BLS OEWS, May 2025), and most small-company roles sit in that band.
An IT administrator inherits the employee lifecycle whether or not anyone planned it. FirstHR gives that work a process: onboarding workflows that assign IT its steps with owners and due dates, e-signature for acceptable use and device policies, document management for asset records and access approvals, and training modules for security awareness before day one. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does an IT administrator do?
An IT administrator keeps a company’s technology running: servers or cloud services, the network, identity and access, endpoints, backups, and the escalated support that a first line cannot resolve. At a small company the same person also handles procurement, licensing, vendor relationships, and the technology half of onboarding and offboarding. The distinguishing feature of the title is breadth rather than depth. A database administrator owns one platform and a network administrator owns connectivity, while an IT administrator owns whatever the business runs on. That breadth is exactly why the title fits companies under a few hundred employees, where nobody can afford to specialize. Write the posting around the two or three systems that actually matter in your environment rather than around a generic list, because candidates judge fit by the platform names.
What is the difference between an IT administrator and a system administrator?
In practice the two titles describe overlapping jobs, and at a company under about two hundred people they are usually the same job. The conventional distinction is emphasis: system administrator signals depth in servers, operating systems, virtualization, and storage, while IT administrator signals breadth across servers, network, identity, endpoints, and user support. Larger organizations enforce the distinction because they have enough people to specialize. Smaller ones cannot. Choose the title by what candidates in your market search for and by what the week actually looks like: if most of it is server and platform work, post a system administrator role, and if it swings between a laptop, a firewall rule, and an access review, post an IT administrator role. Do not post both for the same headcount, because that reads as indecision.
Are IT administrators exempt from overtime?
Often not, and assuming they are is a common and expensive mistake. The FLSA computer employee exemption requires both a pay test, at least $684 per week on a salary basis or at least $27.63 an hour, and a duties test focused on systems analysis, the design or development of systems and programs, and the modification of operating system programs. Federal regulation states plainly that employees engaged in manufacturing, repairing, or maintaining computer hardware, and highly skilled users of software rather than designers of it, do not qualify. A typical small-company IT administrator whose week is provisioning, patching, tickets, hardware, and vendor calls frequently fails that duties test even when the salary clears the threshold. Some states apply a stricter test than the federal one. Classify on duties, state it on the posting, and track hours where the role is non-exempt.
How much does an IT administrator make?
There is no Bureau of Labor Statistics occupation named IT administrator, so the honest benchmark is the nearest classification. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), network and computer systems administrators had a national median annual wage of $99,130, with a percentile ladder running $62,640 at the 10th, $78,010 at the 25th, $126,640 at the 75th, and $155,050 at the 90th. Support-weighted roles benchmark lower: computer network support specialists had a median of $76,220 and computer user support specialists $61,860. A generalist IT administrator at a small company usually lands between the 25th percentile and the median of the administrator classification, shifted by metro, platform scope, and whether the role carries sole ownership. Metro differentials on this occupation are large, so treat the national figure as a starting point.
Should a small business hire an IT administrator or use a managed service provider?
Hire in-house when you need someone physically present, when your line-of-business systems are unusual enough that an outside team will never learn them properly, or when the volume of small requests already fills a week. Use a provider when you need coverage across nights and weekends that one person cannot supply, when you need specialist depth occasionally rather than constantly, or when the environment is small enough that a full-time administrator would be idle half the time. Most growing companies end up doing both, which is the co-managed model: an internal administrator owns access, devices, and anything business-specific, while the provider covers monitoring, after-hours response, and the platforms nobody internally has time to master. The model only works when the split of duties is written down before an outage forces the conversation.
What should an IT administrator job description include?
Eight things: the company size and how many people the role supports, the actual platform list limited to what you run, the responsibilities grouped by system rather than listed at random, experience stated as a band with certifications marked required or preferred, the on-call and change-window expectation with its compensation, a background check notice because the role holds privileged access, the FLSA classification, and the pay or a good-faith range. Add the equal opportunity statement and name a real person to apply to. The most common omission is the escalation structure. Candidates want to know whether they are the last line or whether a provider sits behind them, because the answer changes the job entirely. The six templates on this page carry that structure so you only rewrite the environment-specific parts.
How do I hire an IT administrator without an HR department?
Run a short fixed sequence and decide the scope before you post. Write the posting from what actually breaks today, not from every technology you own. Screen on two things that predict performance: a restore the candidate personally performed, and documentation they can describe in detail. Run a practical scenario instead of a trivia quiz, ask how they would remove access for a departing employee in one hour, and check references with someone who saw them handle an outage. Move quickly, because generalists with real infrastructure experience are usually in more than one process. Then treat day one as its own project: accounts, device, privileged access with an approval record, policy acknowledgments, and security training. FirstHR runs that sequence with onboarding workflows, e-signature, document management, and training modules. Applicant tracking is coming soon to FirstHR.
