Senior Site Reliability Engineer

We are building for reliability, speed, and impact. MyOperator values ownership, critical thinking, and execution. This is a high-expectation, high-learning environment where engineers are empowered to solve complex problems and build systems that directly affect customer outcomes.\n\nKey Responsibilities\nOwn production reliability, uptime, latency, and error budgets across critical services.\nDesign and manage production-grade monitoring using Grafana, VictoriaMetrics (Prometheus), and AWS CloudWatch.\nDefine and enforce SLIs, SLOs, and SLA thresholds for AI communication systems (voice bots, WhatsApp APIs, call routing).\nBuild real-time operational dashboards for incident response, capacity planning, and leadership visibility.\nImplement end-to-end distributed tracing using OpenTelemetry (OTEL Collector).\nDesign and maintain centralized logging with strong correlation between logs, metrics, and traces.\nCreate SLO-based alerting systems with minimal noise and fast incident detection.\nLead incident response lifecycle: alert triage, mitigation, RCA documentation, and preventive improvements.\nDrive MTTR reduction through structured monitoring, automation, and reliability engineering practices.\nMonitor and troubleshoot AWS EKS (Kubernetes) production workloads.\nInstrument and monitor LLM API integrations, AI inference pipelines, and messaging systems.\nAnalyze logs using OpenSearch / ELK for anomaly detection and root cause identification.\nAutomate operational workflows using Python or Bash to eliminate manual toil.\nDrive performance optimization, scalability improvements, and capacity planning.\nCollaborate with engineering teams to instrument new services from day one.\n\nRequired Skills & Qualifications\n3–6 years of experience in Site Reliability Engineering, DevOps, or Platform Engineering roles.\nHands-on experience with: VictoriaMetrics / Prometheus (time-series monitoring), Grafana dashboards and visualization & PromQL for writing complex queries and alerts\nExperience implementing distributed tracing using OpenTelemetry (Mandatory).\nStrong experience with centralized logging systems (ELK / OpenSearch / Loki).\nExperience with alerting frameworks such as Alertmanager or Grafana Alerts.\nStrong understanding of SLIs, SLOs, SLA design, and reliability engineering principles.\nHands-on experience managing AWS production workloads (EC2, RDS, ELB, CloudWatch, IAM).\nExperience with Kubernetes (AWS EKS preferred).\nGood understanding of Linux systems, networking, and cloud infrastructure.\nExperience handling production incidents and participating in on-call rotations.\nAbility to automate operational tasks using Python or Bash.\n\nGood to Have\nExperience with OpenSearch / ELK log pipelines and anomaly detection.\nKubernetes monitoring (pod health, node metrics, autoscaling behavior).\nCI/CD observability integration (Jenkins, GitHub Actions).\nExperience monitoring LLM APIs and AI inference pipelines.\nFamiliarity with MLOps or AI observability tools (Arize, WhyLabs, etc.).\nService mesh exposure (Istio).\nInfrastructure as Code (Terraform, CloudFormation).\nExperience with chaos engineering or load testing tools.\nMulti-cluster or multi-region architecture exposure.\n\nKey Expectations\nOwnership of production systems and high availability.\nStrong troubleshooting and debugging skills.\nFocus on automation and reliability improvements.\nProactive approach to incident prevention.\nAbility to reduce alert noise and improve signal quality.\nData-driven approach to reliability engineering.\n\nThis Role Is Not For\nCandidates with purely development experience and no production ownership.\nCandidates without real incident response or on-call experience.\nFreshers or candidates with less than 3 years of experience.