How to become a cloud engineer (with no prior experience)

So, you’re thinking about starting a career as a cloud engineer? You’ll certainly be in demand! 70% of organizations have the majority of their infrastructure in the cloud, but they’ve got a serious shortage of in-house talent to manage it, according to Pluralsight’s State of Cloud report. Naturally, that puts you in a great position to fill that demand as a must-have employee.

But aside from pay and demand, cloud is also just a really fun and interesting field. Cloud computing underpins nearly everything—cybersecurity, AI, data management, software development, IT ops—which means it’s rarely boring. And the cloud community is very friendly, with tons of industry events and associations to join. Once you’re in, there’s a sense of belonging that’s not quite like any other field in tech.

As someone with presumably zero experience, you might be standing on the ground and staring up at your cloudy aspirations, wondering how you close that gap. I’m here to tell you that it’s entirely possible. In this article, I’ll cover how to get your foot in the door, as well as many other questions you might have: what exactly does being a cloud engineer involve, how to prepare for an interview, and more. 

Let’s start with the real basics: What exactly is the cloud, anyway? After all, you can’t understand what the job is without grasping what you’d be working with—that would be like wanting to be a jockey without having met a horse.

• What are cloud computing systems?
• What is a cloud engineer, and what do they do?
• How hard is it to become a cloud engineer?
• How much do cloud engineers make?
• Are cloud engineers in demand?
• Do I need a degree to become a cloud engineer?
• What methods can I use to become a cloud engineer?
• Do cloud engineers need to know how to code?
• What skills are needed for a job as a cloud engineer?
• Is a cloud engineer the same thing as a cloud specialist or architect?
• Can you switch from development to cloud computing?
• What certifications or qualifications can I get to become a cloud practitioner?
• Should I specialize in AWS, Azure, GCP, or something else?
• What should I highlight in my resume or during interviews?
• How do I prepare for an interview for a cloud engineer role?
• Is thirty or forty too old to start a career as a cloud engineer?

Cloud computing provides internet-based hardware and software resources, letting you rent servers and other resources from providers like AWS, Azure, and Google Cloud. This allows you to use powerful computing, storage, and databases without managing physical hardware.

Put simply, imagine you took everything in your office—all the computers, software, and files—and just moved it into a secure, virtual box on the internet, which you could access at any time. This is really helpful, because suddenly you don’t have to worry about buying, maintaining and patching servers and physical hardware. It’s suddenly someone else’s problem, and this is a big reason cloud computing is now so universally popular.

This is a really high-level explanation, and I’d highly recommend watching Ed Freitas’s free “Cloud Computing Fundamentals” course for more details. The deeper your understanding of the cloud, the more of a feel you’ll get for if it’s the right career for you. To return to our jockey metaphor, think of it as spending some time in a stable and getting riding lessons. 

A cloud engineer designs, implements, and manages cloud-enabled systems. They ensure everything runs smoothly in the cloud using the services offered by cloud providers to design, implement, and manage all the virtual resources within your cloud environment. 

Remember how I mentioned cloud touches practically every domain of computing, from AI to software development? To support these, cloud providers offer hundreds of services across different categories. It’s impossible to know all of them in depth, but cloud engineers are familiar with the main ones at a high level, as well as having a chosen area of expertise. 

If you don’t believe me about there being a smorgasbord of services, as of mid-2024, here's an approximate number of services offered by the major cloud providers:

• Amazon Web Services (AWS): Over 200 services.
• Microsoft Azure: Over 200 services.
• Google Cloud (GC): Over 100 services.

As an engineer, your focus will be on a smaller portion of popular services. Specifically, those involved with designing cloud architecture, deploying, managing, monitoring and optimizing virtual resources, managing security, automatings workflows, and troubleshooting and providing support. 

Since that still might sound like a lot to unpack, let’s break it down even further:

• Designing Cloud Architectures (Planning): As a cloud engineer, you’ll need to figure out the best way to organize and set up this virtual space to fit the business needs.
  
• Deploying and Managing Resources (Setting Up): You’ll configure everything in place online, like creating virtual computers and storage spaces.
  
