--- title: "Cloud Engineer | Managed DevOps Team | Azendo" description: "Assign a Cloud Engineer to your roadmap under one monthly agreement, working from Thailand with an Azendo service delivery manager accountable for delivery." url: "https://azendo.co/services/cloud-and-devops/cloud-engineer/" --- [← Cloud and DevOps](https://azendo.co/services/cloud-and-devops/) # Cloud Engineer assigned to your roadmap. A Cloud Engineer designs and runs the infrastructure your product sits on, including the cost line that grows quietly until someone owns it. Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe. [Contact us](https://azendo.co/get-in-touch/) [See pricing](https://azendo.co/pricing/) Part of our service line [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/) This role is delivered as part of our cloud and DevOps services. Take the role on its own, or the whole discipline as one delivery team. ## What a Cloud Engineer does on a managed DevOps team. Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's. ### Cloud Engineer skills and technology we assign for * [AWS](https://azendo.co/skills/aws/) * [Azure](https://azendo.co/skills/azure/) * [GCP](https://azendo.co/skills/gcp/) * [Terraform](https://azendo.co/skills/terraform/) * [CloudFormation](https://azendo.co/skills/cloudformation/) * [Pulumi](https://azendo.co/skills/pulumi/) * [VPC and networking](https://azendo.co/skills/vpc-and-networking/) * [IAM](https://azendo.co/skills/iam/) * [S3](https://azendo.co/skills/s3/) * [RDS](https://azendo.co/skills/rds/) * [Lambda](https://azendo.co/skills/lambda/) * [EKS](https://azendo.co/skills/eks/) * [CloudWatch](https://azendo.co/skills/cloudwatch/) * [cost management tooling](https://azendo.co/skills/cost-management-tooling/) * Cloud architecture and provisioning across compute, storage, networking and identity. * Cost optimisation, which usually finds more savings in the first month than the role costs. * Security posture, IAM policy and network boundaries, reviewed rather than assumed. * Disaster recovery planning and testing the failover rather than documenting it. * Tagging and account structure so cost can be attributed to a team or product. ## Seniority levels we assign. Mid to senior. Cloud architecture mistakes are expensive and slow to unwind. Seniority is one of the inputs in [how the monthly fee is built](https://azendo.co/pricing/). ## When a Cloud Engineer is the right assignment. Often assigned around a migration, then retained for ongoing operations. On an ongoing roadmap this role is most often assigned alongside a DevOps Engineer or a Site Reliability Engineer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. At Azendo this sits inside [DevOps managed services](https://azendo.co/services/cloud-and-devops/), on the same agreement as the rest of the team. 160 h Typical monthly capacity for this role Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours ## Other roles in cloud and DevOps. [DevOps Engineer Cloud and DevOps role](https://azendo.co/services/cloud-and-devops/devops-engineer/)[Site Reliability Engineer Cloud and DevOps role](https://azendo.co/services/cloud-and-devops/site-reliability-engineer/)[Platform Engineer Cloud and DevOps role](https://azendo.co/services/cloud-and-devops/platform-engineer/) The same delivery team, on your product, month after month. Chiang Mai and Bangkok, Thailand — five hours ahead of Northern Europe ## Questions about assigning a Cloud Engineer. Can you reduce our cloud bill? Usually, and the first review typically finds more than the capacity costs. We will tell you before starting if we do not think there is much there. Do you handle multi-cloud setups? Yes, though we will normally advise against adopting one unless there is a concrete reason beyond avoiding lock-in. ## Add cloud engineer capacity to your roadmap. Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can [talk to a service delivery manager](https://azendo.co/get-in-touch/) first. [Contact us](https://azendo.co/get-in-touch/) [How it works](https://azendo.co/how-it-works/) ## Assign a Cloud Engineer to your roadmap.