🎁 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 →
Role Reasonability MetLife is seeking a Site Reliability Engineer (SRE) to ensure the reliability, availability, and performance of critical applications and platforms. The SRE Engineer will monitor production systems, respond to incidents, improve observability, maintain runbooks, and automate operational tasks. Working closely with engineering, cloud, and infrastructure teams, the role supports SRE practices, operational readiness, and service reliability through SLIs, SLOs, and Error Budget management. Core Responsibilities Monitoring: Monitor service health, dashboards, alerts, and key reliability indicators for assigned applications and platforms. Incident Response: Respond to alerts, support bridge calls, gather evidence, execute runbooks, communicate status, and escalate when required. Observability Support: Create and maintain dashboards, log queries, telemetry checks, alert validation, and actionable monitoring signals. Runbook Management: Document operational procedures, update recovery steps, validate readiness with service owners, and support knowledge sharing. Automation: Create scripts for repetitive checks, data collection, remediation, operational reporting, and toil reduction. Problem Follow-up: Support root cause analysis, postmortem documentation, and closure of assigned corrective/preventive action items. Continuous Improvement: Identify alert noise, toil, monitoring gaps, and preventive improvements for senior SRE review. SRE Alignment: Support adoption of SLOs, SLIs, SLAs, error budgets, operational readiness reviews, and production support standards. AI Readiness: Use or help improve AI-assisted tools for anomaly detection, incident correlation, root cause hints, and operational knowledge retrieval. Collaboration: Work with engineering, infrastructure, cloud, and application teams to align service performance with business goals. Skills and Experience Foundations: Linux, networking fundamentals, application support, cloud fundamentals, production operations, and ITIL-style incident/change processes. Scripting: Python, PowerShell, Bash, or equivalent scripting for automation, diagnostics, evidence collection, and reporting. Tools: Git, CI/CD basics, ServiceNow or equivalent ticketing; exposure to Elastic/ELK, Grafana, Prometheus, Splunk, APM, and Azure Monitor preferred. Cloud & Containers: Azure services, Docker, Kubernetes, and hybrid cloud operations exposure; Terraform or infrastructure-as-code awareness preferred. Reliability: Basic understanding of SLIs, SLOs, SLAs, error budgets, alerting, incident response, postmortems, and operational runbooks. AI / AIOps Readiness: Ability to use AI-assisted investigation, anomaly detection, and correlation tools responsibly, with strong validation of evidence. Database: Hands-on SQL skills for operational diagnostics, data validation, and service health checks. Execution: Disciplined follow-through, evidence capture, documentation, escalation hygiene, and collaboration during incidents. Learning Mindset: Willingness to deepen skills in cloud, Kubernetes, observability, automation, resilience engineering, and secure operations. Minimum Qualifications 2+ years in production support, DevOps, infrastructure, cloud operations, or software engineering. Experience supporting business-critical systems and working in incident, problem, and change management processes. Ability to script and automate standard operational tasks using Python, PowerShell, Bash, or equivalent. Bachelors degree in computer science, engineering, or equivalent practical experience. Exposure to regulated enterprise, insurance, banking, or financial services environments preferred. Business proficiency in English; Japanese language skills are a plus. Preferred Exposure Hybrid cloud platforms including on-premises and Azure-hosted services. Observability platforms such as ELK/Elastic, Grafana, Prometheus, Splunk, Azure Monitor, and Azure Application Insights. GitHub, Azure DevOps, pipelines, repositories, and operational change controls. Kubernetes-based production services and containerized application support. SRE practices including operational readiness reviews, service health reviews, and toil reduction initiatives. About MetLife Recognized on Fortune magazine's list of the "World's Most Admired Companies" and Fortune Worlds 25 Best Workplaces, MetLife, through its subsidiaries and affiliates, is one of the worlds leading financial services companies; providing insurance, annuities, employee benefits and asset management to individual and institutional customers. With operations in more than 40 markets, we hold leading positions in the United States, Latin America, Asia, Europe, and the Middle East. Our purpose is simple - to help our colleagues, customers, communities, and the world at large create a more confident future. United by purpose and guided by our core values - Win Together, Do the Right Thing, Deliver Impact Over Activity, and Think Ahead .
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.