• Monitoring and Optimizing Resources (Maintaining Smooth Operations): You’ll ensure that everything works well, as fast as possible within the assigned budget.
• Security Management: You’ll need to protect this online space from hackers and keep data safe.
• Automating Workflows: You’ll work on creating tools to make the management of this online space easier and more efficient.
  
• Troubleshooting and Support: You’ll resolve any issues that come up and help users with any difficulties within the cloud environments.

A day in the life of a cloud engineer

Prior to working at Pluralsight as an AWS Training Architect, I worked as a cloud engineer slash solutions architect in a large enterprise. We would break our work into clear, manageable chunks, and then tackle them in iterative cycles known as springs, each spanning two weeks.

Each sprint kicked off with planning sessions where we chose tasks to tackle (called “customer stories”) and finished with a review of our progress. This kept our projects well organized, on track, and made sure we met our goals. Here’s a snapshot of what my daily routine looked like:

Early morning:

• Start the day: I’d begin with a quick check of configured alerts to ensure all cloud services were running smoothly and address any immediate issues.
  
• Beginning of day handover: Working with a “Follow the Sun” model across three time zones, I’d communicate with my Hyderabad teammates to pick up where they left off.
• Daily stand-up meeting: I joined a brief scrum meeting to discuss our assigned tasks (stories) and any issues needing collaboration or escalation.
• Troubleshooting: Address any alerts or issues identified earlier.
  

Mid morning:

• Assigned Stories: I’d prioritize and tackle tasks such as:
  
  • Setting up new data pipelines for ingestion.
  • Migrating databases from on-prem to the cloud.
  • Writing Python scripts or configuring automation tools for routine tasks.
  • Configuring databases and setting up automated backups.

Afternoon:

• Scrum Meetings: Depending on the sprint’s stage, I might attend meetings to end the current sprint and plan the next one.

End of day:

• Review: Document the day’s accomplishments.
• End of Day Handover: I’d hand over my work to the Australia team, who would then pass it to Hyderabad. On days with large migrations, like moving petabytes of data to the cloud, I’d monitor alerts to ensure everything was running smoothly and step in if needed.

Challenging, but possible. Becoming a cloud engineer is achievable with the right mindset and resources. However, despite social media’s simplified portrayal, entering cloud engineering demands significant effort and dedication, much like transforming a room takes more than a snap of the fingers.

I’m not saying this to scare you, but to prepare you. Understanding what to expect will help you develop the mindset needed to persevere through the challenges and complexities of this career path. To loop back to our jockey example from earlier, it does nobody any favors if you set your heart on professional horse-racing, and nobody warns you that you need to work out until your weight is below 55 kilograms.

So, why is becoming a cloud engineer tough? It requires a broad skill set. As mentioned earlier, AWS alone has over 200 services. While you don’t need to be familiar with every single service, you’ll need to master several key ones. For instance, when migrating data, you’ll need to be expertise with databases, monitoring, and networking. 

After clearing the hurdle, things get easier

As steep as the learning curve is in the beginning, once you’ve learned a few services—and start having those “Aha!” moments as you use them—the sailing becomes much smoother. Also, compared to other high-paying professions like medicine or traditional engineering, cloud engineering is more accessible. It doesn’t always require a formal degree and can be pursued through various paths, such as certifications and hands-on experience.

So, if you’re considering cloud engineering, it’s definitely doable. You don’t need to spend years in school or follow a strict career path. You can start with online courses and certifications from providers like AWS, Google Cloud, or Microsoft Azure. Just keep in mind that you’ll need to put in consistent effort.

A great success story of getting into cloud computing with no experience is Winston Smith's. He went from phone sales to running a cloud architecture business by studying hard, taking multiple certifications, and getting hands-on practice. To hear about his journey, watch the video below.

The salary of cloud engineers can vary widely based on factors such as location, experience, certifications, and the specific employer. This article “What are the best paying tech jobs to have in 2024?” provides a detailed breakdown of average salaries. 

