Hire developers · AI & Cloud
AI & Cloud
Hire cloud engineers
The engineer who owns what your software runs on — networks, identity, deployment and the pager. The screen is about what they have operated, not which cloud is on the CV.
What they are hired to build
The work, before the CV.
A role written against the work gets a better shortlist than a role written against a stack. These are what Cloud engineer engineers are usually brought in to do.
Roles we recruit: Cloud engineer · Senior cloud / DevOps engineer · Platform engineer · Site reliability engineer.
- Landing zones, account structure and identity design
- Containers and serverless, from build pipeline to production
- Cost work: rightsizing, committed spend and finding the waste
- Migrations between clouds, or off a data centre
- On-call: alerting that means something, and runbooks that are used
The technical screen
What the conversation actually covers.
Every candidate has a real technical conversation with an engineer who has done the job, and you get written evidence per competency. In Cloud engineer, that conversation covers the following.
Usually assessed alongside: Terraform, Kubernetes, Linux and networking, CI/CD.
- Identity and least privilege as practised, not as copied from a policy
- Networking — the outage they caused or fixed, and what it taught them
- Infrastructure as code, and honestly what is still clicked by hand
- A real incident end to end: what broke, what they saw, what changed after
- Where the money goes, and a cut they have actually made
Certifications are not evidence. We screen on what a candidate has operated and broken, and we will pass over a certified candidate who has only ever worked in a sandbox.
Three ways to bring one on
The route changes; the screening does not.
The same three routes apply whichever stack you are hiring for. Which one fits depends on how long you need the person and whether the headcount is approved.
Permanent placement
Companies hiring engineering and data roles
One fee on joining, with a 90-day replacement guarantee.
- Typical timeline
- 3–8 weeks to offer
Contract staffing & staff augmentation
Companies with budget but no headcount
We employ them, you direct them. Monthly, for when the need is real but headcount is not approved.
- Typical timeline
- Monthly, 3-month minimum
Contract to hire
Companies hiring into a new or unclear role
Three to six months as a contractor, then convert. The honest option when neither side is sure.
- Typical timeline
- 3–6 months to conversion
Or have us build it instead
If the need is the work, not the headcount.
Cloud & DevOps
Cloud migration
On-premise to AWS, Azure or Google Cloud, sequenced by risk rather than by ease.
Cloud & DevOps
Cloud cost optimisation (FinOps)
Priced as a share of the savings, so the engagement pays for itself or it does not bill.
Cloud & DevOps
Kubernetes & container platform
Platform engineering for teams that have outgrown running containers by hand.