Cloud Engineer Jobs in Berlin 2026: Application Guide

You want a cloud engineer job in Berlin in 2026, but every listing somehow asks for AWS, Kubernetes, Terraform, security, German, CI/CD, monitoring, and “3 years experience” for a role that still says junior. Annoying, yes. Impossible, no.

Berlin is still one of Europe’s best cities for cloud roles, especially if you’re aiming for AWS, Azure, Google Cloud, platform engineering, DevOps, or infrastructure automation. The trick is knowing what companies actually hire for, what they pay, and how to make your application pass both humans and ATS filters.

Why Berlin Is Still Strong for Cloud Engineer Jobs in 2026#

Berlin’s tech market has cooled compared with the wild hiring years, but cloud skills remain useful because companies still need to ship, scale, secure, and reduce cloud costs.

You’ll find cloud engineer roles across:

1. Fintech
2. Mobility
3. E-commerce
4. Health tech
5. SaaS
6. Cybersecurity
7. AI infrastructure
8. Gaming
9. Logistics
10. Public sector digital projects

Companies in Berlin are not only looking for people to “manage servers.” Most want engineers who can build cloud infrastructure, automate deployments, improve reliability, and help developers move faster without breaking everything.

Typical Berlin companies hiring cloud and DevOps profiles include:

• Zalando
• Delivery Hero
• N26
• Trade Republic
• HelloFresh
• Flix
• SoundCloud
• Contentful
• Miro
• SumUp
• AUTO1 Group
• idealo
• Babbel
• TIER Mobility
• GetYourGuide

You’ll also see cloud roles at consultancies and enterprise tech firms like Accenture, Capgemini, Deloitte, IBM, Microsoft, AWS, Google, SAP, and Deutsche Telekom.

Cloud Engineer Salary in Berlin in 2026#

Let’s talk money, because you should not apply blind.

Cloud engineer salaries in Berlin usually depend on your seniority, cloud provider knowledge, German language ability, and whether the company is a startup, enterprise, or consultancy.

A realistic 2026 salary range looks like this:

For comparison, similar cloud engineering roles in the US often pay much higher:

Berlin pays less than San Francisco, New York, or Seattle, but the cost structure is different, and Germany offers stronger worker protections, public healthcare, paid leave, and notice periods.

That said, Berlin rent is not “cheap” anymore. If you’re relocating, check salary against rent, taxes, and whether the company offers relocation support.

The Cloud Roles You’ll See in Berlin#

Cloud job titles are messy. Two companies can use the same title and mean totally different things.

Here are the common roles and what they usually mean.

1. Cloud Engineer

This is the broadest title.

You might work on:

• AWS, Azure, or Google Cloud infrastructure
• Terraform modules
• Kubernetes clusters
• Networking
• IAM policies
• CI/CD pipelines
• Monitoring and alerts
• Cost optimization
• Incident response

Cloud engineer roles are good if you like variety and want to grow toward senior engineer or cloud architect.

2. DevOps Engineer

In Berlin, DevOps often means “cloud plus CI/CD plus production support.”

You may be expected to:

• Maintain GitHub Actions, GitLab CI, Jenkins, or CircleCI
• Support deployments
• Improve observability
• Manage containers
• Work with developers on release processes
• Automate infrastructure

Some DevOps roles are modern and platform-focused. Others are old-school operations with a new label, so read carefully.

3. Site Reliability Engineer

SRE roles are usually more production-heavy.

Expect work around:

• Reliability targets
• Incident response
• On-call rotations
• SLIs, SLOs, and error budgets
• Monitoring with Prometheus, Grafana, Datadog, or New Relic
• Performance and scaling

If the listing talks a lot about uptime, incident management, and production systems, it is probably SRE work.

4. Platform Engineer

Platform engineering is growing fast in Berlin.

You’ll likely build internal tools and developer platforms, such as:

• Kubernetes platforms
• Internal deployment systems
• Terraform templates
• Golden paths for developers
• Self-service infrastructure
• Developer portals like Backstage

Platform roles are great if you like building systems for other engineers.