Absolutely! Most applications you use are powered by the cloud, and eight in ten organizations have adopted it in their organization. This widespread adoption means skilled cloud engineers are needed across all sectors and company sizes to manage and optimize these systems.

While you’ll find cloud roles in retail, healthcare, financial services, and more, one of the highest demands is naturally in the tech industry, particularly in app design. The cloud allows developers to deliver apps at scale, leveraging its scalability, performance, security, and cost-effectiveness.

If you have the passion and willingness to learn, you can find yourself in a rewarding and well-paying job in no time.

No, you don't need a formal degree to become a cloud engineer. While a degree in a related field can be beneficial, many successful cloud engineers have entered the field through alternative paths.

Some effective paths to becoming a cloud engineer include certifications, online courses, bootcamps, hands-on practice, community engagement, and leveraging work experience. 

1. Certifications and Online Courses

Cloud providers such as AWS, Microsoft Azure, and Google Cloud frequently release certifications along with study materials. Platforms like Pluralsight offer specialized courses to help you prepare for and pass these exams. Notable examples include the AWS Certified Cloud Practitioner, Microsoft Certified: Azure Fundamentals, and Cloud Engineer Learning Path.

2. Bootcamps

Intensive coding bootcamps offer a structured path that combines theoretical knowledge with hands-on experience. These programs are designed to equip you with practical skills in a short amount of time, making them an effective way to quickly gain proficiency in cloud engineering. 

3. Hands-On Practice

Setting up your own cloud projects and experimenting with different services can be invaluable. Many cloud providers offer free tiers, allowing you to practice without incurring costs. This enables you to gain practical experience and build confidence in a risk-free environment. 

4. Community Engagement

Participating in forums, joining meetup groups, and engaging with online communities can help you learn from others and stay updated on industry trends. Networking with professionals in the field can also provide mentorship and job opportunities.

5. Leveraging Work Experience

Many companies support employees in setting customized career goals. You can work with your manager to draft a plan that allows you to transition into cloud engineering, utilizing your existing IT or software development experience as a foundation. This approach can help you smoothly shift into a cloud engineering role while leveraging your current skills.

Yes, cloud engineers typically need to learn coding. Unlike a software engineer, your day job won’t involve heavy coding, but you will still need to dive into code to automate certain features or to debug performance issues.

Here are a few examples of common tasks that require coding skills:

• Automation: A significant part of cloud engineering involves automating tasks such as deployment, scaling, and management of cloud resources. You’ll need to know scripting languages such as Python, Bash, or PowerShell to write these automation scripts.
• Infrastructure as Code (IaC): Cloud engineers often use IaC tools such as Terraform, AWS CloudFormation, or Azure Resource Manager to define and manage cloud infrastructure. These tools require you to write code to specify infrastructure configurations.
• Developing Cloud-Based Applications: While you might not be heavily involved in building cloud-native applications from scratch, you’re likely to work on maintaining them. This is where programming languages such as Java, Node.js, or Go can be useful.
• Integration: Cloud engineers frequently need to integrate various services and APIs, which requires coding skills to connect different systems and automate workflows.
• Troubleshooting and Debugging: When issues arise, you’ll need to troubleshoot and debug problems, often diving into the code to find and fix bugs or performance bottlenecks.

So, having a solid foundation in programming will give you a strong advantage in cloud engineering, even if not every task requires heavy coding.

Utterly new to programming? Check out Simon Allardice's beginner-friendly, language-agnostic course on the fundamentals of programming.

Being a cloud engineer requires a wide range of technical and soft skills. You should have knowledge of the core cloud platforms, networking, storage solutions, database management, container virtualization, automation, security, DevOps, monitoring, and performance management. You should develop or have soft skills in project management, communication, problem solving, collaboration, and adaptability.

Technical Skills

1. Cloud Platforms

You want to be proficient with major cloud service providers such as AWS, Microsoft Azure, and Google Cloud Platform (GCP). These days, it helps to be multi cloud proficient, but you can start by mastering the core services of just one of these.

2. Networking

