• 6+ years of experience in consulting, engineering, SRE, platform engineering, or operations with strong observability responsibility.

• Hands-on experience with modern observability concepts across metrics, logs, traces, alerting, service health, and incident response.

• Experience with Open Telemetry and familiarity with telemetry pipeline design, instrumentation patterns, and collection architecture.

• Working knowledge of open-source observability tools such as Prometheus, Grafana, Loki, Tempo, Mimir, Jaeger, or Elastic.

• Experience with one or more enterprise observability platforms such as Datadog, Dynatrace, Splunk, New Relic, Elastic, LogicMonitor, Honeycomb, Chronosphere, etc.

• Strong understanding of Kubernetes, containers, cloud-native architectures, and at least one major public cloud platform.

• Experience with Terraform, Helm, CI/CD pipelines, Ansible, or related automation and platform tooling.

• Solid understanding of distributed systems, modern application architectures, and operational best practices across SRE, DevOps, or ITSM environments.

• Experience defining service health models, SLIs, SLOs, alerting strategies, or reliability measurement frameworks that connect technical telemetry to operational and business outcomes.

• Ability to lead client-facing conversations, structure ambiguous problems, and translate strategy into executable workstreams.

• Demonstrated ability to operate in ambiguous client environments, identify the practical path forward, and communicate tradeoffs clearly across engineering, operations, and leadership audiences.

• Strong written and verbal communication skills with both technical and executive audiences.

• A continuous learning mindset and a collaborative approach to delivery and practice building.

Nice to have

• Experience operationalizing error budgets, burn-rate alerting, production readiness reviews, or reliability governance practices.

• Experience integrating observability with ServiceNow, incident management platforms, CMDB, or collaboration tools.

• Experience with telemetry cost optimization, sampling strategies, retention policies, tagging standards, cardinality management, or observability governance.

• Familiarity with platform engineering, internal developer platforms, service catalogs, golden paths, or self-service observability patterns.

• Exposure to AIOps, anomaly detection, event correlation, automated remediation workflows, or MCP-enabled integration patterns for AI-assisted operations.

• Familiarity with microservices, service mesh technologies, end-user monitoring, or digital experience monitoring concepts.

• Generalist coding or scripting experience in languages such as Python, Java, Go, JavaScript, or .NET.