share - VP of Network Engineering

• 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 passive optical access (GPON, XGS-PON, OLT/ONU strategy, service profile design) and the fiber plant itself: ODF and splice planning, OTDR traces, loss budgets, and dark-fiber troubleshooting across our leased routes (KETRACO, KPC, Systel, and the ADC, iColo, PAIX metro ring). • 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. • 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. • 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, all the variations); 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: SLOs, 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. • We care much more about depth, judgment, and ownership than about org-chart titles on a résumé. 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. • Senior leadership experience inside an ISP, carrier, or comparable network operator: running a team, owning architecture, and answering for uptime. Not enterprise networking, and not a pure-corporate role detached from operations. • 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. • Hands-on with MikroTik (RouterOS) and Huawei (access or core). These are on our partners' side of the fence and you'll touch them constantly; you can sit on a partner's CLI and read it as fluently as your own. • Fluent in L2/L3 fundamentals: VLANs, STP family, LACP, OSPF/IS-IS, VRFs, NAT, VPNs, QoS. • Comfortable driving troubleshooting end-to-end (tcpdump, Wireshark, iperf, MTR, packet captures on both ends of a session) and able to lead a team to do the same. • Partner- and customer-facing maturity. You can sit on a call with a partner's engineering team and their leadership, read their network, explain what needs to change, and do it without condescension. This role is technical, but not back-office. • A bias for execution. You'd rather ship and iterate than circulate a strategy memo. Hierarchy and corporate theatre exhaust you. • Based in Kenya, or ready to relocate. You'll be close to our facilities in Mombasa and Nairobi and on calls with partners in the same time zone. • Experience running or contributing to SONiC, FRR, or other open-source networking stacks. • Automation chops (Python, Go, or Bash), especially against NETCONF/gNMI, Nautobot, or Jinja-driven config pipelines. • Internet Exchange operations experience: looking-glass and route-server behaviour, IRR/RPKI hygiene, peering negotiations. • 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. • Any PtP/PtMP wireless background is a plus for partner conversations, but it isn't the job: we are not a WISP. • Prior experience as a founding or early-stage network leader at a growth-stage operator.