5. Cloud Security Engineer

Cloud security roles usually pay well because the risk is high and the talent pool is smaller.

You may work on:

• IAM hardening
• Cloud security posture management
• Secrets management
• Container security
• Threat detection
• Compliance
• Security automation
• Incident response

If you know AWS IAM, Kubernetes security, Terraform scanning, and tools like Wiz, Lacework, Snyk, Trivy, or Prisma Cloud, you can stand out.

Skills Berlin Employers Want in 2026#

You do not need every tool on the planet. You do need a clear core stack.

Most Berlin cloud job postings ask for some mix of the following.

Core Cloud Platforms

Pick one main platform and know it well.

Most common in Berlin:

1. AWS
2. Azure
3. Google Cloud

AWS is still the most common for startups and scaleups like e-commerce, fintech, and SaaS companies. Azure is strong in enterprise, consulting, and Microsoft-heavy environments. Google Cloud appears often in data, AI, and analytics-heavy teams.

For AWS, know:

• EC2
• S3
• IAM
• VPC
• RDS
• ECS or EKS
• Lambda
• CloudWatch
• Route 53
• KMS

For Azure, know:

• Azure Virtual Machines
• Azure Kubernetes Service
• Azure Functions
• Azure DevOps
• Entra ID
• Storage Accounts
• Virtual Network
• Key Vault
• Monitor

For Google Cloud, know:

• Compute Engine
• GKE
• Cloud Run
• IAM
• Cloud Storage
• BigQuery basics
• Cloud Build
• VPC
• Cloud Monitoring

Infrastructure as Code

Terraform is the big one.

Berlin employers love seeing Terraform because it shows you can build repeatable infrastructure instead of clicking around in the cloud console.

Useful tools:

• Terraform
• OpenTofu
• Pulumi
• CloudFormation
• Bicep
• Ansible

If you only learn one, learn Terraform.

Containers and Kubernetes

Kubernetes is still everywhere, but not every cloud engineer needs to be a Kubernetes wizard.

You should understand:

• Docker images
• Kubernetes deployments
• Services and ingress
• ConfigMaps and secrets
• Helm charts
• Resource requests and limits
• Basic troubleshooting
• Logs and events
• Horizontal pod autoscaling

If you can debug a crashing pod, read a Helm values file, and explain what an ingress controller does, you’re already ahead of many applicants.

CI/CD

Most teams want cloud engineers who can improve delivery pipelines.

Common tools:

• GitHub Actions
• GitLab CI
• Jenkins
• CircleCI
• Argo CD
• Flux
• Azure DevOps
• TeamCity

GitOps experience is a plus, especially Argo CD or Flux.

Monitoring and Observability

“Production experience” often means you can see what is happening when things break.

Know the basics of:

• Prometheus
• Grafana
• Datadog
• New Relic
• OpenTelemetry
• ELK or OpenSearch
• CloudWatch
• Azure Monitor
• Google Cloud Monitoring

Be ready to talk about alerts you improved, dashboards you built, or incidents you helped fix.

Security and Compliance

Berlin companies in fintech, health tech, and enterprise SaaS care a lot about security.

Useful security topics:

• IAM least privilege
• Network segmentation
• Secrets management
• Encryption at rest and in transit
• Vulnerability scanning
• Container image scanning
• Audit logging
• GDPR basics
• ISO 27001 basics
• SOC 2 basics

You do not need to be a lawyer, but you should know why public S3 buckets and wildcard IAM permissions make people nervous.

Do You Need German for Cloud Engineer Jobs in Berlin?#

Short answer: not always, but it helps.

Berlin has many English-speaking tech teams. Startups and international companies often use English as the working language, especially in engineering.

You can find English-speaking roles at companies like:

• Zalando
• Delivery Hero
• N26
• Trade Republic
• HelloFresh
• Contentful
• Miro
• SoundCloud
• GetYourGuide
• SumUp

But German helps a lot if you apply to:

• Consultancies
• Banks
• Insurance companies
• Public sector projects
• Mittelstand companies
• Enterprise IT departments

