Principal Product Manager, Networks

About Skylo

Skylo is a global Non-Terrestrial Network service provider based in Mountain View, CA, offering a service that allows smartphone and IoT cellular devices to connect directly over existing satellites. Skylo’s direct-to-device service is now live on millions of activated devices across five continents, with more than 60 million square kilometers of coverage, in partnership with multiple satellite operators, mobile network operators (MNOs), Tier-1 chipset makers, and OEMs.

Devices connected over satellite are managed and served by Skylo's commercial NTN vRAN, featuring a 3

GPP standards-based cloud-native base station and core. Skylo provides an anywhere, anytime connectivity solution that seamlessly roams between terrestrial and satellite networks. Our focus is on enabling connected services for people outdoors and connected workflows across three main verticals: mass-market consumer devices, automotive, and industrial IoT.

Location:

Mountain View, CA – onsite 3 days a week in office. However we remain open to considering remote arrangements for the right candidate.

Skylo is looking for a Principal Product Manager with a strong Telco/MNO/MVNO focus who operates as a high‑agency “autopilot” for our most complex technical and commercial challenges. You are the technical authority, part Product Strategist, part Architect, and part Fixer. Your primary mandate is to manage the end-to-end (E2E) onboarding and integration of our service with Mobile Network Operators (MNOs) and Mobile Virtual Network Operators (MVNOs).

This role is singularly focused on achieving integration success with MNOs and MVNOs, covering everything from technical validation to operational handoff, and ensuring Skylo's network solutions are innovative and relevant in a rapidly changing satellite industry. This role requires a rare ability to bridge technical and commercial realities: you must be able to read the code to understand a module failure and read the contract to understand our leverage in fixing it.

• Own the end-to-end (E2E) integration and launch process with M(V)
  NO partners, spanning initial technical validation through full commercial deployment and operational handoff.
• Serve as the central Product point of contact for M(V)
  NO integration efforts, collaborating closely with stakeholders for M(V)
  NO success.
• Proactively assess the evolving satellite-to-device industry landscape, including competitive dynamics, to identify and drive innovative, disruptive network solutions that enable M(V)
  NOs to offer next‑generation satellite‑based connectivity.
• Act as Skylo's key representative in relevant industry and standardization bodies, such as GSMA working groups, to influence technical specifications and represent our commercial interests.
• Define the technical standard and architectural direction for M(V)
  NO connectivity, ensuring alignment across Skylo's network products.
• Rapidly diagnose, propose technical or product fixes, and drive the implementation with engineering for critical, high‑stakes M(V)
  NO integration blockers or network‑related issues.
• Own and influence the Technical Product Roadmap for key M(V)
  NO partners, defining required features and leading high‑stakes technical engagements (e.g., with Tier‑1 MNOs) to ensure native support for critical Skylo features within the M(V)
  NO network stack.
• Bridge business requirements and network reality by challenging M(V)
  NO partners on technical grounds to deliver performant and reliable network‑based products.

• 15+ years of related experience in product management, wireless systems engineering, or M(V)
  NO/Telco ecosystem engagements (or 12+ years with a Master’s degree).
• Expert‑level knowledge of a M(V)
  NO end‑to‑end (E2E) stack and operational structure. This is a critical requirement.
• Deep understanding of the mobile wireless stack, telco network stack. You must be technically credible with Engineering.
• Experience with 3
  
  GPP Release standards & GSMA Working groups is preferred.
• A rare ability to context‑switch between technical deep‑dives (e.g., analyzing M(V)
  NO network logs) and legal/commercial details…