Specialist Director, Service Management Office (SMO) - Cyber Engagement

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraphs about KPMG Advisory practice, then "KPMG is currently seeking a Specialist Director, Service Management Office (SMO) - Cyber Engagement to join our Managed Services practice." That's the role description. Then "Responsibilities:" list. Then "Qualifications:" list. Then there is mention of benefits, compensation, etc. We need to include sections only if real specific content. The posting includes benefits: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." and details about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. Also mentions salary ranges link. So we can include Benefits section with that content. Pay: they mention salary ranges but not specific numbers; they say "If required, the ranges displayed below or via the URL below are specifically for those potential hires..." This is not a concrete salary figure; it's a reference. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state benefits, so Benefits section is okay. Pay: they mention salary ranges but not actual numbers; it's a statement that ranges are displayed elsewhere. This might be considered not specific content; they say "If required, the ranges displayed below or via the URL below are specifically for those potential hires..." It's not giving a range. Probably we should not include Pay section because no explicit salary figure or range given. Schedule: they mention standard work hours, PTO, holidays, breaks. That's schedule-related info. Could include Schedule section? They mention "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 info (PTO, holidays). So we could include Schedule section with that. However rule: Prefer a few substantive sections over many thin ones. Could combine Benefits and Schedule? But they are distinct. Might be okay to have Benefits and Schedule sections. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role (intro), Responsibilities, Qualifications (maybe also Requirements? but Qualifications covers). Could also include Skills? The qualifications include skills. We'll just have About the role, Responsibilities, Qualifications, Benefits, Schedule. Ensure we don't create empty sections. We need to preserve all substantive information; remove boilerplate like EEO, visa sponsorship details? The visa sponsorship text is substantive? It's about eligibility; maybe we keep it as part of Qualifications? It's a requirement: "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)". That's a requirement; we can include in Qualifications or a separate Requirement section. Since we have Qualifications, we can embed that as a bullet. We must not include duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The later part includes EEO statement, etc. Remove that. Also remove "No phone calls or agencies please." etc. Also remove "Los Angeles County applicants: Material job duties for this position are listed above..." That's maybe legal; but it's about criminal history; could be considered boilerplate? It's specific to location; but it's still a legal notice. Might be considered boilerplate; but it's about Fair Chance Act. Probably remove as it's legal boilerplate. Also remove the link to salary ranges? That's not boilerplate; it's about pay transparency. Might keep as part of Benefits or Pay? Since we aren't including Pay, maybe we can include a note in Benefits about pay transparency link? But rule: do not create Pay section unless posting actually states them. The link is about salary ranges; we could mention in Benefits? Not appropriate. Better to omit that link as it's not substantive detail about the job; it's a reference. Could keep as part of Benefits? Not sure. Safer to omit. We need to preserve all substantive information: responsibilities, qualifications, benefits, schedule (PTO, holidays). Also the intro about KPMG Advisory practice. Let's craft HTML:

About the role

... intro paragraphs up to "KPMG is currently seeking a Specialist Director, Service Management Office (SMO) - Cyber Engagement to join our Managed Services practice." We'll include that as a sentence. Then

Responsibilities

with

