Director, Cloud Governance

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. No Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of role, remote opportunity, etc. - Responsibilities: list of duties: Build & Lead Cloud Governance, Define & Enforce Cloud Guardrails, Standardize Cloud Structure, Tagging & Governance, Stakeholder Partnership, AI-Forward Governance & Automation. - Requirements/Qualifications/Skills: The posting has "What We're Looking For" with bullet points: 10+ years..., 3–5+ years leading teams..., Experience operating..., Proven track record..., Experience managing..., Deep hands-on..., Strong experience..., Experience with policy-as-code..., Strong understanding... This could be considered Requirements or Qualifications. Also maybe Skills: Infrastructure as Code, policy-as-code, etc. - Benefits: "In addition to base pay, employees may be eligible for equity, bonuses, and a comprehensive benefits package, including healthcare benefits, retirement benefits, pet insurance, paid holidays, paid Scopely free days, and unlimited paid time off." - Pay: "For candidates in CA, CO, NJ, NY, and WA, the annual salary range is provided below. ... Base pay offered may vary depending on job-related knowledge, skills, and experience. CA, CO, NJ, NY, and WA Annual Salary Range $175,000 - $210,000 USD" - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - About Scopely: That's company description; could be considered "About the company" but not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? Probably not; but we could include as part of About the role? The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also include other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings; but we can also include other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. However they also say "Prefer a few substantive sections over many thin ones." So we could combine some. We need to include all substantive info. The company description (About Scopely) is substantive; we could put it under "About the role" or maybe a separate "About Scopely" heading, but that's not in the list. Safer to include it under "About the role" as part of role description? Might be okay. We must not include boilerplate like EEO, scam warning, privacy notices, etc. Remove those. We must not include duplicated lines. We must not include application instructions. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Thus we will strip out the "Notice to Candidates:" paragraph and everything after that (including privacy notices, EEO statement). Also remove the "About Scopely" paragraph? It's not boilerplate; it's substantive about company. We'll keep it. Now structure:

About the role

Scopely is seeking a Director, Cloud Governance to lead efforts in establishing and enforcing standards, policies, and guardrails across Scopely’s multi-cloud environment. This is a remote opportunity for individuals in Canada or the United States. As a Director, Cloud Governance you will play a pivotal leadership role in defining and executing the Scopely’s Cloud Governance strategy. This team will define, implement, and enforce the policies and controls that govern how cloud infrastructure is used across a decentralized organization of game, platform, and product teams. This role is critical to bringing structure, consistency, and guardrails to Scopely’s cloud footprint, and will be key in modernizing our overall governance posture. As a central leader, you will drive alignment across highly autonomous teams and translate governance into practical, adoptable solutions while balancing control and development velocity. This is a foundational leadership role; you will establish governance from the ground up, introduce scalable and enforceable controls, and drive adoption and buy-in across various teams, stakeholders, and senior leaders.

Maybe also include company description after that? Could add another paragraph about Scopely. But we might want to keep About the role focused on role; company description could be separate heading "About Scopely". However not in list; but we could still use

for any heading; the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to include company description within About the role as a paragraph. Now Responsibilities: we need to list duties. We have bullet points under "What You Will Do". We'll create

