How to move into IT support technician from another career

What actually transfers and what does not

If you have spent years doing anything customer-facing, you already have half of this job. Explaining a problem to someone who does not understand the underlying system, staying calm while they are frustrated, documenting what happened so the next person does not have to ask again — that is most of a Tier 1 help desk shift. Retail, hospitality, call centre work, even teaching: the pattern-matching and de-escalation skills genuinely carry over, and you should say so plainly in your application rather than hiding the job title.

What does not transfer is the technical vocabulary and the tools, and pretending otherwise is where career-change applications usually fail. You need to be able to talk about Active Directory user provisioning, DNS and DHCP basics, ticketing systems (Zendesk, Freshdesk, ServiceNow, or whatever the employer runs), remote support tools like TeamViewer or AnyDesk, and the difference between an incident and a problem in ITIL terms. None of that is hard to learn, but none of it is inferable from a background in another field either, and a hiring manager will not assume it.

One thing that transfers less than people expect: general "I'm good with computers" enthusiasm. Every applicant says this. It does not distinguish you. What distinguishes you is a specific incident you can describe — a printer queue that jammed for a whole floor, a shared drive permissions mess, a laptop that wouldn't join the domain — and how you found the cause. If your previous job gave you anything like that, even informally, lead with it.

The certification route, and why there is no licence

There is no licensing body for IT support technicians. Nobody can strike you off, and nobody requires you to hold a specific credential before you can be paid to do the work. This means the barrier is entirely about convincing an employer you can do the job, not about clearing a regulatory gate. That is good news structurally — the route is open to anyone — but it also means the market is not filtered for you, and you are competing against people who have three years of unpaid IT volunteering and a home lab as well as people with degrees.

The de facto entry credential is CompTIA A+. It is not a legal requirement anywhere, but it appears in enough entry-level job adverts that not having it, or an equivalent, puts you at a disadvantage on paper. It covers hardware, operating systems, networking basics, and troubleshooting methodology — roughly what a Tier 1 technician is expected to know on day one. Studying for it, even before you sit the exam, is a reasonable use of your time because it gives you the vocabulary gap-fill mentioned above.

After A+, the next useful steps depend on which direction you want to specialise:

• CompTIA Network+ if you want to move toward network support rather than staying on the help desk.
• Microsoft Certified: Fundamentals (MS-900, or AZ-900 for Azure environments) if the employers you are targeting run Microsoft 365 or Azure, which most do.
• ITIL Foundation if you are applying to larger organisations with formal service management — it signals you understand incident, problem, and change management as distinct processes, which is the vocabulary those employers use internally.

None of these are substitutes for hands-on experience. A hiring manager who has screened enough candidates can tell the difference between someone who memorised A+ objectives and someone who has actually reimaged a machine, joined it to a domain, and fixed a printer driver conflict. If you can, build a small home lab — a spare machine, a virtual Active Directory environment, a Raspberry Pi running Pi-hole — and be ready to talk about what broke and what you did about it. That is worth more in an interview than the certificate itself.

What your application has to overcome

Three specific problems, in order of how often they sink an application:

Keyword filtering. Applicant tracking systems and the humans scanning CVs are both looking for phrases like "help desk", "Tier 1", "ticketing system", "Active Directory", "remote support". If your CV describes your actual IT-adjacent experience in the vocabulary of your old field instead, it will not surface. This is not about gaming a system; it is about using the words the reader is actually looking for because that is also the accurate description of what you did.

No professional IT experience on paper. This is the real one, and there is no shortcut around it. What works is evidence that substitutes for it: certifications in progress or completed, a home lab you can describe concretely, any informal IT work you have done (fixing family members' laptops does not belong on a CV as a job, but it belongs in an interview answer about why you're making this move), and a genuinely specific explanation of why now. "I've always liked technology" is weak. "I spent eighteen months as the person my department went to when the shared printer or VPN broke, and I realised that was the part of my job I actually enjoyed" is specific and checkable in an interview.

The gap explanation. You will be asked why you're leaving your current field, directly or via a CV screen. Employers hiring for entry-level IT support are used to career changers — it is one of the more common entry routes into IT precisely because there's no licence — so this is not a fatal question, but a vague answer is a wasted opportunity. Have a one-sentence reason ready that is about what you're moving toward, not just what you're moving away from.

The honest timeline

Studying for CompTIA A+ from a standing start typically takes a few months of part-time study, depending on how much of the material is new to you. That gets you exam-ready, not job-ready — the certificate is a door-opener, not a guarantee.

After that, expect the job search itself to be slower than the studying. Entry-level IT support roles get a high volume of applicants because the barrier to entry is genuinely low, which means competition is high even though the skill floor is not. Career changers commonly send a large number of applications before getting interviews, and this is not a reflection of your suitability — it reflects the volume everyone else applying is also up against. Silence after applying is normal and does not mean your CV was bad; it usually means it was one of many for a role with a short list already forming from internal referrals or agency pipelines before the advert was even fully live.

If you already have any adjacent experience — you were the informal tech support person in a previous non-IT job, you've done freelance PC repair, you manage IT for a small organisation as an unpaid extra duty — the timeline compresses because you're not starting the credibility problem from zero. If you are starting from genuinely no IT-adjacent background at all, be realistic that the first few months of the search will be about building that credibility (certs, lab, volunteering to fix things at your current job) as much as about applying.

The route is not hard in the sense of being closed to you. It is hard in the sense that it is crowded, and the way through is specificity: specific certifications, a specific home lab story, specific vocabulary matched to the advert, and a specific answer for why you're changing fields. Generic enthusiasm does not clear that bar; a well-aimed CV does.

What to do next

Pick one certification — CompTIA A+ if you have none of this yet — and set an exam date, not just a study plan, because a date creates a deadline. Build one small home lab task you can describe in detail: reimage a machine, set up a basic Active Directory domain in a virtual environment, configure a ticketing tool. Rewrite your CV so the first third of the page contains the exact terms from the adverts you're targeting — help desk, Tier 1, ticketing, Active Directory, remote support — where they are true of what you've actually done. Then apply to volume, because the honest arithmetic of this market means most applications will not get a reply regardless of how good the CV is, and the difference a strong application makes is in the ratio of interviews to applications, not in guaranteeing any single one.

If the volume of tailoring — matching each CV and cover letter to the specific wording of each advert, across a search that needs dozens of applications to produce a handful of interviews — is the part that is making the search stall, jobmarket.pro reads each advert, prepares the application from your actual work history, and does that matching without inventing experience you don't have.