🎁 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 →
About The Role The Site Reliability Engineering (SRE) team architects, builds, and maintains the rock-solid infrastructure that applications rely on. At the Senior Level, you own reliability, performance, and cost outcomes for the systems under your area end-to-end, not just executing well-defined tasks, but deciding between tradeoffs, scoping ambiguous problems, and driving process and system improvements that span teams. You'll work closely with development, security, and product teams, and mentor other engineers as a technical point of reference for the team. What You Will Do Own the availability, performance, scalability, and security of production systems end-to-end, across cloud (AWS/GCP) and on-premises environments. Design and evolve Kubernetes deployment strategy for production workloads. Own CI/CD and GitOps pipelines in production (ArgoCD or equivalent) and the Terraform that provisions the infrastructure behind them. Diagnose and resolve database performance issues. Build and maintain observability that surfaces problems before they become incidents. Seek out and implement process and system improvements affecting performance and security, coordinating with multiple stakeholders. Scope and lead medium-to-large infrastructure initiatives: gather requirements, prioritize by business impact, and communicate impact to stakeholders. Negotiate technical tradeoffs with stakeholders to meet business SLAs. Provide technical guidance and mentorship to peers and junior engineers; promote best practices and standards across the team. Maintain documentation and process discipline for the systems and incidents you own. Lead structured incident investigation, isolating server, database, and application layers with a metrics-first approach, including on-call during high-traffic events. What Are We Looking For At least 4 years of experience in either SRE, DevOps, MLOps, or platform engineering, including senior-level scope at a high-traffic company. Deep expertise in one major cloud provider (preferably AWS), with a proven ability to ramp up on the other quickly.Production experience & expertise with Kubernetes & Linux fundamentals CI/CD & GitOps (ArgoCD or other equivalent stacks) Database performance analysis & monitoring (MySQL, Postgres) Observability tooling & standards (Datadog, OpenTelemetry) Infrastructure as Code (Terraform) Strong working English, verbal & written communication. Strong documentation and process discipline. On-call & incident handling experience during high-traffic events. Comfortable negotiating with stakeholders to propose technical compromises that meet business SLAs. Demonstrated growth mindset and proven ability to own ambiguous scope.
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.