Anyone who’s delved into cloud engineering quickly finds out how much of it is networking. You want to have a strong understanding of networking concepts, including DNS, TCP/IP, VPN, CDN, and firewall management. Make sure you understand how to set up and manage virtual networks in the cloud.

3. Storage Solutions

Cloud engineers should be familiar with the various cloud storage options (e.g., object storage, block storage, file storage) and how to implement and manage them.

4. Database Management

Databases are one of the most crucial elements of an organization—think of all that customer information or transaction records that need to be stored somewhere, and people need to run queries on. As a cloud engineer, you’ll need to know how to set up these databases for people, both relational (e.g., Amazon RDS, Azure SQL Database) and non-relational (e.g., DynamoDB, Cosmos DB).

5. Virtualization and Containers

Cloud engineers need experience with virtualization technologies (e.g., VMware) and containerization tools (e.g., Docker, Kubernetes) for deploying and managing applications.

6. Automation and Scripting

You should be proficient in scripting languages (e.g., Python, Bash) and infrastructure as code (IaC) tools (e.g., Terraform, AWS CloudFormation) to automate cloud resource management.

7. Security

Cloud engineers need knowledge of cloud security best practices, including identity and access management (IAM), encryption, compliance, and monitoring. Familiarity with tools like AWS IAM, Azure AD, and Google Cloud IAM.

8. DevOps

DevOps is not dead, contrary to some people’s belief. As a cloud engineer, you should have an understanding of DevOps practices and tools (e.g., CI/CD pipelines, Jenkins, Git) to facilitate continuous integration and continuous deployment.

9. Operating Systems

You’ll need proficiency with both Linux and Windows operating systems, as cloud environments often use both.

10. Monitoring and Performance Management

You’ll want experience with monitoring tools (e.g., CloudWatch, Azure Monitor, Stackdriver) to track and optimize performance and ensure system reliability.

Soft skills

In tech, your soft skills can matter more than your technical skills, and working in cloud is no different. That’s not to say tech skills aren’t important—they 100% are, especially as a cloud engineer—but you should certainly not neglect or fail to promote your soft skills. 

Cloud engineering is by its nature a role that involves a lot of interaction with people. Iif you have a proven track record in this area, it can make you stand out from other candidates. and be chosen even if they have more technical skills than you. After all, with work and persistence you can learn all about the cloud, but it’s harder to find people who are natural project managers.

1. Project management

Managing projects comes with being a successful cloud engineer. You need to be adept at planning, tracking, and resource management.

2. Communication

You are in charge of the bedrock that makes the company function, and so you need to be able to communicate when the ground is going to shift beneath their feet. Being able to turn off the technical jargon and speak to non-tech people is a must.

3. Problem solving

A significant portion of cloud engineering is problem solving. You’ll sit there debating how to architect the right solution to your customer’s needs, all while weighing up risk, cost, and efficiency. 

4. Collaboration

You need to be able to work with team members, both inside the cloud team and outside of it, to meet a goal or project. 

5. Adaptability

You need to be able to look at all the options and create a plan, and if things change before you can execute it, you need to be able to pivot and adjust. In the face of service changes, outages, and shifting business requirements, a great cloud engineer adapts to it all.

Contrary to popular belief, you don't need to be born with soft skills---you can develop and improve them. To learn how, check out Pluralsight's video learning path for tech professionals: "Developing Soft Skills for Today’s Workplace." This series covers how to improve all of the soft skills listed above.

Not exactly! While cloud engineers, cloud specialists, and cloud architects are related roles, each has its own focus and responsibilities. Think of them as different players on the same team, each with a unique position. To illustrate this, let’s use a movie production analogy:

• Cloud Engineers: Think of them as the crew working on set—like camera operators or sound technicians. They handle the technical aspects of the production, ensuring everything runs smoothly and making adjustments as needed.
• Cloud Specialists: Imagine them as special effects artists. They have a specific area of expertise and work on complex effects or scenes that require detailed knowledge and skill. They tackle specialized problems within their domain.
• Cloud Architects: They’re like the director or producer who plans the entire film. They design the overall vision and structure, making high-level decisions on how all the elements (actors, script, scenes) come together to create the final product.

