If you're choosing where to start in tech and you don't already have a clean adjacent route in (a relevant degree finishing this summer, a referral into a junior role, an apprenticeship), IT support is almost always the right answer. Not because it's prestigious. Because it installs the operational instincts every later role quietly assumes you already have, and skipping it is what makes year two so painful for people who tried.
Who this is for
- You're new to tech and trying to pick a first job, not your tenth.
- You've been told (by a bootcamp, a Reddit thread, a YouTube channel) to skip support and go straight to cloud or cyber, and something about that advice has started to feel off.
- You're 28 to 45, changing careers, and you keep being told support is "beneath you". It isn't. It's the cheapest possible way to find out whether you actually like the work.
Who it isn't for
- People with a CS or networking degree, a strong placement year, and a junior offer already on the table. Take the offer.
- Career changers from adjacent fields (network engineering at a telco, sysadmin at a school, a developer role at a small shop) who can move sideways into the role they want. Move sideways.
- Anyone who genuinely cannot do public-facing work. Support is people work as much as it's technical work. If a stressed user on the phone is going to break you, that's useful information, but support won't fix it.
What support actually teaches you
The thing that makes a senior engineer senior isn't deeper knowledge. It's pattern recognition over thousands of small incidents, plus a physical sense of how production systems fail. You can't read your way to that. You can't bootcamp your way to it either. You get it by being the person who picks up the phone when something is broken, every day, for a couple of years.
After eighteen months on a desk you'll know things you can't easily articulate. Which error message is misleading. Which user complaint ("it's slow today") translates to which underlying issue. The difference between "it's broken" and "it's broken in a way that matters to the business right now". When a colleague says "have you tried turning it off and on again" and means it as a serious engineering question, not a joke.
Cloud engineers, security analysts, and SREs who came in through support spot incidents earlier and triage them faster than peers who didn't. It's the single most underrated piece of capital in the industry, partly because the people who have it can't really see it themselves.
What people get wrong about the starting decision
The most common mistake is treating the first job as the destination. You're picking a starting point, not a career. The right question isn't "what's the best job?". It's "what's the cheapest way to find out what I actually want to do, with the most doors still open at the end of it?". Support wins that question almost every time.
Second one. People underestimate how hard it is to get an entry job at all in 2026. The "skip support, go straight to cloud" advice was written for a 2018 market that hired juniors aggressively because cloud was new and nobody had experience. That market is gone. Cloud and security teams now hire from inside the company, from sysadmin and infra, or from senior people at other firms. The number of cold external juniors getting hired into those teams is much smaller than the content suggests.
Support, by contrast, still hires. MSPs hire constantly. Internal desks at large employers hire constantly. It isn't glamorous and the starting pay isn't great. It is, however, an actual job, available now, that puts you inside a tech environment with a payslip.
The honest tradeoff
Support pays you in three things. Real money, even if it's modest. Exposure to a working tech estate. And time, in the evenings and at weekends, to build the evidence for whatever you want to do next.
What it takes from you is a couple of years of your life on work that's often dull, occasionally awful, and rarely written up impressively on LinkedIn. The dull is the price. If you can't pay that price, you can't pay the cloud or security price either, because those jobs have more dull in them than the marketing admits.
What "starting in support" should look like
Aim for an internal IT team at a mid-sized employer, or a serious MSP. Avoid call-centre-style outsourced helpdesks where you'll never touch anything beyond password resets. The signal isn't the title. It's whether you'll get hands on Active Directory, MDM, basic networking, a ticketing system, and ideally some cloud admin console.
Plan eighteen months. Not five years. Use the first six to learn the environment cold. Use the second six to start picking up work nobody wants (the irritating automation jobs, the small scripting tasks, the documentation no one's written). Use the final six to apply for the next thing, internal or external, with evidence in your hand.
If you're still on the same desk at month thirty, something has gone wrong. The escape plan is its own essay (linked here), and worth reading early, because the longer you leave it, the harder the optics get.
When to ignore this entirely
There are people for whom support genuinely is the wrong starting point. The honest list is short.
- You've already got a junior offer somewhere harder to get into. Take it.
- You're coming from a closely adjacent role and there's a lateral move available. Take it.
- You're financially in a position where six months of unpaid portfolio-building is realistic and you genuinely don't need a payslip yet. That's rare. Don't pretend it applies to you if it doesn't.
Outside those, the maths is straightforward. Support is available, pays a wage, builds the foundation everything else sits on, and leaves your options open. The "skip it" advice optimises for time you don't have and a market that doesn't exist.
Where this connects on POST
The pathways page lays out the realistic next moves once you've done your time on a desk, by domain. The guided route narrows them down for your situation. For the exit side of this argument (you're on a desk already and progression hasn't shown up), read why most people fail trying to leave helpdesk.