Getting bent out of shape when workers do it is just classist bullshit.
On the other hand, there's a lot more/better self-service capabilities these days and unless you have a dedicated admin who really knows you, having someone else do something for you can be more trouble than it's worth.
Examples: is it in the company's best interest for an expensive developer to spend a paid hour getting some time-off set up, using company processes, rather than two minutes sending an email? If the company switches from Asana to Jira, say, or (god forbid) one developer needs to use multiple such tools because they're working for clients with certain preferences, or across teams in an org that have different tools, is all the switching time, plus the actual day-to-day overhead of using either of those systems, for every single developer, a great use of company money? Or would it be better to have a standard interface for all those administrative tools (i.e. a person)? Someone to handle formatting and proofreading proposals, maybe. All that kind of stuff that you 100% do not need someone with a CS degree and 10+ years of development experience to do.
That sort of thing was common when I was a product manager a couple of decades back. Probably each supported more people than that but they handled a lot of annoying administrivia--albeit as part of much more paper-based manual workflows.
Was he WFH? Nope. He was running these teams from his desk in the cubicle farm. And he was relatively open about it too with management. But he knew so much that everyone kept him around.