Strategy & Operations Program Manager, Global Technical Enablement
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must include only sections with real specific content. We need to parse the posting. We have content: intro paragraph about company, then Minimum Qualifications, Preferred Qualifications, About the Job, then description of GTE team, then Responsibilities (list), then Compensation + Benefits (with salary range). Also mention legal right to work, visa sponsorship, EEO, application deadline, etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop EEO statement, visa sponsorship note, application deadline? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Application deadline is likely an application instruction, so remove. Also "Applicants must have the legal right to work..." is legal boilerplate, remove. Also "Wiz is an equal opportunity employer..." remove. Also "By submitting your application..." remove. Also "Learn more about benefits at Google." maybe keep? It's about benefits but it's a link; we can keep benefits section but not that line? It's not boilerplate but maybe okay. However we should keep substantive benefits info: they mention compensation includes base salary + bonus + equity + benefits. Salary range given. So we can have Pay section with salary range. Benefits section maybe we can include generic statement? The posting does not detail specific benefits beyond "benefits". It says "Compensation + Benefits Compensation for this full-time position includes base salary + bonus + equity + benefits." Then later "Learn more about benefits at Google." No specific benefits listed. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation includes base salary + bonus + equity + benefits, and gives US base pay range. So we can have Pay section with salary range. Benefits section: they mention benefits but no specifics; it's vague. Should we include Benefits heading? The rule: never create Benefits section unless posting actually states them. It does state "benefits" generically, but no detail. Might be considered filler? It says "including base salary + bonus + equity + benefits." That is a statement that benefits exist, but no detail. Could be considered substantive enough? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not details. I'd include a Benefits section with a short paragraph: "Benefits include base salary, bonus, equity, and additional benefits (details available via recruiter)." But we must not invent or summarize away detail. We could just include the sentence as is: "Compensation for this full-time position includes base salary + bonus + equity + benefits." That's a statement about compensation, not benefits specifics. Might be better to put that under Pay section? Actually Pay section is for salary range. Benefits section could be omitted if no detail. The rule: "Prefer a few substantive sections over many thin ones." So maybe we just have Pay section and omit Benefits. Also Schedule: not mentioned, so omit. We need sections: About the role (maybe "About the Job" corresponds to About the role). Responsibilities. Requirements (maybe Minimum Qualifications). Qualifications (maybe Preferred Qualifications). Skills? Not explicitly listed but could be derived from qualifications. But we should not invent. So we can have Requirements (Minimum Qualifications) and Qualifications (Preferred Qualifications). Also maybe "About the role" section from "About the Job:" paragraph. We also have introductory paragraph about company; maybe we can include that as a brief
before sections? The instruction: Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. So we can have a leading
with the company overview (the first paragraph). Then sections.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all details from the posting except boilerplate removed.
Let's extract substantive content:
Intro paragraph (first paragraph up to "Minimum Qualifications:"):
"Come join the organization that is redefining security for the AI era. As one of the fastest-growing startups ever, we enable teams to secure cloud and AI applications by connecting code, cloud, and runtime into a single shared context. Trusted by security teams all over the world, we have a proven track record of success and a culture that values world-class talent. Not to mention, we're now powered by Google, meaning we offer our customers an AI-powered platform that harnesses Google’s Threat Intelligence and Security Operations to better detect, prevent, and respond to threats across all environments, allowing for further innovation. Our Wizards from all over the globe work together to protect the infrastructure of our customers, including over 65% of the Fortune 100, who trust us to scan and secure over 230 billion files daily. We’re honored to be a leading player in a massive and growing market, and we continue to look for exceptional Wizards who are eager to make a significant impact on our team. At Wiz, you’ll have the freedom to think creatively, dream big, and use your full range of skills to contribute to our momentous growth. Come join our team and help us create secure cloud environments that allow even the best companies to move faster, all while having some fun!"
That's substantive; keep.
Then "Minimum Qualifications:" list:
- Bachelor's degree in Business, Computer Science, Engineering, or a related field, or equivalent practical experience.
- 5+ years of experience in business operations, strategy, chief of staff roles, or technical program management, including direct support of senior leaders.
- Proven experience managing operational tech stacks, vendor relationships, and tracking organizational budgets/OPEX or business cases.
- Demonstrated ability to write and speak at a leadership altitude, holding the room and influencing cross-functional stakeholders without formal direct authority.
- Exceptional ability to manage multiple complex threads, ensuring nothing is dropped, everything is documented, and decisions result in action.
Then "Preferred Qualifications:" list:
- Experience in an Office-of-the-CxO or serving as a dedicated right-hand to a senior leader in a high-tech environment.
- Familiarity with cloud concepts (e.g., GCP, AWS, or Azure), cybersecurity, technical lab environments, or developer platforms.
- Experience working inside or directly partnering with technical enablement, customer engineering, sales engineering, or customer success organizations.
- Thrives in high ambiguity, capable of inventing structure when priorities shift rapidly across a distributed, global organization.
Then "About the Job:" paragraph:
"As the Strategy & Operations Program Manager for Global Technical Enablement (GTE), you will serve as the operational right hand and proxy to the Head of GTE. This is not a general program-management role; your mandate is to build the operating system that runs the organization and keep the business inspection-ready at all times. You will not have direct reports; instead, your influence and operational rigor will ensure that critical multi-team programs move smoothly from ideation to delivery. You will sit with the Head, be in the room for the decisions, carry their proxy, and govern the organization's technological, financial, and strategic resources. Ultimately, you will own the living story of the business, the cadence, the data narrative, and the cross-cutting initiatives that belong to no single team; ensuring leadership can speak to status, strategy, and risk at a moment's notice."
Then description of GTE team:
"Wiz’s Global Technical Enablement (GTE) team is the end-to-end owner of technical product mastery. We build and execute role-based onboarding, interactive learning journeys, and hands-on lab environments that enable our technical field teams and customers to position, deploy, and optimize complex cloud solutions at scale. Operating across 8 time zones and 6 countries, we pride ourselves on dependability, radical collaboration, and continuous innovation."
Then "To ensure the strategic value of this role is maintained, please note that it is explicitly:" bullet points (these are clarifications):
- Not a layer between the Head and the four team leaders, their direct line is unchanged.
- Not the owner of team execution: Architecture, TLDD, Experiences, and TEDO run their own work.
- Not an Executive Assistant: no calendar, travel, or expense ownership.
These are substantive; we should keep them maybe under a section like "Role Clarifications" but we don't have a heading for that. Could incorporate into About the Job or Responsibilities? Might be better to include as part of About the Job paragraph? But they are separate bullet points. We could create a section "Role Overview" but we already have About the Job. Perhaps we can incorporate them into About the Job as additional prose. However the instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. We can put the clarifications under About the role (About the Job) as prose.
Then "Responsibilities:" list (many items). We need to output as - .
List items:
- Own the Operating Rhythm: Architect and facilitate leadership staff meetings, strategic quarterly planning, and retrospective sessions across the four GTE pillars to ensure tight cross-team alignment.
- Drive the OKR Lifecycle: Partner with leadership to draft, cascade, and track OKRs, proactively mitigating schedule risks before they impact the business.
- Govern the Decision Log: Ensure that nothing agreed upon leaves the room without an owner and a date, and follow through so that initiatives don't stall or quietly die after kickoff.
- Build the Case (Tech Spend & Forecasting): Lead financial forecasting, budget tracking, and business case development specifically for the organization’s enablement infrastructure (lab environments, software licensing, tool subscriptions, and vendor platforms).
- Vendor & Platform Lifecycle: Oversee the end-to-end renewals of GTE platforms, manage vendor relationships, and optimize the operational tech stack.
- Access & Tech Governance: Manage the integration, provisioning, and access logistics for the org's internal and external enablement platforms, ensuring seamless workflows and security compliance.
- Own the "Walking Deck": Maintain a continuously current narrative of the business (org, strategy, OKR status, metrics, risks, and wins) that is ready to present with zero prep.
- Turn Data into Narrative: Partner with analysts to convert central dashboards, learner throughput, and course CSAT into the actionable story leadership needs.
- Anticipate the Inspection: Prepare the Head of GTE for executive reviews, QBRs, skip-levels, and ad-hoc escalations by running dry-runs, producing briefing docs, and pre-empting leadership questions before they are asked.
- Represent the Head: Act as a proxy in forums the Head cannot attend, carrying context in, bringing decisions back, and holding the room at a leadership altitude.
- Stakeholder Alignment: Act as the primary strategic coordination bridge between GTE pillar leads and key external partners (Product Management, Product Marketing, Solutions Engineering, Support).
- Drive Cross-Cutting Programs: Execute high-priority operational shifts, integrations, and strategic rollouts that span across multiple teams and manage complex global dependencies.
Then "Compensation + Benefits" section:
We have: "Compensation for this full-time position includes base salary + bonus + equity + benefits. Our salary ranges are determined by role, level, and location. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Please note that the compensation details listed in US role postings reflect the base salary only, and do not include bonus, equity, or benefits. Learn more about benefits at Google. The US base salary range for this full-time position is listed below. US Base Pay Range $136,000—
for prose. Do NOT repeat the job title as a heading. So we can have a leading
with the company overview (the first paragraph). Then sections. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all details from the posting except boilerplate removed. Let's extract substantive content: Intro paragraph (first paragraph up to "Minimum Qualifications:"): "Come join the organization that is redefining security for the AI era. As one of the fastest-growing startups ever, we enable teams to secure cloud and AI applications by connecting code, cloud, and runtime into a single shared context. Trusted by security teams all over the world, we have a proven track record of success and a culture that values world-class talent. Not to mention, we're now powered by Google, meaning we offer our customers an AI-powered platform that harnesses Google’s Threat Intelligence and Security Operations to better detect, prevent, and respond to threats across all environments, allowing for further innovation. Our Wizards from all over the globe work together to protect the infrastructure of our customers, including over 65% of the Fortune 100, who trust us to scan and secure over 230 billion files daily. We’re honored to be a leading player in a massive and growing market, and we continue to look for exceptional Wizards who are eager to make a significant impact on our team. At Wiz, you’ll have the freedom to think creatively, dream big, and use your full range of skills to contribute to our momentous growth. Come join our team and help us create secure cloud environments that allow even the best companies to move faster, all while having some fun!" That's substantive; keep. Then "Minimum Qualifications:" list: - Bachelor's degree in Business, Computer Science, Engineering, or a related field, or equivalent practical experience. - 5+ years of experience in business operations, strategy, chief of staff roles, or technical program management, including direct support of senior leaders. - Proven experience managing operational tech stacks, vendor relationships, and tracking organizational budgets/OPEX or business cases. - Demonstrated ability to write and speak at a leadership altitude, holding the room and influencing cross-functional stakeholders without formal direct authority. - Exceptional ability to manage multiple complex threads, ensuring nothing is dropped, everything is documented, and decisions result in action. Then "Preferred Qualifications:" list: - Experience in an Office-of-the-CxO or serving as a dedicated right-hand to a senior leader in a high-tech environment. - Familiarity with cloud concepts (e.g., GCP, AWS, or Azure), cybersecurity, technical lab environments, or developer platforms. - Experience working inside or directly partnering with technical enablement, customer engineering, sales engineering, or customer success organizations. - Thrives in high ambiguity, capable of inventing structure when priorities shift rapidly across a distributed, global organization. Then "About the Job:" paragraph: "As the Strategy & Operations Program Manager for Global Technical Enablement (GTE), you will serve as the operational right hand and proxy to the Head of GTE. This is not a general program-management role; your mandate is to build the operating system that runs the organization and keep the business inspection-ready at all times. You will not have direct reports; instead, your influence and operational rigor will ensure that critical multi-team programs move smoothly from ideation to delivery. You will sit with the Head, be in the room for the decisions, carry their proxy, and govern the organization's technological, financial, and strategic resources. Ultimately, you will own the living story of the business, the cadence, the data narrative, and the cross-cutting initiatives that belong to no single team; ensuring leadership can speak to status, strategy, and risk at a moment's notice." Then description of GTE team: "Wiz’s Global Technical Enablement (GTE) team is the end-to-end owner of technical product mastery. We build and execute role-based onboarding, interactive learning journeys, and hands-on lab environments that enable our technical field teams and customers to position, deploy, and optimize complex cloud solutions at scale. Operating across 8 time zones and 6 countries, we pride ourselves on dependability, radical collaboration, and continuous innovation." Then "To ensure the strategic value of this role is maintained, please note that it is explicitly:" bullet points (these are clarifications): - Not a layer between the Head and the four team leaders, their direct line is unchanged. - Not the owner of team execution: Architecture, TLDD, Experiences, and TEDO run their own work. - Not an Executive Assistant: no calendar, travel, or expense ownership. These are substantive; we should keep them maybe under a section like "Role Clarifications" but we don't have a heading for that. Could incorporate into About the Job or Responsibilities? Might be better to include as part of About the Job paragraph? But they are separate bullet points. We could create a section "Role Overview" but we already have About the Job. Perhaps we can incorporate them into About the Job as additional prose. However the instruction: Use