Cloud Governance Engineer

Join us in bringing joy to customer experience.  Five9 is a leading provider of cloud contact center software, bringing the power of cloud innovation to customers worldwide.   

Living our values everyday results in our team-first culture and enables us to innovate, grow, and thrive while enjoying the journey together. We celebrate diversity and foster an inclusive environment, empowering our employees to be their authentic selves. 

This is a governance role, not a build-and-operate role. You will spend your time defining the rules our cloud estate runs by, making those rules enforceable in code, and proving they are working. You will write standards that other engineering teams have to follow, and you will be the person who explains to Finance, Security, and Product leadership why a given risk matters and what it will cost to fix or ignore.

If what you want is to build and run infrastructure, this is not the right seat. If you want to own how a multi-cloud estate is governed, it is.

About our estate: roughly 70% Google Cloud, with AWS and Azure in scope as secondary platforms. GCP is where the majority of the work sits, so hands-on GCP experience is a hard requirement rather than a preference.

Key Responsibilities

• Define, document, and maintain cloud governance policies and standards across GCP, AWS, and Azure, and turn them into enforceable technical controls using GCP Organization Policy, AWS SCPs and Config, and Azure Policy
• Own the exception and waiver process end to end: intake, risk assessment, time-bound approval, expiry, and follow-up
• Partner with Security to enforce Identity and Access Management and network security standards across the organization, and review access models for least privilege
• Build and maintain dashboards that track governance metrics: security posture, key and credential rotation, policy violations, configuration drift, and time to remediation
• Own resource labeling and tagging standards and enforce them, so that cost, ownership, and environment can be attributed reliably
• Drive cost governance: spend visibility and showback, anomaly detection, commitment and discount coverage reviews, and surfacing waste to the teams that own it
• Collaborate with IT, Finance, Security, DevOps, Cloud Architects, and Product Engineering to keep governance controls consistent across all environments, and translate technical risk into language those stakeholders can act on
• Work with stakeholders to define service level objectives, key performance indicators, and metrics for operational efficiency
• Support the review of new third-party cloud services before they enter the estate