Infrastructure Operations Engineer (remote work)

CloudLinux is a global remote-first company. We are driven by our principles: do the right thing, employees first, we are remote first, and we deliver high-volume, low-cost Linux infrastructure and security products that help companies to increase the efficiency of their operations. Every person on our team supports each other and does what we can to ensure we all are successful. Check out our website for more information: cloudlinux.com We are looking for an Infrastructure Operations Engineer (Linux) to join the CloudLinux Infrastructure Team . Our Operations (L1) team provides access, compute resources, and internal services, operates production infrastructure, and improves recurring operational work through documentation and automation.

This job is perfect for you if you: Can independently troubleshoot Linux systems and networked services Take ownership of tickets and incidents through verified resolution or a clear escalation Make standard production changes safely, with rollback and post-change verification Communicate clearly with requesters and remote teammates Look for practical ways to improve recurring work through documentation and automation

As part of the Infrastructure team, you will: Handle onboarding, offboarding, and access-management requests under established procedures: least privilege, the right approvals, and a check that the requested action actually works, not just the login Own common Linux and infrastructure requests and incidents from triage through verified resolution or escalation to a named owner Execute and verify standard host provisioning and production-server changes across bare metal, private cloud, and public cloud environments; escalate exceptions Troubleshoot DNS and perform approved DNS and domain-management changes under established procedures Execute approved firewall and operating-system changes with rollback and post-change verification Monitor infrastructure and respond to alerts and incidents. Judge recovery by whether people can do their work, not by a green status page, and send regular updates until recovery is confirmed. Tell alert noise from real damage, and fix the routing or ownership of an alert instead of silencing it Handle Jira requests according to agreed priorities and response times, keeping requesters informed Deploy standard services from approved specifications and runbooks; escalate design decisions Document recurring procedures for backup coverage and improve onboarding, offboarding, and access reviews through small automation changes