🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Job Summary We are looking for a DevOps Engineer who is passionate about treating infrastructure as software. Your primary focus will be designing, building, and maintaining automated infrastructure using Terraform. You will be responsible for the "Automation First" strategy, ensuring our cloud environments are scalable, reproducible, and secure through code. This role focuses strictly on provisioning, configuration management, and CI/CD pipelines. Experience Level: 5-8 Years Location: Hyderabad Work Mode: 5 days working from office Key Responsibilities Infrastructure as Code (IaC): Architect and maintain complex infrastructure modules using Terraform to ensure consistent environment setups across Dev, Staging, and Production. Cloud Architecture: Design and deploy scalable, highly available, and fault-tolerant systems on [AWS/Azure/GCP]. CI/CD Pipeline Engineering: Build and optimize automated deployment pipelines (Jenkins, GitLab CI, or GitHub Actions) to streamline the delivery of containerized applications. Containerization: Manage and orchestrate containerized workloads using Docker and Kubernetes (EKS/AKS/GKE). Configuration Management: Utilize tools like Ansible or Packer to automate server configurations and image creation. Security Integration: Implement "Security as Code" by integrating automated vulnerability scanning and IAM policy enforcement within the IaC workflow. Collaboration: Work closely with development teams to "containerize" applications and provide them with self-service infrastructure capabilities. Required Technical Skills IaC Mastery: Expert-level experience with Terraform (HCL), including state management, workspaces, and reusable module development. Cloud Platforms: Strong hands-on experience with [AWS/Azure/GCP] services (VPC, IAM, Compute, RDS, S3). Container Orchestration: Proficiency in Kubernetes and Docker (writing Dockerfiles, managing K8s manifests/Helm charts). Scripting: Advanced proficiency in Python, Bash, or Go for automation tasks. Version Control: Expert knowledge of Git (branching strategies, GitOps workflows). Build Tools: Experience with Maven, Gradle, or similar tools for Java/Node/Python environments. Soft Skills & Mindset Automation-First: A mindset that refuses to perform the same task manually twice. Analytical Thinking: Ability to debug complex networking or deployment issues within a distributed system. Communication: Ability to explain architectural decisions to both technical and non-technical stakeholders. What is NOT required in this role This position does not involve managing or configuring Monitoring/Logging stacks (e.g., Prometheus, Grafana, ELK, Datadog). This is a pure Provisioning and deployment-focused role.
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.