4 ms·
Strongly agree with your sentiment. The number of jobs that require "expertise in AWS/expertise in Google Cloud/etc" is laughable. It's like every company is cr
by totony 6y ago
Strongly agree with your sentiment. The number of jobs that require "expertise in AWS/expertise in Google Cloud/etc" is laughable. It's like every company is creating its own vocabulary for things network engineers have had terms for years.
This serves as an artificial barrier to hiring. I've done years of network engineering but then it comes down to "how many years of experience in AWS."
EDIT: Note that this isn't a new thing, e.g. we're looking for an "Oracle engineer"/"vmware specialist"/etc.
- scarface74 6y agoYou realize there is a lot more to cloud providers than just networking? I had the privilege of working with old school netops people who took one certification, duplicated everything on AWS like they did on prem and ended up costing the company much more money in resources and not saving money by using other AWS services. Once I learned about all AWS had to offer besides what lift and shifters knew, I realized how much money there could be if I learned about the other services instead of thinking of AWS as just a bunch of VMs. The same could be said for Azure and GCP I just fell into AWS.