Cloud Engineer Jobs in Madrid 2026: Application Guide

You keep seeing “Cloud Engineer, Madrid” on LinkedIn, InfoJobs, and company career pages, but every posting wants AWS, Azure, Kubernetes, Terraform, security, CI/CD, Spanish, English, and somehow 5 years of experience for a “mid-level” role. Annoying, yes. Impossible, no.

Madrid is still one of the strongest tech hiring cities in Spain going into 2026, especially if you want cloud roles tied to banks, telecoms, SaaS companies, consultancies, and EU remote-friendly teams. The trick is knowing what companies actually want, what salary range is realistic, and how to package your CV so you do not get filtered out before a human sees it.

Cloud Engineer Jobs in Madrid in 2026: What the Market Looks Like#

Madrid is not just “Spain’s capital with nice weather.” It is a serious cloud hiring hub.

You have big employers like Amazon Web Services, Microsoft, Google Cloud partners, Accenture, Deloitte, Capgemini, Telefónica, Santander, BBVA, Indra, NTT Data, Minsait, Kyndryl, Oracle, and IBM hiring for cloud-related work.

You also have product and SaaS companies like Cabify, Fever, Typeform, Devo, Clarity AI, Celonis, Datadog, and Revolut hiring cloud, platform, DevOps, and infrastructure engineers across Spain or hybrid in Madrid.

For 2026, cloud engineer hiring in Madrid is likely to stay strong because companies are still dealing with:

1. Cloud migration projects that started years ago and are still messy.
2. Cost optimization after moving too much too fast.
3. Kubernetes and container platform work.
4. Security and compliance requirements.
5. Data platform growth.
6. AI infrastructure needs.
7. Multi-cloud environments, usually AWS plus Azure.
8. Legacy systems that need modern deployment pipelines.

That means “Cloud Engineer” can mean very different things depending on the company.

At one company, you might be building Terraform modules and CI/CD pipelines. At another, you might be managing Azure subscriptions, networking, backups, and IAM. At a bank, you might spend a lot of time on governance, security, audit trails, and approvals.

So before applying everywhere, you need to understand the job types.

Common Cloud Engineer Job Titles in Madrid#

Do not search only for “Cloud Engineer.” You will miss a lot.

Use these job titles when searching on LinkedIn, InfoJobs, Indeed, Tecnoempleo, Welcome to the Jungle, Otta, and company career pages:

1. Cloud Engineer
2. AWS Engineer
3. Azure Cloud Engineer
4. GCP Cloud Engineer
5. DevOps Engineer
6. Platform Engineer
7. Site Reliability Engineer, SRE
8. Infrastructure Engineer
9. Cloud Infrastructure Engineer
10. Cloud Operations Engineer
11. Cloud Consultant
12. Cloud Architect
13. Kubernetes Engineer
14. Terraform Engineer
15. Cloud Security Engineer
16. FinOps Engineer
17. Systems Engineer, Cloud
18. Linux Cloud Engineer
19. Cloud Automation Engineer
20. Cloud Support Engineer

In Madrid, many companies use “DevOps Engineer” when they really mean cloud engineer. Others use “Platform Engineer” when they want someone to build internal developer tooling on top of Kubernetes, GitLab, Jenkins, Argo CD, or AWS.

If you are early in your career, include “Junior DevOps,” “Cloud Support,” and “NOC Cloud” in your searches too.

Salary Expectations for Cloud Engineers in Madrid in 2026#

Let’s talk money, because job posts often say “competitive salary,” which usually means “we would prefer if you guess low.”

Madrid cloud salaries are lower than London, Amsterdam, Munich, or Dublin, but they are often decent compared with Spanish cost of living. International companies and remote-first teams usually pay more than local consultancies.

Typical Madrid cloud engineer salary ranges for 2026 may look like this:

For comparison, similar cloud roles in the US often pay around $95k to $160k, with senior roles at companies like Amazon, Microsoft, Google, Datadog, or Stripe going higher. In Germany or the Netherlands, you may see €70k to €110k for senior cloud roles.

Madrid-based multinational roles can sometimes reach €85k or more, especially if the team reports to another European office. Local outsourcing or consulting roles may sit closer to €35k to €55k.

Your salary depends heavily on:

1. Cloud provider experience, AWS, Azure, or GCP.
2. Terraform and infrastructure as code skills.
3. Kubernetes depth.
4. Security and networking knowledge.
5. English level.
6. Whether the employer is local or international.
7. Whether the job is hybrid, remote Spain, or EU remote.
8. Your ability to show business impact, not just tool names.