Absolutely—that’s how I did it! Many skills from my software development background were transferable and highly relevant to cloud computing. Cloud computing often involves writing scripts or code for automation and managing cloud resources, so any experience you’ve got with coding will be beneficial. 

You can make the transition from software engineering to cloud engineering by starting to learn cloud concepts and cloud technologies, getting certified, building practical experience, networking with cloud computing communities, and leverage your development experience.  

1. Understand Cloud Concepts

Familiarize yourself with key cloud concepts like Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and cloud security.

2. Learn Cloud Technologies

Start by learning about cloud platforms like AWS, Azure, or Google Cloud. Many cloud providers offer free resources, tutorials, and certifications.

3. Get Certified

Earning cloud certifications can help demonstrate your knowledge and commitment to potential employers. Certifications like AWS Certified Solutions Architect or Microsoft Azure Fundamentals are good starting points.

4. Build Practical Experience

Work on personal projects or contribute to open-source projects that involve cloud technologies. This hands-on experience will be invaluable.

5. Network and Connect

Join cloud computing communities, attend webinars or conferences, and connect with professionals in the field. Networking can provide insights and opportunities.

For networking advice, especially if you're shy at heart, check out this guide:  "How to network in tech and land jobs (An introvert-friendly guide)."

6. Leverage Your Development Experience

Start by picking tasks that focus on areas like cloud-native application development, DevOps, or cloud automation, where your skills will be highly relevant.

Major cloud providers offer several certifications that are designed to validate your understanding of cloud fundamentals and services. Some key certifications include the AWS Certified Cloud Practitioner, the Microsoft Certified: Azure Fundamentals, and the Google Cloud Digital Leader. 

AWS Certified Cloud Practitioner

The AWS Certified Cloud Practitioner is an entry-level certification that tests your overall understanding of the AWS Cloud. It covers essential concepts such the AWS global infrastructure, core services, security, pricing, and support. 

Microsoft Certified: Azure Fundamentals

The Microsoft Certified: Azure Fundamentals is designed for individuals who are new to cloud services and Microsoft Azure. It covers foundational knowledge of cloud concepts, Azure services, core solutions and management tools, general and network security, governance, privacy, and compliance features. 

Google Cloud Digital Leader

The Google Cloud Digital Leader demonstrates your knowledge of cloud concepts and Google Cloud services. It is intended for those who can articulate the capabilities of Google Cloud core products and services and how they benefit organizations. If you’re interested in pursuing this certification, check out this course. 

There are various ways to select a cloud platform to specialize in. You can compare and contrast the providers, research industry trends to target a specific industry, or explore the types of projects and roles that excite you to determine which platform aligns best with your career interests and goals.

Comparing and contrasting providers

Each provider offers unique features and services tailored to different needs:

• AWS, known for its extensive range of services and market leadership, excels in scalability and flexibility. 
• Azure integrates seamlessly with Microsoft products, making it a strong choice for organizations heavily invested in Microsoft technologies. 
• GCP stands out for its data analytics and machine learning capabilities, leveraging Google's expertise in these areas. 

By evaluating each provider’s strengths, services, and pricing models, you can make an informed decision based on which platform aligns best with your interests and the skills you want to develop. Below is a high-level comparison table of those providers.

Cloud Adoption Industry Trends 

Most industries utilize a mix of cloud services depending on their specific needs, preferences, and historical technology investments. However, although no major industry exclusively uses only one cloud provider, some industries might show a strong preference for one provider due to particular strengths, features, or integration capabilities of that provider. For instance:

• AWS is a popular choice among technology startups, media companies, and enterprises due to its broad service range and early market entry. 
• Azure is favored by enterprises with significant Microsoft technology investments, as well as government and public sector organizations for its hybrid cloud and compliance features. 
• GCP is preferred by industries focused on data analytics, AI, and machine learning for its advanced tools and innovations.

Another approach is to explore the major cloud platforms (AWS, Azure, and GCP) through introductory courses. This will give you a good foundation in each. Thend, depending on your preference, you can either focus on one platform at a time or learn about multiple platforms simultaneously.

