Dedicated cloud engineers for your offshore team.
Offshore cloud engineers in Chiang Mai and Bangkok, working full time on your roadmap and managed by us. A cloud engineer designs and runs the infrastructure your product sits on, including keeping the cloud bill under control.
One agreement and one fixed monthly fee, with a service delivery manager in Thailand who runs your team day to day.
This role is part of a dedicated cloud and DevOps team. It's staff augmentation, fully managed: take one role on its own, or the whole discipline as one delivery team.
One Cloud Engineer, assigned to your product and fully managed.
We assign a Cloud Engineer to your team full time and run everything around them: a service delivery manager who answers for the work, training and coaching, the office and equipment, and HR and payroll. The price below is for a mid-level Cloud Engineer; junior and senior levels are priced in your proposal, and how the monthly fee is built explains the arithmetic.
From price
One mid-level Cloud Engineer, full time, everything below included. All 27 things included ››
- Cloud engineer From USD 3,900 per month
-
Service
We manage and develop the team
- A service delivery manager who runs the team and answers for delivery
- A 1:1 with our Head of Delivery every two weeks
- Weekly delivery scoring and monthly capacity reports
- A Talent Success Manager for every specialist
-
HR
We are the employer
- Recruitment and technical assessment
- Employment contracts
- Salary and payroll
- Tax and social security
-
Facilitation
We provide the workplace
- A desk in our own office in Chiang Mai or Bangkok
- A Workplace Experience Manager on site
- Team events through the year
- IT support
-
Equipment
We supply the tools
- Laptop and hardware
- Software licences
- LinkedIn Learning access
- Device security and management
What a Cloud Engineer does on a dedicated cloud and DevOps team.
They work in your AWS, Azure or GCP accounts through infrastructure code, report on cost and risk every month, and agree changes with your engineering lead.
Cloud Engineer skills and technologies
-
Cloud architecture and provisioning across compute, storage, networking and identity.
-
Cost optimisation, with savings tracked and reported month by month.
-
Security posture, IAM policy and network boundaries, reviewed on a schedule.
-
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.
Cloud Engineer seniority levels.
Mid-level to senior. Cloud architecture choices are expensive to undo, so experience pays for itself. Seniority is one of the inputs into how the monthly fee is built.
When your team needs a Cloud Engineer.
Often added around a migration and kept on for ongoing operations, alongside a DevOps or site reliability engineer. Cloud engineers join as part of a dedicated cloud and DevOps team. It suits companies that hire remote developers and want the cloud bill and the architecture owned by someone who stays.
What we look for in a dedicated Cloud Engineer.
We look for cloud engineers who can read an invoice as well as an architecture diagram. They should design IAM from least privilege, test the failover they write about, and use infrastructure as code by default.
A remote Cloud Engineer's first three months on your team.
- Weeks 1 to 2Reviewing your accounts, network and IAM, and producing a cost and risk baseline.
- Weeks 3 to 6Acting on the first cost savings and security gaps, all in code.
- Months 2 to 3Owning the platform, including disaster recovery testing and account structure.
Questions about adding a Cloud Engineer to your team.
Can you reduce our cloud bill?
Usually, yes. A first review often finds savings in idle resources, oversized instances and storage nobody uses any more. The engineer on your team then keeps watching costs as part of the job, with budgets and alerts in place, so the bill stays under control as the product grows.
Do you handle multi-cloud setups?
Yes. We help you decide whether multi-cloud is worth the extra complexity for your product before building for it, because it often isn't. Where it is, for example for regulatory or resilience reasons, the engineer designs for it from the start with infrastructure code that works across providers.
Add remote cloud engineers to your team.
Tell us your roadmap and your stack, and we'll come back with the right profile, the capacity and a start date. You can also talk to a service delivery manager first.
Tell us what your cloud engineer would work on.
Loading the form…
We reply within one business day.