If a job says “German required,” believe it. If it says “German nice to have,” apply anyway if your technical profile is strong.

A realistic language strategy:

1. For English-only roles, make your CV extremely clear and keyword-rich.
2. For German-friendly roles, mention your level honestly, such as “German: B1, improving.”
3. Do not fake fluency, interviews will expose you fast.
4. If relocating, add “currently learning German” to show commitment.

Visa and Relocation Basics for Non-EU Applicants#

If you are not an EU citizen, Berlin can still be realistic, but your application needs to reduce the employer’s fear.

Germany has options like the EU Blue Card for qualified workers. Cloud engineers often meet salary and qualification requirements, especially for mid-level and senior roles.

Employers may ask:

• Are you currently in Germany?
• Do you already have work authorization?
• Do you need visa sponsorship?
• When can you start?
• Do you have a recognized degree or relevant experience?

Make this easy in your CV header or cover letter.

Example:

“Work authorization: Eligible for EU Blue Card, open to relocation to Berlin, available with standard notice period.”

Or, if you already have rights:

“Work authorization: Valid German residence permit, no sponsorship required.”

If you are applying from outside Germany, focus on companies known for relocation support. Larger tech companies and scaleups are usually better at this than tiny startups.

What Berlin Cloud Engineer Job Descriptions Really Mean#

Job ads are full of coded language. Here is how to read them.

“Hands-on experience with AWS and Kubernetes”

They want someone who has worked on real systems, not just watched tutorials.

Your CV should mention:

• Cluster size
• Services managed
• Production workload
• Availability needs
• Tools used
• Business outcome

Weak bullet:

• Worked with Kubernetes and AWS.

Better bullet:

• Managed EKS workloads for 20 microservices, improved deployment reliability by standardizing Helm charts and GitLab CI pipelines.

“Experience with Terraform”

They want infrastructure automation.

Strong CV examples:

• Built reusable Terraform modules for VPC, RDS, IAM, and EKS.
• Migrated manual AWS resources to Terraform, reducing configuration drift.
• Added Terraform validation and plan checks to CI pipeline.

“Strong ownership”

This usually means you will not wait for someone to tell you every small step.

Show examples like:

• Led migration from Jenkins to GitHub Actions.
• Owned production incident review process.
• Created cloud cost dashboard used by engineering managers.
• Reduced failed deployments by improving pipeline checks.

“Comfortable with on-call”

Ask questions.

You need to know:

1. How often is on-call?
2. Is it paid?
3. Are alerts healthy or noisy?
4. Is there a runbook?
5. Do engineers get recovery time after bad incidents?
6. Is on-call 24/7 or business hours?

Do not ignore this. Bad on-call can ruin your life faster than a bad coffee machine.

How to Build a Berlin-Ready Cloud Engineer CV#

Your CV should be easy to scan in 20 seconds. Recruiters and hiring managers are busy, and ATS software is not patient.

Use a simple structure:

1. Header
2. Professional summary
3. Skills
4. Work experience
5. Projects
6. Certifications
7. Education
8. Languages and work authorization

Header

Include:

• Name
• Berlin or “Relocating to Berlin”
• Email
• Phone
• LinkedIn
• GitHub
• Portfolio if useful
• Work authorization status

Example:

“Berlin, Germany | AWS Cloud Engineer | EU Blue Card eligible | github.com/yourname”

Professional Summary

Keep it tight.

Bad summary:

“I am a passionate cloud engineer looking for an exciting opportunity where I can grow and contribute to a dynamic company.”

Better summary:

“Cloud Engineer with 4 years of experience building AWS infrastructure with Terraform, EKS, GitLab CI, and Prometheus. Improved deployment reliability for SaaS platforms, reduced cloud spend by 18%, and supported production systems with on-call rotations. Open to Berlin-based hybrid roles.”

Skills Section

Do not dump every tool you ever touched once.

Group skills like this:

• Cloud: AWS, Azure
• Infrastructure as Code: Terraform, CloudFormation
• Containers: Docker, Kubernetes, Helm
• CI/CD: GitLab CI, GitHub Actions, Argo CD
• Monitoring: Prometheus, Grafana, Datadog
• Security: IAM, KMS, Secrets Manager, Trivy
• Scripting: Python, Bash
• Databases: PostgreSQL, Redis