When preparing your resume and getting ready for interviews for a cloud engineering position, it's essential to emphasize both your technical expertise and relevant experiences. Here's what you should focus on:

On Your Resume

1. Certifications: Highlight relevant certifications such as AWS Certified Solutions Architect, Microsoft Certified: Azure Administrator, Google Cloud Professional Cloud Architect, etc.
2. Technical Skills: List your technical skills in detail. Specify the scripting languages you’re familiar with (Python, Bash), the Devops tools (Jenkins, Docker, Kubernetes) and any other relevant technologies. 
3. Projects: Detail any work related, personal, or academic projects related to cloud computing. In this section, explain your work, the services  you used, and the outcome. You can also use this section to showcase soft skills such as communication, teamwork, and project management. 
4. Automation and DevOps: Highlight any experience with automating cloud infrastructure using tools like Terraform, Cloudformation, or Ansible.

If you're completely new to tech and not just to cloud computing, check out this course by seasoned cloud specialist and software developer Amber Israelsen: "Careers in IT: How to Get Your First Job."

Here’s a breakdown of topics that will help you demonstrate your technical skills in interviews:

• Discuss the cloud platforms you’re familiar with, the specific services you’ve used, and the underlying principles of cloud computing. For a novice (entry-level) role, you might be asked to describe fundamental services like AWS EC2, Azure VMs, or Google Compute Engine, or storage-related services like AWS S3, Azure Blob Storage, or Google Cloud Storage.
• Go over use cases and architectures. The complexity will depend on the role you’re applying for. For a novice (entry-level) role, you might be asked to discuss basic scenarios such as deploying a static website, setting up a single server, or using a managed database service.
• Troubleshoot hypothetical issues to test your problem-solving skills.
• Provide detailed examples of your past projects, and be ready to walk through your thought process and elaborate on decisions made.
• Research the company ahead of time to learn as much as you can about their cloud platform and application tier.

For more advice on interviewing for tech positions, check out this article: "8 tech interview and resume tips to stand out and get hired."

The rapid pace of technology might make you wonder if starting a career in cloud engineering at thirty or forty is too late, especially if you’ve been out of the workforce for a while. Encountering new terms every other sentence while browsing learning paths can be overwhelming and make you feel lost.

I get it—it's overwhelming! But remember two things: 1) It’s never too late to start. 2) The learning curve, though steep at first, becomes more manageable over time.

Choose a structured learning path on Pluralsight, such as the Cloud Engineer Learning Path, and stick with it. If you find a particular lesson challenging, focus on absorbing what you can, then move on to the next. Repeating this process across different paths will help concepts start to click.

The moments when things finally make sense are incredibly rewarding. Your unique experiences, even if they’re from outside the tech world, will add value to your journey. Whether you’ve been in a non tech field or focused on caregiving or raising children, those life skills can give you an edge in the cloud engineering field. Embrace your past experiences—they’ll enrich your perspective and make you stand out.

Conclusion

If you want to become a cloud engineer with no prior experience, start by earning certifications from major cloud providers like AWS, Azure, or Google Cloud. Take online courses to learn cloud fundamentals, work on hands-on projects to build practical skills, and join cloud tech and engineering communities to network and stay updated. 

You’re on the start of an exciting cloud journey, and I wish you the best with landing your first role as a cloud engineer!

Additional learning resources

If you’re looking for more advice on furthering your tech career, you might benefit from reading the articles below:

• How to get into tech with no experience: 12 tips and tricks
• How to become an AI expert with no experience
• How to get into cybersecurity with no prior experience
• How to become a software developer with no prior experience
• The 10 most in-demand tech skills in 2024 (with skill tests)
• What are the best paying tech jobs to have in 2024?
• 8 tech interview and resume tips to stand out and get hired
• How to network in tech and land jobs (An introvert-friendly guide)

Interested in contributing to the Pluralsight community?

If you’ve got an article you want to write, we want to hear from you! Visit our community contribution page and register your interest.