🎁 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 →
As a Lead DevOps Engineer, you will serve as a technical leader and platform architect, responsible for designing and driving sophisticated infrastructure automation strategies, deployment platforms, and reliability initiatives across multiple teams and products. You will partner closely with Development, QA, client-facing teams, and leaders across the organization to shape how we build, deploy, and operate modern software. You will define cross-team deployment strategies, establish enterprise-level infrastructure-as-code standards, and mentor DevOps and software engineers to uplift our operational maturity. You will regularly evaluate new technologies, build proof-of-concept automation solutions, and lead continuous improvements in CI/CD, containerization, observability, and reliability practices. You bring deep expertise in Terraform, Ansible, AWS, and modern DevOps practices, and are comfortable across a broad range of systems including GitLab CI, Jenkins, Octopus Deploy, Kubernetes, networking, scripting, and monitoring. You are not a pure operations engineer. You bring deep expertise in platform architecture, systems internals, and debugging across the infrastructure stack. You are the kind of engineer who will spend a whole day investigating why something broke the way it did, then design the automation that prevents it from ever happening again. Above all, you will champion a culture of automation-first engineering, ensuring that our platforms are reliable, scalable, secure, and built with infrastructure as code at their core. Your mission: unify and modernize deployment. Today, our products are deployed through a mix of pipelines and tooling that grew up alongside the businesses. You will lead the effort to bring them together: designing a single, modern, standardized deployment platform used across the organization, and evolving our CI/CD stack toward containerized, infrastructure-as-code-driven delivery. This is a build-and-transform role, not a keep-the-lights-on role: the robust, automated pipelines you architect are how we reduce manual work, deployment risk, and off-hours incidents. ResponsibilitiesOwn infrastructure and platform architecture, designing scalable, secure, and cost-effective AWS environments, spanning compute, containers, networking, data stores, and messaging, that support our hosted enterprise applications.Define and drive DevOps strategy and standards across teams: infrastructure as code practices, CI/CD pipeline architecture, deployment patterns, and environment management.Lead the unification and modernization of our CI/CD platform, consolidating todays tooling (GitLab CI, Jenkins, Octopus Deploy) into a standardized, modern deployment solution adopted by engineering teams.Lead automation initiatives using Terraform, Ansible, and scripting (Shell, Python) to eliminate manual work, reduce configuration drift, and standardize environments.Drive containerization and orchestration strategy with Docker and Kubernetes, guiding adoption, cluster architecture, and operational best practices.Lead incident response and rootcause analysis for complex infrastructure and deployment issues, ensuring durable corrective action, improved observability, and reduced recurrence.Champion reliability, observability, and security, building the monitoring, alerting, and selfhealing automation that catches issues before they page anyone, including SSO, IAM, and accessmanagement solutions for hosted client environments.Mentor and uplevel DevOps and software engineers, raising the bar on automation, infrastructure design, debugging, and operational excellence.Partner with engineering leadership, development, and clientfacing teams to align infrastructure roadmaps with product and business priorities, and communicate operational posture clearly to technical and nontechnical stakeholders.Evaluate and prototype new tools and technologies, guiding adoption decisions with proofs of concept and datadriven recommendations.Shape AI tooling strategy for engineering, evaluating emerging AI tools, defining standards for their use, and driving adoption across teams.Architect AIaugmented workflows and automation pipelines, such as autonomous agent loops that carry multistep engineering tasks to completion, contributing to agent frameworks that optimize context and prompting across the organization.Mentor engineers across levels on effective AI integration into their development and operations practices, considering the broader implications of AI tooling on team productivity, code quality, and engineering culture.Qualifications7+ years of experience in DevOps, infrastructure, platform, or systems engineering roles, with demonstrated technical leadership on complex initiatives.Operating Systems: handson experience administering both Linux and Windows servers in production.DevOps: strong experience designing and owning CI/CD processes and tools (GitLab CI, Jenkins, Octopus Deploy).Containerization: .
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.