This helps both ATS systems and humans.

Experience Bullets

Your bullets need tools plus impact.

Use this formula:

Action + tool/system + result

Examples:

• Built Terraform modules for AWS VPC, EKS, RDS, and IAM, reducing new environment setup time from 3 days to 4 hours.
• Migrated 35 services from EC2 to EKS, improving deployment consistency and reducing manual release steps.
• Created Grafana dashboards and Prometheus alerts for payment APIs, cutting mean time to detect incidents by 40%.
• Reduced monthly AWS spend by €12k through rightsizing, S3 lifecycle policies, and unused resource cleanup.
• Implemented GitHub Actions pipelines with security scanning, blocking vulnerable container images before production.

Numbers matter. Even estimates are better than vague claims, as long as they are honest.

Certifications That Help in Berlin#

Certifications are not magic, but they can help you get interviews, especially if you are switching careers or applying internationally.

Useful cloud certifications:

AWS

• AWS Certified Solutions Architect Associate
• AWS Certified Developer Associate
• AWS Certified SysOps Administrator Associate
• AWS Certified DevOps Engineer Professional
• AWS Certified Security Specialty

Azure

• AZ-104 Azure Administrator
• AZ-305 Azure Solutions Architect
• AZ-400 DevOps Engineer Expert
• AZ-500 Azure Security Engineer

Google Cloud

• Associate Cloud Engineer
• Professional Cloud Architect
• Professional Cloud DevOps Engineer
• Professional Cloud Security Engineer

Kubernetes and DevOps

• Certified Kubernetes Administrator
• Certified Kubernetes Application Developer
• Terraform Associate
• Linux Foundation certifications

If you are junior, AWS Solutions Architect Associate plus Terraform Associate can be a strong combo.

If you are mid-level or senior, certifications help less than project depth, but they still add search keywords to your CV.

Portfolio Projects That Actually Impress#

If you lack German work experience or direct cloud job experience, a strong project can help.

Do not build another basic static website and call it a day.

Better project ideas:

1. Production-Style AWS Platform

Build:

• VPC
• EKS or ECS
• RDS
• Load balancer
• CI/CD pipeline
• Terraform
• Monitoring
• Secrets management

Document:

• Architecture diagram
• Security decisions
• Cost estimate
• Deployment steps
• Failure scenarios

2. GitOps Kubernetes Demo

Use:

• Kubernetes
• Argo CD
• Helm
• GitHub Actions
• Prometheus
• Grafana

Show how code changes move from Git to cluster.

3. Cloud Cost Optimization Project

Create a small project that tracks and reduces cloud cost.

Include:

• AWS Cost Explorer screenshots
• Budget alerts
• S3 lifecycle rules
• Rightsizing example
• Terraform code

Companies love people who can save money without breaking production.

4. Secure Cloud Baseline

Build a secure AWS account baseline with:

• IAM roles
• MFA policy
• CloudTrail
• GuardDuty
• KMS
• VPC flow logs
• S3 public access block
• Terraform

Security-aware cloud engineers are valuable.

Where to Find Cloud Engineer Jobs in Berlin#

Do not only apply on LinkedIn and hope.

Use several sources.

Big Job Boards

Check:

• LinkedIn Jobs
• Indeed Germany
• StepStone
• Glassdoor
• Wellfound
• Honeypot
• Arbeitnow
• JOIN
• BerlinStartupJobs

Company Career Pages

Go directly to companies like:

• Zalando
• Delivery Hero
• N26
• Trade Republic
• HelloFresh
• Flix
• SumUp
• Contentful
• Miro
• GetYourGuide
• Babbel
• SoundCloud
• idealo

Company sites sometimes show roles before job boards do.

Recruiters

Specialized tech recruiters can help, but be selective.

Good recruiters will ask about:

• Your stack
• Salary expectations
• Visa status
• Notice period
• Work style
• German level
• On-call comfort

