Senior Security Engineer, National Security, Google Public Sector

We need to output HTML fragment with sections: headings

for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. We need to parse the posting. Key content: - Onsite client-facing work 5 days a week in Dayton, Ohio. - Must be US Citizen. - Minimum qualifications: Bachelor's degree or equivalent practical experience. - 5 years of experience with security assessments or security design reviews or threat modeling. - 5 years of experience with security engineering, computer and network security and security protocols. - 5 years of coding experience in one or more general purpose languages. - Must possess an active Top Secret/SCI security clearance. - Preferred qualifications: Master's degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or a related technical field. - Experience building, deploying, or evaluating AI-native solutions and generative AI technologies, including integrating LLMs or agentic workflows into complex operational environments. - Experience in offensive security, red teaming, or advanced pen testing, with the ability to apply an attacker's mindset to infrastructure defense and defensive engineering. - Experience in Developer Security Operations practices, including designing high-performance evaluation pipelines, building security automation, and integrating security controls directly into Continuous Integration (CI)/Continuous Deployment (CD) workflows. - About The Job: description of Security team, Google Public Sector etc. - Salary Info: Individual pay determined by factors... US: $174000 - $252000 (USD) + 15% bonus target + equity + benefits - Responsibilities: list of duties (bulleted). - Benefits: mention "benefits" but not detailed; we have only mention of benefits in salary line: "+ equity + benefits". Not specific benefits listed. Should we create Benefits section? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states benefits generally but not specifics. It says "+ equity + benefits". That's vague. Probably we should not create a Benefits section because no specific benefits listed. However we could include a short sentence about benefits in Pay section? The Pay section can include salary and bonus and equity and benefits mention. The rule: include a section ONLY when posting has real, specific content for it. Pay: we have salary range and bonus target and equity + benefits. That's specific enough for Pay. So we can have Pay section with that info. Schedule: we have onsite client-facing work 5 days a week in Dayton, Ohio. That's schedule/location. Could be Schedule section? The rule: use

for Schedule if posting actually states them. It states "onsite client-facing work 5 days a week in Dayton, Ohio." That's schedule/location. Could be placed under Schedule or maybe under a generic "About the role"? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to use. We have location and work schedule: could go under Schedule. Or could be part of About the role. Since we have a specific Schedule heading allowed, we can use Schedule. We have Requirements: Minimum qualifications etc. Could be Requirements. We have Preferred qualifications: could be Qualifications. We have Skills: maybe list of specific skills like coding, security assessments, etc. Could be Skills. We have Responsibilities: list. We have About the role: description of team etc. We have Pay: salary range etc. We have Benefits: not specific, so omit. We must not repeat job title. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information. Let's extract sections: About the role (or About The Job): The paragraph starting "About The Job Our Security team works..." includes description of team, GPS etc. We'll put that under

About the role

maybe. Responsibilities: bullet list after "Responsibilities Learn more about benefits at Google ." Actually there is a line "Learn more about benefits at Google ." That's likely a link; we should remove as boilerplate? It's not substantive; it's a link. We'll ignore that line. Then bullet list items. Requirements: Minimum qualifications etc. Could be under

Requirements

. Qualifications: Preferred qualifications etc. Could be under

Qualifications

. Skills: maybe combine coding experience etc. But we already have those in Requirements. Could also have Skills separate but might be redundant. The rule: prefer a few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section? But we have headings list; we can choose to use Requirements and Qualifications both if they have content. However we might combine them into Requirements and Qualifications separate but they'd be thin? Let's see. Minimum qualifications: Bachelor's degree or equivalent practical experience. 5 years experience with security assessments etc. 5 years experience with security engineering etc. 5 years coding experience. Must possess active Top Secret/SCI clearance. Preferred qualifications: Master's/PhD in fields. Experience building AI-native solutions etc. Experience in offensive security etc. Experience in Developer Security Operations practices. That's substantive. Could be two sections: Requirements (minimum) and Qualifications (preferred). That seems fine. Skills: maybe we could list specific skills like "security assessments, security design reviews, threat modeling, security engineering, computer and network security, security protocols, coding in general purpose languages, Top Secret/SCI clearance, AI-native solutions, generative AI, LLMs, agentic workflows, offensive security, red teaming, pen testing, Developer Security Operations, CI/CD pipelines, security automation". But that's essentially same as qualifications. Might be redundant. Better to not add Skills if we already have Requirements and Qualifications. Schedule: Onsite client-facing work 5 days a week in Dayton, Ohio. Pay: Salary info. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule, Pay. We must not include Benefits. Now format. We need to use

for each section heading. Under each heading, we need

for prose,

• for lists. For About the role: prose paragraph(s). Could be one

  containing the description. For Responsibilities: list of duties. Each bullet as

