Getting stuck in IT support happens when you rely on internal promotion instead of building an external exit plan in parallel from month one. The fix isn't "just get a cert." It's a 12-24 month sequence: pick a lane, stack proof of work, apply externally on a schedule, and stop waiting for a manager who keeps promoting their friends instead of you.
This is a real pattern, not a one-off complaint. A recent thread on r/ITCareerQuestions laid out the exact trap: help desk gets sold as a "launchpad," but internal sysadmin and network openings quietly go to internal transfers or whoever the hiring manager already knows. Meanwhile the pay creeps up, the job goes remote, and suddenly leaving feels riskier than staying stuck.
Why does IT support feel like a dead end even though everyone calls it a launchpad?
Because a launchpad only works if someone launches you. Most help desk teams have no formal promotion pipeline. Sysadmin and network roles open rarely, and when they do, the hiring manager defaults to the person they already trust: an internal transfer from another team, a referral, or someone they golfed with. You're competing on tenure and visibility, not just skill. If you're not visible to the people who make that call, two years of good ticket metrics won't move you up.
The second trap is comfort. Remote work, a decent raise, and a manager who likes you make staying feel safe. But safe and stuck are different things. If your last title change was a pay bump with the same job description, that's not progression. That's retention.
In plain terms: help desk gives you access, not a guarantee. You have to build the case for promotion yourself, both inside and outside the company.
What's the actual help desk to sysadmin path, step by step?
Skip the vague "learn networking" advice. Here's a sequenced plan that assumes you're currently in tier 1 or tier 2 support and want a sysadmin, network, or cloud role within two years.
- Pick one lane in month 1-2. Sysadmin (Windows/Linux server administration), network (routing, switching, firewalls), or cloud (AWS/Azure infrastructure). Don't split effort across all three. Recruiters and hiring managers filter for depth, not breadth, at this level.
- Get the entry cert for that lane by month 4-6. Sysadmin: CompTIA Server+ or a Windows/Linux admin fundamentals cert. Network: CCNA. Cloud: AWS Certified Cloud Practitioner, then Solutions Architect Associate. One cert, done well, beats three half-finished ones.
- Volunteer for adjacent work at your current job by month 3-9. Ask to shadow the sysadmin team on patch nights. Take on Active Directory account management. Own a small server migration or a firewall rule change under supervision. This is the proof-of-work that makes your resume credible, not the cert alone.
- Build a home lab and document it by month 6-9. Spin up a small Windows Server + Active Directory environment, or a pfSense firewall with VLANs, or an AWS free-tier VPC. Write it up. This gives you talking points for interviews that go beyond "I reset passwords."
- Start applying externally at month 9-12, even if you're not promoted internally yet. Don't wait for the internal role to open. External hiring managers care about skills and certs, not office politics. Applying externally also tells you your market value in real time.
- Give your internal path one clear, timed shot. Tell your manager directly, around month 10-12: "I'm targeting a sysadmin/network role. Is there a path here in the next 6 months, or should I plan externally?" A vague answer or another "not yet" is your answer.
- Set a hard exit deadline at month 18. If you haven't moved up internally by then, and you've been applying externally without traction, it's time to reassess the resume and target easier employers (MSPs, smaller IT shops) that promote from tier 1 support faster than large corporate environments.
- Take the lateral move if it's a real lateral, not a lateral in disguise. An external "IT Support II" title with a 15% raise and a road to sysadmin within a year beats staying in a role where you've been told "next cycle" three cycles in a row.
Plain-language summary: pick a lane, get certified, get hands-on experience on the job and at home, and apply externally starting around month 9 instead of waiting for an internal opening that may never come.
When should you apply externally vs. wait for an internal promotion?
Apply externally in parallel from the start, but weigh the decision using concrete signals, not gut feel.
| Signal | Wait internally | Apply externally now |
|---|---|---|
| Manager has given a specific timeline (e.g. "Q2 review") | Yes, but keep applying quietly | Still apply, timelines slip often |
| Last 2 open roles went to internal transfers with less experience than you | No | Yes, the pattern is the answer |
| You've hit your cert/skill milestone but title hasn't changed in 12+ months | No | Yes |
| Company has a documented, followed promotion ladder | Maybe, give it one more cycle | Apply anyway as backup |
| You're comfortable (remote, decent pay) but title is stagnant | No — comfort isn't progression | Yes, comfort is the trap |
In short: internal promotion is worth one honest, timed attempt. It's never worth an open-ended wait, especially once you've watched the same seat go to an internal transfer twice.
How do golden handcuffs keep IT support workers stuck?
Golden handcuffs in help desk look like this: you got remote flexibility, a raise that keeps pace with inflation, and a manager who's friendly. None of that is a promotion. It's retention dressed up as progress. The risk is that "not bad" becomes your ceiling, because leaving means giving up something tangible (remote days, PTO balance, seniority) for something uncertain (a new employer, new team, new probation period). The way to break this without reckless risk: negotiate your next role, whether internal or external, around title and scope first, and compensation second. A same-pay lateral into an actual sysadmin or junior network role is worth more over 3 years than another 4% raise in the same help desk seat. If your current employer counters with money but not title or scope change, that's confirmation you're being retained, not developed.
What should your resume and job search look like once you decide to move?
Once you hit the month-9 to month-12 window and start applying externally, treat it like a real job search, not a side project. Keep one master resume tuned for sysadmin/network/cloud roles rather than rewriting from scratch each time (see One Master Resume vs. a New Resume Per Job for the system). Apply fast, because infrastructure and admin roles at MSPs and mid-size companies get buried in applicants within hours of posting. For the full mechanics of the sysadmin transition itself, including which certs and lateral titles actually open doors, see Desktop Support to Sysadmin: The Actual Path Out of Underpaid IT Roles.
Speed matters more than most people in help desk realize. Postings for sysadmin and junior network roles at smaller companies often get 100+ applicants in the first day. Getting your application in within hours of a posting going live, and following up with a direct recruiter message rather than sitting in the applicant tracking system queue, changes your odds meaningfully. This is exactly the gap GiraffyReach's auto-apply and recruiter outreach engine is built to close: it flags new postings the moment they go live and gets your application and a direct message in front of the hiring manager before the queue fills up.
Get moving instead of waiting on someone else's timeline
Help desk is a launchpad only if you build the launch mechanism yourself. Pick your lane, get the cert, get real hands-on reps, and start applying externally well before you're desperate. The people who break out of support roles fastest are the ones treating months 9 through 18 as an active search, not a backup plan they hope they never need.