Should You Negotiate in Madrid?

Yes, politely.

If the recruiter asks for your expectations, give a range. For example:

“My target range is €55k to €65k depending on the full package, remote policy, on-call expectations, and bonus.”

That sentence does four good things:

1. It gives a realistic range.
2. It shows you understand total compensation.
3. It brings up on-call, which matters a lot in cloud jobs.
4. It gives you room to move.

Ask about meal vouchers, private health insurance, training budget, certification budget, pension, bonus, stock options, home office budget, and on-call pay.

On-call is a big one. If they expect 24/7 rotation, you should know how often and how it is paid.

What Skills Madrid Employers Want in 2026#

Most cloud engineer postings in Madrid are written like wish lists. Do not panic if you do not have every single requirement.

Still, there are patterns. If you want more interviews, build your CV around these skill groups.

1. Cloud Provider Skills

AWS and Azure dominate most Madrid job ads. GCP appears too, especially in data, analytics, and certain SaaS teams, but AWS and Azure are more common.

For AWS, employers often ask for:

1. EC2
2. VPC
3. IAM
4. S3
5. RDS
6. EKS
7. ECS
8. Lambda
9. CloudWatch
10. Route 53
11. CloudFormation or Terraform
12. Security Groups and NACLs
13. AWS Organizations
14. Cost Explorer

For Azure, expect:

1. Azure Virtual Machines
2. Azure Networking
3. Azure Active Directory, now Microsoft Entra ID
4. Azure Kubernetes Service, AKS
5. Azure DevOps
6. Azure Monitor
7. Key Vault
8. Storage Accounts
9. App Service
10. Resource Groups
11. Azure Policy
12. ARM or Bicep
13. Terraform
14. Defender for Cloud

For GCP, useful skills include:

1. Compute Engine
2. Cloud Storage
3. GKE
4. IAM
5. Cloud SQL
6. Cloud Build
7. Cloud Run
8. Pub/Sub
9. VPC
10. BigQuery basics

You do not need to master all three providers. It is better to be strong in one and readable in another.

2. Terraform and Infrastructure as Code

Terraform is one of the most important cloud engineer keywords for Madrid.

If your CV says you “worked with AWS,” that is fine. If it says you “built reusable Terraform modules for AWS VPC, IAM, EKS, and RDS across dev, staging, and production,” that is much better.

Employers want infrastructure as code because it helps with:

1. Repeatable deployments.
2. Change tracking.
3. Code review.
4. Security standards.
5. Faster environment creation.
6. Lower manual error.

Other tools you may see include Pulumi, AWS CDK, CloudFormation, Bicep, and Ansible.

But if you are choosing one thing to learn for Madrid cloud jobs, pick Terraform.

3. Containers and Kubernetes

Kubernetes is not required for every cloud engineer job, but it opens better roles.

In Madrid, Kubernetes appears often in platform engineer, SRE, and DevOps roles. Companies may use EKS, AKS, GKE, OpenShift, Rancher, or self-managed clusters.

You should understand:

1. Pods
2. Deployments
3. Services
4. Ingress
5. ConfigMaps
6. Secrets
7. Helm charts
8. Namespaces
9. RBAC
10. Resource requests and limits
11. Horizontal Pod Autoscaler
12. Troubleshooting with kubectl
13. Logs and events
14. Basic networking

You do not need to pretend you are a Kubernetes wizard. But if you can deploy, troubleshoot, and explain how traffic reaches an app, you are already ahead of many applicants.

4. CI/CD and Automation

Cloud engineering is rarely just clicking buttons in AWS Console.

Madrid employers want engineers who can help teams ship safely and repeatedly. That means CI/CD.

Common tools include:

1. GitHub Actions
2. GitLab CI
3. Jenkins
4. Azure DevOps Pipelines
5. Argo CD
6. CircleCI
7. TeamCity
8. Bitbucket Pipelines

Good CV line:

“Created GitLab CI pipelines to build Docker images, scan dependencies, deploy to Kubernetes via Helm, and reduce manual release steps from 12 to 3.”

Bad CV line:

“Experience with CI/CD.”

See the difference? One sounds like a person who did the work. The other sounds like a keyword dump.

5. Linux, Networking, and Security

This is where many cloud applicants are weak.

You can learn AWS services quickly, but employers love candidates who understand the basics underneath the cloud layer.

