3 ms·
(I've worked with GCP, AWS, and Azure. And reach hardware. And Rackspace. …) > When looking a job now, it's very common that I'm rejected before TI because I w
by deathanatos 2y ago
(I've worked with GCP, AWS, and Azure. And reach hardware. And Rackspace. …)
> When looking a job now, it's very common that I'm rejected before TI because I wasn't working with AWS. Is it really so fundamentally different from GCP or any other cloud provider for that matter?
It's idiotic to reject someone for this reason. You should be, in the interview, getting at whether the person understands the fundamental aspects underneath the services: do you understand the basics? It'd vary depending on the service, but the basic ideas of a service translates pretty well between clouds. If you've used S3, GCS (GCP) or Blobstore (Azure) are not going to be hard to figure out for you. What's important in a hire is that they're not rigid in their mental model; when you approach a new service, you need to approach it as "vaguely like S3", but not "new service == S3". Each of them have their own quirks, as you note. But "that many to stifle your performance?" … no.
But résumé screeners looking for particular keywords do exist, unfortunately. As someone else in the thread notes, if you're in a conversation with those, and you get "Do you have experience with S3?", you're not obligated to answer the question exactly as it is posed. "I have experience with cloud-based blob-storage systems similar to S3" is a positive answer, but still truthful about the experience, and might very well satisfy the person you're talking to.
While I know all 3 major clouds now (and then some) … for each of those, I obviously could not have known it when I started the job that taught me it. Which is why it's moronic to not hire someone simply for not using that service specifically; that means nobody would ever learn that service, doubly so for costly paid clouds providers like these (this isn't some FOSS DB I can run at home on a laptop and learn). (Or more pointedly, such a company does not want to invest in training employees, and expects other companies to do that, for them, for free, and that's a red flag as to their culture, IMO.)