Senior Cloud Engineer
Your mission is to bring senior cloud engineering depth into this programme and help us build infrastructure that is genuinely easier to operate, scale, and reason about — not just infrastructure that works today.
- 32-40
- Senior position
- Hbo/wo
- € 6.000 - 7.000
- Delft
What You’ll Be Doing
At TOPdesk, our SaaS infrastructure is what keeps service management running for thousands of organisations worldwide. As our platform scales and modernises, we are looking for a Senior Cloud Engineer to take ownership of a real piece of that infrastructure and make it faster to change, cheaper to operate, and more resilient by design.
This is not a “keep the lights on” role. Our Azure SaaS estate is stable and battle-tested. You will be here to evolve it — migrating workloads into a modern Cloud Adoption Framework, re-architecting our Kubernetes topology, and building the automation that replaces manual incident response. You will work closely with our CloudOps and SRE teams, and alongside development teams to ship infrastructure changes that affect production for millions of users.
Your mission
TOPdesk’s SaaS platform runs across multiple global datacenters. We are mid-way through a set of transformations to Azure Cloud Adoption Framework landing zones, a re-architecture of our AKS cluster topology, an observability overhaul, and the build-out of AI infrastructure to support new product capabilities.
Your mission is to bring senior cloud engineering depth into this programme and help us build infrastructure that is genuinely easier to operate, scale, and reason about — not just infrastructure that works today.
What you will own
- CAF migration. Migrate workloads into our new Azure Cloud Adoption Framework landing zones. Design reusable Terraform modules, enforce FinOps tagging, and reduce manual administration across environments so development teams can manage their own infrastructure with less bottlenecks.
- Kubernetes re-architecture. We are evolving our Kubernetes platform to improve scalability, resource efficiency, and operational flexibility. You will contribute to cluster topology changes, workload organisation, and networking improvements — keeping downtime as close to zero as our SLAs demand.
- Toil elimination and self-healing automation. You will identify toil, classify it, and engineer it out — and feed your findings directly into our reliability roadmap.
- Observability platform consolidation. Standardise monitoring deployments across all datacenters, close coverage gaps on cloud workloads, and improve infrastructure and database monitoring — with the goal of measurably reducing our alert-to-incident ratio from baseline.
- Global datacenter provisioning. Provision and maintain infrastructure across multiple data centers — from configuring application servers to deploying networking infrastructure in new regions — using our infrastructure-as-code pipeline.
- Data resilience. Implement backup strategies with appropriate retention policies, configure replication for disaster recovery, and validate recovery procedures across all production sites.
- AI infrastructure. Our product squads are rolling out AI-powered features to power our ITSM product. You will provision and operate the cloud AI infrastructure that powers them.
- Runbooks that get used. Every alert links to a runbook; every runbook links to an automation candidate. You leave things more legible than you found them.
PS, we already answered some questions you might have about the role on the bottom of this page, so keep scrolling!
Where will you end up?
This role is based at our Delft head office (minimum 3 days per week). Given the close collaboration with CloudOps, SRE, and multiple product squads, regular co-location is genuinely important.
Are you our new Cloud Engineer?
Qualifications
- Proven hands-on experience as a Cloud or Infrastructure Engineer in a production cloud environment.
- Deep Terraform expertise — you write modules, manage state, and debug provider quirks, not just apply existing code.
- Kubernetes at operator level: Helm, namespace management, ingress controllers, RBAC, persistent volumes.
- Linux system administration — you understand what Puppet or Ansible is doing, not just whether it ran green.
- Experience working within or migrating toward an Azure Cloud Adoption Framework or enterprise landing zone structure is a strong advantage.
- Familiarity with observability tooling at scale — Grafana, Prometheus, VictoriaMetrics, or equivalent.
- Comfortable in an on-call rotation with real SLA obligations and the maturity to know when to escalate.
- Strong written communication — your documentation, runbooks, and architecture notes are unambiguous.
What we look for
This is a structural ownership role. We are looking for someone who thinks in patterns and policy, not just individual incidents — someone who finds “this has always been done this way” more motivating than deterring. You are genuinely curious about the systems you run: not just the happy path but understand the failure modes and mitigation. You document what you learn. You automate what you repeat.
You can hold a strategic conversation with a FinOps stakeholder in the morning and review a Terraform module in the afternoon and enjoy both.
This is what you do it for
The nicest colleagues, a laptop, and a salary that grows with you. That is a no-brainer, of course. But there’s more. Much more. In the Employee Handbook, you’ll discover all of our employment conditions.
10 to Grow
Devote 10% of your working time and a budget equivalent to 10% of your gross annual salary to personal development.
Paid parental leave
Receive your full salary for 9 weeks + 50% of your salary for 17 weeks. Why? Because parenting is hard work.
Volunteering
Simply do it during work time. Did we mention helping people is part of our DNA?
10 to Grow
Devote 10% of your working time and a budget equivalent to 10% of your gross annual salary to personal development.
Paid parental leave
Receive your full salary for 9 weeks + 50% of your salary for 17 weeks. Why? Because parenting is hard work.
Volunteering
Simply do it during work time. Did we mention helping people is part of our DNA?
The job interview process. This is how we do it!
1 You apply
You send your CV and cover letter. Within the week, you'll hear if we're going to meet.
2 Who am I speaking to?
During a phone screening interview, we’ll check if our expectations are aligned. If so, we’ll get together for the first interview.
3 First interview: culture
You'll get to know TOPdesk, and we’ll get to know you! If you have the true TOPdesk spirit, we’ll meet again for a second interview.
4 Second interview: job details
Let’s find out if your experience and skills make you the perfect fit for the job and team.
5 Contract discussion
Everyone excited? Check! Time to draw up a contract and choose your start date.
6 Welcome to TOPdesk!
Once you’ve signed the contract, we’ll arrange everything for your first day. Let the adventure begin!
Got excited?
When reviewing applications, we focus on the signals that matter most: scope, ownership, constraints, and outcome. If you can back these up with metrics — uptime improvements, cost savings, deployment speed, incidents reduced — even better, as they help us understand the real impact of your work. That said, we don’t expect every bullet point to include hard numbers; what matters most is clear evidence of the scale you’ve worked at, the ownership you took, and the judgment you showed. So whether you have precise figures or not, if your experience reflects that, we’d love to hear from you.
Apply now