Temporary Manager, Senior Event Management Engineer

We need to output only HTML fragment with sections: About the role? The posting includes intro paragraph about KPMG, then "KPMG is currently seeking a Temporary Manager, Senior Event Management Engineer..." That's about the role. Then Responsibilities list, Qualifications list, Benefits description, maybe Pay? There's a link to salary ranges but not explicit numbers. The instruction: include a section ONLY when 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. Benefits: they mention comprehensive benefits package, list medical/dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. That's specific enough to include Benefits section. Pay: they mention salary ranges via link but no explicit numbers; they say "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." No actual numbers given. So we should NOT create Pay section because no specific salary info. Schedule: they mention standard work hours, years of service, PTO, holidays, breaks. That's somewhat schedule info but not explicit schedule like "full-time", "40 hrs/week". Might be considered schedule? The rule: include Schedule section only if posting actually states them. It mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." That's not a specific schedule. Safer to omit Schedule. Also we should not include Job ID etc. We need headings: About the role (maybe "About the role") using

. Responsibilities, Qualifications, Benefits. Possibly also "Qualifications" as heading. Use

• for lists. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove the line about "No phone calls or agencies please." etc. Also remove the link to benefits page? Might keep as part of benefits? The instruction: remove duplicated lines, application instructions. The benefits paragraph includes a link to benefits page; we can keep that as part of benefits description? It's not boilerplate; it's a reference. Probably okay to keep. We need to preserve the responsibilities list exactly as given. Let's extract responsibilities lines: - Design, develop, and maintain Python, JavaScript, and/or Go-based services that support event ingestion, transformation, enrichment, correlation, and automation workflows - Build, configure, and enhance IBM AIOps and IBM Netcool (OMNIbus/Impact) solutions to improve event management, noise reduction, and operational efficiency - Develop and maintain event normalization, deduplication, correlation, enrichment, and policy-driven automation capabilities across enterprise monitoring ecosystems - Design, integrate, and support topology data sources and entity relationship models to enable accurate event correlation, impact analysis, and service visibility - Create and maintain REST API integrations, JSON-based event processing solutions, and workflow automations that support end-to-end event operations - Collaborate with monitoring, platform engineering, and operations teams to improve alert quality, operational workflows, and overall reliability of event management services - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment Qualifications list: - Minimum five years of recent experience in software development, automation engineering, platform integration, or event management, including hands-on experience with IBM Netcool/OMNIbus and Impact - Bachelor's degree from an accredited college or university is preferred; minimum of a high school diploma or GED required - Strong proficiency in Python, JavaScript and/or Go, with demonstrated experience developing automation, integrations, and event processing solutions; deep understanding of event management concepts, including event lifecycle management, enrichment, deduplication, correlation, and noise reduction techniques - Experience designing and implementing REST API integrations, JSON-based data exchanges, and enterprise integration patterns - Strong Linux/UNIX administration and troubleshooting experience in large-scale enterprise environments - Experience with IBM Cloud Pak for AIOps, ServiceNow integrations, CMDB/ITSM and SQL-based enrichment sources, message bus technologies (Kafka/MQ), and CI/CD pipelines using Git-based workflows is preferred - 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) Benefits 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." Also there is a link for salary ranges: "Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6701_9_26". Since no explicit salary, we should not create Pay section. But we could maybe include that link in a Pay section? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits, so we include Benefits. It does not state specific pay, so we omit Pay. We also need an "About the role" section: The intro paragraph about KPMG and the role description: "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. KPMG is currently seeking a Temporary Manager, Senior Event Management Engineer to join our our Digital Nexus organization for a twelve month assignment." We should preserve that as prose in

  . Possibly split into two paragraphs? But we can keep as one

  . We must not repeat job title as heading. Already we have About the role heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove the line about "No phone calls or agencies please." and "KPMG recruits on a rolling basis..." etc. Also remove the Los Angeles County applicants section (that's specific legal). Also remove the link to compliance? Probably remove. We must keep the link for salary ranges? It's not boilerplate but it's about pay transparency. Since we are not including Pay section, maybe we can drop that link entirely as it's not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive info about pay transparency. If we drop it, we lose info. But we cannot create Pay section because no explicit salary. However we could include the link within About the role or Benefits? It's about pay transparency, not benefits. Could we include a

  with that link under About the role? The rule: we can include any content as long as we follow heading rules. We could add a

  after About the role that includes the link. That would preserve info without creating a Pay heading. That seems acceptable. Similarly, the benefits paragraph includes a link to benefits page; we can keep that. We must also keep the line about "KPMG offers a comprehensive compensation and benefits package." That's part of benefits. Now produce 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. KPMG is currently seeking a Temporary Manager, Senior Event Management Engineer to join our our Digital Nexus organization for a twelve month assignment.

  Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6701_9_26

  Responsibilities

  • Design, develop, and maintain Python, JavaScript, and/or Go-based services that support event ingestion, transformation, enrichment, correlation, and automation workflows
  • Build, configure, and enhance IBM AIOps and IBM Netcool (OMNIbus/Impact) solutions to improve event management, noise reduction, and operational efficiency
  • Develop and maintain event normalization, deduplication, correlation, enrichment, and policy-driven automation capabilities across enterprise monitoring ecosystems
  • Design, integrate, and support topology data sources and entity relationship models to enable accurate event correlation, impact analysis, and service visibility
  • Create and maintain REST API integrations, JSON-based event processing solutions, and workflow automations that support end-to-end event operations
  • Collaborate with monitoring, platform engineering, and operations teams to improve alert quality, operational workflows, and overall reliability of event management services
  • Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment

  Qualifications

  • Minimum five years of recent experience in software development, automation engineering, platform integration, or event management, including hands-on experience with IBM Netcool/OMNIbus and Impact
  • Bachelor's degree from an accredited college or university is preferred; minimum of a high school diploma or GED required
  • Strong proficiency in Python, JavaScript and/or Go, with demonstrated experience developing automation, integrations, and event processing solutions; deep understanding of event management concepts, including event lifecycle management, enrichment, deduplication, correlation, and noise reduction techniques
  • Experience designing and implementing REST API integrations, JSON-based data exchanges, and enterprise integration patterns
  • Strong Linux/UNIX administration and troubleshooting experience in large-scale enterprise environments
  • Experience with IBM Cloud Pak for AIOps, ServiceNow integrations, CMDB/ITSM and SQL-based enrichment sources, message bus technologies (Kafka/MQ), and CI/CD pipelines using Git-based workflows is preferred