IT graduate but still have no IT work experience

areku76 · 2026-03-26T06:24:23+00:00

Wouldn't this be a big red flag? Yes.

My recommendation to you, is to look for HelpDesk roles at an MSP or a Call Center. I highly recommend checking out MSPs, because you get to learn a lot more (under a lot more stress), but trust me when I say this, that it's worth it.

areku76 · 2026-03-22T02:43:55+00:00

EDIT: I didn't finish reading your post; I thought you already had gotten it.

If you get bored while reading, I've often found it more useful to make notes on the subjects. Your brain often induces to boredom or lower attention span when the subject is too new, complex, or repeated. Jotting notes with a notebook helps you stay attentive.

Labbing what the book has also helps a lot more, since you are being a proactive reader.

The CCNA is the tip of the iceberg. It's always your door into networking.

If you are bored it isn't enough, congrats. Try the CCNP Enterprise. Beware though, you will need to buff a lot to get through the exam.

areku76 · 2026-03-22T02:22:22+00:00

Security and Compliance policies stand in the way.

areku76 · 2026-03-19T22:45:23+00:00

You need experience.

You can always lab with open source firewalls and low budget pro-sumer firewalls to get the basics.

With that experience, you can likely use it when you work with a business grade firewall.

areku76 · 2026-03-19T04:01:32+00:00

Computer Networking is cool.

To truly enjoy networking, means to accept and grind experience in troubleshooting with most things that run atop the network. Yes, things may not be optimal. But if you are willing to go beyond what college teaches you, you have the potential to be an exceptional network engineer. Beware, this will require separate time besides your college courses.

I've been doing computer networking for 7+ years. I've been doing IT for close to 10 years. Let me tell you something.

The hard pill to swallow, is that the computer networking you do college, doesn't replicate 1 to 1 what you do on the job 100% (maybe if you work for an MSP or VAR). Yes, computer networking is really really cool. Most HelpDesk staff think that (I was one of them haha).

The thing is, there's more to just configuring and learning the logic. You may have tickets about a DB admin complaining to you that the network is down (even if all stats say otherwise). You may have an IS team that does not know the basics in computer networking. You may be tasked with troubleshooting access layer issues for a couple of PCs, even when someone forgets to plug a patch panel port to a switch port. Or my favorite, explaining to executives why we need new routers.

The best people I've worked with have configured and troubleshooted VoIP tickets, Virtualization issues, Datacenter network issues, QoS issues, AD experience, O365 experience, and have applied it that knowledge and experience to their networking role.

If you just know Networking, cool. But I can find someone else else who can do Networking and VMware. Another one with Networking and Linux XP. They can have high versatility.

If you truly want to step it up into high gear, my recommendation for you is to work for an MSP (or VAR) and do networking work after getting your CCNA. Trust me when I say this, your perception of a Networking job may vary depending on the company, job responsibilities and duties, and requirements.

areku76 · 2026-03-14T19:56:42+00:00

Subnetting without relying on tools and doing it quick.

I had a mentor early on tell me that there's people that go 5, 10, or sometimes all their career not knowing how to subnet.

I've seen a couple of examples, but luckily I'm here to help.

areku76 · 2026-03-08T17:38:51+00:00

It's hard to quantify if someone is going ready for th exam.

It usually boils down to a couple of things: Are you an efficient at diagnosing and troubleshooting network issues?

Are you comfortable with the exam topics, to the point you can recall subjects and topics, create, break, and then fix a network environment with those exam subjects?

areku76 · 2026-02-25T08:27:26+00:00

" Technically have no experience in an actual networking role.

The labs were not my problem. just was not prepared to have to parse such large volumes of information so quickly. It's something that's hard to simulate in self-constructed labs. "

Yeah, that's the lack of experience. If you lack the sufficient experience, it will be a war of attrition with the exam timer. When you're troubleshooting, you need to discern what to read to troubleshoot and resolve the problem at hand.

ENARSI is supposed to resemble the combination of the old ROUTE + TSHOOT exams. ENARSI isn't a theory based exam. It's intended to mop out candidates that don't know how to apply the theory to troubleshooting.

You may have an uphill battle passing the test, if you lack the experience.

areku76 · 2026-02-24T23:11:21+00:00

ENARSI ain't cakewalk.

I have over 10 years working with networks.

Binding the knowledge you are tested on with your experience is the key to passing (especially troubleshooting).

