How to Start a Career in IT With No Prior Experience: 7 Steps

Marcus spent nine years managing a restaurant. Then the restaurant closed, and he started applying for IT support roles with nothing on his CV but a CompTIA A+ he'd studied for at night. His first month of applications: 87 sent, zero replies. His second month, after I helped him rebuild his approach around a home lab and a three-line portfolio, he had four interviews. He took a helpdesk job at a managed service provider for $21 an hour.

That was two years ago. He's now a junior systems administrator earning $68,000 — and the only thing that changed between month one and month two wasn't his skill level. It was how he presented work he'd already done.

That gap is what nobody tells you about starting a career in IT with no prior experience. The skills part is learnable. The translating-those-skills-into-hiring-signals part is where most people quietly give up.

Is it possible to get an IT job without prior experience?

Yes — and I'll go further: most people currently working in IT didn't start with IT experience. They started with something adjacent and reframed it.

A retail supervisor who handled point-of-sale outages has incident management experience. A teacher who set up classroom Google Workspace accounts has identity and access management exposure. A warehouse worker who fixed scanner sync issues has hardware troubleshooting under their belt. The problem is none of them write it that way on a CV.

The real barrier is not skill

Here's what I've watched happen repeatedly. Someone spends three months studying for A+, passes, applies to 60 jobs, gets nothing, and concludes the market is broken. Meanwhile someone else with the same certification writes two paragraphs about a homelab they built with Proxmox and a spare ThinkCentre, and gets three callbacks.

Same credential. Different signal.

Hiring managers for entry-level roles are not looking for expertise, because they know you don't have it. They're looking for evidence that you can figure things out without hand-holding. That's the actual job. A homelab, a GitHub repo with a messy but real script, a documented case study of you breaking and fixing your own network — that's the proof.

What doesn't work: listing "hardworking team player" and hoping.

What is the easiest IT job to get with no experience?

If you want the shortest path from zero to a paycheck, it's service desk / helpdesk. Usually tier 1. Usually at a managed service provider (MSP).

I know that sounds unglamorous. It is. It's also the single most reliable on-ramp in the industry, and the reason is structural rather than flattering: turnover in tier 1 support is brutal, so employers are permanently hiring and permanently expecting to train. They don't need you to arrive knowing everything. They need you to show up, follow a ticket queue, and escalate properly.

Why MSP work beats in-house for beginners

An MSP serves dozens of client businesses at once, which means you'll touch Active Directory, Microsoft 365, networking, printer hell, and a customer-facing ticketing system in your first three months. In-house tier 1 at a single company often means resetting the same five passwords for two years.

My honest advice: take the MSP job even if it pays slightly less. You'll be exhausted. You'll also be interviewable in 18 months.

Other realistic entry points, roughly in order of accessibility:

• Remote helpdesk — often $17–$23/hour, high competition, but no commute
• Junior QA tester — lower ceiling, fast entry, increasingly automated
• NOC technician — shift work, decent pay, night differential
• IT asset management / hardware deployment — physical, undervalued, very forgiving entry bar
• Technical support at a SaaS company — better pay than traditional helpdesk, higher bar on communication skills

Notice what's missing from that list: "junior cloud engineer." I'll get into why below.

What jobs pay $4000 a week without a degree?

Very few, and I want to be blunt here because this question sets people up for disappointment.

$4,000 a week works out to roughly $208,000 a year. In IT, roles at that level exist — senior cloud architect, principal SRE, security engineer at a large enterprise — and they are almost never entry-level, degree or no degree. You don't walk into them from a certification.

What is realistic, and what I'd rather you aim at, looks like this:

Role	Typical starting range (US)	Time from zero
Tier 1 helpdesk (on-site)	$18–$24/hour	3–6 months
Tier 1 helpdesk (remote)	$16–$21/hour	3–6 months
NOC technician	$22–$28/hour	5–9 months
Junior sysadmin	$55,000–$70,000	12–24 months
Junior cloud / DevOps	$65,000–$85,000	18–30 months
Security analyst (entry)	$60,000–$78,000	18–30 months

