Cloud engineer: migrating without anyone noticing
A migration has succeeded when nothing remarkable happens on Monday morning. Everything needed for that happens in the weeks before.
This page describes a role group, not an open position. A role on this site means we speak to people for it continuously and keep our pool up to strength — not that a seat is free today. What is actually open sits on our recruitment portal.
What you do
The work as it looks here, not as it sounds in a job profile.
- Preparing and running migrations to Azure, AWS or Google Cloud, in waves and with a way back that has been tried.
- Building environments and making the management of them handoverable afterwards — preferably in code, so it is repeatable.
- Keeping an eye on the cost. A cloud bill grows quietly and it is your job to see what it grows on.
- Explaining what is about to happen to people who know nothing about it, before it happens.
What you bring
Not a shopping list. This is what actually counts.
- Experience with at least one major cloud provider, and enough awareness of the others to know where they differ.
- Knowledge of identity and rights. In the cloud the login is the perimeter, and that is the part that most often goes wrong.
- The habit of being able to go back. A migration without a tested rollback is a gamble with someone else’s Monday morning.
- An interest in what it costs. A technically successful migration that doubles the bill is not a successful migration.
Where you land
ITproposal was founded in 2019 and works from Amsterdam, Antwerp and Karaman. Some of our people work in our own teams, others are placed with a client. Either way the same holds: you are reachable, you write down what you did, and you explain in plain language what is going on.
On critical services support runs 24/7, on a rota rather than on a private mobile. Working outside office hours happens according to that rota, not because there is nobody else.
What you can expect from us sits on the vacancies page: four steps, no endless rounds, and an answer even when the answer is no.
The work this role sits on is described under Cloud services.
Four steps, no endless rounds
Send your details
Mail your CV and a short note to [email protected]. Name this role group and the region you want to work in.
Introduction
We get in touch for a first conversation, by phone or video. We go through your background, what you are after and the kind of work you are looking for.
Technical conversation
If it matches, you speak to a colleague from the same field. That conversation is about practice: which environments do you know and how do you approach a failure.
Feedback
You hear from us what the next step is. If there is no fitting role right now, we keep your profile and get in touch as soon as that changes.
Questions we get about this
The ones that come up most often before someone gets in touch.
Is there an open vacancy for this role right now?
There may be, but this page does not say so. What is open at the moment sits on our recruitment portal, because that is where it is kept current. This page describes the role group itself: what the work is and what we look for. If nothing is open and the role does fit you, get in touch anyway — we keep your profile and come back to you as soon as something appears.
Will I work only in the cloud, or with on-site equipment too?
Almost never only in the cloud. The estates we take over are nearly always mixed: part sits at a provider, part still sits in a server room, and the join between them is exactly where the interesting problems live. If you want to work purely on one platform and have nothing to do with existing equipment, this fits you less well — and we would rather say that now than after three months.
Will I work at ITproposal or at a client?
Both happen. Some of our people work in our own teams, others are placed with a client, sometimes for a few months and sometimes for years. Which you prefer is something we discuss in the first conversation, because it is a real difference: on placement you see more environments, in an in-house team you build on the same thing for longer.
I cannot do everything listed. Is it worth applying?
Yes. The list above describes the role at its broadest and nobody ticks all of it. What we look at is what you have done, how you approach a problem and whether you can explain what you did. What you do not know yet can be learned; how you deal with people when something is broken is much less so.
The other role groups
If this one does not fit, perhaps one of these does.
Recognise yourself in this?
You do not have to wait for a vacancy to appear. Send your CV and a few lines about what you are looking for.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.