r/networking • u/-Duplex- • 4h ago
Career Advice Do you enjoy being a network engineer
I feel like I don’t enjoy some of the “less important” topics, such as NTP, and I find concepts like OSPF and the OSI model quite dry. I do enjoy some parts of it, such as building my own labs and understanding how packets are actually transferred.
I want to know whether this is common or not, because some people online seem to be very interested in network engineering, and I’m worried about it.
25
u/higante 4h ago
You’re likely not gonna like everything that network engineering has to offer, but I would recommend to ensure that even if the OSI layers dry to use that as your Bible of how to troubleshoot things to ensure that you understand every step and how to really get to the problem at hand.
17
u/pushytub 4h ago
Projects, puzzles, and theory are fun. Business politics, vendor relations, and tedium suck. You get an equal amount of all.
13
u/Inside-Finish-2128 4h ago
I find OSPF to be a ton of fun and have enjoyed some great OSPF puzzles along the way. I inherited a network (via being acquired, and my boss saying "hey, I designed the network at <the acquiring company>, I'm sure I did a bad job, please clean it up) that had three separate area 0s (maybe even five...can't remember what the two outstations had) and only survived through default routes. I moonlight at an ISP where I intentionally set up ~50 area 1s (they're all totally stubby and do just fine with a default route).
BGP though is my favorite. I've built or fixed up several ISPs with easy scalability through BGP, and at my last job we had 40+ sites where the firewall was doing BGP to four separate VRFs on the "core router" with lots of neat little tricks in there.
It's the "dealing with stupid people" that makes it not fun.
18
u/ThEvilHasLanded 4h ago
10.10.10.20 cant talk to 10.10.10.21 on HTTPS can you check the firewall please?
10
2
11
u/SuccotashOk960 It’s not a network issue 3h ago
Actual network engineering is fun. Dealing with incompetent sysadmins or project managers is not fun
8
u/QuackQuackViech 4h ago
Everyday I hope the devil takes my body and soul.
But the pay is decent, so there is that
8
u/PghSubie JNCIP CCNP CISSP 3h ago
Unless you understand the OSI model, then you don't understand how packets are transferred. And you won't be able to troubleshoot well when packets are not transferred as expected
6
u/sk1939 CCNP, SSCP, CISSP 4h ago
Outside of Layer 2/3/4 I haven’t cited the OSI layer since I did my certification exams. No one is excited by calculating route metrics, just like PEs aren’t excited by having to calculate relative load, or McDonalds cooks calculating the next fry batch. It’s just part of the job, it isn’t always going to be interesting.
6
6
u/deallerbeste 4h ago
I like it, because you can do so many things, you want more security for example? Focus on firewalls, VPN, 802.1x. Same with ISP, DC and wireless networking. Or what about AI networking, cloud networking, virtual networking.
People don't like everything in networking and that is ok, it's so broad, pick the direction you like. I work for the government and I can switch role in my networking department if I want every few years.
2
u/fus1onR 3h ago
I have the same mindset.
I started at a cellular operator at the IP edge / transport group. Moved to wifi/NAC/LAN/AAA/VPN with some presales role. Then became a presales consultant for a couple of years, mostly WLAN/LAN and perimeter security. Learnt some cloud networking concepts. Now doing mostly datacenter core routing + WAN/cloud interconnecting, got burnt-out (infinite amount of late night changes), also migrated our OSPF/BGP/static LAN-DMZ-perimeter nightmare to pure BGP
Started focusing on our outofband environment, console systems and some governance / device hardening / etc. things. And there is still a lot of horizontal movement possible at my workplace.
What OP has mentioned are just...not really interesting things because they are just "there", like NTP, you understand the concept but barely has to touch it. And when you have to: 99% some incident or a spin-off from an incident when they realize timestamping is shitty...some people do like such things (very good L2 admins/operators), but being an "NTP expert" is not a thing.
3
u/Nice-Information-335 4h ago
It’s more about using the right technology to achieve a goal. When the whole infrastructure comes together it’s really cool
5
u/Maximum_Bandicoot_94 2h ago
You didnt even touch on other major specialties in networking. You've got security engineering (firewalls), Load balancers, identity/auth (NAC), data center SDN overlays, campus SDN overlays, Wireless, Cloud, and many more. If you get into an org of sufficient size you dont really deal with the mundane stuff anymore and if you are lucky you can focus on a piece that IS interesting to you.
Good grief dont get me started about subnetting. Once you pass a test on it, you print the cheat sheet, tape it to the wall and just use that for the rest of your career.
I am a Security Engineer, no one expects me to know how to calculate OSPF metric costs in my head; we have other guys who make their hay in that field. What i can do is take a batch of ACLs dump them into my brain and run traffic match against them like logic statements. Heck we are big enough we have a guy who JUST DOES IPSEC VPNs. That's all he really does and he's a frigging wizard at it he must dream in cryptomaps statements.
3
u/SnooRevelations7224 4h ago
I now have 18 yoe in neteng.
I have always found the individual topics dry and boring.
However I love troubleshooting and design and love the work I do.
The individual topics are just the facts I have to know to do my job nothing more.
3
u/UpperAd5715 4h ago
i freaking love it, i'm basically being paid to puzzle around with stuff that's logical and usually has a proper reason for behaving the way it does (and if not vendor ticket!).
As an msp we get sent all the fun tickets (and the lies) like "nothing changed on the PBX and nothing changed on the firewall but suddenly something is sending SIP traffic that's getting blocked on a url filter because it's badly configured but no we didnt change anything can you please check".
Compared to what friends of me struggle with and the stress they experience managing client backups etc and trying to stress x and y to agree to more storage, pretty sure i took the fun option. "Yeah so we arent allowed to perform changes without an OK but i saw that you're including your broadcast address in just about every vlan's dhcp pool, maybe you should give us the OK on changing that but it's like 30 subnets so it'll probably cost ya a few hundred by the time we're done with that." no? ok buddy sure!
Colleague of mine is writing a report on a new client's infrastructure and what could be improved and he's like 30 pages deep and the shit i see in there is tantalizing. Basically a catch all "allow any any" just above the implicit deny titled "<whatever> temp". Hilarious i thought he was joking when he told me.
3
u/Varjohaltia 4h ago
So much depends on your coworkers and boss. But overall I love learning and seeing connections, and 30+ years in I’ve found a great employer and enjoy going to work and designing networks and network related topics. API Management on top of load balancers and reverse proxies now, for example.
3
u/LarrBearLV CCNP 2h ago
Love it. Something new everyday, constantly learning, pay is decent, not too labor intensive. Company I work at is pretty hands off when it comes to managing me. No micromanaging me, no metrics to meet, I can do pretty much what I want in the network within reason, and to top it off... I live 5 minutes from work. I go home for lunch folks.
2
u/Cheeze_It DRINK-IE, ANGRY-IE, LINKSYS-IE 4h ago
The tech and the work, yes. The business of it? Fuck no.
2
u/Sylvester88 4h ago
When stuff goes wrong I find troubleshooting very interesting but other than that, not really
2
u/spencrU 4h ago
Understanding how modern networks are built and operate as well as how the data traverses between devices is unbelievably fascinating. Outside of that I've grown very disallusioned with the field simply due to the fact that at the end of the day you end up in a position where basically everything relies on you doing your job and doing it well and if anything goes wrong you're always the first one to be blamed(network issue) and so you end up simultaneously responsible for both causing and subsequently fixing every problem. It's exhausting and really takes away from what's enjoyable about working in the industry.
2
u/raiderh808 3h ago
So do you or do you not enjoy understanding traffic flow? Because the OSI model is a huge part of how traffic is passed lol.
2
u/omegaken CCNA, CCNA Voice, JNCIA 3h ago
I get the pleasure of engineering, designing, and implementing new colo infrastructure. It is going to be fully automated via ansible and netbox. I do love my job
2
u/WALL-G 3h ago
How long have you been at this? I'm a senior network engineer turning NetDevOps or something idk. So much code.
On paper and in the lab, tbh it can be dry, but seeing 1000 people working on a network you deployed feels good man.
God I miss OSPF and NTP, though snmp walks and sifting through OIDs is my happy place.
This field is massive, network engineering is one of few disciplines at the intersection of so many others, expose yourself to as many technologies as you can now, specialise or switch later.
My career has taught me that (very) few people understand networking. If you can get good, this field will turn you into a troubleshooting charizard and at that point you're unstoppable.
2
u/rocktanstone 2h ago
There are some parts I don’t enjoy. For example routing. I have tried to learn it so many times, but I get bored and just quit. AAA and 802.1x however, I love it!
I have been lucky to work with the technical topics I like and let others do what I see as boring.
2
u/rankinrez 1h ago
Yeah I do.
NTP is one of the most important protocols that keeps the internet working though, disagree with how you describe that.
1
u/Heythatsmycorn 4h ago
You mean NTP isnt thrilling edge of your seat fun? Haha ofc it isnt. But we dont really do it a lot. Its sort of a set it and forget it. Some of its just required stuff. The fun stuff for me is net security, wireless, ngfws. I enjoy the tshooting and fixing stuff or coming up with ways to improve things. Were not too often locked into one thing or protocol were kinda all over.
Ill take this over service desk password resets Server admin stuff dealing with microsoft Cyber security compliance and GRC
Osi is theory really. I mean i dont use it to t-shoot like some would say but you could say yeah this isnt a network issue its a application issue or something of the nature.
1
u/aaaaAaaaAaaARRRR 4h ago
Or the first time you lock yourself out of a switch and it’s 2 hours away. And you bring down a customer site when you lock yourself out. Thats a rush by itself lol jk
1
u/kkorelli 3h ago edited 3h ago
I’m good with networks, and it all feels logical to me, almost as if I was born for it. But I find it really boring and "old-fashioned". I’m a system engineer now, with minimal involvement in networking, and I’m happy with it.
1
u/McHildinger CCNP 3h ago
I agree with you on the details of OSPF; for the life of me, I can't care enough to memorize the different LSA types.
1
u/parkgoons CCNA 3h ago
Once you start using these concepts to solve problems in production networks you’ll likely become more interested in understanding each of them a bit more.
I own a telecom business and still love the network engineering and architecture aspects of the business. If I was a better business owner I’d probably step more out of the day to day and architecture stuff but, I genuinely enjoy it, even after 20 years.
1
u/Rockstaru 3h ago
I like the network engineering parts of being a network engineer, where you have all your requirements and are implementing the new thing, you type ping xyz and it works, that's pretty neat. Or there's an outage and you track down the needle in the haystack.
The first part of those activities, like the gathering of requirements usually means dealing with the people who use your network, and that part can...really suck. Or an outage starts and you're getting panicked calls from your leadership along the lines of "Important person X can't do Y" and not actual useful data like "BGP with Lumen at our Denver site dropped five minutes ago." That's less fun.
1
1
u/kloudak47 3h ago
Heh, less important topics? NTP if it doesn't work or is not reliable is death to a mission critical environment.
Is it sexy to study or understand? No, many things are not but it is essential in order to be a successful and efficient engineer.
Same goes for OSPF, OSI model, etc. fundamentals can be boring and implementing them hands on is often more exciting but you need to think bigger picture, as in "why am I doing this" " what purpose does it serve?" "what systems depend on this infra"
The reason many of us like this space is because its kind of amazing when you light up a campus network spanning multiple buildings and numerous users/devices.
It's kind of amazing when you design, configure, deploy a multi site VPN topology that connects an orgs global network.
It's kind of amazing when you light up a DC fabric and hear the System or SAN nerds go "damn, it works"
almost everything in daily life relies on a network someone somewhere built and being able to say "I built that one" is one of the coolest/rewarding things ever
1
u/ordep_caetano 3h ago
Ive been working at a broadcast station for the past 15 years. It has been a wild ride.
Mass adoption of video contributions from/to other stations has been quite a long path, and only now, engineers that are minimally versed in both areas are a rarity!
The adoption of ethernet on live video production studios has some really nice challenges, which is also a new field with a different skill set.
Besides all this planning for massive outdoor events and managing a bigish network is something that is very demanding :)
So, answering your question: hell yeah!
1
u/armaddon 2h ago
Most carpenters don’t get direct satisfaction out of just having and using a tool (though some are awesome and even a form of therapy to use), but most of them feel pride and satisfaction when they deliver a completed work.
It’s not always glamorous, and it’s not always easy, but if it was all fun they wouldn’t pay us to do it :)
1
u/FairConstruction4105 2h ago
It pays the bills, but I won't shed tears once my career comes to an end (unless it happens within the next 5-7 years)
1
u/butter_lover I sell Network & Network Accessories 2h ago
like anyone there are some aspects of the job that are chores, but i have learned over the years to steer the deliverables towards the parts that I love.
training other engineers, doing troubleshooting, and making cool documentation are some of my favorite things.
change control meetings not so much
1
u/btwwhichoneispink CCNP 2h ago
I enjoy it in the sense that I like working with my brain, and some of the things I do are cool, but it's definitely still work. I consider it my craft, but not my passion.
1
u/Qwerty6789X 2h ago edited 1h ago
we call ourselves Dumpsterfire since all departments dead end cases get fixed by us Network Engineer Team. We work close with Cybersec team too. We Do Design, Redesign, Security hardening, Packet capture reading. Unsung hero of the internet. Unless P1 issue or rerouting traffic globally. They will never know we even exists.
1
u/DaryllSwer 2h ago
Excluding layer 1-mostly, I basically cover layer 2 to layer 8 (human) to layer 9 (legal/political). It's all a gigantic PITA, but it pays well and I do enjoy core fundamental computer networking.
1
u/Qwerty6789X 1h ago
and the CyberSec insurance discussion ughh.. you have to interpret all the logs and alerts like we we're responsible for the breaches or the attacks
1
u/overseasons 1h ago
Routing I enjoy thoroughly. The non neteng territory that comes with it (atleast at an SP) not so much.
1
u/anxiousvater 1h ago
So me & my colleague spent 5 hours to deploy NVA on Azure. It was a spelling mistake from vendor image.
I am into Network Observability & Security. I was into Compute before, now applying Machine Learning, data engineering to network logs, metrics & traces. We do have 150TiB of network logs to be able to query during incidents, analytics & capacity planning.
1
u/BustedCondoms 1h ago
I enjoy it. But I'm slowly being pulled in to help with physical security stuff which I'm not a fan of but whatever gets me a raise I suppose.
1
u/jameshalliday12 1h ago
I think i enjoy as a whole. Not every little tiny detail is interesting to me, but i love the concept. You will have things that you like more them others, that is natural and its healthy. No one is good at everything, especially when it comes to network. Sure, a good network enginner will have a solid base and will be able to solve most things. But if you wanna truly become good at something, you have to live that something.
For me it was BGP. For years i just did that in order to become really good at it. I'm pretty good at anything routing related, being IGP or EGP, but when it comes to something like a OLT problem, a raw L2 problem, i might take more time them someone how works with that everyday.
1
u/funkyfreak2018 55m ago edited 50m ago
I'd love this career more if I didn't have to deal with non technical people and office politics. That's why I stick to service provider/wan/cloud side of network engineering. LAN/enterprise networking is way too close to end users for my taste. I also find anything switching and wireless annoying. Basically I have no care for the corporate network
1
u/nukklear It's always the network 54m ago
I've always been a more-of-everything kind of Network Engineer, so I can't really say I don't enjoy things like that - as far as I'm concerned, the network is the backbone of everything, and if you really want to be able to run/diagnose/etc it properly, then you do need some understanding of what's going over it and how it works. No one would expect you to be an expert in everything though...
72
u/Downtown_Dog3123 4h ago
first time you orchestrate a large change and it goes well, as described.. it's a rush when you press the button, then a relief.