I Analysed 100+ Cloud Job Descriptions: Here's What I Discovered

[@openupthecloud]

Hey folks, if you're coming to this video in 2022 and beyond, there's now a new version based on 2,000 job descriptions, since I automated the whole process. Here's the link if you want to check it out: kzbin.info/www/bejne/nmO6ZH-Emd5ngK8

[@imuser007]

Thank you so much. These data is really helpful while learning & moving towards cloud engineer job roles

[@sakshammaliksakshammod]

Thank You Lou.

[@openupthecloud]

You're very welcome, Saksham, thanks for stopping by!

[@BadWeatherfreak]

For someone new to cloud with no IT background, what do you suggest to follow to get a job in the cloud within 6 months?

[@openupthecloud]

As a start, go check out: learntocloud.guide cloudresumechallenge.dev You need to start to do your research on what role you want. And what jobs are available in your local area.

[@davidpeterson3535]

As someone who is getting back into system engineering after an entrepreneurial sabbatical, I found this strategy (working backwards from job descriptions) and this video to be helpful. Thank you for your hard work!

[@openupthecloud]

Glad to hear it, David! Best of luck!

[@harinathdharamkar8730]

Thanks Lou! Making Great Contents and information. Can you make something for Data Engineer

[@openupthecloud]

Hey Harinath, I wanted to do this first video just manually, but now that I have the process I do want to automate it and host it somewhere, I could certainly include data engineer profiles in that. 🙏

[@openupthecloud]

Did you find any of the data surprising? Is your learning plan on track? Or are you going to change anything because of the results here? I'd love to know 🤓👇 P.S If anyone wants to help contribute to the spreadsheet, let me know and I can give you access!

[@remoterevolutions4791]

I would speculate that bash was likely the shell that were using with Linux, with scripting connected to it. Did they just list bash or was it connected with coding or scripting?

[@openupthecloud]

So, in this case, I was mostly collecting keywords like "bash" or other programming language mentions to make the groupings easier, so that's a hard one to answer retrospectively. The spreadsheet is linked up in the description if you wanted to play around with it 🙏 You could pull out for instance how many mention any programming language at all, for a high-level view. But yeah...that is one of the limitations, when some employers say "Linux" they may implicitly also mean bash, so some interpretation is required.

[@lukamilicevic712]

Great video

[@openupthecloud]

Thanks ! 🙏

[@engasaleh]

So cool ❤️😎

[@openupthecloud]

Thanks, Abdallah!!

[@denizural5390]

That's great work! Thank you very much! 👏👏👏

[@openupthecloud]

🙏 - glad it was helpful !

[@anirbanmajumdar9506]

Amazing video... looking forward to more such content

[@openupthecloud]

Of course, much more on these types of topics, if you have suggestions / recommendations, let me know !

[@nebolos]

Thanks, Lou. Wish I had this when I started out. I'll be sharing with my community.

[@openupthecloud]

For sure dude! Trying to equip people with the data so they can make the best decisions for themselves 🚀

[@Pavankumar-rt5oc]

May i know how can i access spreadsheet?

[@openupthecloud]

Sure, it's in the description! But here's a link 🙏 docs.google.com/spreadsheets/d/1nnl2uUDvfX1U_1szNwsEMIjjgxcyB_NSyKqQB9wKE0Y/edit#gid=1772949255

[@SounokDeb]

In your research, did work experience played a major role in candidate selection or was hands-on experience enough to land a job as cloud engineer.

[@openupthecloud]

Great question... I didn't see many companies specifying anything about years of experience in the job descriptions. Experience is a tricky one. I did want to measure it, as lots of people ask about it, but I couldn't find a good way to quantitatively measure it, so I didn't gather that data this time. However, from looking at the job descriptions myself, I also didn't see many specifications of years of experience (almost none). In my experience, companies will review experience (somewhat subjectively) in the interview stage, and it's hard to say what companies would be willing to "accept". That said, if you do have low amounts of experience in the technologies requested, building (as complex as you can possibly tolerate) projects of your own can be a substitute for commercial experience. Another "hack" is to do build some projects for friends or family, which can be constituted as "freelancing"... this way you can get some real experience down without going through gatekeepers.

[@openupthecloud]

To answer your question more directly: I've heard many stories of people landing jobs as cloud engineers without commercial experience. I don't think it's easy, but it's certainly possible.

[@remoterevolutions4791]

What I am finding is it is possible to build a portfolio demonstrating skills in cloud areas that can be put up on the web.

[@matteogioioso896]

Certifications are usually need if you are planning to work for AWS partners

[@openupthecloud]

That's very true, Matteo - good point! Yeah, consultancies and other client-facing companies do have a bias for certifications (to show to their own clients, and for keeping up with their partner status).

[@remoterevolutions4791]

I believe having the certs enables the partner to improve their scorecard with AWS.

[@openupthecloud]

@@remoterevolutions4791 Yep! Precisely! 🙏 🚀

[@remoterevolutions4791]

@@openupthecloud and obtaining certifications is one thing I can control, just as targeting work I can do remotely and getting good at it.

[@yashsolanki069]

Great content sir👍

[@openupthecloud]

Thanks, Yash! Much appreciated!

[@ndundirokamau5940]

Very insightful data. Guides one in prioritizing the learning process.

[@openupthecloud]

Glad it was useful to you, Ndundiro!