🎁 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 Team The Cybersecurity Product Engineering Team designs, develops, and operates strategic platforms that support security posture visibility, operational intelligence, enterprise risk management, and secure engineering outcomes. The team works at the intersection of cybersecurity, cloud engineering, data engineering, site reliability engineering, and artificial intelligence. Reliability and operational excellence are central to how we deliver secure, resilient, scalable services to global stakeholders. About The Role We are seeking a highly motivated Lead Site Reliability Engineer (SRE) Support Engineer (3P) to join the Cybersecurity Product (Software) Engineering Team. This role is responsible for maintaining the reliability, availability, and operational performance of critical cloud-native services running in Microsoft Azure currently, with potential to extend to AWS, GCP Cloud Service Providers. This is a full-time night-shift role (9:00 PM to 6:00 AM IST) supporting US business hours. While office presence requirements can be discussed, candidates must be based in Hyderabad and available to work from the Hyderabad location as needed. The successful candidate will partner with software engineers, platform engineers, data engineers, and cybersecurity stakeholders to support production services, manage incidents, improve observability, automate repetitive work, and drive continuous operational improvement. The ideal candidate combines strong troubleshooting skills with an ownership mindset and practical experience using AI-assisted engineering tools. Technical Job Description Own and manage DevOps pipelines for the platform across application code, data, RAG, and ML workloads; build and enhance pipelines as needed to improve reliability, automation, and deployment efficiency.Provide hands-on Production Support for product with clear, timely incident updates that summarize impact, investigation status, mitigation, and next actions.Drive incidents through containment, recovery, validation, closure, and handoff when cross-shift follow-up is required.Contribute to root cause analysis and track corrective and preventive actions to completion.Participate in a 24x7 support and on-call model as required by business and service needs. Site Reliability Engineering Improve service reliability, resilience, scalability, and operational effectiveness through engineering-led support practices.Identify recurring failure patterns, reliability risks, and opportunities to reduce manual operational toil.Contribute to Service Level Indicators (SLIs), Service Level Objectives (SLOs), availability targets, and service health reviews.Partner with engineering teams on operational readiness, recovery procedures, capacity considerations, and platform hardening.Use incident and service-health learnings to recommend durable technical and process improvements. Azure-Native Observability Use Azure Monitor, Application Insights, Log Analytics workspaces, Azure Alerts, and Azure Service Health to monitor and diagnose services.Investigate system behavior through metrics, logs, distributed traces, dependency maps, queries, and correlated events.Build and improve actionable dashboards, alert rules, health views, and operational reports.Tune monitoring and alerting to improve signal quality, reduce alert fatigue, and shorten detection and recovery cycles.Contribute to observability standards and consistent telemetry practices across supported services. Data Platform Operations Support the operational reliability of cloud-based data services and analytics workloads.Troubleshoot Snowflake connectivity, access, workload, query performance, and operational issues within the scope of the support role.Investigate data ingestion, transformation, reporting, and pipeline failures in collaboration with data engineering teams.Validate data availability and operational recovery after incidents, releases, or maintenance activities.Use SQL to investigate data issues, validate processing outcomes, and support incident diagnosis. Automation and Operational Excellence Develop and maintain Python, PowerShell, or shell-based automation for health checks, evidence gathering, diagnostics, and routine support activities.Create reusable utilities and workflow improvements that reduce manual effort and improve response consistency.Identify opportunities for safe self-service and self-healing capabilities with appropriate controls and auditability.Improve support processes through standardization, measurable outcomes, documentation, and continual learning.Contribute operational feedback to backlog prioritization and engineering improvement plans. AI-Assisted Operations Use approved enterprise AI assistants and copilots to accelerate troubleshooting, knowledge retrieval, scripting, documentation, and incident summarization.Apply effective prompt engineering techniques to produce clear, context-aware operational outputs and .
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.