Network Operation Engineer

🔥 0 minutes ago

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

Share

WebsiteLinkedInAll Job Openings

11 - 50 employees

Founded 2024

📡 Telecommunications

🏪 Marketplace

☁️ SaaS

Telecommunications • Marketplace • SaaS

Share is a carrier-neutral, open-access network and bandwidth marketplace that aggregates telco infrastructure into a single intelligence layer. It connects fiber routes, ISPs, CDNs, data centers, subsea cables and infrastructure providers to enable enterprises, ISPs, hyperscalers, and AI companies to buy, sell, and trade bandwidth with standardized pricing, SLA-backed services, automated payments via a Share wallet, and public APIs for quick onboarding. Share monetizes underutilized capacity for suppliers and provides buyers with unlimited, redundant backhaul with no commits, focusing currently on deployment across African cities with plans in Europe and the US.

📋 Description

• 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 pulled out of deep work, or out of bed, to deal with. • Keep the network healthy, not just alive. A quiet shift is not an idle one. Run the proactive passes: check that routes are propagating the way they should, that RPKI and filter chains are doing their job, that peering and transit sessions are clean across the edge, that no PoP is drifting toward a capacity wall. Catch the slow degradations that never trip an alert. The day team should inherit a network in a known good state. • Build and automate. The repetitive parts of this job should not stay repetitive. Write the scripts that turn a manual check into a scheduled one. Push our config automation forward (Jinja driven generation, NAPALM or NETCONF/gNMI against the devices) so changes ship from data, not from memory. When the assistive layer keeps missing the same thing, that is a candidate for automation, and you are well placed to build it during the hours nobody else is online. • Move the work forward. You are part of the network team, working the same board they do. Pick up tickets from the Linear queue, take config changes through review to merge, and keep our source of truth (Nautobot) accurate as the estate changes. Real work lands while East Africa is offline, so the team wakes up further ahead than they went to bed. • Report exactly what is happening. For everything you cannot or should not fix alone, the handoff has to be clean: what is wrong, where, since when, what is affected, whether it is getting worse, and what you have already tried. No guessing dressed up as fact. No "the internet is down." A clear, written incident note a senior engineer can act on the moment they open it, and a tidy handover to the East Africa team at the end of your shift. • Escalate well. Know the ladder cold: what you are cleared to touch, what you must not touch alone, and who to bring in for what. Escalating early on a genuine outage is good judgment. Sitting silently on a problem because you were unsure is the one thing that gets people out of bed angry. Handle what you can, raise the rest fast and clearly, and do not turn either dial too far.

🎯 Requirements

• Strong networking competence, held in your hands rather than on paper. CCNA and well beyond it. You understand TCP/IP, routing and switching, IP addressing and subnetting, DNS, DHCP, NAT, and how they behave when they go wrong. • Real troubleshooting instinct. Given a degraded link or a dropped session, you know where to look and what to rule out. You can read BGP session state, follow a path with ping and traceroute, and tell a local fault from an upstream one without waiting to be told. • Working BGP knowledge. Reading communities and route policy, spotting a flap or a leaky origin, understanding how transit, peering, and RPKI behave at the edge. • Comfortable on the gear and the CLI. Linux, network device CLIs, and dashboards are familiar ground. We run MikroTik (RouterOS) across the network and so do many partners, so RouterOS experience is a real plus. • Comfortable working with config in Git. Configuration lives in repos, not on devices. Reading a diff, understanding why a config changed, and proposing one yourself should not be foreign to you. • Some scripting, and the appetite to do more. Bash or Python, enough to automate the repetitive parts away and to grow into our config and automation pipelines. We are not hiring a button pusher. • Clear written English. You can describe a technical situation accurately and briefly so someone picking it up cold understands it instantly. • Calm under pressure and dependable. When the graphs go red you get more precise, not more panicked. You show up for every shift, alert and on time. • Located in New Zealand or a nearby time zone where covering our deep overnight maps onto your normal working day.

🏖️ Benefits

• Competitive salary and private health and wellness benefits • Fully remote