3 ms·

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

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.

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.