Staff Network Reliability Engineer

📋 Job Overview

Skylo has pioneered a standards-based approach to satellite connectivity. We connect smartphones and IoT devices directly to satellites. No special hardware, no entirely new networks. Just billions of existing devices, suddenly reachable anywhere on Earth. We're not building toward this future. We're already in it.

🏢 About Skylo

Our direct-to-device service is live on millions of activated devices across five continents, covering more than 72 million square kilometers, in partnership with leading satellite operators, mobile network operators, Tier-1 chipset makers, and OEMs worldwide. And we're just getting started.

🎯 The Role

As a Staff Network Reliability Engineer, Core Operations, in the Global Product Support & Customer Success organization, you are the 5G Core domain authority within Skylo’s production NTN network. Where the Incident Manager coordinates the bridge, you own the technical outcome. You are the escalation target for every Core-domain Sev 1–2 event — the engineer who diagnoses AMF registration failures, SMF session establishment drops, UPF forwarding anomalies, IMS SIP/Diameter failures, and IMSI provisioning breakdowns at a protocol level, and delivers a resolution or a definitive root cause.

✅ Key Responsibilities

• Own 24×7 5G Core health across Skylo’s production NTN stack: AMF/SMF/UPF/AUSF pod status, NAS/NG-AP signaling success rates, session establishment and tear-down metrics, subscriber registration KPIs, IMS registration state, and Core-layer SLA compliance.
• Monitor and triage Core NF alarms using OSS dashboards, Grafana/other inhouse telemetry, and Loki log correlation — distinguish transient anomalies from systemic degradation before escalating or acting.
• Execute and own Core-domain runbooks for P2–P4 fault categories: pod restarts, persistent storage recovery, certificate rotation, IMSI state reconciliation, and BSS-IIS cluster incident response — without requiring engineering team involvement for covered fault classes.
• Maintain DMP certificate management procedures and own escalation to BOSS (BSS & OSS) for DMP outages, certificate rotation failures, and EMS alarm integration issues.
• Own IMSI lifecycle operations: activation, deactivation, KML file management, subscriber state reconciliation, and exception handling for provisioning failures through the OSS platform.
• Serve as the L3 escalation authority for all Core-domain incidents: take ownership from the Incident Manager, diagnose at the protocol level using NAS traces, NG-AP message flows, Diameter/SIP signaling captures, and NF-specific log analysis, and deliver a resolution or a decision-grade root cause.
• Lead Core-domain troubleshooting bridges: command the technical investigation, direct vendor and engineering participants, correlate signals across AMF, SMF, UPF, AUSF, PCF, and IMS NFs, and drive the bridge to a documented resolution or a clear engineering handoff.
• Diagnose and resolve Core failure modes: UE registration failures, PDU session establishment drops, handover interruptions, IMS registration and call setup failures, SEPP interconnect errors, subscriber provisioning mismatches, and signaling loop conditions.
• Engage vendors with technical specificity: reproduce failures with log evidence, own the vendor ticket lifecycle, enforce SLA response commitments, and escalate vendor delays with full impact context.
• Participate in the global 24×7 on-call rotation as the Core domain escalation tier — reachable within defined SLA windows for Sev 1 events; function as the technical decision-maker, not the first responder.
• Own Core-domain RCA end-to-end: lead the post-incident investigation, document the complete causal chain from triggering condition through downstream NF impact, and deliver systemic action items with owners, timelines, and measurable success criteria.
• Deliver Initial RCA documentation within defined SLA windows post-incident closure; own the final RCA through engineering review and sign-off.
• Identify systemic failure patterns — configuration drift, missing alarm coverage, stale thresholds, vendor software defects — and translate them into engineering requirements with clear impact, scope, and acceptance criteria.
• Contribute to the weekly