Earlier quoted context omitted.
One question for you: how does an engineer know what to automate?
How does a people manager know what to automate? And, more importantly, what might be the massive unintended consequences of routing your org's permission structure in the same way you route its head-count? Strategic decision-making is not the same as people managing, and people managing can even create blind-spots that get in the way of good decision-making.
Would you rather have developers wearing every hat in an org? When would they find time to code? I know many developers who don't want to have to do all of that work simultaneously, and are extremely grateful for a manager who can take many of these tasks off their plate.
When was the last time you tried to add a recurring meeting to a development team's calendar? They... don't like it, in my experience, and I respect the hell out of that.