Cloud
We ask candidates to design a secure network and service layout, explain identity boundaries, and make explicit trade-offs between resilience, complexity and cloud cost.
- AWS
- AWS S3
- Azure
- Azure Front Door
- GCP
- Google Cloud
- Vercel
UK, Europe, USA
DevOps and cloud engineer recruitment
Infrastructure recruitment that tests operational judgement across cloud, delivery, security and observability.
Instruct us
Technical screening by developers and CTOs is included.
DevOps and cloud recruitment for production responsibility
We recruit DevOps, platform and cloud engineers across AWS, Azure and Google Cloud environments. Technical screening covers infrastructure as code, container platforms, delivery automation, observability, security and the practical operation of production systems.
When to hire DevOps and cloud engineers: A product team formalising its platform. A cloud migration or infrastructure rebuild. A team improving deployment reliability and observability.
Technologies, requirements and soft skills
We clarify whether the role is primarily platform engineering, cloud architecture, site reliability, deployment automation or hands-on infrastructure support.
Platform and delivery
We probe container behaviour, Terraform state, deployment safety and Kubernetes failure modes with scenarios involving failed rollouts, drift and service discovery.
- Kubernetes
- Docker
- Terraform
- CI/CD
- Serverless functions
Operations
We present an incident signal and ask what they inspect first, which telemetry is missing, how they limit impact and what changes should follow the post-incident review.
- InfoSec
- Sentry
- Datadog
- Grafana
- CloudWatch
Soft skills and working style
Infrastructure engineers must stay composed during incidents, communicate impact and uncertainty clearly, and balance delivery speed with security, reliability and the needs of the developers using the platform.
- Operational ownership
- Calm under pressure
- Risk awareness
- Service mindset
- Clear incident communication
How we assess infrastructure engineers
The interview examines what candidates do when systems change, fail or need to scale, not only whether they recognise a tool.
Cloud architecture
Service selection, networking, security boundaries, cost and resilience trade-offs.
Delivery systems
CI/CD, infrastructure as code, containers and safe deployment practices.
Operational response
Monitoring, incident reasoning, debugging and learning from production failures.
What every candidate needs to demonstrate
Tool names are not enough. Across every role, we look for technical depth, disciplined use of AI and an honest approach to solving unfamiliar problems.
Understands what happens behind the scenes
We keep asking why and how until we reach the underlying behaviour. Candidates should understand what their framework, runtime, database, browser, cloud service or design tool is doing for them, how they work behind the scenes (and why), and how they would investigate a failure without relying on copying fixes from ChatGPT.
Uses AI with engineering discipline
We expect candidates to use AI productively, but never as a substitute for judgement. They need to explain how they verify generated code, designs and tests, protect confidential data, catch unsafe assumptions and remain accountable for the result. We expect them to use MCPs, skills, and goals. So basically - we are looking for structured AI-assisted work, not vibe coding, vibe designing or vibe testing.
Combines initiative with honesty
Strong candidates have a can-do mindset and will investigate, experiment and learn when the answer is not obvious. At the same time, they are fair and transparent about what they know, what they have not done before and when they need support.
Looking to hire?
Give us a few details about the role and your hiring plans. We'll assess your needs and get back to you with a practical next step.
Frequently Asked Questions
Our recruitment experience includes AWS, Azure, GCP and related services such as AWS S3, Azure Front Door, CloudWatch and serverless functions.
Yes. We define the operational ownership and tooling required, then adapt sourcing and assessment to the role.
Yes. Technical screening can cover Kubernetes, Docker, Terraform, CI/CD and the architecture decisions around them.