> Markdown version of [/jobs/ext/4496891-cloud-engineer](https://www.wearedevelopers.com/jobs/ext/4496891-cloud-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Cloud Engineer

- **Company:** Rabot Energy
- **Location:** Hamburg, Germany
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** .NET Framework, Artificial Intelligence, Microsoft Azure, Bash Shell, Cloud Computing, Cloud Engineering, Continuous Integration, DevOps, Python (Programming Language), Windows PowerShell, Datadog, Git Flow, Kubernetes, Azure AKS
- **Published:** November 1, 2026
- **Apply:** https://startup.jobs/cloud-engineer-m-f-d-rabot-energy-10636503

## About the Role

* Platform engineer: You bring 3+ years in Platform, DevOps or SRE, run Kubernetes in production and are at home in a public cloud, ideally Azure.
 * Automation-first: Infrastructure as Code, CI/CD pipelines and scripting (Python, Bash or PowerShell) are second nature. You automate what matters instead of operating by hand.
 * Builder for growth: You build the platform for scale, not just keep it running, and you create self-service that product teams actually adopt.
 * Partner and communicator: You work as a partner to product teams and explain trade-offs clearly.
 * Owner: You take a problem from idea to production and keep things pragmatic and simple.
 * Language: Confident English, which is our working language.

## Description

You build and scale the foundation every RABOT product runs on: our cloud infrastructure (Azure, Kubernetes), CI/CD, GitOps deployments and monitoring.

Your focus is leverage, not toil. You find the most painful manual work and automate it, and you build self-service capabilities that product teams actually use, so they can handle common infrastructure tasks themselves. As we grow, you keep the platform stable, scalable and fast, without the operational work growing with it. You take problems from idea to production, keep things simple and explain your trade-offs clearly.

Your Results

We think in outcomes, not task lists. If you are successful, here is what that looks like:

Month 3 (ramp-up)

 * You know our platform and ship changes independently.
 * You have identified the most painful manual tasks and the best candidates for automation and self-service, and agreed priorities with the team.

Month 6 (performance)

 * You have built the first automations and self-service capabilities from that list.
 * The operational work for the team has measurably dropped.

Month 12 (scale)

 * Product teams handle common infrastructure tasks themselves through self-service.
 * The platform scales with our growth without the operational work growing with it., Nice to have: Azure Kubernetes Service (AKS), GitOps / ArgoCD, Azure DevOps, observability (for example Datadog), security and compliance in regulated environments, supporting .NET or Python services, AI tools in your daily work, and experience building internal developer platforms (IDP / self-service)., * Room to shape: You build the platform for growth, not just run it, with the freedom to automate and simplify.
 * Stack: Azure, Kubernetes, CI/CD, GitOps and modern observability, with AI tools as part of how we work.
 * Culture: Transparent collaboration. We celebrate mistakes as long as we learn from them.