DevOps, SRE, and Cloud Engineers – Unveiling the Exciting Differences!

Today, we’ll take a thrilling ride through the world of software engineering, exploring three fantastic roles: DevOps Engineer, Site Reliability Engineer (SRE), and Cloud Engineer. Let’s unlock their unique characteristics and discover how they work together:

1️⃣ DevOps Engineer – The Teamwork Champion

DevOps, as we all know it already, promised us agility.

DevOps Engineers bring software development and IT operations together, creating harmony and smooth deployments. They focus on efficiency, collaboration, and communication. Key tasks include:

– Crafting reliable Continuous Integration (CI) and Continuous Delivery (CD) pipelines

– Speeding up infrastructure and application deployment with automation

– Keeping a watchful eye on apps to proactively tackle issues

2️⃣ Site Reliability Engineer (SRE) – The Reliability Expert

The SRE ensures systems are reliable, scalable, and perform at their best. They merge software and systems engineering techniques to achieve stability under pressure. Their responsibilities involve:

– Setting Service Level Objectives (SLOs) and Service Level Indicators (SLIs)

– Finding bottlenecks, increasing system performance, and tackling technical debts

– Proactively resolving potential issues to maintain system reliability

3️⃣ Cloud Engineer – The Cloud Maestro

Cloud Engineers help organizations take full advantage of cloud environments like AWS, Azure, and GCP. They focus on designing, deploying, and managing cloud-based applications and infrastructure. Their key skills include:

– Moving on-premises apps to expansive cloud landscapes

– Building and deploying state-of-the-art cloud-native apps and infrastructure

– Selecting the right cloud resources and services for specific tasks

Platform Engineering

Platform engineering is the practice of building and maintaining processes and systems that support the development, deployment, and operation of software applications.

This includes the tools, processes, and procedures that enable developers to build, test, deploy, and manage the software they build. The core is creating reusable tools and automated self-service actions for developers, that provide for a better developer experience, since actions can be done seamlessly within the development process and better comply with policies, compliance and requirements from the platform side.

Platform engineering is closely related to DevOps, which is the practice of building and maintaining a culture of collaboration between software developers and IT operations professionals. At the center of platform engineering lies the internal developer portal. 

Is devops dead?

‍As DevOps matures and becomes more complex, in software as in infrastructure, developers require easy access to an ever-increasing number of moving parts. Microservices, DevTools, CI, CD, Scripts, Saas, Cloud resources, IaC – this ever growing list and the many tools just listed in CNCF promise a huge cognitive load. Almost everyone in the industry agrees that this cognitive load is reducing developer productivity. 

Answering the question “what is deployed where” and the potential relations and dependencies that are explicit and implicit is becoming more difficult. 

From the devops point of view, serving developers has become too complex and overly reliant on “Ticket Ops”.

  • Developers flood devops with multiple tickets for one overall activity – for instance, scaffolding a microservice
  • Devops automations still require developers to make choices and increase the cognitive load as well as the chances of an error; gitops approaches work only partially
  • Temporary environments stay on forever and become orphaned
  • It becomes nearly impossible to track migrations, versions and perform audits.‍


In conclusion, each of these roles is unique but interconnected, empowering organizations to create strong and efficient systems.

Stay tuned for more eye-opening DevOps Tips & Tricks!


Blog Cuong Nguyen

Leave a Reply

Your email address will not be published. Required fields are marked *