🎁 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 →
Project Role : DevOps Engineer Project Role Description : Responsible for building and setting up new development tools and infrastructure utilizing knowledge in continuous integration, delivery, and deployment (CI/CD), Cloud technologies, Container Orchestration and Security. Build and test end-to-end CI/CD pipelines, ensuring that systems are safe against security threats. Must have skills : DevOps Good to have skills : NA Minimum 3 Year(s) Of Experience Is Required Educational Qualification : 15 years full time education Summary: We are looking for an experienced Azure DevOps Engineer to design, build, and operate a scalable CI/CD platform on Azure DevOps. This role focuses on pipeline engineering, infrastructure automation, security integration, and developer enablement. You will act as a platform owner, enabling product teams to deliver software reliably, securely, and at scale. Roles & Responsibilities Own the Azure DevOps (ADO) platform as a shared service for engineering teams Define and maintain standards, best practices, and guardrails for pipelines, repos, and artifacts Design scalable CI/CD platform architecture aligned with enterprise needs Partner with security, cloud, and engineering leadership on platform roadmap Enforce RBAC, least privilege, and approval gates Design, build, and maintain reusable Azure DevOps YAML pipelines Create pipeline templates for build, test, security scanning, and deployment Enable multi-stage deployments across Dev, Test, UAT, and Production Implement and manage IaC using ARM, or Terraform Maintain version-controlled infrastructure definitions in Azure Repos or GitHub Enforce consistent environment provisioning and configuration Monitor ADO services, pipeline performance, and agent health Troubleshoot pipeline failures and platform issues (L3 support) Implement alerting and incident response for CI/CD services Third-party tools (SonarQube, JFrog, ServiceNow) Implement governance around pipeline usage, agent pools, and artifacts Optimize build agent usage and reduce CI/CD costs Participate in architectural reviews and technical design forums Technical Skills Strong expertise in Azure DevOps Services (Repos, Pipelines, Artifacts, Boards) Advanced YAML pipeline development Infrastructure as Code (Terraform) Azure platform knowledge (PaaS, Storage, Networking, Identity, Compute) Scripting: PowerShell, Python, YAML, JSON CI/CD platform design at scale Reusable templates and shared libraries DevSecOps practices Additional Information: The candidate should have minimum 3 years of experience in DevOps. This position is based at our Hyderabad office. A 15 years full time education is required.
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.