Hire developers
Hire cloud engineers who can move your systems and keep them running.
A migration with a fixed date, deployments still done by hand, alerts nobody set up. We send vetted cloud and DevOps engineers for AWS or Google Cloud who are available and want the work. You hire them directly, or let us manage them.
When teams bring us this brief
- A move to AWS or Google Cloud that needs more hands before a fixed date
- Releases that depend on one person running scripts late at night
- A team that runs production but has no one who owns monitoring and alerts
What the job covers in practice
Migrations in waves
Move applications one wave at a time, each with a cutover date and a way back.
Pipelines and containers
Build, test and deployment pipelines on GitLab CI, with Docker and Kubernetes.
Monitoring and alerts
Logs, metrics and alerts that warn you before your users notice.
Runbooks
Written procedures, so your own team can run each system after they leave.
Tools this role often works with
- AWS
- Google Cloud
- Docker
- Kubernetes
- GitLab CI
- Linux
How it works
- 01
Tell us who you need
A short brief: the role or skills, when they should start and for how long. A rough idea is enough.
- 02
Get a shortlist
Vetted people who are available and have said they are interested. You see their experience, skills and why we picked them.
- 03
Choose for each person
Hire them directly, or let SDK manage them. Or pass, and we keep looking.
- 04
They start
We introduce you and agree the start date. We stay your contact while they work.
Two ways to work with each person
You decide for each person on your shortlist, so you can mix both on the same team.
Hire directly
They work for you, on your own contract.
- We introduce you and hand them over
- They join your team on your terms
- You manage their work, admin and payments
- Best when you want them for the long run
Let SDK manage them
They work on your project, under our contract.
- They join your project under SDK's contract
- We handle the paperwork, admin and payments
- If it does not work out, we find a replacement
- Best when you want to start fast with no admin
Work our own engineers have delivered
These case studies are our team's track record, not work by the freelancers on your shortlist. Our engineers review every candidate before we propose them.
We worked on the team that moved 600+ Crédit Agricole internal applications from legacy VMs to AWS, and delivered 50+ of those migrations ourselves.
Questions before you hire
Can a cloud engineer join our existing migration program?
Yes. Tell us how the program is organized in your brief. On Crédit Agricole's migration, our own engineers worked as one block inside the program's plan and standards.
AWS or Google Cloud?
Both. Say which one you run, or plan to run, and which services matter most, and we shortlist people with that experience.
What is the difference between a cloud engineer and a DevOps engineer?
The titles overlap. Cloud engineers usually focus on the platform: accounts, networks and migrations. DevOps engineers focus on how code is built, tested and deployed. Many people do both, so describe the problem you need solved.
What happens if the person leaves in the middle of a migration?
If SDK manages them, we find a replacement. If you hired them directly, we can send you new people to consider.
What to put in your brief
A rough idea is enough to start. These details help us send the right people.
- Where you run today and where you are moving, if anywhere
- How you deploy now, and what hurts most
- Whether they join an existing migration or platform team
Tell us who you need.
A short brief takes about two minutes. We reply by email with the next step.