Senior Technical Program Manager, Security
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include.
Content:
- Intro paragraph about company: "Come join the organization that is redefining security for the AI era..." etc. That's prose.
- Minimum qualifications: list bullet points.
- Preferred qualifications: list bullet points.
- About the job: description.
- Responsibilities: list bullet points.
- Compensation + Benefits: includes description of compensation: base salary + bonus + equity + benefits, salary range, note about US base pay range.
- Also note about legal right to work, visa sponsorship, equal opportunity, privacy policy, application deadline. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove equal opportunity statement, privacy policy, application deadline? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the equal opportunity paragraph, the privacy policy sentence, and the application deadline. Also "Applicants must have the legal right to work in the country where the position is based, without the need for visa sponsorship. This role does not offer visa sponsorship." That's maybe not boilerplate but could be considered a requirement? It's about eligibility. Might be considered substantive? It's not a list but a statement. Might keep as a short paragraph? The instruction says fold minor metadata into a short
or drop it. This is about eligibility; could be considered minor metadata. Probably we can drop it or keep as a short p. But we need to preserve ALL substantive information. Is eligibility substantive? Possibly yes, but it's not a qualification. The instruction says we can fold minor metadata into a short
or drop it. So we could include a short p for that.
We also have "Learn more about benefits at Google." That's a link? Might be considered boilerplate? It's a reference. Might keep as part of compensation section.
We need to avoid creating sections with filler. So we need sections: About the job (maybe "About the role"), Responsibilities, Minimum qualifications (maybe "Requirements" or "Qualifications"), Preferred qualifications (maybe "Skills"), Compensation + Benefits (maybe "Pay" and "Benefits"? But we have both compensation and benefits described together. Could make a single section "Compensation + Benefits" but the allowed headings list includes Benefits, Pay, Schedule. We could use "Pay" for salary range and "Benefits" for benefits description. However the posting mentions base salary + bonus + equity + benefits, and gives US base pay range. It also mentions "Learn more about benefits at Google." So we could have a Pay section with salary range, and a Benefits section with description of benefits (bonus, equity, benefits, learn more). But we need to avoid filler. The posting does give specifics: base salary + bonus + equity + benefits, salary range $189k-$258k. That's specific. So we can include Pay section with that range. Benefits section: mention bonus, equity, benefits, and link to learn more about benefits at Google. That's specific enough.
We also have Schedule? Not mentioned. So we skip Schedule.
We also have "About the job" which could be "About the role". We'll use
About the role
with prose.
Responsibilities: list.
Minimum qualifications: list.
Preferred qualifications: list.
We could combine Minimum and Preferred into Requirements and Skills? But better to keep separate as they are distinct.
We need to avoid duplication: The posting repeats some sentences: "Partner with heads of practice to develop and manage a unified security and compliance framework across the organization." appears twice in responsibilities. We should deduplicate.
Also "Partner with heads of practice to develop and manage a unified framework across the team." duplicate.
We need to preserve all substantive information but remove duplicated lines. So we should include each unique responsibility once.
Let's extract responsibilities bullet points:
- Drive large-scale, multi-team programs spanning security, IT, and engineering teams from strategy through execution.
- Coordinate cross-functional leadership and technical owners across security, legal, engineering, and business teams to align on priorities, dependencies, and shared outcomes.
- Partner with heads of practice to develop and manage a unified security and compliance framework across the organization.
- Own end-to-end project / program governance, tracking risk, scope, and timelines, and proactively surfacing blockers to leadership.
- Partner with heads of practice to develop and manage a unified framework across the team. (duplicate of previous? Slightly different: "across the team" vs "across the organization". Might be considered similar but we can keep both? Might be duplicate-ish. We'll keep one maybe combine? Safer to keep both as they are slightly different but could be considered duplicate. The instruction says remove duplicated lines. So we should keep only one instance. We'll keep the first: "Partner with heads of practice to develop and manage a unified security and compliance framework across the organization."
- Integrate various external drivers and frameworks to streamline and automate efforts.
- Ensure controls are applied correctly in alignment with Wiz business objectives.
- Proactively assess and mitigate associated risks with industry frameworks and ensure the organization's overall risk posture is managed effectively.
- Stay informed about evolving customer expectations and adjust approach accordingly to meet new requirements.
- Drive continuous improvement by integrating realized events into controls framework.
- Collaborate across teams fostering a culture of compliance within Wiz.
That's the list.
Now Minimum qualifications bullet points:
- BA/BS degree in Management Information Systems, Computer Science or related Information Technology field, or equivalent practical experience.
- 10+ years of experience in Security, IT or Compliance.
- Proven understanding of the security and compliance landscape, including prevalent threats, compliance frameworks (SOX), existing technologies and security architectures.
- Ability to manage multiple priorities and meet deadlines in a fast-paced environment.
Preferred qualifications bullet points:
- Deep understanding of regulatory landscapes.
- Technical project and program management track record in technology domains.
- Thrives in ambiguous, high-growth environments where priorities and scope can shift quickly.
- Demonstrated experience presenting technical concepts to technical and non-technical audiences.
- Strong leadership, strategic thinking, and the ability to bridge the gap between technical aspects and business goals.
- Leadership through collaboration, a bias for action, and experience working within fast-paced, high performance teams.
- Strong technical background with a deep understanding of software development processes
- Proven creative problem-solving, analytical skills, and a collaborative, team-player work style.
- Cybersecurity certifications a plus (CISM, CISSP, etc).
Now About the job paragraph: "Wiz is looking for a senior leader to join our security team. The Senior Technical Program Manager will have the ability to protect cloud-native SaaS software companies and be able to balance risk mitigations with the demands of supporting a hyper-growth organization. Your key responsibilities include aligning security and compliance initiatives with strategic goals, optimizing processes to enhance efficiency, and measuring the tangible benefits derived from compliance efforts. The Senior Technical Program Manager focuses on demonstrating the positive impact of compliance on Wiz's performance, risk mitigation and customer satisfaction. This person will work directly for the Head of Security Program Management and focus on breaking down silos, optimize processes and foster collaboration between security practices."
We can keep that as prose.
Now Compensation section: Pay: US Base Pay Range $189,000—$258,000 USD. Also note that compensation includes base salary + bonus + equity + benefits. Salary ranges determined by role, level, location. Within range, individual pay determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Recruiter can share more about specific salary range for preferred location during hiring process. Note that compensation details listed in US role postings reflect base salary only, and do not include bonus, equity, benefits. Learn more about benefits at Google.
We need to avoid filler. This is specific enough.
Benefits section: Could mention base salary + bonus + equity + benefits, and learn more about benefits at Google. But we already mentioned bonus, equity, benefits in Pay section? Might be redundant. Better to have Pay section for salary range, Benefits section for bonus, equity, benefits and link.
Thus:
Pay: US Base Pay Range $189,000—$258,000 USD (base salary only). Note that individual pay determined by location, skills, experience, education.
Benefits: The position includes base salary + bonus + equity + benefits. Learn more about benefits at Google.
We could also mention that salary ranges determined by role, level, location. That's more about pay.
We'll keep Benefits section concise.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
About the role
...
Responsibilities
- ...
...
Minimum qualifications
- ...
...
Preferred qualifications
- ...
...
Pay
...
Benefits
...
We should not include Schedule.
Check for any duplicated content: Ensure we didn't repeat.
Now we need to ensure we removed boilerplate: equal opportunity, privacy policy, application deadline, visa sponsorship note? The visa sponsorship note might be considered minor metadata; we could drop it. The instruction says fold minor metadata into a short or drop it. We could include a short p for eligibility but it's not required. Safer to drop it.
Also "Applicants must have the legal right to work in the country where the position is based, without the need for visa sponsorship. This role does not offer visa sponsorship." We'll drop.
Also "Learn more about benefits at Google." We'll keep in Benefits.
Now check for any other boilerplate: "Wiz is an equal opportunity employer..." drop. "By submitting your application, you acknowledge that Wiz will process your personal data in accordance with Wiz's Privacy Policy." drop. "The application deadline is: 06/12/2026." drop.
Now ensure we preserved all substantive information: company intro, about the job, responsibilities, qualifications, pay, benefits.
Now we need to ensure we didn't miss any substantive details: The intro paragraph includes many details about company: "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
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. Content: - Intro paragraph about company: "Come join the organization that is redefining security for the AI era..." etc. That's prose. - Minimum qualifications: list bullet points. - Preferred qualifications: list bullet points. - About the job: description. - Responsibilities: list bullet points. - Compensation + Benefits: includes description of compensation: base salary + bonus + equity + benefits, salary range, note about US base pay range. - Also note about legal right to work, visa sponsorship, equal opportunity, privacy policy, application deadline. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove equal opportunity statement, privacy policy, application deadline? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the equal opportunity paragraph, the privacy policy sentence, and the application deadline. Also "Applicants must have the legal right to work in the country where the position is based, without the need for visa sponsorship. This role does not offer visa sponsorship." That's maybe not boilerplate but could be considered a requirement? It's about eligibility. Might be considered substantive? It's not a list but a statement. Might keep as a short paragraph? The instruction says fold minor metadata into a short
or drop it. This is about eligibility; could be considered minor metadata. Probably we can drop it or keep as a short p. But we need to preserve ALL substantive information. Is eligibility substantive? Possibly yes, but it's not a qualification. The instruction says we can fold minor metadata into a short
or drop it. So we could include a short p for that. We also have "Learn more about benefits at Google." That's a link? Might be considered boilerplate? It's a reference. Might keep as part of compensation section. We need to avoid creating sections with filler. So we need sections: About the job (maybe "About the role"), Responsibilities, Minimum qualifications (maybe "Requirements" or "Qualifications"), Preferred qualifications (maybe "Skills"), Compensation + Benefits (maybe "Pay" and "Benefits"? But we have both compensation and benefits described together. Could make a single section "Compensation + Benefits" but the allowed headings list includes Benefits, Pay, Schedule. We could use "Pay" for salary range and "Benefits" for benefits description. However the posting mentions base salary + bonus + equity + benefits, and gives US base pay range. It also mentions "Learn more about benefits at Google." So we could have a Pay section with salary range, and a Benefits section with description of benefits (bonus, equity, benefits, learn more). But we need to avoid filler. The posting does give specifics: base salary + bonus + equity + benefits, salary range $189k-$258k. That's specific. So we can include Pay section with that range. Benefits section: mention bonus, equity, benefits, and link to learn more about benefits at Google. That's specific enough. We also have Schedule? Not mentioned. So we skip Schedule. We also have "About the job" which could be "About the role". We'll use
About the role
with prose. Responsibilities: list. Minimum qualifications: list. Preferred qualifications: list. We could combine Minimum and Preferred into Requirements and Skills? But better to keep separate as they are distinct. We need to avoid duplication: The posting repeats some sentences: "Partner with heads of practice to develop and manage a unified security and compliance framework across the organization." appears twice in responsibilities. We should deduplicate. Also "Partner with heads of practice to develop and manage a unified framework across the team." duplicate. We need to preserve all substantive information but remove duplicated lines. So we should include each unique responsibility once. Let's extract responsibilities bullet points: - Drive large-scale, multi-team programs spanning security, IT, and engineering teams from strategy through execution. - Coordinate cross-functional leadership and technical owners across security, legal, engineering, and business teams to align on priorities, dependencies, and shared outcomes. - Partner with heads of practice to develop and manage a unified security and compliance framework across the organization. - Own end-to-end project / program governance, tracking risk, scope, and timelines, and proactively surfacing blockers to leadership. - Partner with heads of practice to develop and manage a unified framework across the team. (duplicate of previous? Slightly different: "across the team" vs "across the organization". Might be considered similar but we can keep both? Might be duplicate-ish. We'll keep one maybe combine? Safer to keep both as they are slightly different but could be considered duplicate. The instruction says remove duplicated lines. So we should keep only one instance. We'll keep the first: "Partner with heads of practice to develop and manage a unified security and compliance framework across the organization." - Integrate various external drivers and frameworks to streamline and automate efforts. - Ensure controls are applied correctly in alignment with Wiz business objectives. - Proactively assess and mitigate associated risks with industry frameworks and ensure the organization's overall risk posture is managed effectively. - Stay informed about evolving customer expectations and adjust approach accordingly to meet new requirements. - Drive continuous improvement by integrating realized events into controls framework. - Collaborate across teams fostering a culture of compliance within Wiz. That's the list. Now Minimum qualifications bullet points: - BA/BS degree in Management Information Systems, Computer Science or related Information Technology field, or equivalent practical experience. - 10+ years of experience in Security, IT or Compliance. - Proven understanding of the security and compliance landscape, including prevalent threats, compliance frameworks (SOX), existing technologies and security architectures. - Ability to manage multiple priorities and meet deadlines in a fast-paced environment. Preferred qualifications bullet points: - Deep understanding of regulatory landscapes. - Technical project and program management track record in technology domains. - Thrives in ambiguous, high-growth environments where priorities and scope can shift quickly. - Demonstrated experience presenting technical concepts to technical and non-technical audiences. - Strong leadership, strategic thinking, and the ability to bridge the gap between technical aspects and business goals. - Leadership through collaboration, a bias for action, and experience working within fast-paced, high performance teams. - Strong technical background with a deep understanding of software development processes - Proven creative problem-solving, analytical skills, and a collaborative, team-player work style. - Cybersecurity certifications a plus (CISM, CISSP, etc). Now About the job paragraph: "Wiz is looking for a senior leader to join our security team. The Senior Technical Program Manager will have the ability to protect cloud-native SaaS software companies and be able to balance risk mitigations with the demands of supporting a hyper-growth organization. Your key responsibilities include aligning security and compliance initiatives with strategic goals, optimizing processes to enhance efficiency, and measuring the tangible benefits derived from compliance efforts. The Senior Technical Program Manager focuses on demonstrating the positive impact of compliance on Wiz's performance, risk mitigation and customer satisfaction. This person will work directly for the Head of Security Program Management and focus on breaking down silos, optimize processes and foster collaboration between security practices." We can keep that as prose. Now Compensation section: Pay: US Base Pay Range $189,000—$258,000 USD. Also note that compensation includes base salary + bonus + equity + benefits. Salary ranges determined by role, level, location. Within range, individual pay determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Recruiter can share more about specific salary range for preferred location during hiring process. Note that compensation details listed in US role postings reflect base salary only, and do not include bonus, equity, benefits. Learn more about benefits at Google. We need to avoid filler. This is specific enough. Benefits section: Could mention base salary + bonus + equity + benefits, and learn more about benefits at Google. But we already mentioned bonus, equity, benefits in Pay section? Might be redundant. Better to have Pay section for salary range, Benefits section for bonus, equity, benefits and link. Thus: Pay: US Base Pay Range $189,000—$258,000 USD (base salary only). Note that individual pay determined by location, skills, experience, education. Benefits: The position includes base salary + bonus + equity + benefits. Learn more about benefits at Google. We could also mention that salary ranges determined by role, level, location. That's more about pay. We'll keep Benefits section concise. Now we need to output HTML fragment only, no /, no markdown. We'll structure:About the role
...
Responsibilities
- ... ...
Minimum qualifications
- ... ...
Preferred qualifications
- ... ...
Pay
...
Benefits
...
We should not include Schedule. Check for any duplicated content: Ensure we didn't repeat. Now we need to ensure we removed boilerplate: equal opportunity, privacy policy, application deadline, visa sponsorship note? The visa sponsorship note might be considered minor metadata; we could drop it. The instruction says fold minor metadata into a shortor drop it. We could include a short p for eligibility but it's not required. Safer to drop it. Also "Applicants must have the legal right to work in the country where the position is based, without the need for visa sponsorship. This role does not offer visa sponsorship." We'll drop. Also "Learn more about benefits at Google." We'll keep in Benefits. Now check for any other boilerplate: "Wiz is an equal opportunity employer..." drop. "By submitting your application, you acknowledge that Wiz will process your personal data in accordance with Wiz's Privacy Policy." drop. "The application deadline is: 06/12/2026." drop. Now ensure we preserved all substantive information: company intro, about the job, responsibilities, qualifications, pay, benefits. Now we need to ensure we didn't miss any substantive details: The intro paragraph includes many details about company: "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