Posted Jul 11, 2026

Senior Cloud Network Engineer (remote-only, worldwide remote)

Apply for this Position →

CloudLinux and TuxCare build Linux, security, and enterprise infrastructure products used by hosting providers, software vendors, and engineering teams around the world. The Infrastructure team runs the platforms behind that work: data centers, public cloud providers, OpenNebula, Kubernetes/Talos, Ceph, CI/CD, observability, identity and access systems, and internal services.

We are hiring a hands-on Senior Cloud Network Engineer to own and evolve the network layer of our hybrid infrastructure. This is an engineering role with real architecture ownership: you will design, implement, monitor, document, automate, secure, and troubleshoot production networking across data centers, cloud regions, Kubernetes/Talos clusters, OpenNebula environments, and bare metal.

This is a technical ownership role. It is not a diagrams-only architecture position, and it is not a people-management role. You will define technical solutions, ship production changes, verify behavior, support incidents, and leave behind the runbooks, diagrams, and automation that make the next change safer.

How We Work:

We are a remote-first Infrastructure team organized into small senior cells. You will work with one existing network engineer, core infrastructure engineers, and adjacent Infrastructure teams. Networking is a high-impact shared dependency, so we value calm incident work and automation that reduces repeat pressure. The value of this role is turning complex demand into reliable systems, clear ownership, safer changes, and observable operations.

This role is a strong fit if you enjoy moving between architecture, packet captures, production configuration, monitoring, runbooks, rollback plans, and failure drills. You should want real ownership of cross-DC, on-prem, private cloud, and public/provider infrastructure.

It is probably not the right fit if you are looking for a pure architecture role, a large dedicated network team, only planned project work, no incident participation, or manual CLI-only changes without documentation, review, automation, and validation.

What You Will Own:

What Success Looks Like:

Requirements

What You Bring:

Nice to Have:

These capabilities are beneficial but not mandatory for every candidate.

Benefits

What's in it for you?

By applying for this position, you consent to the processing of your personal data as described in our Privacy Policy ( ), which provides detailed information on how we maintain and handle your data.

Originally posted on