Is it even possible to get a job in computer networking without experience?

Yes, it is possible, it’s even probable if you want it bad enough. You just need to think outside the box a little bit and take a non-traditional approach.

Most everyone will tell you ABSOLUTELY NOT, you need lots of experience, multiple certifications, an IT degree and have moved your way up the ranks to get to network administration or technician status.

And while this is the traditional approach that does work, there are other more non-traditional and possibly even faster ways to get there.

What most people think when they think “Network experience” is either having worked for a company in some network role. Whether that is a network technician, network administrator, network engineer, NOC (Network Operations Center) or whatever for X amount of years.

It usually also means having certifications such as Comptia Network +, CCENT, CCNA, JNCIA, etc.

Lastly it typically means having a college degree, preferably a Bachelors Degree in Computer Science or a related field.

Having all three of these is the traditional approach, and the way 90% of people applying for network jobs got their experience.

And YES.. I would argue that this traditional approach is ideally the way you would want to get there. But I also understand there are circumstances where this isn’t feasible for some people, the traditional approach takes a lot of time and money. For some people, it can also mean taking a pay cut to work in a low-level IT support role in an attempt to build up that experience.

Well I’m writing this to show you, there is another way to do this and get hired in a network role.

So, let’s assume you don’t have either certifications or work experience, but still want to get a job in computer networking. How do you do it?

Well lets take a step back for a minute and work backwards.

The End goal is to get hired in a company in some type of IT network role. Before you can get hired, you would have needed to get called for an interview AND kicked butt in that interview.

To get called for that interview you would have needed to apply to the job and submit your resume…

Before you could have submitted your resume, you would have needed to create a resume with relevant experience pertinent to the job in which you are applying.

But wait a minute, I thought you said I can get a Network job without experience?

Yes, you can get hired in a network role without TRADITIONAL experience, but you DO need some type of experience to put on your resume to even get in the door.

There is no way around that.

IT in itself is a specialized skill, networking is often seen as a step or two up from basic IT so it’s even MORE of a specialized skill.

You would be hard-pressed to get hired as a Network administrator by only being able to put your experience as a grocery store bagger on your resume.

Now this is NOT going to be an article on how to scam the system to get hired as a network admin. I’ve seen people try to do this before, I’ve even interviewed people who lie on their resume, and you can see right through these people within minutes.

DO NOT LIE on your resume, you will get caught and you will regret it.

As I said before, you will need some experience, and something to put down on your resume. I am going to show you the most effective non-traditional ways to get the experience you need to put on your resume and get that job!

GETTING THE EXPERIENCE

1. Shadow the IT guy/gal at your existing job

Every company nowadays has IT systems, network equipment that the business runs on, and people hired to manage these all these systems.

If you have a job now, or had a job in the past I’m sure if you think about it, you can recall that there was more than likely WIFI in the building, maybe even shared drives, computers, laptops etc. This means there ARE IT guys there somewhere maintaining this stuff.

Most IT people really enjoy talking about IT and showing people what they are working on (Like me which is why I made this blog).

Next time you are on your lunch break or after your shift, find one of the IT guys and just ask him what he does, if he likes it, some of the things he’s working on etc. You can even tell him or her that you are trying to get into the IT field yourself.

Just keep the lines of communication open with this person.

The goal here is to eventually ask this person if you would be able to sit in, or even help them with some of the projects they are working on (outside of your shift and normal work function duties of course).

***Now full disclosure, depending on how strict the company is you may need to get approval from a higher-up before you can “help out” in the IT office.

This help and learning that you are offering NEEDS to be under the assumption you are working for FREE. You are simply donating your own time to help or learn… And hey, in some cases they may even pay you, and if so GREAT… But if not, this experience is more than enough payment.

If you can pull this off and assist a real network engineer, even just a little bit, you CAN and SHOULD put this on your resume.

Make sure everything you assist with, you write down because if you are going to put it on your resume, you need to be able to speak to it.

Now, as the “help”, it’s going to be easy think you aren’t doing anything worthy enough to put on a resume… because maybe all you are doing is unpacking and repacking boxes of new network equipment.

And that may be true, but why are you unpacking new network equipment?

Is there a new site going in? How big is the site, what type of network equipment is going in? Is this new site going to connect to an existing site? If so, how?

The point is, even though you may have only played a small role, you were involved in a BIG networking project. As long as you watch closely, pay attention, and take notes as to what is going on… Even if you are not doing the high impact stuff, if you can understand to some extent what is going on and can speak to it, you can put that you were involved in this project on your resume, because YOU WERE INVOLVED.

2. Mentor or friend who is already in networking

A friend who is already in networking can be a great asset for gaining experience. Not only can they help explain and even train you, depending on where they work, you may be able work with them on certain projects (for free of course).

