GSOC Security Engineering Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. First paragraph: "Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others. If you're as passionate about your future as we are, join our team." That's about the company, could be "About the role"? Actually "About the role" would be description of role. But we have no explicit "About the role" heading. However we can treat the initial paragraph as "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have "Responsibilities:" list. So we will have a Responsibilities section with

• items. We have "Qualifications:" list. That could be Requirements or Qualifications. The posting includes "Qualifications:" then bullet list. Also there is "Minimum ten years of recent experience..." etc. Also there is "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship..." That's a requirement but maybe part of Qualifications. Also there is "KPMG LLP and its subsidiaries ... complies with all local/state regulations regarding displaying salary ranges." That's boilerplate legal; we should remove. Then there is "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." That's Benefits. Then "California Salary Range: $198000 - $368000" That's Pay. Also "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." That's Schedule? Actually schedule info about PTO and holidays. Could be considered Schedule or Benefits. But we have Benefits already; schedule maybe separate. The instruction: include Schedule section only if posting actually states them. It does mention standard work hours? Not explicitly. It mentions PTO and holidays. That's more about benefits/time off. Could be considered Benefits. But we could put under Benefits. We also have "KPMG offers a comprehensive compensation and benefits package." That's generic. We also have "KPMG is an equal opportunity employer..." boilerplate to remove. We also have "No phone calls or agencies please." That's application instruction; remove. We also have "KPMG recruits on a rolling basis..." application instruction; remove. We also have "Los Angeles County applicants: Material job duties for this position are listed above. Criminal history may have a direct, adverse, and negative relationship with some of the material job duties of this position...." That's legal/EEO; remove. Thus we need to extract substantive content: - About the role: maybe the introductory paragraph describing KPMG and the team? Could be considered "About the role". We'll include that as a

  . - Responsibilities: list of items after "Responsibilities:" until "Qualifications:" starts. Let's capture responsibilities text: "Own the engineering architecture, availability, performance, resilience, scalability and cost efficiency of the GSOC (Global Security Operations Center) technology estate; contribute to the platform strategy and translate it into a deliverable, prioritized technical roadmap Set and deliver the automation, orchestration, integration and content-as-code roadmap; drive DevOps maturity through CI/CD, infrastructure-as-code, automated testing, observability and release engineering, with measurable reduction in manual analyst effort and mean time to detect and respond Lead the design, evaluation and productionization of AI and agentic capabilities across detection, triage, investigation, enrichment and response Run a structured innovation pipeline from horizon scanning through proof-of-value to controlled adoption; partner with vendors, the wider GISG innovation community and KPMG member firms to test emerging capability, evidence benefit, and transition proven solutions into production or retire them decisively Establish and enforce design, build, testing, release, secure development, AI-usage and documentation standards; approve production readiness, own technical debt and risk remediation, and ensure the estate is auditable and evidence-ready for internal audit, regulatory and client assurance Lead, resource, coach and develop the global engineering team; own objectives, performance, career development, succession pipeline and engagement, and build the DevOps, cloud, data and AI engineering skills required for the future service Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment" We need to split each bullet as separate

• . The semicolons separate clauses but each line seems a bullet. We'll treat each line as a bullet. - Qualifications: The section after "Qualifications:" includes: "Minimum ten years of recent experience in security operations engineering, with proven success leading an engineering team in a 24x7 security operations center or managed security service Bachelor's degree from an accredited college or university in a related discipline such as computer science or information technology is required with minimum ten years of equivalent professional experience; certifications requirements: CISSP and either CCSP or CCSK, or equivalent industry experience; other certifications of importance: AZ-500 – Microsoft Azure Security Technologies, Google Professional Cloud Security Engineer, AWS Certified Security - Specialty MCSE: Cloud Platform and Infrastructure, AWS Certified Solutions Architect Proven ownership of SIEM and SOAR platform engineering at global scale, covering log source onboarding, data pipeline design, and the end-to-end detection content lifecycle Experience supporting CSIRT and major incident response, providing the tooling, telemetry and technical escalation that responders rely on under time pressure Deep knowledge of the Microsoft security stack, including Microsoft Sentinel, Defender XDR, Microsoft Entra ID and the wider Microsoft 365 security tooling suite Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)" We need to decide if we separate into Requirements and Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We could put the experience/education under Requirements, and certifications etc under Qualifications. But we have to avoid thin sections. Perhaps combine into one Qualifications section. However we have both Requirements and Qualifications headings as examples; we can choose to include only Qualifications if content fits. The posting says "Qualifications:" then list. So we can use Qualifications heading. We also have "Skills:" maybe not explicitly listed; but we could infer skills from qualifications. But we should not invent. So we skip Skills unless explicit. Benefits: we have paragraph: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package, with options designed to help you make the best decisions for yourself, your family, and your lifestyle. Available benefits are based on eligibility. Our Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health. Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday. Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." We should keep that as Benefits section. Also note the link to Benefits & How We Work is maybe application instruction? It's a reference; we can keep as part of benefits description but not as a link? The instruction: output only HTML fragment, we can include maybe? It didn't forbid links. But we might keep the text without the link. Safer to keep plain text. Pay: we have "California Salary Range: $198000 - $368000". Also earlier: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." That's boilerplate but includes info about salary determination. We should keep the salary range. The boilerplate about compliance can be removed as it's legal. So we keep the salary range line. Schedule: Not explicitly given besides PTO and holidays which we put under Benefits. Could we make a Schedule section? The posting does not mention standard work hours, shift, etc. So we skip Schedule. Now About the role: we could include the introductory paragraph about KPMG and the team. That seems appropriate. We must not repeat job title. So no heading for Director, Global Security Engineering Lead. We must not include Job ID etc. We must not include boilerplate like EEO, equal opportunity, scam warning, application instructions, etc. We must preserve all substantive information. So we need to ensure we keep all bullet points from responsibilities and qualifications, benefits, pay. Let's craft HTML:

  About the role

  Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others. If you're as passionate about your future as we are, join our team.

  Responsibilities

  • Own the engineering architecture, availability, performance, resilience, scalability and cost efficiency of the GSOC (Global Security Operations Center) technology estate; contribute to the platform strategy and translate it into a deliverable, prioritized technical roadmap
  • Set and deliver the automation, orchestration, integration and content-as-code roadmap; drive DevOps maturity through CI/CD, infrastructure-as-code, automated testing, observability and release engineering, with measurable reduction in manual analyst effort and mean time to detect and respond
  • Lead the design, evaluation and productionization of AI and agentic capabilities across detection, triage, investigation, enrichment and response
  • Run a structured innovation pipeline from horizon scanning through proof-of-value to controlled adoption; partner with vendors, the wider GISG innovation community and KPMG member firms to test emerging capability, evidence benefit, and transition proven solutions into production or retire them decisively