I'm currently pursuing a master's degree in Cloud Computing and I've been really curious about what the day-to-day responsibilities of cloud engineers actually entail. Do they primarily write code, or are they more often found managing cloud services through interfaces like the AWS Management Console? Do they spend their time optimizing existing systems or creating new infrastructure? I just want to understand what these professionals really do in their jobs.
5 Answers
Daily tasks can really vary. If something's broken, I troubleshoot it; if it’s slow, I optimize it; and if it's outdated, I patch it. Plus, there’s always the challenge of cost management—figuring out why expenses suddenly spike and taking steps to address it. If everything seems fine, I still look for potential improvements. It's a broad mix of responsibilities.
What I see in my job is a broad range of tasks, from setting up meeting discussions about new workloads in the cloud to doing actual architectural work and coding. Day-to-day, I'm often building solutions while keeping security, governance, and cost management at the forefront. It's rarely just about the cloud; it's about implementing solutions that help our business grow.
Anyone dealing with cloud tech knows the struggle with YAML! It seems to be a common theme in our work. Generally, you should be prepared to deal with YAML while setting up your cloud infrastructure.
As a Platform Engineer, I work a lot with AWS and my focus is on creating tools for CI/CD to standardize our software delivery. I also define Infrastructure as Code (IaC) configurations using Terraform, guide teams on AWS deployment best practices, and help automate processes. While AWS is a significant part of my work, it’s not the only aspect. I often find it's more about enabling teams and optimizing modern technologies.
A lot of your time will end up focused on managing costs and optimizing services. It wasn’t as emphasized during my studies, but knowing how to read billing reports and right-sizing resources is crucial. Every cloud engineer seems to juggle coding, deploying infrastructure, and understanding the financial impact of their services.
Do you visually map out the infrastructure, or do you have a mental model of how things tie together?