In my early days of the IT world, a good friend of mine was already a Network Engineer. At the time he worked for a small company (I talk about the benefits of working for a small company often, especially in the beginning of your career) that afforded him a significant level of trust and freedom to do his work.

I was able to stop over at his office from time to time and assist him with higher level tasks and projects that I could not work on at my current job.

And you can do the same!

If you don’t have a friend that is already in networking, you can find a mentor to accomplish the same thing (and hopefully they will become a friend!).

Finding a mentor to work with may be more difficult than just using a friend, but it can be done. A good place to start looking is social media platforms. Facebook and LinkedIn can be great resources for finding a mentor.

Heck, you may already have an old friend on Facebook who is already in networking. You never know unless you look.

Once you find a friend/mentor and begin to work with them for some time, you will want to put your newly found experience on your resume, as you should!

Because you are not working for the company, you cannot put that you are. But what you can do, is write things like “Assisted Network Engineer with building out new site”, and things like that.

Get creative with it, but just be honest.

3. Business owner

Maybe you know someone who owns a business, maybe your family knows someone who owns a business.

Knowing someone who owns a business can be a great asset for getting the experience you need. As I stated before, every company has some sort of IT infrastructure and needs someone to manage and maintain it. If you or your family are close with someone who owns a business, reach out to them and see if they need any IT help!

I used this same technique when I was just starting out. A friend of mine from high school, his father owned a small Structural Engineering company in town.

At the time, I was desperate for relevant experience without having to quit my current job. I knew he must have some sort of IT department, and that maybe I could volunteer to help his network admin.

I wasn’t even sure if he remembered me from high school, but I took a chance, and sent him an email.

At the time, I worked nights, so I explained that I was trying to get more experience in the IT network field and would love to volunteer at his company (free of charge) helping his network admin in the morning for a few hours every day before work.

To my surprise, he responded that he would NOT accept me volunteering. He would only allow me to work in the Network department if he could pay me.

My official title on the books was Network Associate. I am forever grateful to him for the chance he took on me, and the experience I gained working for his company.

Even though it was just part time, you bet your butt that I put this role and the projects I worked on in my resume!

Now certainly I was fortunate by this stroke of luck, having known someone who could afford me this opportunity. But had I never taken the chance and ASKED, I would have never gotten this opportunity.

So, ask your family and friends if they know any business owners. And if so, take that chance and reach out to them.

Sometimes if there are no opportunities in front of you, you need to go out and create your own opportunities.

4. IT Company

If you don’t have the skills or experience to get a job working in an IT role, but you do have other skills such as sales or even customer service that an IT company could take advantage of; a good option could be taking a job with an IT company in a non-technical role.

Let’s assume you have sales experience and take a job in IT sales. Though this may not be the role you want, there are many advantages to working in sales for an IT company.

• In order to sell IT products and services, you undoubtedly need to learn about IT.
• Sales and the ability to talk to people and communicate well is a soft skill that can often give you a leg up in the IT world.
• Working for an IT company; obviously there will be many Network engineers that you work with which you can shadow and befriend.

Though you may not be able to use your IT sales experience alone to get a job in as a Network admin, the potential the role offers though learning and possibly shadowing a Network Engineer IS experience that you can use.

This technique may take a little more time than some of the other techniques, but it may also be an easier option if you already have non-technical skills that an IT company can benefit from.

5. If you can’t get experience, create experience

If you don’t have the ability to work with the IT people, or maybe you don’t even have a job, so you can’t get that “at work” experience. What do you do?

You can create your own experience.

There are many different facets of networking and many different components that make up a network. If you could hone-in on one of these, teach yourself enough to be able to assist other people, not only could you be getting real world networking experience, you could also get paid for it!

The reason why you choose just one facet of networking to hone-in on, is because trying to train yourself on everything there is to know about networking is impossible and will take waaaaay too long.

The point when you finally get your first networking job is to then become a “jack of all trades” in everything networking. Right now, you want to learn just one facet of networking, enough to be able to help someone else out for the experience.

Let me give you an example, let’s say the facet of networking you wanted to hone-in on was wireless. You could buy your own wireless equipment, teach yourself how to set it up, IP everything, set the SSID’s, and encryption keys, etc. Heck, you could even break it and see if you can fix it. You can watch YouTube videos, buy a book, and just watch and read everything you can get your hands on until you are comfortable enough to do this wireless setup/troubleshooting for someone else.

Now I am not saying you need to become a wireless networking expert, but you do need to be familiar just enough with the technology to be able to set up, deploy and/or do basic troubleshooting on a network that is NOT your own.

