Network Operation Engineer

Network Operations Engineer 1. About the role Share is the global marketplace for bandwidth. We aggregate telco infrastructure into a single layer and give ISPs, hyperscalers, and AI companies a clean path to deliver connectivity into every home and business across Kenya and the continent. Behind that marketplace is a real network: a BGP edge peering with Tier 1 transit, hyperscalers, and local exchanges, an MPLS backbone, aggregation and access gear, and the systems that watch all of it. For the partners who run on us, the network is the product, and the NOC is where they feel it. A clean shift is a partner who never knew anything happened. That is the bar. We are early and the team is small, so we cannot afford a pair of hands that only knows how to escalate. We need a capable network engineer who can stand a shift, resolve real faults without waking anyone, and then keep building the network while East Africa sleeps: propagation and peering checks, health passes across the estate, config changes through to merge, tickets off the board, automation that takes the next repetitive job off everyone's plate. The watching is the floor of this role, not the ceiling. The NOC you would be joining is not a legacy one. We are building it as an AI assisted operations environment from the ground up. The forwarding plane runs on open source routing and forwarding software, every device configuration lives in Git, and an LLM layer sits on top of the live network state. When something moves, that layer reads the telemetry, correlates it against the topology and the config history, and puts a probable cause and a candidate fix in front of the engineer on shift. The point is not to replace your judgment. It is to collapse the time between an alert firing and you knowing where to look, so mean time to repair is measured in minutes. You sit inside that system. You use it, you push back on it when it is wrong, and what you catch that it misses is part of how it gets smarter. As we build automation out across the NOC, you are not just a consumer of the tooling. You help write it. 2. What you'll do Watch, and know what you're looking at. Sit on our monitoring stack (Zabbix and Grafana dashboards, flow telemetry, alerting) and actually read it. Learn what normal looks like so abnormal jumps out at you: a BGP session that dropped, a link that went down, latency climbing on a path, a capacity threshold breached, a partner suddenly pushing or pulling nothing. Troubleshoot and resolve. This is where you earn your seat. Confirm the alert is real, gather the facts, and localise the fault: one peer or many, us or upstream, a real outage or a monitoring blip. The assistive layer surfaces a likely diagnosis and a suggested fix, the config history is right there in Git, and the runbooks are live. Your job is to read all of it critically, decide what is actually true, and close out what you can on your own. Every ticket you resolve yourself is one our senior people did not get p