3 ms·

> That said; we also have "Cloud Engineer" as a job title, so I'm not sure we will learn this lesson. Comparing something as vast and broadly reaching as "Clou

> That said; we also have "Cloud Engineer" as a job title, so I'm not sure we will learn this lesson. Comparing something as vast and broadly reaching as "Cloud" is a disengenous comparison to something as specific as a tool like Google Analytics, kind of a wierd comparison IMO. The entire pattern of tech is towards the "cloud" - even if you refuse to use the big ones like Amazon, Microsoft, or Google, it's still technically "cloud" if it's managed servers (wherever they may be). To be honest I never got into the hype behind Google Analytics and I'm glad that I never spent more than 5 minutes at a time dropping the occasional tag on sites I built. (I've also never worked for anyone big enough where the analytics ultimately proved useful or valuable anyway). These tags are now easy to remove by deleting a few lines of code. I really wonder if the larger orgs really should have spent the extra few hours / weeks of development to develop an in house solution all along...

pbmonster 3y ago
> Comparing something as vast and broadly reaching as "Cloud" is a disengenous comparison to something as specific as a tool like Google Analytics Is it? Tons of cloud people I know are very narrowly specialized and certified on AWS or Azure. They certainly don't ever apply for jobs using the other... I'm sure they could retrain. But I'm also sure they don't want to.
- moduspol 3y ago
  At this point, being a "cloud" engineer essentially means that you're good at understanding and adapting to new services / value propositions, since they become available quite regularly. It doesn't mean, "really good at EC2, and incapable of learning more."
  - delecti 3y ago
    If I were reviewing resumes and saw someone list themselves as a "cloud engineer", I would make very sure their skills listed the cloud provider used where I was hiring. That title would make me assume they were a specialist in a cloud until I saw otherwise.
    - firstplacelast 3y ago
      That says more about you than them, though. You’re projecting your own inability to translate knowledge into new systems and assume the same of others.
      - delecti 3y ago
        I'm not projecting my inability, I'm assuming incompetence. I'm a cynic, not insecure. I wouldn't blanket block a resume that said "cloud engineer", I'd just make sure to probe that they aren't just an "AWS engineer" or "Azure engineer".
        TheNewsIsHere 3y ago
        That is entirely reasonable. A title I have frequently worked under is “Cloud Engineer”. I’m strongest in AWS, secondly Azure. But I also am extensively using Linode’s platform and Kubernetes too. My best friend’s title has also been “Cloud Engineer” and he is exclusively in AWS. He doesn’t really know more about Azure than he needs to get things connected to AAD. How anyone could know that without asking eludes me. If you’re hiring for a position, you have a responsibility to know.
    - mr_toad 3y ago
      You know that the big clouds (and to a lesser extent the smaller ones) have more in common than they are different? They use different jargon, they love to market themselves on their differences (because why compete on price?), but the fundamentals are really very similar and the skills transfer. Anyone who’s telling you that Cloud X is vastly different from Cloud Y is either trying to sell you something, or has gotten their knowledge from someone who was selling them something.
- scarface_74 3y ago
  I work at AWS Professional Services, people move around among AWS ProServe, Google/GCP, and Microsoft/Azure all of the time. Heck plenty of people come into ProServe with no AWS experience. But they know their areas of specialty well and it only takes a couple of months to use AWS specific services.
Jiocus 3y ago
> it's still technically "cloud" if it's managed servers (wherever they may be). Thank you for this. No more second thoughts about pointing cloud.example.com at our local HPE rack.

pbmonster 3y ago

> Comparing something as vast and broadly reaching as "Cloud" is a disengenous comparison to something as specific as a tool like Google Analytics Is it? Tons of cloud people I know are very narrowly specialized and certified on AWS or Azure. They certainly don't ever apply for jobs using the other... I'm sure they could retrain. But I'm also sure they don't want to.

moduspol 3y ago
At this point, being a "cloud" engineer essentially means that you're good at understanding and adapting to new services / value propositions, since they become available quite regularly. It doesn't mean, "really good at EC2, and incapable of learning more."
- delecti 3y ago
  If I were reviewing resumes and saw someone list themselves as a "cloud engineer", I would make very sure their skills listed the cloud provider used where I was hiring. That title would make me assume they were a specialist in a cloud until I saw otherwise.
  - firstplacelast 3y ago
    That says more about you than them, though. You’re projecting your own inability to translate knowledge into new systems and assume the same of others.
    - delecti 3y ago
      I'm not projecting my inability, I'm assuming incompetence. I'm a cynic, not insecure. I wouldn't blanket block a resume that said "cloud engineer", I'd just make sure to probe that they aren't just an "AWS engineer" or "Azure engineer".
      - TheNewsIsHere 3y ago
        That is entirely reasonable. A title I have frequently worked under is “Cloud Engineer”. I’m strongest in AWS, secondly Azure. But I also am extensively using Linode’s platform and Kubernetes too. My best friend’s title has also been “Cloud Engineer” and he is exclusively in AWS. He doesn’t really know more about Azure than he needs to get things connected to AAD. How anyone could know that without asking eludes me. If you’re hiring for a position, you have a responsibility to know.
  - mr_toad 3y ago
    You know that the big clouds (and to a lesser extent the smaller ones) have more in common than they are different? They use different jargon, they love to market themselves on their differences (because why compete on price?), but the fundamentals are really very similar and the skills transfer. Anyone who’s telling you that Cloud X is vastly different from Cloud Y is either trying to sell you something, or has gotten their knowledge from someone who was selling them something.
scarface_74 3y ago
I work at AWS Professional Services, people move around among AWS ProServe, Google/GCP, and Microsoft/Azure all of the time. Heck plenty of people come into ProServe with no AWS experience. But they know their areas of specialty well and it only takes a couple of months to use AWS specific services.

Jiocus 3y ago

> it's still technically "cloud" if it's managed servers (wherever they may be). Thank you for this. No more second thoughts about pointing cloud.example.com at our local HPE rack.