This could take anywhere from a couple of weeks, to a couple of months depending on how fast you become comfortable. But once you are comfortable enough, you need to find a small business or even a residential customer that could benefit from your help.

And lucky for you, you can offer them a deal they can’t refuse. Not only do you charge significantly less than your average Network wireless guy, you agree to only collect payment IF you can resolve the issue.

Because after all, this is more about getting paid in experience than it is about money.

Sure, depending on what you a building out or troubleshooting for the customer, you may take a little longer than average, but eventually you will get it, all while gaining experience along the way so you can do it even better for the next customer.

Make sure you write down all the projects you handled and issues you troubleshooted for your customers, because you will want to put this on your resume as real, quality experience.

Owning and working in your own small business in networking looks great on a resume and not only proves you have network skills, it proves you are held accountable for your work and it proves you are responsible.

APPLYING TO THE JOB

5. The Resume

Hopefully you have been writing down and keeping track of all the projects you have worked on, and technologies you have been working with, because this is where you need to showcase that information.

It’s all about getting in the door and getting that interview.

I won’t go into too much detail in this post on how to make a killer resume that stands out, but I will share some tips that you should use when making your resume and applying to jobs.

Most people just make a resume, and then send it out to multiple employers and hope for the best.

DO NOT DO THIS. This is one of the biggest mistakes people make. They send out the same resume after resume and NEVER get a call back for an interview.

Every job posting is unique, requesting different skill-sets and experience from their applicants. And your resume should be different too.

Every job posting includes a job description that includes KEY information that you can use to your advantage.

For example, the post will often include “proficiency in XYZ networking equipment”. This is your clue that they probably have XYZ systems in their environment.

If you DO have experience in XYZ, GREAT! Make sure to make that STANDOUT on your resume…

But what if I have no experience in XYZ systems?

If you don’t have that experience, what you should do is highlight and draw attention to SIMILAR systems you have worked with. (I don’t mean take a highlighter pen to your resume, but do what you can to make this section standout.)

For example, if they are requesting experience with Aruba Access Points, and you have only worked with Meraki Access points, you can be sure they are looking for someone that has wireless experience. And even though you may not have Aruba experience, you need to make it stand out that you DO have other wireless experience.

People continue to make this mistake over and over when applying to jobs. You need to tweak your resume to more closely match the job description for every job you apply to.

Yes I know it can seem like a lot of work, but that ten extra minutes of adjusting your resume will be worth it if you get that call for an interview.

6. The Cover Letter!

The cover letter is more important than your resume.

Let me say that again..

THE COVER LETTER IS MORE IMPORTANT YOUR YOUR RESUME.

While the resume is more of a fancy laundry list of all your experience and skills, the cover letter is the highlight reel of what you really have to offer.

This is where you can really tailor your experience and skills to what the employer is looking for. This doesn’t mean lying, but rather highlighting the relevant experience you do have, and not drawing attention to the areas where you may lack.

It’s also the only opportunity in the application process where you can really let your personality shine through, and make yourself stand out.

I have sifted thought tons of applicants and resumes in my day, and while I do look at the resumes, they tend to all blend together and frankly, they get boring.

Applicants that include a cover letter immediately give the impression that they CARE and want the job. In addition they are just plain easier and more fun to read.

When you create your cover letter, keep the job description on hand. Use it as a guide to touch on all the key areas they are looking for in an applicant.

Always end you cover letter with a THANK YOU in your own words. Be sincere.

If you don’t submit a cover letter with your application, you might as well not even apply.

7. Type of jobs to apply to

Especially when you are just starting out in your IT and networking career, you DO NOT want to work for, OR apply to a large company.

ONLY apply to small companies, no larger than 500 employees.

You may need to do your research on the company to get an idea of how big they are, but that’s OK because you should always be researching every company you apply to anyway.

Why small companies are better for IT people

• Small companies generally need the IT people they hire to be more of a “jack of all trades” and learn a lot about all sides of IT (networking, servers, desktops, support, etc). Larger companies can be very compartmentalized, limiting your ability to learn about other areas which can limit your future potential.
• Smaller team means a bigger emphasis on personality fit.
• In a smaller company, it is harder to get lost in the weeds and go unnoticed, which can lead to promotions.
• The interviews tend to be less focused on technical questions, and more of a less formal open dialogue format.

THE INTERVIEW

8. Be likable

You followed all the of above steps and have been called in for an interview.

DON’T SWEAT.

be glad you got to this point because this is part where you will shine if you know what to do.

I won’t go into too much detail in this post on how to ace the interview, but I will give a few KEY tips.

FIRST and FOREMOST… BE LIKABLE.

Since you were called in for the interview, this means they have already seen your resume and cover letter and are at least somewhat confident that your technical abilities and skills are sufficient for the job.

