Hire cloud engineers who think about the bill as well as the architecture
Centricone places cloud engineers for migration, architecture, and cost work — screened on identity, networking, and cost reasoning, which is where most cloud problems actually originate.
Screening
What we check that a keyword match does not
Every candidate sits a live assessment with an engineer who does this work. For this role, that conversation covers:
- Identity and access design, the control plane everything else depends on
- Networking: VPC design, connectivity, and the questions that reveal real experience
- Cost reasoning — what they would look at first on an unexplained bill
- Migration judgement: what to rehost, what to re-architect, and what to leave alone
What they do once they are in your team
Landing zone and account structure design
Workload migration in waves with rollback paths
Cost attribution, budgets, and rightsizing
Security posture: least privilege, encryption, and logging
Which level you actually need
Most briefs ask for senior by default. Sometimes that is right; often the work is better served by a mid-level engineer and a clearer specification.
Implements infrastructure against an agreed design, with review on identity and networking decisions.
Owns architecture for a workload or domain, including cost and recovery objectives.
Sets the target architecture and governance for a migration programme.
Questions about hiring cloud engineers
Not sure what you need? Describe the work and we’ll tell you which role fills it.