Network Engineer, Network Administrator, or System Administrator: Which Tier 3 Role Does Your MSP Need?
Key takeaways
- At an MSP, Tier 3 refers to whatever Tier 1 and Tier 2 can't close. Server and identity escalations belong with a sysadmin. Network faults and design changes belong with a network admin or engineer.
- Network engineers spend most of their week on Tier 3 and project work. Sysadmins and network admins sometimes split their time with Tier 2 queues.
- Two to three months of tagged escalations, plus your project pipeline, will show you which role you need to add next.
- One person can cover network and systems administration for a while. That setup breaks once sites, firewalls, or projects multiply.
You open a blank job description for your next senior tech and stall on the first line. Sysadmin? Network admin? Network engineer? The person handling your hardest tickets today probably does a bit of all three, so any title feels like a guess.
It's worth getting right, though, because the title shapes who applies and which escalations finally leave your desk. This guide settles the system administrator vs. network administrator question in MSP terms, then adds the network engineer to the comparison. You'll see what each role handles and where it sits in your Tier 1–3 structure.
LTVplus is the managed technical support partner MSPs trust to handle their most important clients, and our dedicated engineers cover the work of all three roles. If you're still mapping your tiers, start with our guide to dedicated Tier 1–3 engineers for MSPs. For certifications by tier, see our IT support certifications guide.
System administrator vs. network administrator vs. network engineer: what's the difference?
A system administrator keeps servers, identity, and endpoints running. A network administrator keeps the network healthy day to day, from Wi-Fi to VPN access. A network engineer designs, builds, and changes the network. At an MSP, any of the three can own Tier 3 escalations, depending on what's breaking.
The titles blur because the work overlaps. Here's how the roles usually split.
| System administrator | Network administrator | Network engineer | |
|---|---|---|---|
| The question they answer | "Why can't this user or server do its job?" | "Why is the connection slow or down?" | "What should the network look like next?" |
| Tier 3 work they own | Server, identity, and tenant escalations | Network fault escalations | Design changes and projects |
| Common certifications | Microsoft 365 Administrator, Azure Administrator, Endpoint Administrator | CompTIA Network+, CCNA | CCNA, Fortinet NSE |
| When clients need them | Constantly | When sites and devices multiply | During growth, moves, and security projects |
What does a system administrator do at an MSP?
Your sysadmin owns what runs on top of the network. In a typical week, that includes:
- Fixing failed backups and testing restores
- Managing users and access in Active Directory and Entra ID
- Keeping Windows Server and Hyper-V or VMware hosts patched and healthy
- Handling Microsoft 365 changes to mailboxes, Teams, SharePoint, and licenses
- Pushing device policies and apps through Intune
- Scripting repeat jobs in PowerShell
The U.S. Bureau of Labor Statistics (BLS) puts sysadmins and network admins in a single occupation, network and computer systems administrators. It describes the job as installing, configuring, and maintaining an organization's networks and systems. That shared category explains a lot of the confusion in job postings.
For MSPs with Microsoft 365-heavy clients, much of the sysadmin's day happens inside tenants rather than on servers. That's the work our Microsoft 365, Azure, and Intune engineers take on.
What does a network administrator do?
A network admin's job is to make sure nobody notices the network. The day-to-day work looks like this:
- Configuring VLANs and switch ports
- Troubleshooting Wi-Fi drops and running wireless surveys
- Setting up client VPN access
- Making firewall rule changes and firmware updates
- Diagnosing latency, packet loss, and ISP issues, then working them with carriers
- Backing up device configs and keeping network documentation current
System administrator vs network administrator: when one person covers both
Career guides often describe a network administrator as a "specialized kind of system administrator." On paper, that's fair. In an MSP queue, though, the two kinds of work behave differently. Network changes wait for change windows, while server and tenant tickets pile up during the day.
A combined network and systems administrator works well when:
- Most clients run one or two sites
- Your client base is mostly Microsoft 365 with simple firewall setups
- Network projects come up a few times a year
However, it's time to split the role when:
- Firewall changes keep getting pushed to "after hours" and then pushed again
- Server escalations sit untouched while network work runs
- One person holds all the credentials and all the context for both
What does a network engineer do, and how is it different?
Network engineers decide what the network should look like and then make it happen. Their work includes:
- Designing networks for acquisitions and client growth
- Planning capacity as clients add users and locations
- Building firewall architecture and network segmentation
- Running migrations, such as a move to SD-WAN
BLS tracks network engineers under computer network architects. Most reach the role after five or more years in a related job, often as a network or systems administrator. BLS also notes that architects may manage and troubleshoot the networks they've built, so the line between engineering and administration isn't sharp.
Network engineer vs. network administrator: where the handoff happens
The handoff usually happens at the change request. A network admin makes changes inside the existing design. When a request changes the design itself, such as a new site, a new firewall vendor, or a new WAN, it goes to the engineer.
Expert tip: Write that boundary into your runbook. List which network changes a Tier 2 admin can make on their own and which need an engineer's sign-off. It stops the "quick VLAN change" that quietly breaks a client's segmentation.
What skills and background does each role need?
The task lists above double as each role's core technical skills. When you write the job description or plan an interview, these are the differences worth testing.
| System administrator | Network administrator | Network engineer | |
|---|---|---|---|
| Scripting | PowerShell for user, tenant, and server tasks | Light scripting for config backups and reports | Python or similar for network automation |
| Interview scenario | "A file server slows to a crawl every afternoon. Walk me through your first hour." | "A client says the internet is slow. What do you check, and in what order?" | "A client opens a second office next month. How would you connect it?" |
All three also need solid troubleshooting habits, clean documentation, and the ability to explain a problem to a client without jargon. BLS lists a bachelor's degree as the typical entry point for network and computer systems administrators, but for an MSP hire, hands-on time with stacks like your clients' usually tells you more.
Where does each role sit in your Tier 1–3 structure?
Tier 3 is the senior layer that handles root-cause analysis, server and network faults, and changes that need deep platform knowledge. The useful question is which kind of Tier 3 ticket your clients generate most.
| Tier | Example ticket | Usual owner |
|---|---|---|
| Tier 1 | Password reset, MFA re-enrollment, printer mapping | Help desk tech |
| Tier 2 | Mailbox permissions, a new hire's account setup, a shared folder that won't map | Sysadmin or network admin |
| Tier 3 (systems) | A Conditional Access policy locking out a department, a Hyper-V host that keeps crashing | Senior sysadmin |
| Tier 3 (network) | A site-to-site VPN tunnel that keeps dropping, slowdowns nobody can reproduce | Senior network admin or network engineer |
| Tier 3 (projects) | Replacing every firewall in a client fleet, an on-prem to Azure move | Network engineer or systems engineer |
For how tickets should move between these layers, see our guides to MSP escalation workflows and the MSP help desk.
Tier 3 tickets stacking up on one senior tech? LTVplus can add a dedicated network or Microsoft 365 engineer who works inside your PSA and follows your escalation rules. For one-off work, like a migration or a new client onboarding, our Tier 3 engineers scope and quote the project up front.
See network engineering services or see Tier 3 and project engineering.
How do these roles grow inside an MSP?
Most senior techs start on the help desk. After Tier 2, the path usually splits into two tracks:
- Systems track: sysadmin, then systems engineer or cloud engineer
- Network track: network admin, then network engineer
Either track can lead to service delivery management or technical leadership. BLS backs up the network side: experienced network architects may move into computer and information systems manager roles, which are sometimes called chief technology officers.
Reporting lines depend on your size. A common setup has admins reporting to a service delivery or operations manager and network engineers reporting to the CTO or VP of Service Delivery.
This matters for hiring because a visible ladder is what makes upskilling a real option. A Tier 2 tech who can see the next step is more likely to take on escalations and stay long enough to grow into them. For how many people each layer needs, see our MSP staffing ratio guide.
How to decide which Tier 3 role your MSP needs next
Your ticket history already holds the answer. Here's how to pull it out:
- Pull 60–90 days of Tier 2 and Tier 3 tickets. A shorter window can mislead you if one big client incident skews the month.
- Tag each ticket by domain: server/identity, Microsoft 365/Azure tenant, network operations, or network change/project.
- Note who closed each one and how long it waited for that person. Wait time shows you where the bottleneck sits.
- Add your project pipeline for the next two quarters. Count onboardings, migrations, and site builds you've already sold or expect to sell.
- Map your client stacks. Many sites and firewalls point one way. Heavy Microsoft 365 use points another.
- Match the pattern to a role using the table below.
| If most escalations are… | Add… | Matching LTVplus service |
|---|---|---|
| Server, identity, or Microsoft 365/Azure | A senior sysadmin or Microsoft 365 engineer | Microsoft 365, Azure, and Intune management |
| Day-to-day network faults across many sites | A network admin | Network engineering services, which cover configuration and troubleshooting |
| Firewall, VPN, and site changes | A network engineer | A dedicated network engineering seat, with larger projects quoted as fixed-price work |
| Spiky: migrations, onboardings, root-cause investigations | Project capacity rather than a new headcount | Tier 3 and project engineering, as fixed-price projects or a monthly escalation retainer |
Should you hire, upskill, or add a dedicated engineer?
Once you know the role, you still have to decide how to fill it. Each route fits a different situation.
| Full-time hire | Upskill a Tier 2 tech | Dedicated engineer | Tier 3 project engineering | |
|---|---|---|---|---|
| Time to productivity | Recruiting time plus ramp-up | Months of training while still carrying Tier 2 work | About 30 days from scoping call to go-live with LTVplus | Starts once the project is scoped |
| Cost structure | Salary, benefits, tools, and training | Training and certification costs, a raise, and Tier 2 backfill | From $3,000 per month per dedicated engineer seat with LTVplus | Fixed-price project or monthly escalation retainer |
| Coverage | One person's working hours | Same as today, with a gap in Tier 2 | Business hours, extended, or 24/7 | Scheduled project windows plus escalation hours |
| Knowledge risk | Leaves with the person unless documented | Stays in-house | Documented in your platforms, with backup coverage | As-built docs written into your platforms |
| Best for | Steady, predictable volume in one domain | A strong Tier 2 tech who already takes escalations | Steady volume without the recruiting cycle | Migrations, onboardings, and one-off root-cause work |
A dedicated engineer can come through staff augmentation or a managed team. Both are valid, and the right one depends on how much day-to-day management you want to keep. Our guide to staff augmentation vs. managed services compares them in detail.
To compare the in-house side with your own numbers, try our MSP technician cost calculator or check current rates on our pricing page.
Match the role to the work, not the title
Your clients don't file tickets by job title. Whichever role you add next should match the escalations that keep landing on your senior team, and the projects already in your pipeline.
LTVplus offers Managed Technical Support for MSPs. We build remote teams that seamlessly integrate with your company, including dedicated network and Microsoft 365 engineers and Tier 3 project engineers who work in your PSA, under your brand.
FAQs
Is a network administrator the same as a system administrator?
No. A network administrator keeps the network itself running, while a system administrator looks after the servers, accounts, and devices that use it. At smaller MSPs, one person may handle both, but the jobs usually separate as the client base grows.
Can one person handle both network and systems administration at an MSP?
Yes, but only for a while. A combined role works best when few clients have multiple sites and big network projects are rare. Once the workload grows, splitting the role keeps both kinds of tickets moving.
Is a network engineer a Tier 3 role?
Usually. Network engineers take the complex network escalations and projects that Tier 1 and Tier 2 can't resolve. At smaller MSPs, a senior network admin may also handle Tier 3 network faults.
Which certifications should MSP sysadmins and network admins hold?
It depends on the technologies your clients run and what each role owns. Microsoft's role-based certifications suit most sysadmin work at MSPs, and vendor-neutral or Cisco certifications are common starting points for network admins. Our IT support certifications guide breaks them down by tier.