Group Product Manager, Agentic Code Security
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content. We have:
- About the job: content describing role, Google, etc. So we can have About the role
with paragraphs.
- Responsibilities: list of responsibilities bullet points. So Responsibilities
with - .
- Minimum qualifications: list of qualifications. Could be under Requirements or Qualifications. The instruction: Use headings for sections like Requirements, Qualifications, Skills. We have Minimum qualifications and Preferred qualifications. We could combine into Requirements (minimum) and Qualifications (preferred) or Skills. Let's decide: Use
Requirements
for minimum qualifications. Use Qualifications
for preferred qualifications. Also maybe Skills: we have some skill statements like "Experience with large-scale monorepos..." etc. Those could go under Skills. But we can also put them under Qualifications. However we need to avoid thin sections. Let's see content:
Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 10 years of experience in product management, technical program management, or software engineering leadership.
- 3 years of experience building, launching, or managing products within Application Security, Cloud Security, Code Analysis, Vulnerability Management, or Developer Tools (CI/CD, DevOps).
- 3 years of experience driving products from conception to launch (0 to 1 and scaling enterprise developer or security platforms).
Preferred qualifications:
- Master’s degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or an MBA with a strong technical background.
- Experience with large-scale monorepos, distributed build/CI systems, and containerized sandbox execution environments
- Deep domain understanding of application security concepts: vulnerability classes (CWE, OWASP Top 10, memory safety, logic flaws), threat modeling, static/dynamic code analysis, Kythe/code property graphs, fuzzing, or automated test generation.
- Exceptional written and verbal communication skills.
- Track record of defining product metrics for AI/ML systems (precision, recall, hallucination mitigation, token optimization) and developer productivity metrics (DORA, triage velocity, SLA compliance).
We could treat the preferred qualifications as Qualifications section. Skills could be maybe the "Experience with large-scale monorepos..." etc. But we can also put them under Qualifications. To avoid many thin sections, we could have Requirements (minimum) and Qualifications (preferred) and maybe Skills not needed. Benefits: we have detailed benefits. Pay: we have salary range and bonus. Schedule: not mentioned. So we should not include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to strip boilerplate: remove EEO, legal, accommodation, etc. Also remove the San Francisco Fair Chance etc? That's boilerplate but maybe considered legal; we should remove. Also remove "Note: By applying to this position you will have an opportunity to share your preferred working location..." That's maybe application instruction? It's about location preference; could be considered part of job posting but not a section; we could keep as a paragraph under About the role? It's not about role but location options. Might be considered metadata; we could drop it as it's not substantive? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." This note about location preference is minor metadata; we could drop it. Also remove "Learn more about benefits at Google ." That's a link; we can drop.
We need to preserve all substantive information: responsibilities, qualifications, benefits, pay, about the job.
Let's extract About the job paragraphs:
"At Google, we put our users first. The world is always changing, so we need Product Managers who are continuously adapting and excited to work on products that affect millions of people every day. In this role, you will work cross-functionally to guide products from conception to launch by connecting the technical and business worlds. You can break down complex problems into steps that drive product development. One of the many reasons Google consistently brings innovative, world-changing products to market is because of the collaborative work we do in Product Management. Our team works closely with creative engineers, designers, marketers, etc. to help design and develop technologies that improve access to the world's information. We're responsible for guiding products throughout the execution cycle, focusing specifically on analyzing, positioning, packaging, promoting, and tailoring our solutions to our users.
Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems."
We can keep as paragraphs.
Responsibilities bullet points:
- Define the multi-year product goal, narrative, and strategic roadmap for agentic security auditing across Google Cloud development workflows.
- Author Product Requirement Documents (PRDs) and Spec-Driven Development (SDD) artifacts, partnering closely with Engineering, Security Researchers, Program Managers, and UX to translate requirements into quarterly OKRs and deliver high-impact releases.
- Establish rigorous qualitative and quantitative evaluation frameworks (e.g., True Positive Precision, Exploitability Validation Rate, Signal-to-Noise Ratio, Mean-Time-to-Remediate, Token/Compute ROI) to benchmark and improve agentic scanning/triage accuracy.
- Design intuitive, low-friction developer workflows across multiple touchpoints including presubmit/postsubmit blocking gates, IDE integrations, triage workflows, and automated CL patching.
- Partner with security gatekeepers and leadership across Product Areas to standardize security domain knowledge assets, threat model integration, and rollout strategies, while monitoring emerging AI security trends, open-source vulnerability intelligence, and academic breakthroughs in agentic security.
Requirements (minimum) bullet list as above.
Qualifications (preferred) bullet list as above.
Benefits: list:
- Health, dental, vision, life, disability insurance
- Retirement Benefits: 401(k) with company match
- Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holidays: 13 paid days per year
We could format as
- each.
Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $240000 - $333000 (USD) + 25% bonus target + equity + benefits"
We can put as paragraph.
We must not include sections with filler like "commensurate with experience". Not present.
Now produce HTML fragment: start with
About the role
then ... maybe multiple paragraphs. Could combine into one
with line breaks? Better to separate paragraphs.
We'll output:
About the role
At Google, we put our users first. The world is always changing, so we need Product Managers who are continuously adapting and excited to work on products that affect millions of people every day. In this role, you will work cross-functionally to guide products from conception to launch by connecting the technical and business worlds. You can break down complex problems into steps that drive product development. One of the many reasons Google consistently brings innovative, world-changing products to market is because of the collaborative work we do in Product Management. Our team works closely with creative engineers, designers, marketers, etc. to help design and develop technologies that improve access to the world's information. We're responsible for guiding products throughout the execution cycle, focusing specifically on analyzing, positioning, packaging, promoting, and tailoring our solutions to our users.
Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems.
Then Responsibilities:
Responsibilities
- Define the multi-year product goal, narrative, and strategic roadmap for agentic security auditing across Google Cloud development workflows.
- Author Product Requirement Documents (PRDs) and Spec-Driven Development (SDD) artifacts, partnering closely with Engineering, Security Researchers, Program Managers, and UX to translate requirements into quarterly OKRs and deliver high-impact releases.
- Establish rigorous qualitative and quantitative evaluation frameworks (e.g., True Positive Precision, Exploitability Validation Rate, Signal-to-Noise Ratio, Mean-Time-to-Remediate, Token/Compute ROI) to benchmark and improve agentic scanning/triage accuracy.
- Design intuitive, low-friction developer workflows across multiple touchpoints including presubmit/postsubmit blocking gates, IDE integrations, triage workflows, and automated CL patching.
- Partner with security gatekeepers and leadership across Product Areas to standardize security domain knowledge assets, threat model integration, and rollout strategies, while monitoring emerging AI security trends, open-source vulnerability intelligence, and academic breakthroughs in agentic security.
Requirements:
Requirements
- Bachelor's degree or equivalent practical experience.
- 10 years of experience in product management, technical program management, or software engineering leadership.
- 3 years of experience building, launching, or managing products within Application Security, Cloud Security, Code Analysis, Vulnerability Management, or Developer Tools (CI/CD, DevOps).
- 3 years of experience driving products from conception to launch (0 to 1 and scaling enterprise developer or security platforms).
Qualifications:
Qualifications
- Master’s degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or an MBA with a strong technical background.
- Experience with large-scale monorepos, distributed build/CI systems, and containerized sandbox execution environments.
- Deep domain understanding of application security concepts: vulnerability classes (CWE, OWASP Top 10, memory safety, logic flaws), threat modeling, static/dynamic code analysis, Kythe/code property graphs, fuzzing, or automated test generation.
- Exceptional written and verbal communication skills.
- Track record of defining product metrics for AI/ML systems (precision, recall, hallucination mitigation, token optimization) and developer productivity metrics (DORA, triage velocity, SLA compliance).
Benefits:
Benefits
- Health, dental, vision, life, disability insurance
- Retirement Benefits: 401(k) with company match
- Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holid
Requirements
for minimum qualifications. UseQualifications
for preferred qualifications. Also maybe Skills: we have some skill statements like "Experience with large-scale monorepos..." etc. Those could go under Skills. But we can also put them under Qualifications. However we need to avoid thin sections. Let's see content: Minimum qualifications: - Bachelor's degree or equivalent practical experience. - 10 years of experience in product management, technical program management, or software engineering leadership. - 3 years of experience building, launching, or managing products within Application Security, Cloud Security, Code Analysis, Vulnerability Management, or Developer Tools (CI/CD, DevOps). - 3 years of experience driving products from conception to launch (0 to 1 and scaling enterprise developer or security platforms). Preferred qualifications: - Master’s degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or an MBA with a strong technical background. - Experience with large-scale monorepos, distributed build/CI systems, and containerized sandbox execution environments - Deep domain understanding of application security concepts: vulnerability classes (CWE, OWASP Top 10, memory safety, logic flaws), threat modeling, static/dynamic code analysis, Kythe/code property graphs, fuzzing, or automated test generation. - Exceptional written and verbal communication skills. - Track record of defining product metrics for AI/ML systems (precision, recall, hallucination mitigation, token optimization) and developer productivity metrics (DORA, triage velocity, SLA compliance). We could treat the preferred qualifications as Qualifications section. Skills could be maybe the "Experience with large-scale monorepos..." etc. But we can also put them under Qualifications. To avoid many thin sections, we could have Requirements (minimum) and Qualifications (preferred) and maybe Skills not needed. Benefits: we have detailed benefits. Pay: we have salary range and bonus. Schedule: not mentioned. So we should not include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to strip boilerplate: remove EEO, legal, accommodation, etc. Also remove the San Francisco Fair Chance etc? That's boilerplate but maybe considered legal; we should remove. Also remove "Note: By applying to this position you will have an opportunity to share your preferred working location..." That's maybe application instruction? It's about location preference; could be considered part of job posting but not a section; we could keep as a paragraph under About the role? It's not about role but location options. Might be considered metadata; we could drop it as it's not substantive? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." This note about location preference is minor metadata; we could drop it. Also remove "Learn more about benefits at Google ." That's a link; we can drop. We need to preserve all substantive information: responsibilities, qualifications, benefits, pay, about the job. Let's extract About the job paragraphs: "At Google, we put our users first. The world is always changing, so we need Product Managers who are continuously adapting and excited to work on products that affect millions of people every day. In this role, you will work cross-functionally to guide products from conception to launch by connecting the technical and business worlds. You can break down complex problems into steps that drive product development. One of the many reasons Google consistently brings innovative, world-changing products to market is because of the collaborative work we do in Product Management. Our team works closely with creative engineers, designers, marketers, etc. to help design and develop technologies that improve access to the world's information. We're responsible for guiding products throughout the execution cycle, focusing specifically on analyzing, positioning, packaging, promoting, and tailoring our solutions to our users. Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems." We can keep as paragraphs. Responsibilities bullet points: - Define the multi-year product goal, narrative, and strategic roadmap for agentic security auditing across Google Cloud development workflows. - Author Product Requirement Documents (PRDs) and Spec-Driven Development (SDD) artifacts, partnering closely with Engineering, Security Researchers, Program Managers, and UX to translate requirements into quarterly OKRs and deliver high-impact releases. - Establish rigorous qualitative and quantitative evaluation frameworks (e.g., True Positive Precision, Exploitability Validation Rate, Signal-to-Noise Ratio, Mean-Time-to-Remediate, Token/Compute ROI) to benchmark and improve agentic scanning/triage accuracy. - Design intuitive, low-friction developer workflows across multiple touchpoints including presubmit/postsubmit blocking gates, IDE integrations, triage workflows, and automated CL patching. - Partner with security gatekeepers and leadership across Product Areas to standardize security domain knowledge assets, threat model integration, and rollout strategies, while monitoring emerging AI security trends, open-source vulnerability intelligence, and academic breakthroughs in agentic security. Requirements (minimum) bullet list as above. Qualifications (preferred) bullet list as above. Benefits: list: - Health, dental, vision, life, disability insurance - Retirement Benefits: 401(k) with company match - Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment - Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance - Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks - Baby Bonding Leave: 18 weeks - Holidays: 13 paid days per year We could format as
- each.
Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $240000 - $333000 (USD) + 25% bonus target + equity + benefits"
We can put as paragraph.
We must not include sections with filler like "commensurate with experience". Not present.
Now produce HTML fragment: start with
About the role
then... maybe multiple paragraphs. Could combine into one
with line breaks? Better to separate paragraphs. We'll output:
About the role
At Google, we put our users first. The world is always changing, so we need Product Managers who are continuously adapting and excited to work on products that affect millions of people every day. In this role, you will work cross-functionally to guide products from conception to launch by connecting the technical and business worlds. You can break down complex problems into steps that drive product development. One of the many reasons Google consistently brings innovative, world-changing products to market is because of the collaborative work we do in Product Management. Our team works closely with creative engineers, designers, marketers, etc. to help design and develop technologies that improve access to the world's information. We're responsible for guiding products throughout the execution cycle, focusing specifically on analyzing, positioning, packaging, promoting, and tailoring our solutions to our users.
Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems.
Then Responsibilities:Responsibilities
- Define the multi-year product goal, narrative, and strategic roadmap for agentic security auditing across Google Cloud development workflows.
- Author Product Requirement Documents (PRDs) and Spec-Driven Development (SDD) artifacts, partnering closely with Engineering, Security Researchers, Program Managers, and UX to translate requirements into quarterly OKRs and deliver high-impact releases.
- Establish rigorous qualitative and quantitative evaluation frameworks (e.g., True Positive Precision, Exploitability Validation Rate, Signal-to-Noise Ratio, Mean-Time-to-Remediate, Token/Compute ROI) to benchmark and improve agentic scanning/triage accuracy.
- Design intuitive, low-friction developer workflows across multiple touchpoints including presubmit/postsubmit blocking gates, IDE integrations, triage workflows, and automated CL patching.
- Partner with security gatekeepers and leadership across Product Areas to standardize security domain knowledge assets, threat model integration, and rollout strategies, while monitoring emerging AI security trends, open-source vulnerability intelligence, and academic breakthroughs in agentic security.
Requirements
- Bachelor's degree or equivalent practical experience.
- 10 years of experience in product management, technical program management, or software engineering leadership.
- 3 years of experience building, launching, or managing products within Application Security, Cloud Security, Code Analysis, Vulnerability Management, or Developer Tools (CI/CD, DevOps).
- 3 years of experience driving products from conception to launch (0 to 1 and scaling enterprise developer or security platforms).
Qualifications
- Master’s degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or an MBA with a strong technical background.
- Experience with large-scale monorepos, distributed build/CI systems, and containerized sandbox execution environments.
- Deep domain understanding of application security concepts: vulnerability classes (CWE, OWASP Top 10, memory safety, logic flaws), threat modeling, static/dynamic code analysis, Kythe/code property graphs, fuzzing, or automated test generation.
- Exceptional written and verbal communication skills.
- Track record of defining product metrics for AI/ML systems (precision, recall, hallucination mitigation, token optimization) and developer productivity metrics (DORA, triage velocity, SLA compliance).
Benefits
- Health, dental, vision, life, disability insurance
- Retirement Benefits: 401(k) with company match
- Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holid