Global Cybersecurity Manager, Google.org
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content: location note (Playa Vista, CA campus) and Fair Chance statements. Those are minor metadata; we can fold into a short
maybe under a generic heading? But we should not create headings for metadata unless we have a section like "About the role" maybe includes location and EEO? However we should avoid boilerplate EEO etc. The location note and Fair Chance statements are not boilerplate? They are specific to location and legal compliance; they might be considered minor metadata; we can put them in a
without a heading? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a
for location and Fair Chance statements. We have Benefits section: detailed list. So we need
Benefits
with- items.
We have Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $136000 - $196000 (USD) + 15% bonus target + equity + benefits". That's pay info. So we need
Pay
with. We have Schedule? Not mentioned. So omit. We have Responsibilities: there is a list of duties after "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google . Lead global strategy development..." So we need to extract responsibilities as list items. We have Requirements/Qualifications: Minimum qualifications and Preferred qualifications. Could combine into Requirements section? The instruction: Use headings like Requirements, Qualifications, Skills. We have both minimum and preferred qualifications. Could make a
Qualifications
with sublists? Or separate Minimum and Preferred as- inside. We'll include Qualifications.
Skills: maybe we can extract from preferred qualifications: Experience leveraging AI-assisted tools, workflow automation, modern analytical methods; Significant experience in cybersecurity, digital resilience, open-source security; Expertise in philanthropy within tech philanthropy sector; Excellent strategic thinking and analytical skills; Exceptional leadership and collaboration skills. Those are skills. Could put under Skills heading.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one Qualifications section. However instruction says prefer a few substantive sections over many thin ones. We have Benefits, Pay, Responsibilities, Qualifications (including minimum/preferred and skills). That's four sections.
We must not repeat job title as heading. So no heading for job title.
We must not include boilerplate like EEO, accommodation, etc. Remove those lines.
We must preserve all substantive information. So we need to keep location note and Fair Chance statements somewhere. We'll put them in a
- Lead global strategy development for the Cybersecurity portfolio, establishing measurable goals, developing clear grant roadmaps, and acting as the central point of contact for cybersecurity grantmaking.
- Build strategic global programs and grants, including AI-enabled defense tools, while developing partnerships and co-funding opportunities across the philanthropic sector.
- Lead AI-enabled operational efficiency by integrating AI-assisted research and diligence workflows to accelerate grant evaluation, landscape mapping, and portfolio synthesis.
- Build and lead a global community of practice to foster
after an optional heading? Maybe we can include a short
under a heading like "Location & Compliance"? But that's not a prescribed heading. Could just put a
without heading? The instruction says output only HTML fragment; we can include
directly. It didn't say every
must be under a heading. So we can have a leading
for location and Fair Chance statements. Then sections:
Responsibilities
with- .
Qualifications
with maybe two- for Minimum and Preferred? Or we can combine into one
- with items prefixed? Better to separate:
Minimum Qualifications
andPreferred Qualifications
but those are not in the list of allowed headings (they are not exactly "Requirements", "Qualifications", "Skills"). However we could useQualifications
and inside have Minimum qualifications: etc. But that may be considered filler? Probably acceptable. We also need Skills section: we could incorporate into Qualifications. Let's decide: UseResponsibilities
,Qualifications
,Skills
,Benefits
,Pay
. That's five sections. Check if we have content for Skills: yes we have several skill statements from preferred qualifications. We'll extract them. Now we need to preserve all substantive information: location note, Fair Chance statements, responsibilities list, qualifications (minimum and preferred), skills list, benefits list, pay info. We must not include duplicated lines, boilerplate, navigation, legal, EEO, etc. Remove lines about Google being equal opportunity, accommodation, etc. Now craft HTML. Start with afor location and Fair Chance statements: "This role may also be located in our Playa Vista, CA campus. Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's a bit long but okay. Now Responsibilities: extract list items: - Lead global strategy development for the Cybersecurity portfolio, establishing measurable goals, developing clear grant roadmaps, and acting as the central point of contact for cybersecurity grantmaking. - Build strategic global programs and grants, including AI-enabled defense tools, while developing partnerships and co-funding opportunities across the philanthropic sector. - Lead AI-enabled operational efficiency by integrating AI-assisted research and diligence workflows to accelerate grant evaluation, landscape mapping, and portfolio synthesis. - Build and lead a global community of practice to foster knowledge sharing, and partner with the Evaluation Strategy team to track program effectiveness and ecosystem resilience using modern data analytics. - Serve as the primary liaison for global Policy, Security, Communications, and Marketing to drive high-profile program launches and build compelling narratives for external stakeholders and key industry events. Now Qualifications: Minimum qualifications: - Bachelor's degree or equivalent practical experience. - 5 years of experience in program or project management. - 5 years of experience managing cross-functional or cross-team projects involving AI-augmented workflows or emerging technology. Preferred qualifications: - Experience leveraging AI-assisted tools, workflow automation, or modern analytical methods to streamline internal team operations and enhance program delivery. - Significant experience working in the field of cybersecurity, digital resilience, or open-source security. - Expertise in philanthropy within the tech philanthropy sector, with a focus on developing evidence-based social impact solutions and executing effective interventions within complex portfolio areas. - Excellent strategic thinking and analytical skills, with the ability to assess technical risks, identify ecosystem gaps, and create new opportunities. - Exceptional leadership and collaboration skills, with the ability to build consensus and drive results across teams and stakeholders. Now Skills: Could be same as preferred qualifications? Might be redundant. Perhaps we can omit Skills section and just have Qualifications covering both minimum and preferred. But we need to avoid thin sections. If we make Skills separate, we would duplicate content. Better to combine: Use Qualifications heading and inside have two subheadings? But we cannot use headings inside? We could use Minimum qualifications: and Preferred qualifications: as paragraph leads. Thus we have only Qualifications section. Now Benefits: list items: - 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 Note: The benefits list includes a line "Health, dental, vision, life, disability insuranceRetirement Benefits: 401(k) with company match" appears as one string missing space. We need to separate: "Health, dental, vision, life, disability insurance" and "Retirement Benefits: 401(k) with company match". We'll split. Now Pay:
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $136000 - $196000 (USD) + 15% bonus target + equity + benefits
Now we must not include any extra text like "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." That's location options; we might consider that as location metadata. Should we include? It's substantive about possible locations. Could include in the location paragraph. We'll add that sentence after location note. Thus location paragraph: "This role may also be located in our Playa Vista, CA campus. By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Atlanta, GA, USA; Chicago, IL, USA; New York, NY, USA; Los Angeles, CA, USA; Seattle, WA, USA; San Francisco, CA, USA; Washington D.C., DC, USA. Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." Now we need to ensure we didn't include any boilerplate like "Google is proud to be an equal opportunity workplace..." etc. Remove. Now produce HTML fragment. We'll wrap sections in ? Not required. Just output the HTML. Let's craft:This role may also be located in our Playa Vista, CA campus. By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Atlanta, GA, USA; Chicago, IL, USA; New York, NY, USA; Los Angeles, CA, USA; Seattle, WA, USA; San Francisco, CA, USA; Washington D.C., DC, USA. Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees.
Responsibilities