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.

Hiring for one cloud specifically?AWSAzureGCP

Category
AI & Cloud
Roles
4
Screening
By an engineer, with written evidence
Terms
Quoted per role, in writing

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
Worth saying up front

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.