People rarely get stuck on a service desk because they're short on certs or hours. They get stuck because they treat the desk like a waiting room. The assumption is that doing the job well, for long enough, eventually gets you moved up. It doesn't. If anything, being good at helpdesk is what keeps you there.
Who this is for
- You've been on a service desk somewhere between six months and four years, and the progression you were quietly promised hasn't shown up.
- You've been grinding certs in the evenings and none of it has turned into interviews, never mind offers.
- You're starting to suspect the "do two years on the phones and move internally" advice isn't really how it works anymore. It isn't.
Who it isn't for
- People who genuinely like frontline support and want to grow inside it. Team lead, service delivery, ITSM. That's a proper career and a decent one. None of this applies to you.
- Anyone in their first three months on a desk. You haven't earned the right to be frustrated yet. Stay put, learn the tooling, make friends with the people in the teams you'll later want to join.
The real tradeoff
Helpdesk pays you in two things: stability and pattern recognition. What it quietly takes from you is positioning. Every ticket you close, every password reset, every Outlook profile you rebuild trains your brain to be reactive and narrow. That's a real skill. It just happens to be the wrong one for the job you want next, and nobody on the inside is going to sit you down and tell you, because the business needs you on the phones.
The longer you stay, the more your CV starts reading like someone whose ceiling is helpdesk. Recruiters skim. They aren't going to dig three screens deep for the bit of Terraform you wrote in your evenings.
What people get wrong
Number one by miles: stacking certs as a substitute for evidence. A+, then Network+, then Security+, then maybe an AZ-900 because someone on Reddit said so. Twelve months of evenings, a couple of hundred quid, and absolutely nothing you can show anyone. Then surprise when the interviews don't come.
Passing a multiple-choice exam proves you can pass a multiple-choice exam. A junior cloud or security or sysadmin role is hiring for somebody who has done a thing. Even a small thing. Outside the ticket queue. Those two are not the same and haven't been since about 2021.
The other big one is misreading the internal move.
People assume the company that took them on will eventually shuffle them sideways into the team they want. In a 40-person business that sometimes happens. In a mid-sized or large one it very rarely does. Three reasons for that.
- The team you want is hiring against a budget and a written job spec. Your name is on neither.
- Your current manager has every reason to keep you where you are. Losing a competent T1 costs them real money and real sleep.
- The internal recruiter has no idea you exist, and neither does the hiring manager on the team you're eyeing up.
What the next twelve months actually look like
If you're serious about leaving (not "would be nice" serious, but "this is the project for the next year" serious), here's what it looks like.
Hours. Six to ten a week, sustained. Not twenty-five for a fortnight and then nothing for a month. The people who get out are deeply boring about it.
Money. Under £300 for the year is plenty. A cloud free tier, a domain, a cheap VPS, one paid cert in the back half of the year. Spending more than that is usually procrastination wearing a costume.
What you build. Pick one direction. Cloud and infra, or security, or networking, or automation. Don't pick all four. Build three things in it. They don't need to be perfect. They need to be finished, visible, and yours. A home lab on GitHub. A short write-up explaining a problem you hit and how you got around it. A bit of automation that solves something real on your current desk. That last one is gold, because it's evidence and a talking point in the same artefact.
What stalls people. Tutorial loops. Watching a third Azure fundamentals course rather than breaking something on a real subscription. The dopamine of learning isn't the same as the discomfort of doing, and only the second one shows up on a CV.
What it feels like, day to day. Mostly boring. Sometimes a bit demoralising. Punctuated by a very specific feeling, usually around month seven or eight, when you realise the gap between you and the colleagues who aren't doing this has become visible to other people. When that lands, you're close.
When to walk away from the plan
Not every helpdesk leaver should leave IT, and not every IT person should leave helpdesk. Some honest disqualifiers.
- You can't realistically hold down six hours a week of focused project work outside your job for half a year. That isn't a moral failing, it's usually a life-stage thing. The plan above won't work for you right now and pretending otherwise is how people end up quitting the industry altogether.
- What you really want is more money, not a different job. Sometimes the right move is a sideways jump to a better-paid T2 desk at a bigger employer.
- You don't enjoy the technical side and were quietly hoping the next role would fix that. It won't. The next role is more technical, not less.
The honest alternative
For most people stuck on a service desk, the highest-probability next step isn't "junior cybersecurity analyst" and it isn't "cloud engineer". Usually it's one of these.
- Sysadmin, or IT support engineer at T2/T3. The boring answer. Closest adjacent jump, quickest pay rise, opens the most doors two years later. Massively underrated.
- Junior network engineer. If your current desk touches networking at all, and you got on alright with CCNA material, this is a real route. Less crowded than cloud or security and the bar is set somewhere sensible.
- Junior SOC analyst at the right kind of employer. MSSPs and large in-house SOCs hire at this level. Boutique consultancies almost never do. Apply accordingly and don't waste your time elsewhere.
- Internal automation or scripting work. If you've written any PowerShell or Python to make your own desk less painful, this is probably the most undervalued lateral move in the industry. Companies want it badly and have no idea how to write a job advert for it.
Cloud engineer and security analyst aren't closed routes. They're just longer and more competitive than the marketing pretends. If you want them, build the evidence and accept the timeline. If you don't fancy that, take the boring adjacent jump. You end up in the same places three or four years later and you get paid more on the way.
Where this connects on POST
For the realistic next two or three roles, the pathways page lays out lanes for IT support into sysadmin and cloud, helpdesk into networking, and helpdesk into SOC. The guided route narrows those down for your situation. If you want to know how any of this gets written and what gets left out on purpose, the methodology page is honest about it.