Make sure you can talk about:

1. Linux permissions and processes.
2. Systemd services.
3. Logs in /var/log.
4. DNS basics.
5. TCP/IP basics.
6. Firewalls.
7. Load balancers.
8. TLS certificates.
9. CIDR ranges.
10. Private and public subnets.
11. NAT gateways.
12. VPN and peering.
13. IAM least privilege.
14. Secrets management.
15. Vulnerability scanning.

Security is not optional anymore. Even junior cloud engineers should understand why public S3 buckets, wide-open security groups, hardcoded secrets, and admin-level IAM permissions are dangerous.

Spanish and English Requirements#

Here is the honest answer: English is usually more important for technical cloud roles, but Spanish can decide whether you get the offer.

Many Madrid companies work in Spanish day to day, especially consultancies, banks, government-adjacent companies, and local teams. International SaaS companies often work mostly in English.

A rough guide:

1. Local consultancy: Spanish usually required, English nice to have.
2. Bank or insurance company: Spanish often required, English useful.
3. Big tech or international SaaS: English required, Spanish helpful.
4. Remote EU role based in Spain: English required, Spanish often not needed.
5. Client-facing cloud consultant: Spanish and English both important.

If your Spanish is B1 or B2, do not hide it. Put it clearly:

• Spanish: B2, professional working proficiency
• English: C1, daily technical communication

If your Spanish is weak, focus on companies where English is the working language. Search for job posts written in English, not only translated Spanish listings.

Where to Find Cloud Engineer Jobs in Madrid#

Do not rely on one job board. The best roles are spread around.

Use this search plan.

LinkedIn

LinkedIn is still the main place for cloud jobs in Madrid.

Search terms:

1. “Cloud Engineer Madrid”
2. “DevOps Engineer Madrid”
3. “Platform Engineer Madrid”
4. “AWS Engineer Madrid”
5. “Azure Engineer Madrid”
6. “SRE Madrid”
7. “Kubernetes Madrid”
8. “Terraform Madrid”
9. “Cloud Security Engineer Madrid”
10. “FinOps Madrid”

Use filters:

1. Date posted: past week.
2. Location: Madrid, Spain, Remote.
3. Experience level: Associate, Mid-Senior.
4. Job type: Full-time.
5. Workplace type: Hybrid, Remote.

Also check who posted the job. If it is a recruiter, send a short message after applying.

Example:

“Hi Laura, I applied for the Cloud Engineer role in Madrid. I have 4 years with AWS, Terraform, Kubernetes, and GitLab CI, including production EKS support. Happy to share more context if useful.”

Simple. Not desperate. Easy to answer.

InfoJobs and Tecnoempleo

InfoJobs is still big in Spain. Tecnoempleo is more tech-focused and has many Spanish market roles.

These platforms can be useful for consultancies, local companies, and mid-level roles.

Watch out for vague posts from outsourcing firms. Some are fine, but if they do not name the client, tech stack, salary, remote policy, or project details, ask before spending too much time.

Company Career Pages

For stronger applications, go direct.

Check careers pages for:

1. AWS
2. Microsoft
3. Google
4. Oracle
5. IBM
6. Accenture
7. Deloitte
8. Capgemini
9. NTT Data
10. Kyndryl
11. Telefónica
12. Santander
13. BBVA
14. Cabify
15. Fever
16. Devo
17. Clarity AI
18. Celonis
19. Revolut
20. Datadog

Create a simple spreadsheet with:

1. Company
2. Role title
3. Link
4. Salary if listed
5. Tech stack
6. Remote policy
7. Date applied
8. Contact person
9. Follow-up date
10. Status

Yes, it feels boring. It also keeps you from applying to the same role twice and forgetting where you stand.

How to Write a Madrid Cloud Engineer CV That Gets Interviews#

Your CV needs to pass two audiences:

1. ATS software scanning for keywords.
2. A human recruiter or hiring manager skimming in 15 seconds.

So your CV should be clear, boring in structure, and strong in content.

Do not make it pretty at the expense of readability.

Best CV Structure

Use this order:

1. Name and contact details.
2. Professional headline.
3. 3 to 5 line summary.
4. Technical skills.
5. Work experience.
6. Projects, if useful.
7. Certifications.
8. Education.
9. Languages.

Your headline should be specific:

“Cloud Engineer | AWS, Terraform, Kubernetes, GitLab CI | Madrid”

Better than:

“IT Professional Looking for New Opportunities”

That second one tells nobody anything.

