This role is for a network engineer who can troubleshoot end-to-end, not just “check the router” and bounce. You’ll handle incidents across internet and data center networks, work with routing protocols, and live close to Linux, containers, and modern traffic tooling like F5/Nginx.
About Axiom Software Solutions Limited
Axiom Software Solutions Limited supports organizations with infrastructure and cloud operations talent. This role focuses on keeping networks stable, fast, and observable in environments that blend traditional routing with modern containerized platforms.
Schedule
• Remote (United States)
• Type not listed (confirm contract vs full-time)
• Collaboration with globally distributed peers
• Incident-driven work, with ownership expectations
What You’ll Do
• Troubleshoot and resolve network incidents across layers (routing, transport, application paths)
• Support internet and data center network operations with strong uptime focus
• Work with routing and HA protocols (BGP, OSPF, IS-IS, HSRP/VRRP) and VPNs (IPSEC)
• Support monitoring and visibility through tools like SNMP and other observability platforms
• Partner closely with teams working around Kubernetes, containers, and server infrastructure
• Drive owned issues to resolution with clear communication and strong follow-through
• Contribute to automation via scripting and tooling (where applicable)
What You Need
• 3+ years experience supporting internet and data center networks
• Working knowledge of most of: BGP, OSPF, IS-IS, HSRP/VRRP, IPSEC, SNMP
• Familiarity with Kubernetes, containers, and servers (enough to troubleshoot the full path)
• CentOS/Red Hat experience
• Strong troubleshooting skills with proven ability to resolve complex issues
• Clear communication and strong ownership mindset
• Ability to collaborate effectively with global teams
Nice to Have
• F5 and/or Nginx experience (strongly desired)
• Linux/Unix networking expertise
• Scripting or automation: shell, Perl, Python, Ansible
• Monitoring tools: Watch4Net, Cacti, Splunk
Benefits
• Not listed (confirm pay, hours, on-call expectations, and whether this is more ops or project work)
Quick reality check: they’re mixing “network engineer” with “cloud-native adjacency” (Kubernetes, containers). If your resume reads purely like classic routing and switching, add 2–3 bullets showing you’ve troubleshot traffic into k8s services, worked with ingress/load balancing (F5/Nginx), or partnered with SRE/dev teams.
Happy Hunting,
~Two Chicks…