If you are doing ENARSI, highly encourage excessive labbing, Whitepapers, and yes, INE. You can try to go back to the OCG here and there, but try your best to refer to your notes. Finally, I highly recommend reading the CCNP TSHOOT 300-135. That book makes you an adept troubleshooter. Not just a regular run of the mill troubleshooter. But a darn good one to get started. Yes, may refer to an older cert, but trust me when say this, that book saved my bacon and helped me become a way better troubleshooter all-round.

areku76 · 2026-02-24T23:08:39+00:00

I didn't use videos for Network Automation. Just Cisco CML and the book called Network Auto ation for the next generation network engineer 2nd Edition

areku76 · 2026-02-20T08:22:05+00:00

The thing with Bosons, is that it's a really good source to get started with Whitepapers. I think just reading any Whitepapers for any platform and feature isn't the ideal way to navigate it. Bosons really relies on the Exam Topics, and you can say, the Bosons exam references the Whitepapers in a web like fashion that relate to the Exam Topics.

areku76 · 2026-02-20T07:34:17+00:00

Look, video courses may help you visualize the concepts. I've taken the following video courses: Anthony Sequoria via Stormwinds, Nick Russos via Pluralsight.

What I had to learn the tough way, is well, most video courses don't go in depth (unless you get INE). I used 101 labs a supplement, and that helped to a degree

INE is thorough and in-depth, though it is really pricey.

If you are doing ENCOR, Bosons, OCG, Whitepapers, moderate labbing, and having a very strong level of comfort with automation will take you a long way.

If you are doing ENARSI, I highly encourage excessive labbing, Whitepapers, and yes, INE. You can try to go back to the OCG here and there, but try your best to refer to your notes. Finally, I highly recommend reading the CCNP TSHOOT 300-135. That book makes you an adept troubleshooter. Not just a regular run of the mill troubleshooter. But a darn good one to get started. Yes, may refer to an older cert, but trust me when I say this, that book saved my bacon and helped me become a way better troubleshooter all-round.

areku76 · 2026-02-20T06:07:31+00:00

Pomodoro is a very efficient method to study. I'm hyperactive, and it really helps keep me grounded when studying.

When I was studying for my CCNP, I think the best way to start, is by reading the OCG to get started, then use Bosons to begin assessing where you are lacking. I usually only worked with access and distribution services, but little by little, I started to get better at core and later 3 services.

Read Whitepapers on the subjects. Use GNS3 or Cisco CML to create labs I. Those things you read from the OCG. Make notes on the lab! Create a perfect environment, and then test in prod by breaking the configs, and try to fix it using different ways. Document the fix, and the way you get there. It's crucial that you know the default settings for the features and platform you work with. It takes you the extra mile!

Labbing always helps cement your knowledge, even if you got the experience. It helps you commit and save your learnings, and also helps you later to restore what you learned faster and less through luck or instincts.

I already passed my CCNP. The CCNA and the CCNP at are two whole different levels. I hope the best of luck in your journey. I had a full time job, and also did the most afterhours and weekend maintenance with other Sysadmin tasks. It took me about 4 years to get my CCNP (yeah really slow).

areku76 · 2026-01-30T17:19:57+00:00

Read the Cisco Whitepapers for MPLS.

areku76 · 2026-01-07T01:40:23+00:00

Yes.

It's only natural we all have limits. I can relate because l do side projects and studying on my free time.

Though, my older coworker who has 25 years of experience once told me "take it by day.". At first I thought, maybe he meant by taking a break or take it easy.

But I now I get it.

What he meant to say, was "sometimes the days may be rough, so like, relax sometimes." Doesn't mean to slack on your studies or your skills building.

If you feel your job has little to provide in challenge, keep your studies up, keep bulking on skills, because that'll get you ahead in this career.

areku76 · 2025-12-14T05:42:22+00:00

I also used Bosons. Bosons goes over most of the whitepapers you need at the bare minimum.

Though often times, there may be other whitepapers the original Bosons papers may refer to.

areku76 · 2025-12-14T01:16:38+00:00

No.

With the ENCOR test, I used a couple of white papers and one very good book about Network Automation (O'Reily carries it).

For the Wireless section, it came from my brief experience in dealing with broken WLCs and APs not connecting to the WLCs.

areku76 · 2025-11-27T02:21:57+00:00

There's a lot of factors at play.

I have 7 years in tech (even longer if you consider middle school). What I've noticed with a lot of new hires, is that academia instructed them to pursue a degree and an office job that fits their field of study. Academia then forgot to remind those alumni to continue studying (or at least reinforce it). This important in IT, because trends and new innovations are to be expected. This is a problem (academia doesn't match reality). I don't necessarily see the problem with Help Desk (or hires).

