Cloud Architect Vs Cloud Engineer

A clear distinction between Cloud Engineer and Cloud Architect

Olawale Olaleye
CloudAdventure
2 min readJul 14, 2020

--

Via: Archylounge

In building construction industry, it is easier to identify the roles and responsibilities of an Architect and an Engineer. It is somewhat confusing and abused within the Cloud Technology space. This read gives an insight into the major differences between the key personnel behind a successful cloud infrastructure.

Worthy to note, a cloud engineer uses the same technology as a cloud architect. However, their job focus is different and so are their skills.

Cloud Architect

A cloud architect designs a solution and implements it. He combines both business requirements and technical requirements to deliver successful customer implementations. A critical part of his responsibility is designing and planning.

Core Responsibilities

  • Designing
  • Planning
  • Feasibility
  • Optimization
  • Building
  • Deploying
  • Managing

Cloud Engineer

A cloud engineer primarily operates a solution, monitors it, maintains it, and continuously evolves it as business circumstances change. He is not faced with the requirements of the business. His sole focus on the technical requirements.

Core Responsibilities

  • Building
  • Deploying
  • Managing

Work Scenario Example

A customer has a need to roll out an enterprise application and they’ve clearly established their need for a microservices architecture that is independent of any cloud provider’s infrastructure.

A cloud architect would be saddled with the responsibilities of how to design a Kubernetes cluster to meet this customer’s requirements.

A cloud engineer would run jobs, deployments, or services on the cluster and be more focused on monitoring the cluster, measuring, and maintaining its performance.

Depending on the size of the organization, a cloud architect would find him/herself designing and planning for several projects/tasks. Designs are also subject to improvements and this sometimes leads to redesigning an already implemented architecture.

Another example, when concerned with the scalability of the underlying infrastructure of a company in the event of sudden or planned growth, you can count on a Cloud Architect. When the need is about finding and resolving faults immediately and keeping SLA promises of a business, you can shift attention to a Cloud Engineer.

Progression

Looking at how some organizations are structured, growing from a Cloud Engineer to Cloud Architect may not be a form of progression. In the context of roles and responsibilities, adding design and planning skills to existing skills improves one’s competence.

--

--

Olawale Olaleye
CloudAdventure

DevOps Pro | Cloud Solutions Architect | MultiCloud Specialist