Bad recruiters spam your CV everywhere. Do not let them.

Meetups and Communities

Berlin has active tech communities.

Look for meetups around:

• AWS
• Kubernetes
• DevOps
• Platform engineering
• Security
• Terraform
• SRE
• Cloud Native Computing Foundation

A five-minute chat at a meetup can sometimes beat 50 cold applications.

How to Apply Without Wasting Your Life#

You do not need to send 300 applications. You need better targeting.

Use a 3-tier system.

Tier 1: Dream Fits

These are roles where you match 70% or more and really want the company.

For these:

1. Customize your CV.
2. Write a short cover letter.
3. Message a recruiter or hiring manager.
4. Reference specific tools from the job ad.
5. Apply within the first week if possible.

Tier 2: Good Fits

You match around 50% to 70%.

For these:

1. Adjust your summary and skills.
2. Reorder your bullet points.
3. Apply with a clean CV.
4. Skip long cover letters unless required.

Tier 3: Long Shots

You match less than 50%, but the role looks interesting.

For these:

1. Apply fast.
2. Do not spend an hour customizing.
3. Use them for market testing.
4. Track responses.

If a role asks for 10 tools and you know 6 well, apply. If it asks for German C1 and you only speak A2, probably skip unless the company also says English is fine.

Cover Letter Template for Berlin Cloud Engineer Roles#

Many tech companies do not care much about cover letters, but German companies sometimes do.

Keep it short.

Here is a simple version:

Hi [Name],

I’m applying for the Cloud Engineer role at [Company]. I have [X years] of experience with [AWS/Azure/GCP], Terraform, Kubernetes, and CI/CD, mainly in [SaaS/fintech/e-commerce/etc.].

In my current role, I [specific achievement with number], and I’ve also worked on [second relevant achievement]. Your role stood out because of [specific reason from job ad], especially the focus on [tool, platform, reliability, migration, security].

I’m based in/open to relocating to Berlin, and my work authorization status is [status]. I’d be happy to discuss how my experience fits your team.

Best, [Name]

Do not write a life story. Nobody has time.

Interview Process for Cloud Engineer Jobs in Berlin#

Most Berlin cloud hiring processes look like this:

1. Recruiter screen
2. Technical interview
3. Practical task or system design
4. Team interview
5. Final interview
6. Offer

Some companies do take-home tasks. Some do live coding. Some ask system design questions.

Recruiter Screen

Expect questions like:

• Why are you looking?
• Why Berlin?
• What salary do you expect?
• What is your notice period?
• Do you need visa support?
• Are you okay with hybrid work?
• What cloud platforms do you know?

Have your salary number ready. For mid-level cloud engineers in Berlin, saying €70k to €80k is realistic. For senior, €85k to €105k is common. For lead or architect, €105k+ is reasonable.

Technical Interview

You may be asked about:

• Designing AWS infrastructure
• Debugging Kubernetes issues
• Terraform state
• IAM policies
• CI/CD pipeline failures
• Monitoring strategy
• Networking basics
• Incident response
• Cloud cost reduction

Example question:

“How would you deploy a high-availability web application on AWS?”

A strong answer mentions:

• Multi-AZ setup
• Load balancer
• Auto scaling
• RDS with backups
• Private subnets
• Security groups
• IAM roles
• CI/CD
• Monitoring and alerts
• Terraform
• Rollback plan

Practical Task

Common tasks include:

• Write Terraform for a small AWS setup
• Create a CI/CD pipeline
• Debug a Kubernetes manifest
• Design a monitoring setup
• Review an insecure cloud architecture
• Containerize an app

Do not overbuild. Follow instructions, write clean README notes, and explain tradeoffs.

Questions You Should Ask Before Accepting#

A cloud role can look great on paper and still be chaos inside.

Ask these questions:

1. What cloud providers do you use?
2. How much infrastructure is managed with Terraform or similar tools?
3. How mature is your CI/CD process?
4. What does the on-call rotation look like?
5. Is on-call compensated?
6. What are the biggest reliability problems right now?
7. How are incidents reviewed?
8. How do developers interact with the platform team?
9. What percentage of work is project work versus support?
10. What are the goals for the first six months?

