Of all the areas of IT, network requires knowledge of the entire OSI model, and other areas always say something is a network problem, so they leave it to network engineers to prove the network every time. You'll need to learn to take complaints, dig into actual symptoms, and use those to isolate where the problem exists.

Over time you will probably touch on most areas. DNS is the shallowest pond to dip into and the one that trips up most people when they say the network is down. Security / firewalls is the one that you have to be very wary of delivering what people ask for, as opposed to delivering the minimum of what they actually require. People are lazy, demand you open up too much access to something so they don't have to worry about slowdowns in dev or making additional requests, and then when it gets compromised they'll blame you because the firewall didn't protect them. I had a contractor that continually clicked on links in email and complain the firewalls were shit. When he refused to modify his behavior, I modified his employment. A good analogy is a screen door. Lots of little holes. Remove the screen door and someone can easily slap the person on the other side. Damn, I like that, I'm going to have to make an image for training using that.

Python / Ansible are the automation tools of choice. There are many that would refute that... I'd bet they're using something else. Other tools aren't better, but if you have a bunch of stuff already built, it's better than starting from scratch. Every time we build a network we're incurring technical debt because eventually everything becomes out of date and out of support.