• for each. List: - Build & Lead Cloud Governance - Build and lead a Cloud Governance team - Define the operating model for how governance partners with game teams, security, and FinOps - Establish clear ownership and enforcement mechanisms for cloud policies - Define & Enforce Cloud Guardrails - Design and implement enforceable controls across AWS and GCP, including: - AWS Organizations, Service Control Policies (SCPs) - GCP Organization Policies and IAM constraints - Establish guardrails around: - Resource provisioning and service usage - Region restrictions and data residency - Identity and access management - Network architecture and environment isolation - Own the mandate to enforce policies, including the ability to restrict or block non-compliant usage - Standardize Cloud Structure - Define and implement standards for: - AWS account structure and GCP project/folder hierarchy - Environment segmentation (prod, staging, dev) - Naming conventions and resource organization - Bring consistency across a fragmented, multi-team cloud footprint - Tagging & Governance - Define and enforce tagging standards in partnership with FinOps - Ensure all resources are attributable (ownership, environment, cost center) - Enable downstream cost allocation and operational visibility - Stakeholder Partnership - Collaborate with FinOps on cost allocation and optimization levers (budgets, quotas, usage controls) - Partner with Security to align governance with security and compliance requirements - Work directly with game teams to safely roll out and drive adoption of policies and standards - AI-Forward Governance & Automation - Define and execute an AI-native vision for cloud governance, transforming the function into an intelligent, policy-driven operating model powered by autonomous and agentic systems - Establish the organization’s strategy for governance autonomy, defining where fully autonomous operations, human-on-the-loop oversight, and human-in-the-loop approvals are appropriate based on risk, business impact, and compliance requirements - Architect and drive agentic governance capabilities that continuously monitor cloud environments, detect risk, and autonomously remediate anomalies at scale - Partner across engineering, data, and security, and platform teams to embed responsible AI governance into cloud platforms, establishing guardrails for AI adoption, autonomous decision-making, and auditability We could flatten into a single list of responsibilities, but better to keep subheadings? The instruction only says use

  for section headings, not subheadings. Could use

  ? Not allowed? They didn't forbid other tags, but they said use

  for section headings. Could still use

  for subheadings but maybe not needed. We could just list each responsibility as a

  with the detailed description inside. Simplify: each major bullet as a

  containing the description. We'll produce:

  • Build & Lead Cloud Governance: Build and lead a Cloud Governance team; define the operating model for how governance partners with game teams, security, and FinOps; establish clear ownership and enforcement mechanisms for cloud policies.
  • Define & Enforce Cloud Guardrails: Design and implement enforceable controls across AWS and GCP, including AWS Organizations, Service Control Policies (SCPs) and GCP Organization Policies and IAM constraints; establish guardrails around resource provisioning and service usage, region restrictions and data residency, identity and access management, network architecture and environment isolation; own the mandate to enforce policies, including the ability to restrict or block non-compliant usage.
  • Standardize Cloud Structure: Define and implement standards for AWS account structure and GCP project/folder hierarchy, environment segmentation (prod, staging, dev), naming conventions and resource organization; bring consistency across a fragmented, multi-team cloud footprint.
  • Tagging & Governance: Define and enforce tagging standards in partnership with FinOps; ensure all resources are attributable (ownership, environment, cost center); enable downstream cost allocation and operational visibility.
  • Stakeholder Partnership: Collaborate with FinOps on cost allocation and optimization levers (budgets, quotas, usage controls); partner with Security to align governance with security and compliance requirements; work directly with game teams to safely roll out and drive adoption of policies and standards.
  • AI-Forward Governance & Automation: Define and execute an AI-native vision for cloud governance, transforming the function into an intelligent, policy-driven operating model powered by autonomous and agentic systems; establish the organization’s strategy for governance autonomy, defining where fully autonomous operations, human-on-the-loop oversight, and human-in-the-loop approvals are appropriate based on risk, business impact, and compliance requirements; architect and drive agentic governance capabilities that continuously monitor cloud environments, detect risk, and autonomously remediate anomalies at scale; partner across engineering, data, and security, and platform teams to embed responsible AI governance into cloud platforms, establishing guardrails for AI adoption, autonomous decision-making, and auditability.

  Now Requirements/Qualifications/Skills. We have "What We're Looking For" bullet list: - 10+ years in cloud infrastructure, platform engineering, or SRE - 3–5+ years leading teams in complex, multi-team environments - Experience operating in decentralized or federated engineering organizations - Proven track record implementing cloud governance and enforcement at scale - Experience managing or influencing environments with $50M+ cloud spend - Deep hands-on experience with AWS and/or GCP - Strong experience with Infrastructure as Code (e.g., Terraform) - Experience with policy-as-code and governance tooling (e.g., OPA, Sentinel, AWS Config) - Strong understanding of cloud networking, identity, and multi-account design We could split into Requirements (years, experience) and Skills (technologies). But we can combine into one section "Requirements" and maybe another "Skills". The instruction allows both. We'll create:

  Requirements

  • 10+ years in cloud infrastructure, platform engineering, or SRE
  • 3–5+ years leading teams in complex, multi-team environments
  • Experience operating in decentralized or federated engineering organizations
  • Proven track record implementing cloud governance and enforcement at scale
  • Experience managing or influencing environments with $50M+ cloud spend

  Skills

  • Deep hands-on experience with AWS and/or GCP