Confirmed on the employer's own hiring board on Nov 19, 2026. First seen by Alion on Nov 19, 2026. E-Space scores B on the Alion truth index.
We are hiring an OSS Telemetry Engineering Lead to lead the team that makes the health and performance of our distributed mobile network systems visible and actionable, and to set its technical direction.
This is a hands-on leadership role for someone who owns operational visibility end to end, from telemetry collection through dashboards, alerts, and verified service recovery, while building and guiding the engineers who deliver it. You will lead the OSS telemetry team, partner closely with NOC engineers and cross-functional teams, act with urgency when service is at risk, and stay engaged until issues are resolved.
Your mission
Build and lead a dependable observability capability that helps teams detect problems early, understand their impact, and restore service quickly. Set the standards for how mobile network behavior is translated into KPIs, SLOs, dashboards, and alerts. Make ownership and escalation clear across teams, verify that recovery actions restore the required service performance, and grow a team that can do all of this at scale.
What you will own
Observability strategy and roadmap. Define the observability architecture and roadmap across distributed systems, microservices, and the 5G core, aligned with network, product, and operations priorities.
Team leadership. Lead, hire, and mentor OSS Telemetry Engineers. Set engineering standards, review designs and code, and plan and prioritize the team’s work.
Monitoring platforms. Own the architecture, scalability, and reliability of Prometheus, Grafana, and the ELK Stack, including capacity, retention, high availability, and upgrades. Extend telemetry collection to network functions in orbit and on the ground, including data carried over constrained or intermittent satellite links. Run monitoring as a production service.
Alerting standards and anomaly detection. Set standards for thresholds, severity, routing, and noise reduction. Lead the use of AI-powered anomaly detection, and ensure every critical alert links to evidence, a runbook, and a clear escalation path.
KPIs, SLOs, and service health. Define the network KPI framework and the SLIs and SLOs that matter, working with network, product, and operations stakeholders. Ensure dashboards reflect true service health and support operational and business decisions.
Tracing and logs. Drive standards for distributed tracing and log aggregation so teams can follow faults across services and identify their causes.
Incident leadership and recovery validation. Act as the telemetry escalation point for the NOC during major incidents. Verify recovery through the right metrics and lead post-incident reviews that improve visibility.
Cross-functional partnership. Work with core network, satellite, platform, and SRE teams to build observability into new features from design onward, and make telemetry readiness part of release criteria.
Operational knowledge. Own the training program and documentation for KPIs, dashboards, and runbooks so NOC and engineering teams can interpret telemetry and act independently.
What you bring
Deep expertise in monitoring tools (Prometheus, Grafana, ELK Stack), including designing them for scale, high availability, and long-term retention.
Strong knowledge of distributed systems, microservices architecture, and Kubernetes, and a solid understanding of 5G core architecture and network functions (e.g., AMF, SMF, UPF, NRF).
Proficiency in Python, Linux, and Bash, with experience automating monitoring and alerting workflows.
Experience with cloud platforms; AWS preferred, GCP or Azure also considered.
Hands-on experience defining and operating SLOs, SLIs, SLAs, and error budgets.
A track record of leading incident response and post-incident reviews.
Excellent communication and interpersonal skills, with fluent written and spoken English and the ability to explain service health to both engineers and leadership.
Preferred experience
Familiarity with 3GPP NTN (Releases 17 and 18) and its impact on core network behavior and monitoring.
Experience with OpenTelemetry and with AIOps or ML-based anomaly detection in production.
Experience building or scaling an observability or NOC tooling team.
Experience in a startup or fast-paced R&D environment where architectural decisions move at product speed.
Experience operating or monitoring LEO satellite networks or other systems in orbit.
What success looks like
NOC engineers can see service health, identify performance gaps, and follow clear escalation paths. SLOs are defined, tracked, and reviewed with stakeholders, and every critical alert has an owner, a runbook, and supporting evidence, with low alert noise. Recovery is confirmed through the right metrics. New features ship with observability built in, monitoring platforms scale reliably with the network on the ground and in orbit, and the telemetry team grows into a strong, self-directed group. Training helps teams act independently, and every significant incident leads to measurable improvements in visibility.