If they cannot answer basic questions about on-call, infrastructure ownership, or priorities, be careful.

Red Flags in Berlin Cloud Job Ads#

Watch out for these.

1. Too Many Jobs in One

If the ad wants cloud engineer, backend developer, security engineer, data engineer, Scrum Master, and office IT support, run slowly but firmly.

2. “Startup Mindset” With Low Pay

Sometimes this means long hours and no process.

Equity is nice, but your landlord wants euros.

3. No Salary Range

Not always bad, but annoying.

If they refuse to discuss salary early, protect your time.

4. “Must Be Available 24/7”

Serious companies have rotations, compensation, escalation, and runbooks.

Chaos companies just call you at 2 a.m.

5. Manual Infrastructure Everywhere

If they have no Terraform, no documentation, and no plan to improve, you may spend months cleaning up old messes.

That can be good experience, but only if the salary and support are right.

Best Strategy for Juniors#

Junior cloud roles in Berlin are competitive because companies often prefer mid-level engineers who can handle production.

If you are junior, focus on proof.

Do this:

1. Get one cloud certification.
2. Build two serious portfolio projects.
3. Learn Linux, networking, Docker, and Terraform basics.
4. Contribute to internal cloud tasks if you already work in IT.
5. Apply to junior DevOps, cloud support, platform trainee, and system engineer roles.
6. Consider consultancies if they offer training.
7. Show GitHub projects with clear READMEs.

Target salary: €45k to €60k.

Do not pretend to be senior. Show that you are reliable, curious, and able to learn without needing babysitting every hour.

Best Strategy for Mid-Level Engineers#

Mid-level cloud engineers have the best market if they can show production experience.

Your CV should prove you have handled:

• Real cloud infrastructure
• Deployment pipelines
• Monitoring
• Incidents
• Team collaboration
• Some security
• Some cost awareness

Target salary: €60k to €80k, sometimes €85k if you match the role very well.

Your best move is to specialize just enough. For example:

• AWS plus Terraform plus EKS
• Azure plus AKS plus Azure DevOps
• Google Cloud plus GKE plus data infrastructure
• Kubernetes plus platform engineering
• Cloud security plus Terraform scanning

Best Strategy for Seniors#

Senior roles in Berlin are about judgment, not just tool lists.

Companies expect you to:

1. Design systems.
2. Make tradeoffs.
3. Mentor others.
4. Improve reliability.
5. Handle incidents calmly.
6. Reduce cloud waste.
7. Work with engineering managers and product teams.
8. Set standards without becoming a blocker.

Target salary: €80k to €105k for senior, €100k to €125k for lead, and up to €140k for architect roles at stronger-paying companies.

Your CV should include business outcomes, not just tasks.

Example:

• Reduced platform incident volume by 35% by redesigning alert rules, creating runbooks, and improving service ownership.
• Led AWS account separation project for 6 product teams, improving security boundaries and deployment autonomy.
• Cut annual cloud spend by €180k through rightsizing, reserved instances, and storage lifecycle policies.

Final Checklist Before You Apply#

Before sending your cloud engineer application in Berlin, check this list:

1. Your CV has AWS, Azure, or Google Cloud keywords.
2. Terraform or IaC experience is visible.
3. Kubernetes or container experience is clear.
4. Your bullets include measurable results.
5. Your work authorization status is easy to find.
6. Your location or relocation plan is clear.
7. Your LinkedIn matches your CV.
8. Your GitHub has clean projects if you are junior or switching.
9. Your salary expectation matches Berlin ranges.
10. Your CV is ATS-friendly, with no weird tables or graphics.

Berlin cloud jobs in 2026 are not “easy mode,” but they are very reachable if your application tells a clear story: you can build cloud systems, automate boring work, keep production stable, and help teams ship safely.

Before you apply, run your CV through JobRise’s free ATS checker so you can catch missing keywords, formatting issues, and weak bullet points before recruiters do. Try it here: https://jobrise.io/en/free-ats-checker/