VP of Network Engineering

We are the global marketplace for bandwidth. Share aggregates telco infrastructure into a single intelligence layer, giving ISPs, hyperscalers, and AI companies a seamless path to deliver connectivity into every home and business. Before you read further: deep network expertise is the price of entry for this role, not the thing that will set you apart. We assume you can hold your own in the protocol details. What we're actually hunting for is the person who can run and operationalize the network team, someone who thinks in workflows, team structures, product roadmaps, and cross team collaboration as naturally as they think in routing tables. This is an operator's role with an engineer's foundation. The rare candidate has both an operational, business mind and the technical credibility to back it up, and that combination is exactly the variable we've been looking for. We're hiring a VP of Network Engineering to lead the function that makes this real. This is the senior‑most networking role at Share, reporting directly to the founders. You will own the entire technical estate (backbone, aggregation, access, peering, the systems they depend on, and the partner integrations they touch) and the team that builds and runs it. This is a role for someone who wants to create, not just operate. The mandate is to design the protocols, define the standards, and develop the reference architectures that an entire ecosystem of partner ISPs will inherit from us, and to leverage AI across the operational surface so the network behaves more like a system that thinks than a stack of boxes that's been configured. The expectation is still hands‑on. You'll set technical direction, run a small high‑leverage engineering team, and stay close enough to the daily operations that you can sit on a BGP debug call at 2am and not be the bottleneck. This is also a deeply partner‑facing role: you'll absorb partner ISPs into our platform and push each one past whatever ceiling they walked in with.

2. WHAT YOU'LL OWN

The network as a system Design the protocols, standards, and reference architectures that the rest of the ecosystem inherits from us. Partner ISPs across the continent will adopt the patterns you set (peering policy, hand‑off contracts, AI automations,service profiles, security posture) because conforming to Share's baseline is how they unlock the speeds we deliver. This is closer to standards work than to operations management: it ships as configuration, but it lives as doctrine. Make the architectural calls that don't have a textbook answer yet: how a shared physical backbone is sliced across many partner ISPs at multi‑tenant scale, how policy is expressed once and enforced everywhere, where the control plane goes next, what we retire, and what we keep. Treat the network as a system that learns. Drive the use of AI in operations: anomaly detection across flow and streaming telemetry, predictive failure analysis on optical and routing layers, automated triage and runbook execution, traffic‑engineering and peering decisions informed by models, and config‑drift detection across partner hand‑offs. You won't build the models from scratch, but you'll set the bar for where AI replaces human reaction time and where it doesn't. The routing and peering core Own the strategy for our BGP edge: IP transit with Tier 1 providers, PNIs and Caches with hyperscalers & CDNs, and local IX connections. Own the policy posture: filter chains, route policy, communities, RPKI, and traffic‑engineering logic across our border fabric and downstream. Manage our MPLS backbone (L3VPN and EVPN for partner isolation, services delivery, and multi‑tenant scale) and decide where the control plane goes next (LDP vs. SR, address‑family strategy). Aggregation, access, and the services plane Own the disaggregated, white‑box switching & routing stack: modern NOS stacks on commodity silicon (SONiC, IP Infusion OcNOS, and similar). Direct L2/L3 aggregation (VLANs, MC‑LAG/EVPN‑VXLAN, QoS, clean L2 hand‑offs to partner ISPs) and BNG strategy (PPPoE/IPoE termination, QoS, CGNAT where needed, CoA‑driven session control that hooks into our AAA layer). Own the CPE management plane: TR‑069 / CWMP from the ACS down, TR‑181 data models, ONU and CPE autoconfiguration on first attach, firmware management and staged rollouts across heterogeneous CPE, and the operational discipline to keep a fleet that scales from hundreds of thousands of devices into the millions in a known good state. This is where most access networks quietly degrade; we don't intend to. Partner with the Systems team on the AAA stack (FreeRADIUS proxy architecture, per‑partner containerized instances, Splynx integrations, CoA relay for payment‑driven session control). They own that stack; you own the network‑side of every integration, every session‑control decision, and every end‑to‑end accounting flow. Own the network‑layer services the AAA plane depends on: NAT/CGNAT, DHCP, IPAM, DNS, IP/ASN planning, IPv6, and dual‑stack rollout. The team Hire, develop, and lead the network engineering team, including the junior and senior engineers we'll add as we scale. You set the bar, the culture, and the bench. Build a team that writes things down. Push our source‑of‑truth (Nautobot) and config automation (Jinja‑based generation) forward with the Systems and Dev teams, so the network is driven by data rather than tribal knowledge. Run a team that’s allergic to ticket‑shuffling and bureaucracy: runbooks, post‑mortems, automation, and a real culture of operational discipline. Partner ISPs Lead the technical relationship with our partner ISPs. You'll sit on senior calls with their leadership and engineering teams, walk their networks, and own the technical commitments we make on both sides of the hand‑off. Translate between “this is what we need to deliver 100x speeds on your network” and “this is the concrete change on your OLT, your router, or your peering config tomorrow morning.” Every partner shows up with their own vendor mix and habits (MikroTik on RouterOS, Huawei on access); the job is to bring each one to our baseline and push them past whatever ceiling they walked in with. Own the technical credibility of Share with partners. When their senior engineer is on the call, you should be the person they want on the other end. Uptime and the broader platform Own PoP and backbone reliability end‑to‑end: SLAs, incident response, post‑mortems, and the culture around them. Catch degradations before partners do. Sit at the leadership table as the voice of the network. Inform product decisions, capital allocation on capacity, peering strategy, and how we expand geographically.

