No degree. No experience. No idea how to get a job in IT without experience.
That's where most people begin.
And yet, people break into IT every single week from exactly that position. Some come from retail. Some from hospitality. One person I came across online had spent six years driving trucks before landing a help desk role at 34.
Another went from a coffee shop to an IT administrator position in under a year. No degree. No prior tech job. Just a CompTIA A+ and a willingness to apply relentlessly.
The path exists. It's just not obvious until someone shows it to you.
Most guides tell you what to do. This one starts with what the person reading your application is thinking.
When a hiring manager opens a resume from someone with no IT background, they are asking one question: is there any evidence this person can learn fast and won't give up?
That's it. Not "do they have five years of experience." Not "do they have a degree." Just - can they learn, and will they stick around long enough to become useful?
Before you study for a single certification, spend one hour doing this:
Open five job postings for entry-level IT support or help desk roles. Read them carefully. Write down every skill, tool, and quality they mention more than once.
You will see the same words repeat: Active Directory. Windows 10. Ticketing systems. Communication skills. Problem-solving.
That list is your roadmap. Every decision you make from this point - what to study, what to build, what to put on your resume - should be aimed directly at those words.
Most people study in a vacuum and then apply. The people who get hired study the job first, then fill the gaps.
CompTIA A+ is not exciting. But it is the single credential that most entry-level IT hiring managers treat as a baseline filter.
Here is what most guides don't tell you: the A+ alone is rarely enough. What gets you hired is the A+ combined with evidence that you have actually used the knowledge.
So study for it. Pass it. Then immediately move to Step 3 before you apply to a single job.
One certification, studied properly with hands-on practice alongside it, is worth more than three certifications studied purely from books. Hiring managers have interviewed enough candidates to know the difference in about 90 seconds.
A realistic timeline: 8 to 12 weeks of consistent study, roughly two hours a day. Platforms like TryHackMe let you practise real scenarios in virtual environments so your knowledge is applied, not just theoretical.
Here is the thing about home labs that most guides skim over: the lab itself is not the point. The story it gives you is.
When an interviewer asks "tell me about a technical challenge you've worked through" - most candidates with no experience go blank. A candidate with a home lab has three answers ready.
You do not need expensive equipment. A second-hand laptop running VirtualBox costs under $100 total. Set up a basic Windows Server environment. Create some user accounts in Active Directory. Break something and fix it. Document what you did.
That documentation is your experience. It is real. It is specific. And almost nobody else applying for that entry-level role has done it.
When you say "I built a home lab to practise the scenarios I'd face on the job" - you have already separated yourself from 80% of the applicants in the pile.
Here is a resume structure that works specifically for candidates with no IT work history:
Professional summary - two sentences maximum. State your certification, your hands-on practice, and the exact role you are targeting. No fluff.
Technical skills - list every tool, operating system, and platform you have touched. Windows 10, Windows Server, VirtualBox, Active Directory, basic networking. If you used it in your home lab, it belongs here.
Projects and lab work - this is the section most people skip and it is the most important one. Describe what you built, what you practised, and what you learned. Three to four bullet points.
Work history - your previous jobs, reframed. If you worked in retail, your bullet points are not "served customers." They are "resolved complaints under time pressure" and "communicated technical product issues to non-specialist customers." Every job has IT-adjacent skills if you look for them.
Certifications - at the bottom, with the date achieved.
Keep it to one page. No exceptions.
This is the advice almost nobody gives, and it is one of the most consistently useful pieces of guidance for people breaking into IT.
Managed Service Providers - companies that handle IT for multiple small and medium businesses - are the single best target for your first role.
Here is why. A big company like a bank or a retailer gets hundreds of applications for every entry-level IT role. An MSP with 30 employees gets a handful. The competition is dramatically lower.
MSPs also give you faster and broader experience than almost any other first role. In one year at a busy MSP, you will deal with more environments, more problems, and more technologies than you would in two years at a large company with a structured IT department.
Once you have 12 to 18 months of MSP experience on your resume, doors open that were completely closed before. Not sure where MSPs sit in the wider IT landscape? Our breakdown of IT support roles explains how the different positions connect.
If you want to know more about what day-to-day support work looks like before you commit, read our overview of help desk vs desktop support.
Most networking advice tells you to "connect with people in IT." That is vague enough to be useless.
Here is something specific that works.
Find three to five IT professionals on LinkedIn who post regularly about their work - not influencers, just working technicians or team leads sharing day-to-day insights. Leave thoughtful comments on their posts for two to three weeks. Not "great post" - actual responses that show you read it.
After a few weeks, send a connection request with a short note referencing one of their posts.
Once connected, send one message. Not asking for a job. Asking one specific question about their experience - how they got their first role, what they wish they had known, what skills they see missing in junior candidates.
Most people will respond. Some will not. The ones who do are now part of your network. And when a role opens up at their company, you are not a stranger applying cold - you are someone they have had a real conversation with.
One internal referral is worth more than 20 cold applications. That is not an exaggeration.
Most candidates wait until they have an interview scheduled to start preparing. By that point, you have a week at most.
Start preparing now. Read our guide to IT support interview questions and work through the answers while your study is still fresh. If you are targeting help desk roles specifically, our help desk interview questions and answers guide covers the scenarios you will actually face.
The candidates who perform best in IT interviews are not the ones who crammed the night before. They are the ones who have been thinking about these questions for weeks and have specific, real examples ready - including examples from their home lab.
Looking at the stories of people who made this transition successfully, the same pattern appears repeatedly.
They did not wait until they felt ready. They got the certification, built something, and applied before they felt fully qualified.
They applied to far more roles than felt comfortable - often 60, 80, or more before landing the first one.
They targeted smaller companies and MSPs rather than chasing well-known names.
They used their soft skills actively in interviews rather than hiding behind technical knowledge they were still developing.
And they treated the first role as a starting point, not a destination. The goal was never to stay in that job. The goal was to get the experience that made the next move possible.
Ready to start? Browse entry level support jobs on itsupportjob.com. And if you are coming from a customer service background, it is worth knowing the longer-term picture - read about high paying customer service careers to see where the path can lead.
