Is there more of an automation/programmability use case in ServerEng vs NetEng?

Pretty much the title.

• Certifications/education: The current flagship certification (CCIE) consists entirely of learning a proprietary operating system with no education about writing your own modules or writing any code at all. On the other hand, certain MCSE tracks include the basics of powershell. The RHCE also includes some basic shell scripting. I'm choosing these certifications to try my best at making equivalents but please correct me if I'm wrong.

• Coding: Most NetEng I've worked with do not know any coding at all. Their automation is limited to column highlighting with N++ and find/replace. Sometimes extremely basic regex. Certainly no config management, automated provisoning, orchestration, etc. But maybe that's because this use case doesn't exist or isn't as strong in networking? I'd love to hear from some of you on this.

• Proximity to developers: SysEng is way closer to developers (people who only code and do little to no Ops). So they feel more pressure to automate QA build-outs (VMs, DBs, LB configs, etc.) because the business puts pressure on SysEng to not delay Dev as that directly impacts profits.

To frame the question another way, if someone knows they love automation/coding but also knows they don't want to do development and would rather do operations, would they have more opportunity to code/automate if they went the NetEng route or the SysEng route?

These are some of the comparisons I've tried to make but I'd love to hear from people who have had more exposure to this in their career. Is there more of a use case for automation/coding in ServerEng than NetEng?