🎁 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 seeking a proactive and experienced Site Reliability Engineer (SRE) with 46 years of hands-on experience in managing cloud-native infrastructure, ensuring high availability, and improving the reliability of enterprise applications. The ideal candidate should possess strong expertise in Kubernetes, Python, Linux, and modern observability tools such as Dynatrace and Prometheus. You will work closely with development, DevOps, and cloud teams to automate operations, optimize system performance, and build resilient production environments. Key Responsibilities : - Design, deploy, and manage highly available applications on Kubernetes clusters. - Develop automation scripts and operational tools using Python. - Administer, monitor, and troubleshoot Linux/Unix production servers. - Implement and maintain monitoring, alerting, and observability solutions using Dynatrace, Prometheus, and related tools. - Analyze production incidents, perform root cause analysis (RCA), and implement preventive measures. - Monitor infrastructure performance, application health, and system capacity to ensure maximum uptime. - Collaborate with DevOps and development teams to improve deployment strategies and operational efficiency. - Support CI/CD pipelines and automate operational workflows wherever possible. - Maintain system documentation, operational runbooks, and incident response procedures. - Participate in on-call rotations and provide production support for critical enterprise applications. - Drive continuous improvements in system reliability, scalability, security, and operational excellence. Required Skills : - 46 years of experience in Site Reliability Engineering (SRE), DevOps, or Platform Engineering. - Strong hands-on expertise in Kubernetes administration and container orchestration. - Proficiency in Python scripting for automation and operational tasks. - Strong experience with Linux/Unix system administration and troubleshooting. - Hands-on experience with monitoring and observability tools such as Dynatrace and Prometheus. - Experience supporting production environments with high availability requirements. - Knowledge of incident management, root cause analysis, and system performance tuning. - Familiarity with CI/CD pipelines and DevOps methodologies. - Strong analytical, troubleshooting, and communication skills. Mandatory Skills : - Kubernetes - Site Reliability Engineering (SRE) - Python - Linux / Unix Administration - Dynatrace - Prometheus - Monitoring & Observability - Production Support - Incident Management - Automation & Scripting (ref:hirist.tech) .
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.