1

Open Telemetry Jobs (NOW HIRING)

The role involves implementing Open Telemetry-based instrumentation and integrating with observability tools while collaborating with the internal Python team to address challenges in legacy systems.

AWS DevOps Engineer

Malvern, PA · On-site

$51.75 - $71/hr

Creation of telemetry for applications using Splunk, App Dynamics/Honeycomb (open telemetry) Qualifications: 8+ years of experience Senior DevOps Engineer specializing in AWS cloud services, fraud ...

... Open Telemetry, Elastic, Splunk, Grafana/Prometheus, equivalent) • Experience ingesting telemetry via APIs, event streams (Kafka/Kinesis), log frameworks • Prior success instrumenting multiple ...

Telemetry - Team Leader

Greenville, MS · On-site

$1.8K - $2.5K/wk

Job Openings >> Telemetry - Team Leader Telemetry - Team Leader Summary Title: Telemetry - Team Leader ID: 2069 Location: Greenville, MS Department: TELEMETRY Job Type: Full Time (Nights) More about ...

Experience with monitoring large scale distributed systems with Open Telemetry, Splunk, Prometheus and Grafana Education:Employment Type: FULL_TIME

Senior Site Reliability Engineer

Los Angeles, CA · Hybrid

$61.50 - $81.50/hr

Implement best practice observability with Open Telemetry, logging, standard SLOs, * You will own the Incident Response process design and followups * Employ automated testing practices to ensure ...

Senior Observability Engineers

Dallas, TX · On-site

$103K - $142K/yr

Open Telemetry (OTEL) implementation experience. Monitoring, logging, alerting, and distributed tracing experience. Linux administration and cloud platform experience. Automation/scripting with ...

Senior Site Reliability Engineer

San Francisco, CA · Hybrid

$67.25 - $89.25/hr

Implement best practice observability with Open Telemetry, logging, standard SLOs, * You will own the Incident Response process design and followups * Employ automated testing practices to ensure ...

Staff Site Reliability Engineer

Los Angeles, CA · Hybrid

$61.50 - $81.50/hr

Implement best practice observability with Open Telemetry, logging, standard SLOs, * You will own the Incident Response process design and followups * Employ automated testing practices to ensure ...

SRE/Observability Engineer

Mclean, VA · On-site

$58.50 - $77.75/hr

The ideal candidate will possess deep expertise in modern observability platforms, application performance monitoring, Open Telemetry implementation and cloud technologies, with a strong focus on ...

Staff Site Reliability Engineer

San Francisco, CA · Hybrid

$67.25 - $89.25/hr

Implement best practice observability with Open Telemetry, logging, standard SLOs, * You will own the Incident Response process design and followups * Employ automated testing practices to ensure ...

next page

Showing results 1-20

Open Telemetry information

See salary details

$1.2K

$2.3K

$3.2K

How much do open telemetry jobs pay per week?

As of Sep 10, 2026, the average weekly pay for open telemetry in the United States is $2,320.96, according to ZipRecruiter salary data. Most workers in this role earn between $1,942.31 and $2,653.85 per week, depending on experience, location, and employer.

What is the difference between Open Telemetry vs Cloud Monitoring Engineer?

AspectOpen TelemetryCloud Monitoring Engineer
Required CredentialsKnowledge of observability tools, programming skillsCertifications in cloud platforms (AWS, Azure, GCP), monitoring tools
Work EnvironmentDeveloping and implementing observability solutions, working with APIsManaging and configuring cloud monitoring services, analyzing metrics
Industry UsageUsed across industries for application monitoring and tracingPrimarily in organizations utilizing cloud infrastructure
Search & Comparison IntentUnderstanding open-source observability toolsImplementing cloud monitoring solutions

Open Telemetry focuses on developing open-source tools for application observability, while Cloud Monitoring Engineers implement and manage cloud-specific monitoring solutions. Both roles require familiarity with cloud environments, but Open Telemetry emphasizes tool development and integration, whereas Cloud Monitoring Engineers focus on configuring and maintaining monitoring services within cloud platforms.

What cities are hiring for Open Telemetry jobs?

Cities with the most Open Telemetry job openings:

Infographic showing various Open Telemetry job openings in the United States as of September 2026, with employment types broken down into 1% Internship, 1% As Needed, 77% Full Time, 18% Part Time, and 3% Contract. Highlights an 90% Physical, 2% Hybrid, and 8% Remote job distribution, with an average salary of $120,690 per year, or $58 per hour.

Open Telemetry (OTel) Instrumentation Engineer

Woodland Hills, CA • On-site

Contractor

Re-posted 5 days ago


Job description

Role: Senior Open Telemetry (OTel) Instrumentation Engineer
Descriptions:
"Core Responsibilities
1. SaaS Instrumentation
• End-to-End Instrumentation: Instrument SaaS products utilizing OTel SDKs (Python, Node.js, Java, Go) to ensure spans, metrics, and structured logs are emitted at the appropriate granularity.
• Semantic Conventions: Define and enforce attribute naming conventions (e.g., service.name, tenant.id, feature.flag) aligned strictly with OTel semantic standards.
• Multi-Tenant Observability: Instrument multi-tenant surfaces to guarantee robust tenant-level observability while preventing cross-tenant data leakage.
2. Cloud Infrastructure
• Collector Fleet Management: Deploy and maintain the OTel Collector fleet across AWS, GCP, and Azure, including receiver configurations, processor pipelines, and exporter routing.
• Runtime Instrumentation: Instrument serverless (Lambda, Cloud Run) and container runtimes (EKS, GKE, AKS) utilizing auto-instrumentation where feasible, and manual instrumentation when technical nuance requires it.
• Metric Normalization: Collect and normalize cloud provider metrics (CloudWatch, Cloud Monitoring, Azure Monitor) via OTel receiver plugins.
3. Network Telemetry
• Data Collection: Gather network flow data (sFlow, NetFlow/IPFIX), SNMP traps, and BGP state via OTel-native and bridged receivers.
• Context Propagation: Correlate network events with application traces using consistent trace-context propagation across network boundaries.
• Strategy Collaboration: Partner with NetOps to define the MELT (Metrics, Events, Logs, Traces) strategy for on-prem, SD-WAN, and cloud interconnect segments.
4. Application Observability
• APM Ownership: Own Application Performance Monitoring (APM) instrumentation, including distributed tracing, custom span attributes, database query capture, and error fingerprinting.
• Asynchronous Workloads: Instrument async workloads (Kafka, SQS, Celery) ensuring W3C Trace Context propagation across message boundaries.
• SLI/SLO Definition: Define and instrument Service Level Indicators (SLIs) and Service Level Objectives (SLOs)—such as latency histograms, error-rate counters, and availability gauges—queryable directly from the Lakehouse.
5. Platform & Standards
• Internal Libraries: Build and maintain internal instrumentation libraries and language-specific wrappers that encode organizational conventions.
• Governance: Author and review instrumentation RFCs while driving the adoption of OTel semantic conventions across all engineering teams.
• Data Alignment: Collaborate with the AIOps ML team to ensure telemetry schemas meet feature engineering and ML model requirements.
• Pipeline Operations: Operate the Collector pipeline at scale, managing backpressure handling, sampling strategies (tail/head), and cardinality budgets."
"Strong expertise in:
OpenTelemetry (SDKs, APIs, Collector, OTLP)
Distributed tracing, metrics, logging principles [opentelemetry.io]