1

Observability Engineer Jobs in Chicago, IL (NOW HIRING)

Splunk Observability Engineer Location: Chicago, IL (Hybrid) Duration: 12 months Synopsis: To design, implement, and optimize a full-stack observability strategy using the Splunk Observability Cloud ...

New

The main function of a site reliability engineer is to participate in the full development lifecycle of creating automated solutions by designing and implementing performance tests, identify ...

Observability Engineering * Design and implement monitoring, alerting, and dashboards in New Relic (APM, Infrastructure, Logs, Synthetics) across Azure and AWS; write NRQL queries for troubleshooting ...

Site Reliability Engineer, Observability

Chicago, IL · On-site

$58.75 - $78/hr

Observability Engineering * Design and implement monitoring, alerting, and dashboards in New Relic (APM, Infrastructure, Logs, Synthetics) across Azure and AWS; write NRQL queries for troubleshooting ...

Staff SRE - Observability

Chicago, IL · On-site

$58.75 - $78/hr

We are seeking an experienced Staff Observability Consultant with deep expertise in OpenTelemetry and strong Platform Engineering capabilities to help organizations implement, optimize, and scale ...

Position Senior Site Reliability Engineer - part of Ripple's Technical Operations team. This role focuses on observability, releasability, security, and DevSecOps practices to keep Ripple's products ...

next page

Showing results 1-20

Observability Engineer information

What does an observability engineer do?

An Observability Engineer is responsible for designing, implementing, and maintaining monitoring, logging, and tracing systems to ensure the health, performance, and reliability of applications and infrastructure. They work with tools like Prometheus, Grafana, OpenTelemetry, and ELK to collect and analyze telemetry data. Their goal is to provide visibility into system behavior, detect and diagnose issues quickly, and improve overall system observability. They collaborate with developers, SREs, and operational teams to create automated and scalable observability solutions.

What are the key skills and qualifications needed to thrive as an observability engineer?

To thrive as an Observability Engineer, you need a solid understanding of monitoring, logging, and tracing systems, as well as expertise in programming, cloud infrastructure, and incident response. Proficiency in tools like Prometheus, Grafana, ELK stack, and familiarity with cloud platforms such as AWS, Azure, or GCP are commonly required, and certifications like AWS Certified DevOps Engineer can be advantageous. Strong analytical thinking, collaborative skills, and effective communication are essential soft skills for diagnosing issues and working across development and operations teams. These competencies are vital for proactively maintaining system reliability, ensuring performance, and resolving complications before they impact business operations.

How much do observability engineers make?

Observability engineers typically earn between $90,000 and $150,000 annually, depending on experience, location, and company size. Senior roles or those with expertise in tools like Prometheus, Grafana, or cloud platforms may command higher salaries.

What are the most commonly searched types of Observability Engineer jobs in Chicago, IL?

The most popular types of Observability Engineer jobs in Chicago, IL are:

What job categories do people searching Observability Engineer jobs in Chicago, IL look for?

The top searched job categories for Observability Engineer jobs in Chicago, IL are:

Infographic showing various Observability Engineer job openings in Chicago, IL as of August 2026, with employment types broken down into 91% Full Time, 5% Part Time, and 4% Contract. Highlights an 86% Physical, 6% Hybrid, and 8% Remote job distribution.

Splunk Observability Engineer

MethodHub

Chicago, IL • On-site

Other

Posted 2 days ago

New


Job description

Splunk Observability Engineer

Location: Chicago, IL (Hybrid)

Duration: 12 months

Synopsis:

To design, implement, and optimize a full-stack observability strategy using the Splunk Observability Cloud (formerly SignalFx) and Splunk Enterprise/Cloud. You will ensure that engineering teams have 360-degree visibility into system health, moving the organization from reactive "firefighting" to proactive "pattern-based" incident prevention.

Key Responsibilities:

  • Data Orchestration: Architect the ingestion of the "Three Pillars" (Metrics, Logs, Traces) using OpenTelemetry (OTel) collectors.
  • Aggregation Strategy: Develop logic to aggregate high-cardinality data to reduce "noise" while maintaining "signal" for troubleshooting.
  • Analytical Modeling: Use SPL (Search Processing Language) and SignalFlow to perform pattern analysis, detecting anomalies before they trigger traditional threshold alerts.
  • Visual Storytelling: Build executive and technical dashboards that correlate disparate data points (e.g., showing how a spike in 500-errors in Logs relates to a specific span in a Trace).

Required Hands on Technical Skills:

  1. Telemetry & Data Specialization
  • Logs: Proficiency in "Logging-in-Context." You must be able to link logs directly to trace IDs so developers can jump from a failing trace to the specific line of code in the logs.
  • Metrics: Expertise in SignalFlow (Splunk s background streaming analytics language). You should know how to calculate percentiles ($P95, P99$), rates of change, and historical averages.
  • Traces: Deep understanding of Distributed Tracing. You must know how to instrument applications (Java, Python, Go) to capture spans and identify bottlenecks in microservices.
  1. Pattern Analysis & Aggregation
  • Anomaly Detection: Ability to configure Metric Finder and MDetector using standard deviations or "Mean Absolute Deviation" to find outliers.
  • Data Scrubbing: Skills in using Splunk Ingest Actions or Edge Processors to filter, mask, or aggregate data at the edge to save on license costs and improve search speed.
  • Pattern Discovery: Using Splunk s machine learning commands (e.g., findkeywords, cluster) to group millions of log events into a few dozen "patterns" for faster root cause analysis.
  1. Hands on - Dashboards & Visualization
  • High-Cardinality Handling: Designing dashboards that don t "break" when viewing thousands of containers.
  • Contextual Drill-downs: Building "Glass Tables" (in ITSI) or Unified Dashboards that allow a user to click a metric and immediately see the associated logs.
  • Frameworks: Familiarity with the Dashboard Studio and JSON-based dashboard definitions for version control (GitOps).

Preferred Qualifications & Certifications:

  • DevOps & IAC skills
  • Splunk Cloud Certified Metrics User: Focuses on the metrics and alerting side.
  • Splunk Core Certified Power User: Essential for mastering complex SPL for log analysis.
  • OpenTelemetry Expert: Knowledge of the OTel Collector configuration (receivers, processors, exporters) is currently the most "in-demand" skill for this role.