A practical 90-day path from complete beginner to credible IT job candidate
How do you get started in information technology when you have zero IT experience, no computer science degree, and nobody seems willing to give you a chance?
I know that question can feel impossible to answer because I once faced it myself.
Before I explain how I got started, I want you to understand what is possible.
At one point in my IT career, I was paid $85 an hour and earned approximately $163,000 that year. During one particularly busy year, a massive amount of overtime pushed my earnings to almost $250,000.
I am not telling you this to impress you.
I am telling you because I want you to understand how far an IT career can take someone who starts with nothing.
I did not have a computer science degree. My only college degree was a two-year degree in Health Sciences, which was completely unrelated to information technology.
I did not follow the traditional path into IT.
I created my own path.
The path into IT is not easy, but it is straightforward:
Learn basic Linux, networking, and troubleshooting.
Build a virtual home lab.
Document what you build and repair.
Find a way to gain genuine experience.
Apply for jobs before you meet every listed requirement.
Let’s break down exactly how to do it.
The First Requirement Is Passion
The most important requirement for beginning an IT career is not a degree, certification, expensive computer, or personal connection.
It is passion.
At one point in my career, I was hired as a Communication Engineer, Advanced. The company offered me a salary considerably higher than the amount I had requested.
Later, I asked my manager a question out of curiosity.
“What made you decide to hire me?”
He looked directly into my eyes and gave me a one-word answer:
“Passion.”
He could tell that I did not simply want another paycheck. I was genuinely excited about the technology. I wanted to understand how everything worked, and I was willing to do the work required to learn it.
That enthusiasm came through during the interview.
Can You Make Yourself Passionate About IT?
You cannot force yourself to love something you hate.
You can, however, develop passion by discovering what technology can make possible—for companies, for other people, and for your own life.
Wanting an IT career is not the same as wishing you had one.
You must crave it enough to:
Study when you would rather watch television.
Practice after working your regular job.
Sacrifice some evenings and weekends.
Make mistakes and try again.
Ask questions when you feel embarrassed.
Take chances when success is not guaranteed.
Keep learning when the technology becomes frustrating.
Most importantly, you must believe that you are capable of learning the skills.
You do not have to know everything today.
You must believe that you can learn what you do not know.
As I explained in You Don’t Need a Computer Science Degree to Land a Great Technology Job, many employers will consider equivalent experience instead of requiring a four-year technology degree.
The challenge is finding a way to gain that experience.
How Do You Get Experience When You Have No Experience?
Nearly every IT job posting asks for some amount of experience.
Even positions described as entry level sometimes ask applicants to have one, three, or even five years of experience.
That creates the problem every beginner faces:
Nobody will hire me without experience, but how can I get experience if nobody will hire me?
The answer is that your experience does not have to begin with a high-paying, full-time IT position.
You can begin through:
A paid internship
An apprenticeship
Part-time technical work
An entry-level help desk position
Temporary or contract work
Volunteer work for a nonprofit organization
Technology support for a church or community organization
Helping a legitimate small business
Projects completed in your own home lab
Your first goal should not be finding the perfect job.
Your first goal should be finding an opportunity to work with real technology, solve real problems, and place credible experience on your résumé.
Find a Company Willing to Give You a Chance
Find a company that uses the type of technology you want to learn.
It does not have to be a large company. In fact, a small company may give you a better opportunity because you may be exposed to several different systems instead of being assigned one narrow task.
Look for paid internships and apprenticeships first.
Approach the company and explain what you have already been studying. Ask whether it offers:
Paid internships
Apprenticeships
Job-shadowing opportunities
Part-time technical work
Volunteer projects
Entry-level support positions
Do not simply say, “I want to work in IT.”
Explain what you have already learned and what you hope to learn next.
Wait—Did You Say Work for Free?
In some situations, a legitimate unpaid internship or volunteer arrangement may help you gain experience that would otherwise be difficult to obtain.
Do not automatically think of it as giving a company your labor for free. When the arrangement is legal and genuinely educational, you may be receiving valuable training and résumé experience at no cost.
You can think of it as the company giving you experience for free.
However, there is an important difference between an educational internship and a company using someone as an unpaid employee.
In the United States, the Department of Labor uses a “primary beneficiary” test when determining whether an unpaid intern at a for-profit business is legally considered an employee. Other countries have their own labor laws.
Make sure the arrangement:
Is legal where you live.
Is genuinely intended to teach you.
Has clear learning objectives.
Does not simply replace a paid employee.
Gives you meaningful exposure to technology.
Do not allow a business to take advantage of you indefinitely.
An internship does not have to be full time. A few evenings, one day a week, or several hours on weekends can gradually build meaningful experience.
Who knows? The company may decide that you are too valuable to lose and offer you a paid position.
That happens.
Do Not Approach a Company Knowing Absolutely Nothing
You will have a much better chance of obtaining an internship when you can show that you have already begun learning.
Do not walk into a company and say:
“I don’t know anything about computers, but will you teach me everything?”
Instead, be able to say something like:
“I have been studying Linux and basic networking. I built a small virtual lab, installed a Linux server, configured IP addresses, connected several virtual devices, and practiced troubleshooting connectivity problems. I would like an opportunity to continue learning in a real working environment.”
The words knowledge of Linux, networking, routers, switches, and troubleshooting can carry a lot of weight when you can support them with actual examples.
How do I know?
Because that is essentially how I got started.
Build Your Own IT Lab
Virtualization has made it easier and less expensive than ever to gain practical IT experience.
Virtualization allows you to run several simulated computers, servers, routers, switches, and operating systems inside one physical computer.
When I began, today’s virtualization tools were not available to me. I bought old, discarded computers and networking equipment on eBay and built a lab in my home.
Today, you can build a more capable lab without filling a room with used equipment.
You will need a reasonably capable computer. Ideally, it should have:
A modern Intel Core i5, Core i7, AMD Ryzen 5, or Ryzen 7 processor
At least 16GB of RAM
A solid-state drive
Enough free storage for several virtual machines
Virtualization enabled in the BIOS or UEFI settings
You may be able to begin with less, but additional memory will allow you to run more virtual machines at the same time. If you plan to build a serious lab, 32GB of RAM is even better.
For more information about choosing a suitable computer, read Buying a New Laptop? Understanding i3, i5, i7, RAM, SSDs, and What You Really Need.
Start With GNS3
GNS3 is a free, open-source network-emulation platform that allows you to design virtual networks and practice working with routers, switches, servers, firewalls, and other devices.
Visit the GNS3 website, watch the introductory videos, and read the installation documentation.
Do not become discouraged if the software looks complicated at first.
Trust me—you can figure it out.
Start small. You do not need to build a worldwide corporate network during your first afternoon.
Begin with two virtual computers connected to a simple virtual switch. Then add a router. Learn how to assign IP addresses and test communication between devices.
After that, create a second network and configure routing between the two networks.
Important Warning
GNS3 does not provide commercial Cisco operating-system images. You must supply legally obtained images yourself. GNS3’s official documentation tells users not to request or download unauthorized Cisco images.
Do not search questionable websites for copyrighted router and switch software.
Downloading software from an unknown website may expose your computer to:
Viruses
Trojans
Password-stealing malware
Ransomware
Licensing violations
Modified or corrupted software
Good antivirus protection is important, but antivirus software cannot make an illegal or untrustworthy download safe.
Another Excellent Option: Cisco Modeling Labs
Another excellent way to learn networking is Cisco Modeling Labs, commonly called CML.
Cisco Modeling Labs is the current replacement for the older product known as VIRL.
Cisco now offers CML-Free, a no-cost version designed for individual learners. It allows beginners to create labs using authorized Cisco and open-source reference platforms without searching unknown websites for questionable images.
Five nodes are enough to begin learning:
Routers
Switches
IP addressing
Routing
Connectivity testing
Network troubleshooting
GNS3 provides more flexibility and supports many different platforms. CML may be easier for someone who specifically wants to learn Cisco networking with authorized Cisco images.
Either one can help you build practical knowledge.
Install VirtualBox and Linux
Oracle VirtualBox allows you to create virtual computers inside your existing computer.
You can use it to install and operate Linux without removing Windows or making permanent changes to your physical computer.
A good Linux distribution for a beginner is Ubuntu.
Ubuntu is widely used, free to download, and supported by an enormous collection of tutorials and documentation.
Download Ubuntu only from the official Ubuntu website. Create an Ubuntu virtual machine in VirtualBox and begin learning how Linux works.
Practice tasks such as:
Installing and updating Ubuntu
Creating users and groups
Navigating directories
Creating, moving, and deleting files
Changing file permissions
Installing software
Checking network settings
Connecting remotely with SSH
Viewing system logs
Starting and stopping services
Troubleshooting a failed service
Configuring a basic web server
Backing up important files
After becoming comfortable with Ubuntu, you can explore an enterprise-oriented distribution such as CentOS Stream. CentOS Stream is the current CentOS distribution and should not be confused with the older CentOS Linux releases that are no longer maintained.
Do not follow a tutorial once and immediately declare that you know Linux.
Repeat the tasks until you understand what the commands do.
Then deliberately break something and figure out how to repair it.
That is how you learn troubleshooting.
Learn Basic Networking
Networking is involved in nearly every area of modern information technology.
You should understand at least the fundamentals of:
IP addresses
Subnet masks
Default gateways
DNS
DHCP
Routers
Switches
Network ports
TCP and UDP
Private and public IP addresses
Local and wide-area networks
Firewalls
Basic network security
You do not have to memorize an entire networking textbook before applying for an internship.
You should, however, be able to explain what happens when a computer attempts to communicate with another device.
You should also be able to perform basic troubleshooting.
For example:
Does the computer have a valid IP address?
Can it reach its default gateway?
Can it reach another device by IP address?
Can it resolve a hostname through DNS?
Is the problem affecting one computer or the entire network?
What changed immediately before the problem began?
Employers value people who can think logically and reduce a complicated problem into smaller possibilities.
Troubleshooting May Be Your Most Valuable Skill
Technology changes constantly.
The specific router, operating system, cloud service, or software program you learn today may eventually be replaced.
The ability to troubleshoot will always be valuable.
Good troubleshooters ask questions:
What is the exact problem?
When did it begin?
What changed?
What still works?
Can the problem be reproduced?
Is the failure limited to one device or user?
What evidence do the logs provide?
What is the simplest possible explanation?
How can I test that explanation?
Do not randomly change settings and hope the problem disappears.
Develop a theory, test it, record the result, and move to the next possibility.
That process is what separates someone who knows how to follow instructions from someone who can actually solve problems.
Document Everything You Build
A home lab becomes much more valuable when you document it.
For every project, record:
What you were trying to accomplish
What equipment or software you used
How you designed the environment
What problems you encountered
How you diagnosed those problems
What changes you made
What you learned
What you would do differently next time
Take screenshots and create simple network diagrams.
Remove passwords, public IP addresses, license keys, and other sensitive information before sharing anything online.
Your documentation can become:
A technical portfolio
A résumé accomplishment
A LinkedIn post
A GitHub project
An interview example
Evidence for a prospective internship supervisor
A hiring manager may not be impressed simply because you installed Linux by following a video.
The manager may be impressed when you can explain why the installation failed, how you diagnosed the failure, and what you changed to make it work.
Choose Skills Employers Are Actually Seeking
Do not choose your entire career based only on what you think is a fun/cool job.
You may want to become a game designer, but how many game-design jobs are available compared with positions involving networks, Linux, cloud computing, cybersecurity, technical support, or automation?
That does not mean you should never pursue game design.
It means you should investigate the job market before investing years in a skill.
Search current job openings in your area and in locations where you would be willing to work.
Record which technologies appear repeatedly.
Look for patterns.
You may repeatedly see skills such as:
Linux
Basic networking
Troubleshooting
Routers and switches
Windows administration
Cloud services
Cybersecurity
PowerShell
Python
Virtualization
Technical support
In my post Why I’ve Been Retired for a Year and Recruiters Still Contact Me Every Week, I explained how the law of supply and demand applies to employment.
When thousands of applicants possess the same basic skills, an employer has thousands of choices.
When employers urgently need a skill that relatively few applicants possess, qualified people become much more valuable.
Go where the most fish are—not where you think you might catch the biggest fish someday.
Even though I am retired, I still receive requests to interview for technology jobs, often specifically because of my experience with Linux, networking, virtualization, troubleshooting, and enterprise systems.
Those skills continue to have value.
Turn Your Lab Experience Into Résumé Accomplishments
Do not simply write:
Knowledge of Linux.
Write:
Built and administered an Ubuntu virtual server, created user accounts and permissions, configured SSH access, installed services, and diagnosed network-connectivity failures.
Instead of:
Familiar with networking.
Write:
Created a virtual network lab using routers, switches, Linux servers, and multiple subnets; configured addressing and routing and documented troubleshooting procedures.
Instead of:
Worked as an IT intern.
Write:
Assisted with diagnosing Windows, printer, account-access, and network-connectivity problems for a small business.
Be truthful, specific, and prepared to discuss every statement during an interview.
Never claim knowledge or experience that you do not have.
You do not need to exaggerate what you have done when you can clearly explain what you learned.
Apply Before You Meet Every Requirement
A job description often represents the employer’s ideal candidate—not necessarily the only person the company will consider.
Do not reject yourself simply because a posting asks for three years of experience and you have one year of part-time experience supported by a serious home lab.
Apply honestly and explain what you have done.
An employer may value your:
Motivation
Home-lab projects
Internship experience
Troubleshooting ability
Communication skills
Willingness to learn
Ability to explain technical concepts clearly
Once you have accumulated several months of genuine hands-on experience, begin applying for jobs related to the skills you have developed.
Do not wait until you feel completely ready.
You will probably never feel completely ready.
A Simple 90-Day Plan for Getting Started
Days 1–30: Learn the Foundations
Study:
Computer hardware
Windows basics
Linux fundamentals
IP addressing
DNS
DHCP
Routers and switches
Basic troubleshooting
Spend more time practicing than watching videos.
Watching someone else configure a router is not the same as configuring one yourself.
Days 31–60: Build and Document Your Lab
Install VirtualBox and Ubuntu.
Set up a Linux server.
Build a small virtual network in GNS3 or Cisco Modeling Labs.
Practice:
Creating users
Configuring IP addresses
Connecting devices
Testing network communication
Reading logs
Installing services
Diagnosing failures
Restoring a failed configuration
Document every project.
Days 61–90: Look for Real Experience
Contact:
Small businesses
Nonprofit organizations
Churches
Community groups
Schools
Local IT companies
Computer repair businesses
Managed service providers
Ask about:
Paid internships
Apprenticeships
Volunteer technology projects
Part-time work
Job shadowing
Entry-level support positions
At the same time, begin applying for jobs such as:
Help desk technician
Desktop support technician
Junior IT technician
Technical support specialist
Network operations center technician
Field service technician
Junior systems administrator
Your first IT job may not be your dream job.
It may be the door that eventually leads to it.
What You Should Have After 90 Days
After 90 days of serious effort, you should have:
A functioning virtual home lab
A Linux virtual machine
A basic virtual network
Several documented projects
Screenshots and network diagrams
A basic technical résumé
An updated LinkedIn profile
Enough practical knowledge to discuss your work during an interview
Will 90 days make you an expert?
No.
It can make you a credible beginner who has done more than simply say, “I want to work in IT.”
That alone can separate you from many other applicants. Can you really do this in 90 Days? Absolutely, but only if you're willing to sacrafice and put in the effort. If you currently don't have a job, treat this like your full time job.
Your First Job Is Only the Beginning
I did not begin my journey as an advanced communications engineer or enterprise systems architect.
I began by believing that I could learn.
I studied.
I experimented.
I built my own lab.
I made mistakes.
I took chances.
I gained experience wherever I could find it, and I kept building on what I had learned.
Eventually, companies were willing to pay me $85 an hour for the knowledge, experience, and problem-solving ability I had developed. During one overtime-heavy year, I earned almost $250,000.
Again, I do not say that to brag.
I say it because someone reading this may be sitting at home with no technology degree, no IT experience, and no idea how to begin.
I was once that person.
You do not need a computer science degree to land a great-paying technology job.
But you do need passion.
You need discipline.
You need curiosity.
You need hands-on practice.
You need the courage to ask someone for an opportunity.
Most of all, you need to believe that your life can become better—and then be willing to do the work required to change it.
You may have zero experience today.
That does not mean you must still have zero experience six months from now.
Once you have developed knowledge through your home lab, internship, volunteer work, or entry-level position, make sure you document it on your résumé and LinkedIn profile.
Sign up for ExtraHelp.us email updates so you will be notified when I publish new articles about creating a strong résumé, using LinkedIn, building a home lab, protecting yourself online, and developing practical technology skills.
If you found these suggestions helpful, please support this blog by subscribing, leaving a comment, asking questions, or sharing the article with someone who may need it. It only takes a few minutes, and you may help someone change the direction of their life.
I will never share your email address with anyone.
Get New Posts by Email