Example Cloud Engineer Summary

Use a summary like this:

“Cloud Engineer with 4 years of experience building and supporting AWS infrastructure for SaaS and internal platforms. Strong in Terraform, Docker, Kubernetes, GitLab CI, Linux, monitoring, and incident response. Experienced with production EKS, IAM, VPC design, and cost optimization. Based in Madrid, available for hybrid or remote roles, English C1 and Spanish B2.”

That gives recruiters what they need fast.

Technical Skills Section

Keep it grouped.

Example:

• Cloud: AWS, Azure, EC2, VPC, IAM, S3, RDS, EKS, Lambda, Azure AKS, Azure Monitor
• IaC: Terraform, CloudFormation, Ansible
• Containers: Docker, Kubernetes, Helm
• CI/CD: GitLab CI, GitHub Actions, Jenkins
• Observability: Prometheus, Grafana, CloudWatch, ELK
• Scripting: Python, Bash
• Security: IAM, secrets management, vulnerability scanning, TLS
• Operating Systems: Linux, Ubuntu, Debian, Windows Server

Do not list tools you cannot discuss. If “Kubernetes” is on your CV, expect Kubernetes questions.

Work Experience Bullets That Work

Your bullets should show action, tool, and result.

Use this formula:

“Did X using Y, resulting in Z.”

Examples:

1. “Built Terraform modules for AWS VPC, IAM, RDS, and EKS, reducing environment setup time from 3 days to 4 hours.”
2. “Migrated 12 legacy services from EC2 to Kubernetes on EKS, improving deployment consistency and reducing manual release work.”
3. “Created GitHub Actions pipelines for Docker build, security scan, and deployment to staging and production.”
4. “Improved CloudWatch alerting and Grafana dashboards, reducing mean time to detect incidents by 35%.”
5. “Implemented IAM least-privilege policies and removed unused admin permissions across 40 AWS users.”
6. “Optimized EC2 and RDS usage, saving approximately €4,500 per month in cloud costs.”
7. “Supported production on-call rotation for a platform serving 250k monthly users.”

Numbers matter. Even rough but honest numbers help.

If you do not know exact impact, use scale:

1. Number of servers.
2. Number of AWS accounts.
3. Number of applications.
4. Number of developers supported.
5. Number of deployments per week.
6. Size of cloud bill.
7. Uptime target.
8. Incident volume.

Certifications That Help in Madrid#

Certifications do not replace experience, but they help you get noticed, especially if you are switching into cloud.

Useful certifications for Madrid cloud roles:

AWS Certifications

1. AWS Certified Cloud Practitioner, good for beginners.
2. AWS Certified Solutions Architect Associate, strong choice.
3. AWS Certified Developer Associate, useful for app-focused cloud roles.
4. AWS Certified SysOps Administrator Associate, good for operations.
5. AWS Certified DevOps Engineer Professional, strong for senior roles.
6. AWS Certified Security Specialty, excellent for security roles.

Azure Certifications

1. AZ-900 Azure Fundamentals, beginner.
2. AZ-104 Azure Administrator, very useful.
3. AZ-305 Azure Solutions Architect Expert, senior path.
4. AZ-400 DevOps Engineer Expert, useful for CI/CD and Azure DevOps.
5. SC-900 Security, Compliance, and Identity Fundamentals.
6. AZ-500 Azure Security Engineer Associate.

Kubernetes and DevOps Certifications

1. Certified Kubernetes Administrator, CKA.
2. Certified Kubernetes Application Developer, CKAD.
3. HashiCorp Terraform Associate.
4. Linux Foundation Linux certifications.
5. Google Professional Cloud DevOps Engineer.
6. Google Professional Cloud Architect.

If you are not sure where to start, this path is practical:

1. AWS Solutions Architect Associate or AZ-104.
2. Terraform Associate.
3. CKA if you want platform or SRE roles.

That combination looks good in Madrid and supports real job tasks.

How to Apply Without Wasting Your Life#

You do not need to rewrite your whole CV for every job. You do need to adjust the top third.

That means:

1. Headline.
2. Summary.
3. Skills order.
4. First few bullets.

If the job is AWS-heavy, lead with AWS. If it is Azure-heavy, lead with Azure. If it mentions Kubernetes five times, make sure Kubernetes appears clearly in your summary, skills, and recent experience if true.

The 20-Minute Application Method

For each good role, spend 20 minutes:

