You want to hire a cloud engineer, but how do you know whether someone is really good? The market is full of profiles that look strong on paper, while the practice disappoints. What do you look for to bring in the right one, and not the most expensive or the smoothest talker?
In this article you will learn what to look for when hiring a cloud engineer: which skills and certifications matter, how much experience you need, and how to arrange the Dutch DBA Act well. That way you choose on quality, not on feeling.
This blog is for clients: IT managers and hiring managers seeking a freelance cloud engineer and wanting to choose the right one.
This article is about selecting, not about prices. If you want to know what a cloud engineer costs, read our blog on cloud engineer rates. Here I focus on how you assess whether someone is the right one.
Which technical skills does a good cloud engineer have?
That depends on your platform and your assignment, but there is a core. A strong cloud engineer masters at least one major cloud platform in depth, can set up infrastructure as code, and understands networking, security and automation. Generalists without depth often fall short on complex assignments.
More important than a long list of tools is the depth per component. Someone who really masters one platform is more valuable than someone who knows a bit of everything. So determine in advance which specific expertise your assignment requires, and test for that. A sharp profile is half the work.
Which cloud platform should someone master?
The platform you use or are going to use. The major platforms differ enough that in-depth experience with one is not automatically transferable to another. If you seek someone for a specific platform, test for demonstrable experience with it, not for general cloud knowledge. For a migration, experience with multiple platforms can be valuable.
Which certifications are relevant?
Certifications from the major cloud providers are a useful indication, especially at architect and professional level. They show that someone masters the material and keeps up. But a certificate is no guarantee of practical experience; see it as supporting evidence, not as decisive.
Weigh certifications together with demonstrable project experience. Someone with a relevant certificate and experience in comparable assignments is stronger than someone with only paper or only experience. Probe on what someone with a certification has actually done in practice. That distinguishes the doer from the theorist.
How much experience do you need?
That depends on the complexity of your assignment. For a critical, complex environment you want a senior who makes choices independently and sees pitfalls in advance. For defined, clear work, a medior can be perfectly sufficient, at a lower rate. Match the level to the assignment, not the other way around.
Watch not only years, but relevant experience. Someone who has done exactly your type of environment and challenge before is more valuable than someone with more years in a different kind of work. Ask about concrete projects that resemble yours. The more specific the match, the sooner someone is productive.
How do you assess whether someone can really do what they claim?
By probing on concrete experience, not on a list of tools. Have the cloud engineer describe a project that resembles your assignment: which choices did they make, what problems did they run into, what would they do differently now? Those who really did it can explain the trade-offs effortlessly.
Watch whether someone can go into details or stays stuck in generalities. Vague, smooth answers without concrete examples are a signal to be careful. A good intake exposes this difference. Want to know how to conduct that conversation? Read our blog on assessing a freelancer in an intake.
How do you arrange the Dutch DBA Act when hiring a cloud engineer?
Cloud assignments are often long-running and intensive, and precisely then disguised employment lurks. Steer on a defined result, avoid the engineer becoming embedded as a permanent team member, and make sure the practice matches the contract. Since 2025, the Dutch DBA Act is actively enforced.
For a long-running, intensive cloud assignment, the intermediary construction can be the safe route, where the Dutch DBA Act risk is covered while the engineer stays independent. Want to know how the assessment works? Read our guide to the 9 assessment factors of the Dutch DBA Act.
What else should you look for?
Besides technique and compliance, a few things determine whether the collaboration succeeds. The match with your team, the communication, and the availability of the engineer. A technically strong cloud engineer who does not communicate or is barely available still causes hassle.
A few points to weigh:
- Communication: can someone clearly explain complex choices to your team?
- Match: does their way of working fit yours and do they ask good questions?
- Availability: do they have enough time for your assignment, or juggle too much?
- Independence: can they run independently quickly in your environment?
- Continuity: is there a backup if they unexpectedly drop out?
Those who watch these points besides the hard technique prevent an expensive mismatch. A good cloud engineer is not only technically strong, but also fits how you work. That combination makes the difference between an assignment that succeeds and one that disappoints.
Frequently asked questions about hiring a cloud engineer
Which skills are most important in a cloud engineer?
In-depth mastery of at least one major cloud platform, infrastructure as code, and knowledge of networking, security and automation. More important than a long tools list is the depth per component. Determine in advance which specific expertise your assignment requires and test for that in a targeted way.
Are certifications enough to assess someone?
No. Certifications show knowledge and that someone keeps up, but are no proof of practical experience. Weigh them together with demonstrable project experience. Someone with a relevant certificate and experience in comparable assignments is stronger than someone with only paper or only years.
Do I always need a senior cloud engineer?
Not necessarily. For a critical, complex environment you want seniority; for defined, clear work a medior often suffices at a lower rate. Match the level to the complexity of your assignment. Paying for seniority you do not need is a waste.
How do I avoid Dutch DBA Act problems with a cloud engineer?
Steer on a defined result, avoid embedding as a permanent team member, and make sure the practice matches the contract. Cloud assignments are often long-running, so this requires attention. For long-running, intensive assignments, the intermediary construction can cover the risk. If in doubt, consult an employment lawyer.
What if I do not have enough technical knowledge to assess?
Involve a technical colleague, or work with an intermediary who can test and pre-select cloud profiles. You then mainly assess communication, approach and match, while someone with the content knowledge tests the technique. That way you avoid going by a nice story.
Conclusion: choose on quality, not on feeling
Hiring a good cloud engineer is about more than a rate or a nice CV. Watch in-depth platform knowledge, relevant certifications and experience, and probe on concrete projects. Arrange the Dutch DBA Act well, and weigh communication, match and availability. That way you choose on quality.
For whom is this most relevant? For clients who select a cloud engineer themselves and want to choose the right one. For whom less? For those who outsource pre-selection to an intermediary who tests the profiles.
My advice: determine sharply in advance which level and expertise your assignment requires, and test for that in a targeted way. A good match costs some effort up front, but prevents an expensive mismatch and an assignment that disappoints.
Help finding the right cloud engineer?
Want the pre-selection done for you, so you only meet a suitable, tested cloud engineer? Plan a no-obligation call with me. I assess the engineers personally before I propose them.
Note: regulations around the Dutch DBA Act may change. For current information, consult rijksoverheid.nl or belastingdienst.nl.
