Getting Started in Network Engineering: Glenn’s Practical Guide
The world of IT can look intimidating from the outside. Rows of blinking lights, endless acronyms, late-night troubleshooting marathons. But underneath the jargon, at its core, network engineering is about solving puzzles — and keeping people connected.
If you’re curious about jumping in, here’s a set of hard-earned lessons, mixed with a few resources Glenn thinks any aspiring network engineer should keep handy.
Start with the Basics: Understand How Networks Actually Work
You can’t skip this. Before you even think about fancy tools or certifications, you need to understand fundamental concepts: IP addressing, routing, switching, VLANs, subnetting, and the OSI model.
A classic primer is Cisco’s Introduction to Networking, which remains one of the best free foundational resources. Even if you never work on Cisco gear, their approach to explaining how packets move is timeless.
Get Hands-On Early
Reading theory only goes so far. Set up your own lab, even if it’s just a few cheap switches and an old router. Sites like GNS3 and Cisco Packet Tracer let you simulate networks virtually before you buy gear.
Glenn insists that learning through failure is the fastest way forward: “Break it, fix it, break it again. That’s the real training.”
Learn to Love Troubleshooting
Troubleshooting is 80% of the job. You need to develop a mindset that treats failures as clues rather than roadblocks.
A recommended read is Network Troubleshooting and Analysis from the Wireshark team. Even if you’re not deep-diving into packet captures yet, understanding systematic debugging will pay dividends.
Start Building Your Toolkit
You don’t need every shiny toy, but a few basics will help you immensely:
A solid cable tester (like a Fluke LinkRunner or cheaper alternatives)
A punchdown tool and crimpers
Label maker — trust us, future you will thank you
Basic set of spare cables and loopback plugs
You can always expand later, but these basics set you apart early on.
Certifications: Useful but Not Everything
Certifications like CompTIA Network+ or CCNA can open doors, especially for entry-level roles. They’re respected and show a base level of commitment.
But as Glenn likes to remind folks: “Certs help you get the first interview. Your actual skill keeps you on the job.”
A helpful rundown of certification paths is available from CompTIA and Cisco.
Find a Community
Networking isn’t just about switches — it’s about people. Join local user groups, attend meetups, or engage on forums like r/networking or The Bearded IT Dad. You'll find mentors, learn from shared war stories, and stay motivated.
Get Comfortable with Odd Hours
Events, rollouts, and upgrades often happen outside 9–5. Glenn’s worked more graveyard shifts than he can count — not because he wanted to, but because that’s when networks can go down without taking a company with them.
If you enjoy a predictable schedule, this might not be your space. But if you can embrace the chaos, there’s a certain satisfaction in knowing your fixes keep the lights on.
Final Words from Glenn
"The best way in is to start messing with real gear. Don’t wait for the perfect moment or the perfect cert. Get your hands dirty and keep asking why."
That’s really it. Get started, stay humble, keep learning — and before long, you’ll find yourself solving problems you didn’t think you could handle.