• each responsibility bullet. The responsibilities list is long with semicolons separating multiple items; we need to split into list items. The text after "Responsibilities:" includes many items separated by semicolons and line breaks. We'll need to parse them into separate
• . Ensure we keep all content. Similarly Qualifications: after "Qualifications:" we have bullet-like sentences separated by line breaks. We'll split. We'll also include a

  Benefits

  with
  • for each benefit item: medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, personal well-being benefits, Personal Time Off, holidays, breaks. Schedule: maybe we can combine with Benefits? But we have separate schedule info: standard work hours, PTO per fiscal year, calendar of holidays, two breaks each year (year end and around July 4th). We'll put in Schedule section. We must not include heading with empty content. Let's extract responsibilities text: "Own integrated service performance across cyber workstreams, geographies, and delivery partners, including quality, resilience, contractual outcomes, and value realization; serve as the senior operational interface among client executives, Engagement Partners, cyber leaders, and delivery teams; translate strategy and commitments into an actionable service roadmap; maintain executive visibility into service health, cyber risk, dependencies, financial performance, transformation progress, and required decisions; build trusted relationships with CISO, technology, risk, procurement, business, and engagement leaders; advise stakeholders on service maturity, operational resilience, cyber-risk priorities, transformation, and value realization; set expectations and communicate performance, risks, trade-offs, and opportunities clearly; convert client feedback into accountable improvement actionsDesign and operate the governance framework, including decision rights, escalation paths, controls, meeting cadence, and action tracking; lead service reviews, MBRs, QBRs, steering committees, transformation forums, and CISO-level updates; deliver concise executive reporting across SLAs/KPIs, incidents, backlog, capacity, financials, risks, dependencies, transformation, and value; lead and develop service and workstream leads across cyber towers, establishing clear accountability, performance expectations, and succession coverage; coordinate cross-tower priorities, dependencies, handoffs, and integrated delivery across onshore and offshore teams; drive collaboration across security operations, engineering, architecture, transition, transformation, commercial, finance, and risk functionsGovern SLAs, KPIs, operational-level agreements, experience measures, control indicators, thresholds, and data ownership; monitor service health across incidents, requests, problems, changes, vulnerabilities, security events, backlog, demand, capacity, and continuity; lead major-incident and escalation governance, including communications, root-cause analysis, corrective action, and post-incident review; use trend analysis, problem management, quality assurance, and service improvement plans to reduce recurrence, operational risk, and cost to serveEnsure compliance with Statements of Work, service levels, pricing assumptions, deliverables, acceptance criteria, and commercial obligations; partner with engagement and finance leaders on forecasting, budget, revenue protection, margin, productivity, and resource utilization; identify scope changes early and govern change requests through impact assessment, negotiation, approval, and execution; support sustainable engagement growth by identifying opportunities to improve services and expand valueGovern mobilization, transition, implementation, stabilization, and transformation through milestones, readiness criteria, stage gates, and acceptance measures; integrate steady-state operations with the transformation roadmap and track adoption, business outcomes, and sustained benefits; prioritize improvements in automation, reliability, ticket reduction, control effectiveness, knowledge management, and user experience; champion analytics, workflow automation, and responsible AI-enabled service management to improve insight, speed, quality, and efficiencyIdentify operational, cyber, delivery, regulatory, financial, and contractual risks; establish mitigation, contingency, and escalation plans; ensure alignment with security policies, control requirements, change governance, audit evidence, and regulatory obligations; lead resolution of issues affecting client operations, security posture, reputation, or contractual performance, with transparent executive communicationAct with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment" We need to split by semicolons, but note some sentences have no space after semicolon before next word (e.g., "...actionsDesign..."). We'll need to handle that. We'll manually split into logical items. Better to break at each semicolon and also where a new sentence starts with a capital letter after no space? We'll approximate. Let's list responsibilities items: 1. Own integrated service performance across cyber workstreams, geographies, and delivery partners, including quality, resilience, contractual outcomes, and value realization 2. Serve as the senior operational interface among client executives, Engagement Partners, cyber leaders, and delivery teams 3. Translate strategy and commitments into an actionable service roadmap 4. Maintain executive visibility into service health, cyber risk, dependencies, financial performance, transformation progress, and required decisions 5. Build trusted relationships with CISO, technology, risk, procurement, business, and engagement leaders 6. Advise stakeholders on service maturity, operational resilience, cyber-risk priorities, transformation, and value realization 7. Set expectations and communicate performance, risks, trade-offs, and opportunities clearly 8. Convert client feedback into accountable improvement actions 9. Design and operate the governance framework, including decision rights, escalation paths, controls, meeting cadence, and action tracking 10. Lead service reviews, MBRs, QBRs, steering committees, transformation forums, and CISO-level updates 11. Deliver concise executive reporting across SLAs/KPIs, incidents, backlog, capacity, financials, risks, dependencies, transformation, and value 12. Lead and develop service and workstream leads across cyber towers, establishing clear accountability, performance expectations, and succession coverage 13. Coordinate cross-tower priorities, dependencies, handoffs, and integrated delivery across onshore and offshore teams 14. Drive collaboration across security operations, engineering, architecture, transition, transformation, commercial, finance, and risk functions 15. Govern SLAs, KPIs, operational-level agreements, experience measures, control indicators, thresholds, and data ownership 16. Monitor service health across incidents, requests, problems, changes, vulnerabilities, security events, backlog, demand, capacity, and continuity 17. Lead major-incident and escalation governance, including communications, root-cause analysis, corrective action, and post-incident review 18. Use trend analysis, problem management, quality assurance, and service improvement plans to reduce recurrence, operational risk, and cost to serve 19. Ensure compliance with Statements of Work, service levels, pricing assumptions, deliverables, acceptance criteria, and commercial obligations 20. Partner with engagement and finance leaders on forecasting, budget, revenue protection, margin, productivity, and resource utilization 21. Identify scope changes early and govern change requests through impact assessment, negotiation, approval, and execution 22. Support sustainable engagement growth by identifying opportunities to improve services and expand value 23. Govern mobilization, transition, implementation, stabilization, and transformation through milestones,