Technical Project Manager, Carrier Integrations

The Role

Gigs is opening new markets faster than at any point in its history, and every one of them starts the same way: integrating a Mobile Network Operator, the carrier whose network our product runs on. Every carrier integration is a program spanning technical build, commercial alignment, and regulatory compliance across teams inside and out. Owning the mechanics of how we integrate and upgrade carrier integrations is the job.

You'll sit inside a dedicated integration squad alongside a Network Product Manager, Network Engineers, and Connectivity Operations. You're the one who gets into the weeds: reading a carrier's API and network documentation to work out what's actually supported, scoping the integration, and driving it end-to-end from signed contract to live traffic, chasing down and resolving whatever blocks it along the way.

Technical Project Management, Carrier Integration is a new function at Gigs, still early enough that the team, tools, and playbook are being built as we go. That means being hands-on from day one: technical enough to read a carrier's API documentation, sit in architecture conversations with Engineering as a peer, and make the calls that keep an integration on time, while also helping shape how this role and the function work as we scale into new markets.

What You Will Do

• Orchestrate the integration program. Master timelines, carrier status trackers, risk and decision logs, and launch-readiness checklists, the single source of truth for every integration. You own the playbook.
• Set the pace for the whole squad. Internal teams and the carrier run on the same plan, and you hold both accountable to it.
• Own delivery end-to-end. Track milestones, dependencies, and risk across an integration build, and drive resolution across Product, Engineering, and Connectivity Operations, not just report status.
• Partner with Engineering as a technical peer. Understand API contracts, eSIM/interconnect flows, and network configuration well enough to ask the right questions in architecture discussions and unblock decisions.
• Turn carrier documentation into an execution plan. Read a carrier's technical specs and API docs directly, and translate them into a clear, sequenced build plan the cross-functional integration team can run against.
• Run technical alignment, not just meetings. Agendas, decision logs, and follow-through matter, but the value is spotting a technical or timeline risk before it becomes a blocker.
• Be the connective tissue. Across Gigs, the carrier, and third-party vendors: escalate the right thing to the right person at the right time.
• Help build the playbook. As an early hire into the function, shape the tools, templates, and process for how Gigs runs carrier integrations technically, rather than inheriting one.

What You Will Need

• 5+ years in a technical program/project management, technical delivery, or solutions/partner engineering role at a technology company, with hands-on experience running API-based integrations.
• Comfortable reading API documentation and technical specs directly, and able to hold a substantive technical conversation with engineers about architecture and tradeoffs, not just relay one.
• A track record of owning ambiguous, multi-stakeholder builds end-to-end, including external partners, from kickoff to launch.
• A sharp, structured communicator who can drive alignment across Engineering, Product, and external carrier or vendor stakeholders, including at leadership level.
• A bias to unblock: you spot risk early and drive it to resolution rather than escalate and wait.
• Energized by building something from scratch. This is a new function, and you'll help define how it works, not just execute an existing playbook.

Nice to have:

• Prior exposure to telecom, MVNO, eSIM, or carrier/network operator ecosystems (not required).