Systems and Network Administration · Remote

Remote

Site Reliability Engineer

GoDaddy · Remote · Posted Aug 25, 2026

This posting comes from GoDaddy. Confirm the details on their site before applying.

Overview

Global Compute runs Optimised Hosting, GoDaddy's global platform for all customer hosting products. Squad R is the engineering team responsible for operating, scaling, and continuously improving the OpenStack-based clouds that power that platform. We treat reliability as an engineering problem: we automate toil away, we plan capacity ahead of demand, and we instrument everything so that we understand our systems before they surprise us.

Responsibilities

  • Operate and scale GoDaddy's cloud infrastructure, including our OpenStack-based hosting platform. You'll troubleshoot and improve services spanning compute, networking, and storage in large-scale production environments.
  • Drive the OpenStack migration. Help move customer hosting workloads onto the platform safely — designing and executing migration tooling, validation, and rollback strategies that protect customer experience.
  • Work within a large-scale global hosting environment supporting thousands of servers and customer workloads across multiple regions.
  • Eliminate toil through automation. Build and maintain automation in Python and Puppet to replace manual operational work. Treat repeated manual effort as a bug to be fixed.
  • Strengthen observability. Improve monitoring, alerting, and dashboards so that signal reaches the right engineer at the right time, and so that we can reason about system behavior from data.
  • Participate in on-call and incident response. Take a fair share of the on-call rotation, lead incident response when you're the responder, and drive the blameless post-incident process that turns failures into permanent fixes.
  • Raise the engineering bar. Review peers' code and designs, document systems and runbooks clearly, and mentor SRE engineers.
  • Contribute to the AI/MCP initiative. Help bring AI-assisted workflows and internal MCP tooling into our operations so internal customers can resolve problems and incidents faster.
  • Participate in a shared on-call rotation (after onboarding) and help lead incident response activities when needed.

Requirements

  • 5+ years in SRE, infrastructure, platform, or systems engineering roles operating production systems at scale.
  • Strong Linux systems fundamentals — networking, storage, processes, performance troubleshooting.
  • Proficiency in Python for automation and tooling (writing maintainable, tested code — not just scripts).
  • Hands-on experience operating distributed systems and diagnosing issues across service boundaries.
  • Experience with infrastructure-as-code and configuration management (Puppet, Ansible, or equivalent).
  • Comfort owning production reliability: on-call experience, incident response, and a track record of reducing toil through automation.
  • Clear written and verbal communication — able to document systems, write post-incident reviews, and collaborate across a distributed, remote team.

Preferred qualifications

  • Experience operating OpenStack (Nova, Neutron, Ceph) or comparable cloud infrastructure platforms
  • Experience with Docker, Kolla, or containerised infrastructure
  • Experience supporting large distributed systems at scale
  • Experience operating Ceph or other software-defined storage at scale.
  • Exposure to OpenStack migration or cloud-migration programs.
  • Interest in applying AI/LLM tooling to operational workflows.

Benefits

  • Drive the OpenStack migration.
  • Help move customer hosting workloads onto the platform safely — designing and executing migration tooling, validation, and rollback strategies that protect customer experience.
  • Eliminate toil through automation.
  • Build and maintain automation in Python and Puppet to replace manual operational work.
  • Treat repeated manual effort as a bug to be fixed.
  • Strengthen observability.
  • Improve monitoring, alerting, and dashboards so that signal reaches the right engineer at the right time, and so that we can reason about system behavior from data.
  • Participate in on-call and incident response.
  • Take a fair share of the on-call rotation, lead incident response when you're the responder, and drive the blameless post-incident process that turns failures into permanent fixes.
  • Raise the engineering bar.
  • Review peers' code and designs, document systems and runbooks clearly, and mentor SRE engineers.
  • Contribute to the AI/MCP initiative.

Great fits start here.

Whether you're looking for your next role or your next team member, give people and possibilities a place to meet.