Technical Cloud Operations Lead

Responsibilities

• Establish and help shape the Cloud Operations capability, including clear ownership and operating practices for routine production changes across cloud environments.
• Build an initial service catalog with procedures, risk boundaries, verification steps, rollback paths, and escalation points.
• Take hands-on ownership of appropriate cloud operations and recurring campaigns through verification and completion.
• Reduce routine operational work requiring ad hoc involvement from Platform Services and SRE engineers.
• Partner with Platform Services, SRE, and Support to identify recurring friction and improve automation, tooling, documentation, and self-service.
• Improve visibility into Cloud Operations performance using measures such as operational volume, exceptions, verification time, engineering escalations, and paved-road coverage.
• Help build operational controls and evidence practices for increasingly complex and regulated customer environments.
• Standardize, automate, delegate, or eliminate recurring problems.

Requirements

• Experience in production cloud or SaaS environments in Cloud Operations, Production Operations, Site Reliability Engineering, Platform Operations, DevOps, Application Operations, or a similar technical operations function.
• Familiarity with cloud-native technologies and concepts.
• Experience making recurring or loosely defined operational work structured, documented, and repeatable.
• Strong operational judgment and ability to recognize when to follow procedures, investigate, stop, or involve engineering partners.
• Comfort using logs, monitoring, deployment output, configuration, and other technical signals to understand system state.
• Systems mindset focused on simplifying, standardizing, automating, or eliminating repeated work.
• Strong ownership and follow-through, including verification, documentation, and production-change closure.
• Ability to collaborate across engineering and customer-facing teams and turn operational problems into actionable improvements.
• Clear written and verbal communication for documenting procedures, explaining risk, coordinating changes, and escalating exceptions.

Nice-to-haves

• AWS experience.
• Kubernetes experience.
• Scripting experience.
• Infrastructure-as-code experience.