🎁 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 The AVP, Site Reliability Engineering is a senior SRE lead accountable for the reliability, availability, scalability, and resilience of critical products and platforms. The role drives observability, automation, incident readiness, and recovery engineering to improve service performance and reduce operational toil. Working across engineering, infrastructure, and product teams, this role also leads proactive risk reduction, innovation, and continuous improvement through resilience testing, capacity optimisation, and the responsible use of available AI tools within SGX to enhance operational efficiency and decision-making. Job Responsibilities Reliability Engineering: Operate services against defined reliability objectives. Observability: Build and maintain monitoring, logging and telemetry solutions. Incident Management: Independently manage incident resolution and recovery activities. SLO / SLA Management: Operate systems against agreed SLOs and service targets. Automation: Develop automation to reduce operational effort and toil, utilising modern technology including agentic AI. Performance Engineering: Conduct performance analysis and optimisation. Capacity & Resilience Planning: Forecast and manage capacity for supported services. Cloud & Platform Operations: Independently manage cloud operational services. Operational Risk Management: Ensure operational controls and compliance requirements are met. Engineering Leadership: Coach other engineers in reliability practices. Agentic AI for Reliability & Operations: Use agentic AI to accelerate operational workflows such as alert triage, root-cause analysis, runbook execution support, anomaly investigation and post-incident learning, while ensuring all remediation remains validated and controlled. · Partner with engineering, infrastructure, security, and product teams to embed reliability by design and continuously improve service stability, scalability, and cost efficiency. Job Requirements 5-10+ years of experience in Site Reliability Engineering, Platform Engineering, Cloud Operations, DevOps, or a related technical discipline, with experience leading reliability initiatives in complex enterprise environments. Proven experience defining and managing Service Level Indicators (SLIs), Service Level Objectives (SLOs), error budgets, and reliability governance frameworks. End-to-End Service Ownership to Support the full operational lifecycle of assigned applications and platforms, including onboarding, release readiness, production monitoring, incident response, problem management, recovery validation, and continuous service improvement. Hands-on expertise with observability and monitoring platforms such as Prometheus, Grafana, ELK, AWS CloudWatch, DataDog, Coralogix, or similar technologies. Strong experience operating and supporting cloud-native platforms, Kubernetes/EKS environments, and distributed systems at scale. Proficiency in automation and infrastructure-as-code using tools such as Terraform, Ansible AAP, Python, or equivalent technologies. Experience leading major incident management, problem management, root-cause analysis, and post-incident review processes. Demonstrated capability in capacity planning, performance engineering, resilience testing, and operational risk management within high-availability environments. Strong stakeholder management and communication skills, with the ability to collaborate effectively across engineering, infrastructure, security, product, and business teams. Experience coaching and mentoring engineers while driving operational excellence, reliability culture, and continuous improvement initiatives. Preferred Qualifications Experience or exposure within financial services, financial market infrastructure, exchanges, index calculation platforms, reference data systems, market data services, trading, clearing, settlement, or other highly regulated environments. Professional certifications in cloud platforms (AWS, Azure, GCP), Kubernetes, Site Reliability Engineering, DevOps, or related disciplines. Experience implementing AIOps, observability analytics, predictive monitoring, and intelligent automation solutions. Hands-on experience leveraging AI or agentic AI technologies for alert triage, incident investigation, operational automation, runbook optimisation, and knowledge management. Exposure to FinOps practices, cloud cost optimisation, and platform engineering operating models. Familiarity with security, resilience, and regulatory requirements applicable to critical financial systems. Experience driving large-scale technology transformation, platform modernisation, or cloud adoption initiatives. Advanced knowledge of software engineering practices, CI/CD pipelines, and reliability-focused architecture patterns.
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.