To hire a cloud engineer, define whether you are migrating, building a new environment, or controlling spend on an existing one, because those are three different candidates. Recruit from cloud user groups and certification communities, screen with an infrastructure-as-code review, run an architecture and cost discussion, then close on scope and autonomy.
Cloud practitioners cluster around vendor ecosystems rather than general engineering boards. AWS, Azure and Google Cloud user groups meet in most large cities, and their organisers know who is looking. Certification study communities are a genuine sourcing channel, since people working through an architect-level certification are often preparing for a move. Consultancy and managed-service-provider alumni are worth targeting: they have seen dozens of environments instead of one, which is exactly what a migration needs. Look at people writing publicly about Terraform modules, landing zones or cost reduction. Include the cloud provider by name in your outreach and posting, because that keyword drives their search. Building precise search strings with a [boolean search string generator](/tools/boolean-search-string-generator) sharpens sourcing when the title varies between infrastructure, platform and cloud engineer.
Name the cloud provider, the current state of the environment, and the project driving the hire. "Migrate forty legacy services from a data centre to AWS" and "harden and cost-optimise an existing Azure estate" attract different people with different strengths. Say whether infrastructure is already defined in code or the first job is dragging it out of the console. Be honest about how much manual toil exists, because pretending otherwise leads to a resignation in month four. State how much authority the role carries over architecture decisions and spend. Mention compliance obligations if they shape the work. Certifications belong in the nice-to-have list, not the requirements. Our [cloud engineer job description](/job-descriptions/cloud-engineer) separates provisioning work from reliability work so applicants self-select correctly.
Certifications prove study, not judgement. Screen instead with a small infrastructure-as-code review: give them a Terraform or Bicep module containing an over-permissive role, a hardcoded secret, no state locking and a resource that will be recreated on every apply. Ask what they would change and why. The order in which they raise issues tells you where their instincts sit. Follow with a cost question, since cloud spend is where most companies feel infrastructure decisions: ask how they would find and reduce the largest line item in a bill they have never seen. Strong candidates ask about tagging, commitment discounts and idle resources before suggesting instance downsizing. Structured evaluation matters when applications are heavy with vendor keywords, so score everyone against the same criteria in your [applicant tracking features](/ats-features).
Run a scoping call, the infrastructure-as-code review, an architecture whiteboard, and a stakeholder conversation. In the whiteboard round, describe a real system and ask them to design its network, identity and deployment topology out loud, including what they would deliberately not build yet. Push on identity and access management, because that is where cloud mistakes become breaches. Ask how they would roll back a change that took production down and what guardrails prevent it happening twice. The stakeholder round should involve whoever owns the budget, since cloud engineers work with finance more than most engineering roles. Adapt the technical questions from our [cloud engineer interview questions](/interview-questions/cloud-engineer) and keep the same scorecard for every candidate.
This is a candidate-short market in most regions, and experienced cloud engineers receive regular approaches, so plan a longer search and a shorter decision window than usual. Remote hiring widens the pool considerably, since the work rarely requires a physical presence. Be careful with title inflation: many applicants have console-clicking experience rather than infrastructure-as-code depth, so volume of applications is not the same as pipeline quality. What closes them is scope. Cloud engineers leave when they are ticket-takers and stay when they own the platform, choose tooling and see their cost work recognised. Comparing your offer response rates and drop-off against a wider [talent acquisition](/talent-acquisition) plan will show whether the gap is pay, scope or process speed.
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
