Recently, my employer had some customers ask them, "can you help us go multi-cloud …to Google Cloud". Up until this year, my employer specialized in helping customers with cloud-adoption, and several customers have expressed interest in "multi-cloud". However, the clouds they were all previously interested in were AWS and Azure. We (as a company) have quite a few people that are rather familiar with AWS (e.g., "me": I've been working on AWS for a few months shy of a full decade). We also have a smaller group Azure practitioners. What we didn't have was people with experience with Google Cloud.
Due to a lapse in a contract — currently in re-negotiation — another engineer and I were between active assignments. As a result, our employer asked us to start getting ourselves spun up, enough, on Google Cloud to be able to get certified. So, we each did. Over the past couple months, I trained up on Google Cloud (thank you, CloudSkillsBoost), and then sat exams for an Associate Cloud Engineer (ACE) certification and then a Professional Cloud Architect (PCA) certification. Even gots the proof of having (successfully) sat those exams:
|
|
That said, the priority of the exercise was getting the certifications. Actually having the skills the certifications were supposed to represent was secondary.
Having significant AWS experience under my belt, studying for the Google certification(s) was mostly an exercise in figuring out the deltas. The actual tests were fairly easy: to use a poor metaphor, "if you know how to use a claw-hammer to drive nails, it's not that hard to figure out how to use a ball-peen hammer to do the same thing".
Now, I'm using my "spare time" to close the knowledge gaps… Expect a bunch of GCP-related posts as I leave myself breadcrumbs on how to do things.
No comments:
Post a Comment