1. Read the job post and highlight repeated keywords.
2. Match 8 to 12 keywords in your CV naturally.
3. Adjust your summary to match the role.
4. Move the most relevant skills first.
5. Add one strong project or bullet if needed.
6. Save the CV with a clear file name.
7. Apply.
8. Message the recruiter or hiring manager if visible.

Good file name:

“Carlos_Martin_Cloud_Engineer_AWS_Terraform_Madrid.pdf”

Bad file name:

“CV_final_new_new_2.pdf”

We have all done it. Still bad.

Cover Letter: Do You Need One?#

Sometimes, yes. But keep it short.

Many recruiters will not read a long cover letter. A short note can help if you are changing countries, switching careers, or applying in English to a Spanish company.

Use this structure:

1. Why this role.
2. Why you fit.
3. Your availability.
4. Thanks.

Example:

“Hi team, I’m applying for the Cloud Engineer role in Madrid because the mix of AWS, Terraform, Kubernetes, and production operations matches my recent experience. In my current role, I build Terraform modules, support EKS workloads, and manage CI/CD pipelines with GitLab CI for a SaaS platform. I’m based in Madrid and available for hybrid work. Thanks for reviewing my application.”

That is enough.

Interview Process for Cloud Engineer Roles in Madrid#

Most processes have 3 to 5 steps.

Typical flow:

1. Recruiter call.
2. Technical screen.
3. Technical interview with engineers.
4. Practical task or live exercise.
5. Final interview with manager.
6. Offer.

Consultancies may move faster. Big tech and larger SaaS companies may take longer.

Recruiter Call Questions

Expect:

1. Tell me about yourself.
2. Why are you looking?
3. What cloud platforms do you know?
4. What salary range are you expecting?
5. Are you authorized to work in Spain?
6. Are you open to hybrid in Madrid?
7. What is your notice period?
8. What languages do you speak?

Have short answers ready. Do not ramble for 10 minutes about your whole life.

Technical Questions You May Get

Common questions include:

1. Explain how you would design a highly available web app in AWS.
2. What is the difference between public and private subnets?
3. How does IAM least privilege work?
4. How do you manage secrets in CI/CD?
5. What happens when a Kubernetes pod is in CrashLoopBackOff?
6. How do you troubleshoot high latency?
7. What is the difference between horizontal and vertical scaling?
8. How do you structure Terraform state?
9. How would you reduce a high AWS bill?
10. How do you handle blue-green or rolling deployments?
11. What monitoring and alerting have you built?
12. How do you respond to a production incident?

Answer with real examples. If you only give textbook answers, the interview feels flat.

A good structure is:

1. Situation.
2. What you checked.
3. What you changed.
4. Result.
5. What you learned.

Practical Tasks

You may be asked to:

1. Write Terraform for a basic cloud setup.
2. Create a CI/CD pipeline.
3. Containerize an app with Docker.
4. Troubleshoot Kubernetes YAML.
5. Review an AWS architecture diagram.
6. Propose monitoring for an app.
7. Explain security issues in a sample setup.

Do not chase perfection. Explain your thinking, name tradeoffs, and write clean notes.

If you do not know something, say:

“I have not used that exact service in production, but I would approach it by checking the documentation, testing in a non-production account, reviewing IAM and networking requirements, and adding monitoring before release.”

That sounds professional. Pretending is worse.

How to Stand Out if You Are Junior#

Junior cloud jobs are more competitive because many people are trying to enter cloud.

You can still stand out with proof.

Build 2 or 3 small projects and put them on GitHub.

Good junior projects:

1. Deploy a static website to S3 and CloudFront with Terraform.
2. Build a Dockerized app and deploy it to ECS or Azure App Service.
3. Create a Kubernetes cluster locally with kind and deploy a sample app.
4. Build a GitHub Actions pipeline that tests and deploys.
5. Create monitoring with Prometheus and Grafana.
6. Write a cost report using AWS Cost Explorer.
7. Set up IAM users, roles, and policies with least privilege.
8. Create a small serverless app with Lambda and API Gateway.

Each project should include:

1. README with architecture diagram.
2. Setup instructions.
3. Tools used.
4. Security notes.
5. Cost notes.
6. Screenshots.
7. What you learned.

Hiring managers love candidates who can show work instead of just saying “I am passionate about cloud.”

Visa and Work Authorization Notes#

If you are already an EU citizen or have the right to work in Spain, say it clearly on your CV.

Example:

“Work authorization: EU citizen, eligible to work in Spain.”

Or:

“Work authorization: Valid Spanish work permit.”

If you need sponsorship, be direct but strategic. Some large companies can sponsor, but many local companies will not.

Companies more likely to handle international hiring include Amazon, Microsoft, Google, Oracle, IBM, Accenture, Deloitte, Capgemini, NTT Data, and larger SaaS companies. Smaller local firms may prefer candidates already in Spain.

Remote and Hybrid Expectations in Madrid#

Madrid tech roles are often hybrid now. Common setups:

1. 1 day per week in office.
2. 2 days per week in office.
3. 3 days per week in office.
4. Remote within Spain.
5. Remote within EU.

If the role says “remote,” confirm what that means.

Ask:

1. Can I work from anywhere in Spain?
2. Is there a required office day in Madrid?
3. Can I work temporarily from another EU country?
4. Is the contract Spanish or through an employer of record?
5. Are on-call duties remote?
6. Is equipment provided?

Do not wait until the offer stage to discover “remote” means “remote except Tuesday, Wednesday, and Thursday in Las Tablas.”

Best Application Strategy for 2026#

Here is the simple plan I would use if you were my friend asking in a WhatsApp group.

Week 1: Fix Your Positioning

1. Choose your target: AWS, Azure, DevOps, platform, SRE, or cloud security.
2. Rewrite your CV headline and summary.
3. Add measurable bullets.
4. Clean up your LinkedIn profile.
5. Add Madrid, Spain, or “Open to Madrid hybrid and Spain remote.”
6. List your core tools clearly.

Week 2: Build a Target List

1. Pick 40 companies.
2. Save relevant job posts.
3. Identify recruiters or engineering managers.
4. Apply to 5 to 7 strong matches.
5. Message people after applying.

Week 3: Interview Prep

1. Practice cloud architecture questions.
2. Review Terraform basics.
3. Review Kubernetes troubleshooting.
4. Prepare 5 real stories from your experience.
5. Practice salary answer.
6. Prepare questions about on-call, team setup, and cloud maturity.

Week 4: Improve and Repeat

1. Track response rates.
2. Adjust CV if no replies.
3. Add missing keywords.
4. Continue applying.
5. Follow up after 7 days.
6. Keep learning one skill that appears repeatedly.

If you send 80 generic applications, you may get silence. If you send 25 well-matched applications with a clear CV and recruiter follow-ups, your odds are much better.

Red Flags in Madrid Cloud Job Posts#

Not every job is worth your time.

Be careful when you see:

1. No salary range and vague responsibilities.
2. “Young dynamic team” instead of actual benefits.
3. “Must handle pressure” with no team details.
4. 24/7 on-call with no pay information.
5. Cloud engineer role that is mostly helpdesk.
6. Huge tool list with junior salary.
7. “Remote” but office required several days weekly.
8. No mention of training, documentation, or team structure.
9. Interview process with unpaid production-level project.
10. Contract type unclear.

Ask questions early. Good companies answer clearly.

Questions to Ask Before Accepting an Offer#

Before saying yes, ask:

1. What cloud providers are used in production?
2. How much of the infrastructure is managed with Terraform or similar tools?
3. What does the on-call rotation look like?
4. Is on-call compensated?
5. What are the main projects for the first 6 months?
6. How mature is monitoring and alerting?
7. How are incidents handled?
8. What is the team size?
9. Who owns cloud security?
10. Is there a certification or training budget?
11. What is the remote or hybrid policy in writing?
12. How is performance reviewed?
13. Are salary reviews annual?
14. Is there a bonus or stock package?
15. What equipment is provided?

You are not being difficult. You are making an adult decision about your life.

Final Checklist Before You Apply#

Before applying to a cloud engineer job in Madrid, make sure you have:

1. A clear CV headline with target role and tools.
2. A summary that matches the job.
3. AWS, Azure, or GCP keywords where relevant.
4. Terraform or IaC experience visible.
5. CI/CD tools listed.
6. Kubernetes or Docker included if you know them.
7. Measurable impact in work bullets.
8. Language levels listed.
9. Work authorization listed.
10. Madrid, Spain remote, or relocation preference clear.
11. Clean LinkedIn profile.
12. Salary range prepared.
13. 3 to 5 technical stories ready for interviews.
14. Questions ready for the employer.

Cloud engineer jobs in Madrid in 2026 are very reachable if you stop applying like everyone else. Show the tools, show the impact, speak clearly about your level, and do not let your CV hide the good stuff.

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