If you are interviewing for a position in a smaller company like you should be, the focus will be more on whether you are a good culture fit.

In a small company, you will more than likely need to work in close quarters with a small team every day. And no one wants to spend that much time with someone they don’t like. So if you come across as a unlikable, you will not get hired.

9. Don’t be a know-it-all

What does that mean?

A lot of IT people credit their whole worth on their knowledge and skills. Because of this, they can often come across as a know-it-all, or someone who “if they hire me, I will fix all the IT stuff that is being done wrong here”.

I’ve interviewed people who in the interview, want to get into an “IT pissing match” with me to try and show me how smart they are.. as you can guess, they did not get hired.

The fact of the matter is, no one knows EVERYTHING. What companies are really looking for is someone who actually LIKES IT, and has put effort into learning the craft.

Companies don’t want someone who thinks they already know how to do everything their way, because no matter how much you “know” already, you will still need to be trained on how “we do it here” at the new company.

This is why being green can sometimes work to your advantage, because you aren’t already set in your way of doing things.

10. Be a real person

Don’t come off as a robot or fake.

Interviews can be pretty nerve racking, especially when you have come this far and are trying your hardest not to say the wrong thing and mess it all up.

Being nervous is completely fine and normal. In fact, in some cases it can even make you look more “human”.. But try not to let your nerves consume you. You need to be present mentally, and be actively participating in the interview conversation.

Pro tip***

While you do need to maintain an image of professionalism, you don’t want to come off as a no-personality robot.

You want to do and say subtle things that not only break the tension, but they also let your real personality shine through.

From time to time, you can use REAL conversation words like “Yeah” instead of “Yes” or “Cool” instead of “Great” for example… Cheesy I know, but using “real” words like these shows you are a “real” person.

Your interviewer is more than likely your potential boss, someone you will be spending a lot of time with. So while you need to come across professional in your interview, you need to intentionally let it slip that you are a “real” human being.

11. Tech Jargon

NEVER use too much tech jargon.

Many IT people think they need to use as much tech jargon as possible, especially in an interview because it will convey how knowledgeable they are.

This technique always backfires. If anything is shows you are not good at explaining the complex simply, and will be confusing when talking to users…. Keep the tech jargon to a minimum.

12. Technical interview

If you are interviewing for a tech role such as a network admin, the chances are there is going to be at least some level of technical questions to make sure you know your stuff.

But as I mentioned before, especially with smaller companies, the majority of the interview will be based on if you are a good culture fit.

The one key thing you need to remember for technical interviews, is what I call the Boomerang Technique. I don’t care how much experience you have or lack thereof.. At some point, you will be asked a question about systems that you have no experience with, or a question that you just simply don’t know the answer to.

This is where you need to re-direct the question back to something YOU DO KNOW ABOUT. Every topic has a correlation to another topic, you just need to be able to make that transition smoothly and naturally.

For example, let’s say the interviewer asks you about different routing protocols you have used in the past, but you don’t have experience with routing protocols yet. Rather than stopping the flow of conversations and saying “uhh I don’t know”.

What you could say is something like this:

“While I can understand the benefit of using a routing protocols, the past organizations I have worked in didn’t use them. It was easier for us to keep things simple by making all our routes static.”

Whether this is true or not, what you are doing is steering the conversation back to a topic you are comfortable with and away from a topic you are less comfortable with.. All while keeping the flow of conversation going.

13. Test format

The other thing that may happen on a technical interview (which I hate).. Is the “test” format. Where the interviewer will either give you an actual written test to take or ask you technical questions in test format.

For example, “Tell me the administrative distance of OSPF”.

In my experience, MOST smaller companies tend NOT to do this type of interview as much. But, if you find yourself in a situation where you are being asked technical questions in a test format, there is really not much you can do other than answering the questions the best you can and hope for the best.

If you are not taking a written test and the interviewer is asking you these questions, you can still use the Boomerang technique to bring the situation back to a more conversation-based interview and to a topic in which you can speak to.

The second thing you should do, no matter how well or not well you do on the technical questions, is maintain your likability. As I said before, the key determining factor will be your personality, and if you could fit in well with the culture.

Often times, if you are a good culture fit, how you did in the technical part of the interview will not matter.

To sum it all up

You can get a job in networking without TRADITIONAL experience, but you DO need SOME relevant experience to put down on your resume. What’s often overlooked is the various ways in which you can obtain this experience.

Afterall, EXPERINECE TRUMPS ALL. It won’t matter how many certifications or years of school you have if you don’t have quality experience.

A career in networking can be very rewarding and enjoyable and there are many different paths to get there. With a little hard work, passion, and creativity, you can get the experience you need to get your first networking job.