• . For Requirements: list of minimum qualifications. Could be
  • each. For Qualifications: list of preferred qualifications. Could be
    • each. For Schedule: maybe a

      stating the schedule. For Pay: maybe a

      stating salary range etc. We must preserve all substantive information; do not invent or summarize away detail. Let's extract exact text. From posting: "This position requires onsite client-facing work 5 days a week in Dayton, Ohio. Must be a US Citizen to meet customer and compliance requirements, including potential access to classified information. Minimum qualifications: Bachelor's degree or equivalent practical experience.5 years of experience with security assessments or security design reviews or threat modeling.5 years of experience with security engineering, computer and network security and security protocols.5 years of coding experience in one or more general purpose languages.Must possess an active Top Secret/SCI security clearance. Preferred qualifications: Master's degree or PhD in Computer Science, Artificial Intelligence, Cybersecurity, or a related technical field.Experience building, deploying, or evaluating AI-native solutions and generative AI technologies, including integrating LLMs or agentic workflows into complex operational environments.Experience in offensive security, red teaming, or advanced pen testing, with the ability to apply an attacker's mindset to infrastructure defense and defensive engineering.Experience in Developer Security Operations practices, including designing high-performance evaluation pipelines, building security automation, and integrating security controls directly into Continuous Integration (CI)/Continuous Deployment (CD) workflows. About The Job Our Security team works to create and maintain the safest operating environment for Google's users and developers. Security Engineers work with network equipment and actively monitor our systems for attacks and intrusions. In this role, you will also work with software engineers to proactively identify and fix security flaws and vulnerabilities. The Google Public Sector (GPS) Cyber Defense and Security Operations (CDSO) Group leads our Security Operations function for a range of GPS platforms and services. Combining Mandiant's deep security expertise with Google technologies, our team sets the standard in Security Engineering, Assessment, and Operations across Government Cloud programs. Google Public Sector brings the magic of Google to the mission of government and education with solutions purpose-built for enterprises. We focus on helping United States public sector institutions accelerate their digital transformations, and we continue to make significant investments and grow our team to meet the complex needs of local, state and federal government and educational institutions. Salary Info: Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $174000 - $252000 (USD) + 15% bonus target + equity + benefits Responsibilities Learn more about benefits at Google . Identify security issues and implement and design security controls, tools, and services to improve security systems and processes.Create custom AI-driven detections and workflows. Lead the design of automated, AI-native offensive tools and simulation frameworks to identify vulnerabilities at scale.Implement monitoring strategies, response plans, and awareness programs. Optimize SIEM, IDS/IPS, and core security tools.Conduct ongoing threat hunts using intelligence. Perform forensic analysis and provide actionable post-incident guidance.Embed best practices into the Software Development Life Cycle (SDLC), building automated evaluation pipelines and guardrails for secure code deployment." We need to preserve all info; note there are missing spaces after periods (like "experience.5 years"). We'll keep as is but maybe add spaces for readability? The rule: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not inventing; it's formatting. Probably okay. We need to remove boilerplate: "Learn more about benefits at Google ." That's a line; we should remove it. Also EEO etc removed. Now craft HTML. We'll have:

      About the role

      Our Security team works to create and maintain the safest operating environment for Google's users and developers. Security Engineers work with network equipment and actively monitor our systems for attacks and intrusions. In this role, you will also work with software engineers to proactively identify and fix security flaws and vulnerabilities. The Google Public Sector (GPS) Cyber Defense and Security Operations (CDSO) Group leads our Security Operations function for a range of GPS platforms and services. Combining Mandiant's deep security expertise with Google technologies, our team sets the standard in Security Engineering, Assessment, and Operations across Government Cloud programs. Google Public Sector brings the magic of Google to the mission of government and education with solutions purpose-built for enterprises. We focus on helping United States public sector institutions accelerate their digital transformations, and we continue to make significant investments and grow our team to meet the complex needs of local, state and federal government and educational institutions.

      Responsibilities

      • Identify security issues and implement and design security controls, tools, and services to improve security systems and processes.
      • Create custom AI-driven detections and workflows.
      • Lead the design of automated, AI-native offensive tools and simulation frameworks to identify vulnerabilities at scale.
      • Implement monitoring strategies, response plans, and awareness programs.
      • Optimize SIEM, IDS/IPS, and core security tools.
      • Conduct ongoing threat hunts using intelligence.
      • Perform forensic analysis and provide actionable post-incident guidance.
      • Embed best practices into the Software Development Life Cycle (SDLC), building automated evaluation pipelines and guardrails for secure code deployment.

      Requirements

      • Must be a US Citizen to meet customer and compliance requirements, including potential access to classified information.
      • Bachelor's degree or equivalent practical experience.
      • 5 years of experience with security assessments or security design reviews or threat modeling.
      • 5 years of experience with security engineering, computer and network security and security protocols.
      • 5 years of coding