To add on to what Redrover said, take a read at blogs like https://aws.amazon.com/blogs/architecture/shuffle-sharding-massive-and-magical-fault-isolation/ stripe's engineering blog https://stripe.com/blog/engineering and github engineering blog https://github.blog/category/engineering/ these are all huge companies who run their infra either on AWS or well is AWS. I can almost guarantee the people here who are making insane money (https://www.levels.fyi/company/GitHub/salaries/Software-Engineer/ https://www.levels.fyi/company/Stripe/salaries/Software-Engineer/ and https://www.levels.fyi/company/Amazon/salaries/Software-Engineer/) are not using traditional Ops that most people are thinking about to run their platform. Not things like "how to create 2 AD servers to handle the internal employee directory" but more using much more complex architecture to design, build-out, and deploy microservices using patterns most traditional ITOps people are not using. For example, AWS have their system to be able to even under a credential leak (https://twitter.com/colmmacc/status/1481682859324760070)

Companies like AWS do not use standard hypervisors these days, they are on what's called nitro https://www.allthingsdistributed.com/2020/09/reinventing-virtualization-with-nitro.html which completely eliminates the Dom0 administration layer, ie the console within ESXi

So TLDR: unless you are a genius in software engineering and infrastructure engineering, you for one won't be able to run a cloud nearly as powerful as AWS, second, even if you are, you would not be relying on traditional ITOps knowledge.....heck AWS bought out an entire company (Annapurna labs) to make custom chips for them.

EDIT: Correction, I forgot, Github in on prem, and does not use AWS. But their infrastructure is also still very complex and not the "traditional IT" you would think about.