>but I disagree that "the work remains largely the same I meant at a very high level. The basic responsibilities haven't changed. * Deploy/configure infra

>but I disagree that "the work remains largely the same I meant at a very high level. The basic responsibilities haven't changed. * Deploy/configure infrastructure * Deploy applications into infrastructure * Monitor/Secure/Maintain infrastructure * Scale infrastructure as needed Sure in the 90's there was no Terraform, and deploying infrastructure meant getting physical hardware and racking it up. Now, you can use Terraform to deploy infrastructure to the cloud, on hardware you rent. So yeah, of course over the years the tools have changed. And sure, as you pointed out, even mentalities have changed (being proud to have a server with 300 days uptime, vs. being ashamed of that). You can call it "Sys Admin", "DevOps", "Site Reliability Engineer", or whatever, these are all largely the same "Make sure the infrastructure works, is secure, scalable, and help deploy to it." Even with with "cloud managed" things, you still need to setup, config, and secure it. You can have "cloud managed" k8s, it isn't going to stop developers for using bad practices, like running containers as root, and not having a standard deployment process (because each dev is just doing their own thing).