How to Get Off the Help Desk in Under a Year

I started on an MSP help desk at Level 1 in 2021. About nine months to a year later I was Level 3. It wasn’t luck and it wasn’t time served. It came down to three habits, and none of them need a degree or a special background.

I gave the short version in my 2026 update. This is the practical version: what to actually do, starting this week, if you’re on L1 and want off it.

First, know what you’re aiming for

Tier names mean different things at different companies, but at most MSPs it breaks down roughly like this:

• Level 1: First contact. Password resets, account lockouts, printers, known fixes from the documentation. Your job is to resolve the easy stuff fast and escalate the rest cleanly.
• Level 2: Deeper troubleshooting. Problems that don’t have a documented fix, issues that span more than one system, and smaller project work.
• Level 3: The escalation point. Servers, networking, Microsoft 365 tenants, the problems L2 couldn’t close. You’re the person other techs come to.

The jump from L1 to L3 isn’t about knowing everything. It’s about becoming the person who can be handed a problem with no documented fix and work it to the end. Every habit below builds that.

What Level 3 looked like for me

To make that concrete, here’s the kind of work that landed on my desk once I got there:

• Physical servers, usually chasing a problem all the way down to firmware or a dependency issue.
• Network problems, everything from slow Wi-Fi to intermittent connectivity. That meant running radio scans and taking the building itself into account.
• AWS, from deploying compute and storage to building out the networking.
• Site-to-site connectivity, linking physical offices to other sites, to Azure, and to AWS without disrupting the people working there.
• Rotating encryption keys as needed.
• Root cause analysis on the problems that kept coming back, and security incidents.
• Project scoping and project work, from figuring out what a client actually needed to delivering it.

One lesson from the Wi-Fi work stuck with me: just because a wireless system looks good on paper doesn’t mean it is. Walls, glass, metal, and floor layout change everything. The environment matters just as much as the equipment.

None of that is L1 work, and none of it happens overnight. You get there one hard ticket at a time.

Habit 1: Take the hard tickets

On an MSP help desk, the tickets nobody wants are the ones that teach you the most. Escalations, strange network problems, the client nobody else wants to call back. Most L1 techs avoid them because they hurt ticket counts and take time. That’s exactly why taking them sets you apart.

The hardest one for me early on was the first VPN problem I took on, because I had never done it before. What got me through it was a really good coworker who showed me how, explained it, and answered my questions without doing it for me.

Find that person. Someone who will show you, explain it, and let you do the work. Then let yourself struggle. If you’re uncomfortable, you’re going in the right direction. And remember: if you’re the smartest person in the room, it’s time for a new room.

How to do it without getting in over your head:

• Ask to keep it. When a ticket is above you, ask your lead if you can keep working it with help instead of escalating it away. The worst answer is no.
• Follow your escalations. When you do escalate, read how it got solved. Ask the tech who fixed it to walk you through it for five minutes. Next time, that ticket stays with you.
• Volunteer for the unpopular stuff. After-hours maintenance, onboarding a new client, the messy migration. Those are where you see how the whole environment fits together.

Senior techs notice who’s willing. That matters when a Level 2 or Level 3 spot opens and your manager asks who’s ready.

Habit 2: Keep the certs coming, and tie them to the queue

You don’t need every cert before you apply. I got hired with just A+ and Network+, and I’d passed Network+ only a couple of days before the offer. But don’t stop once you’re in. I passed Security+ a week after I started, then Apple ACSP, then AZ-900. Keep something in progress at all times.

The trick is to pick the next cert based on what you’re seeing in tickets, so the studying and the job reinforce each other:

• DNS, DHCP, VPN, and Wi-Fi tickets? That’s Network+ material.
• MFA problems, phishing reports, compromised accounts? That’s Security+.
• Microsoft 365 licensing, mailbox issues, Intune enrollment? That’s the Microsoft admin certs, MD-102 and the Microsoft 365 admin exam.
• Clients moving servers to the cloud? That’s AZ-104.

When you study something on Tuesday and see it in a ticket on Thursday, both stick. And every cert gives your manager a concrete reason to move you up. The full order I recommend is in the IT cert roadmap for 2026.

Habit 3: Troubleshoot in order, not by guessing

This one came from my years doing electrical work, and it’s the most underrated skill on a help desk. In the trades you don’t guess. You verify power, isolate the circuit, test one thing at a time, and confirm the fix. The same method works on a network outage or a broken sync.

Here’s what that looks like on a ticket like “the internet is down”:

1. Confirm the symptom. Is it one user, one site, or everyone? One website or all of them?
2. Start at the bottom. Link lights or Wi-Fi connection. Does the device have a valid IP address, or a 169.254 address?
3. Work outward. Can it reach the gateway? Can it reach an outside IP address? Does DNS resolve names?
4. Change one thing at a time. If you change three things and it starts working, you don’t know what fixed it, and you can’t fix it next time.
5. Confirm the fix with the user before you close the ticket.

Techs who work in order close tickets faster, escalate less, and write notes other people can follow. Leads notice that fast.

Write tickets senior techs can trust

Your ticket notes are how senior techs and managers judge your work when they’re not watching. Good notes make you look like you’re already working at the next level. Every escalation should answer four questions:

• What’s the symptom, in the user’s words and in technical terms?
• What did you check, and what did each check show?
• What did you change, if anything?
• What do you think is going on, and why?

“User can’t print, escalating” tells the next tech nothing. “Print jobs stuck in queue for one user only. Restarted spooler, cleared queue, same result. Other users on the same printer are fine. Suspect a bad driver on this workstation” gets the problem solved and gets your name remembered.

Make the ask

Doing the work isn’t enough if nobody knows you want to move up. Tell your manager directly that you’re aiming for Level 2 or Level 3, and ask what the gap is between where you are and where they need you to be. Then close that gap and bring it back up at your next one-on-one. A manager who knows what you want and sees you checking off the list is far more likely to put your name forward.

What slows people down

• Hoarding easy tickets to keep the numbers up
• Escalating with no notes, or escalating before trying anything
• Waiting for someone to train them instead of learning from the tickets in front of them
• Stopping certs after the first one gets them hired
• Never telling anyone they want to move up

If I did it again

I’d apply for the job sooner instead of waiting until I felt ready. I’d have gone after Microsoft skills earlier, since that’s most of what an MSP touches every day. And I’d have built a home lab sooner, so I’d have had more to practice on outside of work.

Starting from zero? The cert roadmap lays out what to study first, and the free roadmap PDF on the homepage covers a $0 home lab and how to turn trade or military experience into resume lines an IT hiring manager understands.