🎁 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 Senior Site Reliability Engineer (SRE), you will design and implement highly reliable, scalable, and secure systems. You will lead incident response efforts, improve operational processes, and mentor junior engineers. This role requires strong technical expertise in cloud infrastructure, automation, observability, and reliability engineering practices. Responsibilities: Define and enforce Service Level Objectives (SLOs) and Service Level Indicators (SLIs) for critical systems, ensuring alignment with business goals.Monitor and improve Mean Time to Recovery (MTTR) and Mean Time to Detect (MTTD) across services.Design scalable AWS-based systems, including multi-region deployments and disaster recovery strategies.Develop reusable, version-controlled Terraform modules and maintain scalable Ansible configurations.Design and maintain reliable CI/CD pipelines using tools such as Harness.Build and optimise observability systems using Dynatrace and other monitoring platforms.Lead incident response efforts, conduct root cause analysis, and drive process improvements.Manage production databases (SQL/NoSQL), including replication, failover, and performance optimisation.Implement security controls and ensure compliance with organisational standards.Conduct capacity planning and performance tuning for critical systems.Collaborate with application support teams and third-party vendors to ensure timely issue resolution and SLA adherence.Mentor engineers, collaborate across teams, and promote reliability engineering best practices. Requirements: Minimum 4+ years of relevant experience.Windows Administration and Red Hat Linux Administration.VMware and ESXi experience.Strong proficiency in Bash and PowerShell scripting for automation.Expertise in AWS services and scalable architecture design.Hands-on experience with Terraform and Ansible.Experience in CI/CD pipeline design and release engineering.Experience with Splunk and Observability platforms.Strong understanding of SLOs, SLIs, error budgets, MTTR, and MTTD metrics. Good to Have: Experience leading and improving incident management processes.Ability to coordinate with third-party vendors for application support and issue resolution.Knowledge of security best practices and compliance frameworks.Strong leadership, mentoring, and cross-functional collaboration skills. Preferred Qualifications: Experience with multi-account AWS environments.Familiarity with automation and self-healing systems.Knowledge of performance modelling and long-term capacity forecasting.AWS and/or SRE-related certifications.Bachelor's degree or equivalent practical experience/certification. .
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.