🎁 Antes de postularte, practica esta entrevista. Crea tu cuenta gratis en WorkMundi y recibe un Entrenamiento de Entrevista en HelpsYouSpeak — sin costo, sin tarjeta. Quiero mi entrenamiento →
Location: Madrid or Barcelona (Hybrid, 2–3 days/week in office) Employment type: Full-time We're looking for a Cloud Security Engineer to join a fast-growing security team working across AWS, Azure, and GCP. You'll help us stay ahead of cloud-native threats, strengthen our security posture, and build the automation that lets us scale securely. What You'll Do Review and triage cloud security alerts across AWS, Azure, and GCP, focusing effort where risk and business impact are highest Own the fix for cloud security posture gaps - misconfigurations, identity risks, and exposed resources Investigate and respond to live threats, piecing together signals from different data sources Keep an eye on SaaS security health, spotting issues like identity drift or risky third-party access Build out and refine detection logic in our SIEM, and help grow our SOAR automation Partner with engineering and platform teams to roll out security guardrails and drive adoption of best practices Push shift-left security forward by embedding it into IaC and CI/CD pipelines Help the team keep getting better through automation, solid documentation, and sharing what you learn What You Bring Practical experience locking down cloud environments (AWS, Azure, and/or GCP) Solid grasp of how attackers operate in the cloud (credential abuse, lateral movement, exploiting misconfigurations) and how to detect it Time spent with CNAPP/CSPM tooling (Wiz, Prisma Cloud, Lacework, or similar) A track record of owning security incidents start to finish - investigation, containment, and writing it up Comfort building or working within event-driven detection setups and SIEM/SOAR platforms Understanding of microservices and cloud-native architecture, with an eye toward scalability and resilience Real-world experience with Kubernetes, Docker, and the major cloud platforms (AWS, Azure, GCP) Working knowledge of Infrastructure as Code (Terraform, CI/CD, GitOps) and shift-left approaches Some scripting or automation ability (Python or similar) Clear communicator in English, able to translate technical findings for non-security audiences Why This Role 🚀 A team that's going places - continuously growing, working with the latest technologies including AI, and genuinely pushing the boundaries of what a modern team looks like 📚 Invest in yourself - the company invests heavily in learning & development 🏙️ Great offices, real flexibility - hybrid working (2–3 days in office) from Barcelona or Madrid, with a terrace and stunning views 📈 Build your own path - take ownership, show what you've got, and grow within the team and the company on your own terms ❤️ People come first -flexible working, healthcare, parental leave, and genuine wellbeing support 💰 Competitive package + €2k annual compensation + health insurance, a dedicated learning budget, and more perks on top
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.