3. WHO WE'RE LOOKING FOR

The right person is a builder who happens to have grown into leadership, not an executive who has drifted away from the work. If you've spent the last few years inside a large telco running PowerPoint reviews two layers removed from the CLI, this isn't your role. If you're still close enough to your network to spot a leaky origin from the symptoms before someone hands you a ticket, keep reading. The team you'd be joining is small and very senior: CCIE level network engineers and systems engineers with deep service provider backgrounds. Stepping into the senior seat on a team like this means holding your own on technical substance from day one, not from month six. Must‑have A bias for execution. You'd rather ship and iterate than circulate a strategy memo. Hierarchy and corporate theatre exhaust you. CCIE (Routing & Switching / Service Provider) or equivalent preferred. Long service provider tenure, or comparable hands on credentials taken seriously; the certification is a proxy for the bar, not the bar itself. Senior leadership experience inside an ISP, carrier, or comparable network operator: running a team, owning architecture, and answering for uptime. A real track record of building or leading network engineering teams: hiring, leveling, setting technical direction, and being the person the team escalates to. Deep BGP: route policy, communities, RPKI, route reflection, upstream/peer selection, traffic engineering, and the instincts to debug a leaky origin at 2am, not just direct the people who do. MPLS in production at scale (L3VPN and EVPN), including control‑plane details (LDP, SR, BGP address families) and opinions on where the architecture goes next. Real operational experience with passive optical access (GPON or XGS‑PON), OLT/ONU provisioning, and service modelling. If you haven't run PON, you've run an access network at comparable scale and understand the protocol stack. Comfortable in disaggregated, white‑box environments (SONiC, IP Infusion OcNOS, or similar). You don't need a vendor badge to operate a switch. Nice‑to‑have Experience running or contributing to OcNOS, TR069, FRR, or other open‑source networking stacks. Automation chops (Python, Go, or Bash), especially against NETCONF/gNMI, Nautobot, or Jinja‑driven config pipelines. IPv6 planning and dual‑stack rollout experience at subscriber scale. Working familiarity with FreeRADIUS, CoA/Disconnect flows, and RADIUS‑driven billing integrations. Enough to debug jointly with the Systems team, not to own the stack. Exposure to applying ML or AI in network operations (anomaly detection on telemetry, predictive failure analysis, automated remediation, model‑informed traffic engineering). Prior experience as a founding or early‑stage network leader at a growth‑stage operator.

4. WHAT WE OFFER

Real ownership of strategy, architecture, and execution. No layer of middle management between you and the work. Executive‑level compensation: competitive salary and meaningful equity in a mission‑driven, investor‑backed company (US‑incorporated; Kenya operating entity). Private health and wellness benefits. We'll walk through these during the process. A high‑ownership environment with a steep but well‑supported learning curve. #J-18808-Ljbffr Share