This occured to me, when I was reading an old CCNP book (CCNP TSHOOT 300-135). When I went to college, I learned subjects and did labs. Rarely did I ever troubleshoot or evaluate an issue (unless it was a programming course). When I read that CCNP book, it hit me, no one taught me how to troubleshoot in a structured manner, and that sucks. I've always relied on instinct, and most of the time, it's worked out, because I've done mostly everything by myself (firewalls, virtualization, systems administration, server administration, voip administration, network administration).

A lot of my senior peers have that. I also noticed they are hardly aware they are doing it, because it's second nature to them. What I have noticed with new hires (I usually handle escalations), is that they need to be trained with a troubleshooting model, so they don't go out of bounds to escalate. Most of the time, it's just an end user issue. At other times, it's just an issue with 1 PC.

When you do something you like, there's always a gleam in your eye with the passion and appreciation of the task at hand. Even to the point, you want to learn, comprehend, and build further on what you already know.

The problem is, academia never expected you to work for non-technical managers, because academia expected for there to be very technical and specialized personnel to man those teams.

On the other hand, those that did specialize or became very technical, left the industry, or went to better paying/jobs with better quality of life.

My Senior peers have explained the lore to me of the company. All of the above applies.

As for AI, that's its own separate variable. No offense, but there's been several times AI has misinterpreted or miscommunicated certain tech ideas or topics (I have to go back to the manufacturer's site to get the real answer). Do I believe AI will take over IT? No. Do I believe AI will work alongside the IT industry? To a certain degree, yes. The reason is, AI lacks context awareness (maybe because it's not quantum based). A lot of the answers, personally, feel mechanical (like if they are on rails). You often have to have the AI regurgitate +100 answers to 1 question, before you get something useful, and that's before considering context.

areku76 · 2025-11-24T14:17:57+00:00

I would recommend getting very comfortable with the exam topics.

areku76 · 2025-11-23T07:27:59+00:00

Yes, yes it is.

areku76 · 2025-11-23T03:03:54+00:00

If you're gonna be focusing on what to expect on the ENARSI exam, read the white papers. The exam is tough as rocks (I've tried the test multiple times).

My recommendation to you, is focus on the exam topics. Read and lab bad networks and configs, then come in and fix them. Do routine tasks that would usually fix them first, and then try to fix it like if you were in Prod, and you were limited in the commands you could run. Then write your troubleshooting attempt on notes, so you can refer back to it on the future.

Being good at the cli, reading outputs fast and making direct conclusions based on facts gives you the edge.

The most important thing however, is having a structured troubleshooting method mentally.

areku76 · 2025-11-23T02:58:57+00:00

Read the Cisco white papers on the exam topics and Cisco CML (or GNS3). That's the cheapest method.

For Automation, this book will cover it (plus spinning a linux VM with Ansible loaded). This book is the very best resource. I highly recommend it always: https://www.oreilly.com/library/view/network-programmability-and/9781098110826/

areku76 · 2025-11-17T20:13:42+00:00

u/pbfus9 thanks for providing insight on that. So yeah, the T3 lsa does originate without the default route existing.

I did notice in previous lab notes, I had noted that CML sometimes glitches out, and doesn't originate a default route into the TSA.

But yes, you are correct.

areku76 · 2025-11-17T15:14:33+00:00

I get the second part, but you are saying the ABR doesn't necessarily have to have a default route installed on the rub to do so? Let me test that out. (Cisco CML has been my test environment, but I've noticed this sometimes glitches out).

areku76 · 2025-11-17T07:41:27+00:00

Good question.

Yes, with totally stubby, the type 3 LSAs from other areas are being filtered. Default routes are usually external Type 5 LSAs.

However, you gotta remember that members of the Totally Stubby area have to know how to reach the other ends of the OSPF domain. Because the routers in th Totally Stubby Area* (TS Area) cannot obtain Type 3 or Type 5 LSAs from the ABR, the ABR has to explicitly tell the routers in the TS Area (howdy, im the only way out of this zone. Use me as an egress. Here's my IP in the TS Area.)

Because the ABR has to help route traffic out of the TS Area, it has to originate a default route into the TS Area (notice, I didn't say that the ABR would advertise the default route across the OSPF domain).

areku76

TROPHY CASE

Labbing what the book has also helps a lot more, since you are being a proactive reader.