These are ranges, not promises. They shift with city, shift differentials, and whether the employer is a 40-person MSP or a 4,000-person enterprise.

There are non-IT paths to $4,000 weeks without a degree — certain sales roles, skilled trades with overtime, some healthcare specialties, long-haul trucking in specific conditions. But they aren't IT, and pretending otherwise wastes your time.

The late-starters' advantage

People switching careers at 30, 40, or 50 worry their age is a liability. In my experience it's frequently the opposite. Entry-level IT managers deal with frustrated users all day. A 42-year-old who spent a decade in customer service walks into that room with a skill a 22-year-old graduate simply doesn't have yet.

What you lose in runway you gain in composure. That's a real trade, and it favors you more often than the internet admits.

Is it hard to start a career in IT?

Yes. Not because the material is unusually difficult — most entry-level IT concepts are learnable by anyone with patience — but because the hiring funnel is designed to filter you out before a human ever reads your name.

That's the hard part. Not subnetting.

Beating the ATS filter

Applicant tracking systems scan for keyword matches against the job description. If the posting says "Active Directory" and your CV says "user account management," you may never surface. This is why tailoring each application matters more than volume — I've seen people send 200 identical applications and get nothing, then send 15 tailored ones and land interviews.

Practical version: open the job description, pull the eight to ten recurring technical terms, and make sure each one appears naturally in your CV somewhere true. Don't lie. Just stop hiding.

Projects are your experience

When you have no professional history, projects are your history. Build three things and document them properly:

1. A homelab you can describe in plain language — what it runs, what broke, how you fixed it
2. One small automation that solved a real annoyance (a backup script, a bulk file renamer, anything)
3. A short write-up of a problem you diagnosed from symptom to root cause

Put these on a simple site or a GitHub README. Not a portfolio template with stock photos. Just the work.

In interviews, this changes the conversation entirely. You stop being a candidate with no experience and start being someone who has done the thing, at small scale, in their own time.

Certifications: how much do they matter?

More than nothing, less than you've been told. CompTIA A+ clears HR filters at many employers and gives you structured vocabulary. It will not, on its own, get you hired anywhere competitive.

The pattern I keep seeing: certification gets you the interview, project gets you the offer. Do both, in that order, and don't spend $500 on a cert before you've spent 40 hours in a lab.

A realistic timeline from zero to your first offer

Here's the sequence that has worked for the people I've helped, with honest durations attached:

• Months 1–3: Study CompTIA A+ fundamentals. Build your first homelab alongside studying. Don't wait until you finish the course to start touching hardware.
• Months 3–4: Sit the exams. Build project two. Start a simple portfolio page.
• Months 4–5: Apply aggressively — 10 to 15 tailored applications per week, not 100 generic ones. Start with MSPs and local SMBs before remote roles.
• Months 5–7: Interview, get rejected, adjust your answers. First offers typically land here, sometimes earlier, occasionally at month nine.

Anyone telling you this takes six weeks is either selling a bootcamp or hasn't done it. I'd rather you plan for seven months and finish in five than burn out at month two because reality didn't match the pitch.

What if I can't afford a homelab?

You don't need one. A $90 used office PC plus free virtualization software gets you most of the way. Virtual machines inside your existing laptop work too. What matters is that you break things and fix them — the hardware is a detail.

Should I get a degree instead?

Only if you want to work at a large enterprise or government role where degrees are formal requirements. For most small and mid-size IT employers, certifications plus demonstrable projects beat a degree on cost and speed. Don't spend four years and $40,000 to reach a job you could have reached in seven months.

The part nobody mentions

The hardest transition isn't learning the technology. It's accepting that your first IT job will probably feel beneath you, and taking it anyway.

Marcus was a restaurant manager. On his first day at the MSP, he spent six hours resetting passwords for a dental practice. He nearly quit. Two years later he's the one designing their network.

The industry rewards people who stay past the point where it stops being interesting. That's not a motivational line — it's the actual mechanism. The people who make it aren't the ones who learned the most in month one. They're the ones still there in month eighteen, still curious, still annoyed enough by a broken thing to fix it properly.

Start smaller than feels impressive. Stay longer than feels necessary. The rest tends to sort itself out.