Specialist Director, Service Management Office (SMO) - Cyber Engagement
KPMG US · Charlotte, NC · 1 mo ago
HybridFull-time
We need to produce HTML fragment with headings for sections: 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, etc. Also remove duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see what content we have.
The posting includes:
- Intro paragraph about KPMG Advisory practice, etc. That's about the role? Could be "About the role" or "About KPMG Advisory". We need to decide.
- Then "KPMG is currently seeking a Specialist Director, Service Management Office (SMO) - Cyber Engagement to join our Managed Services practice." That's the job title line; we should not repeat as heading.
- Then "Responsibilities:" followed by a long list of duties (multiple sentences). That is responsibilities.
- Then "Qualifications:" followed by bullet-like sentences (but not bullet list). It includes minimum experience, education, certifications, knowledge, capabilities, travel, work authorization.
- Then after qualifications, there is a paragraph about salary ranges, benefits, etc. That includes: "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. 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. Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M105ADV_2_26 KPMG offers a comprehensive compensation and benefits package."
Thus we have content about Pay (salary ranges) and Benefits (medical, dental, etc.) and Schedule (Personal Time Off, holidays, breaks). So we can include sections for Pay, Benefits, Schedule.
We also have "Skills" maybe not explicit; but qualifications include knowledge and capabilities. Could treat as Skills section. But we need to decide: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have About the role (intro), Responsibilities, Qualifications (maybe also Requirements?), Skills (maybe from qualifications), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". The posting does not have such filler.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details.
We must output only HTML fragment, no /, no markdown fences.
We need to use
for sections: 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, etc. Also remove duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see what content we have.
The posting includes:
- Intro paragraph about KPMG Advisory practice, etc. That's about the role? Could be "About the role" or "About KPMG Advisory". We need to decide.
- Then "KPMG is currently seeking a Specialist Director, Service Management Office (SMO) - Cyber Engagement to join our Managed Services practice." That's the job title line; we should not repeat as heading.
- Then "Responsibilities:" followed by a long list of duties (multiple sentences). That is responsibilities.
- Then "Qualifications:" followed by bullet-like sentences (but not bullet list). It includes minimum experience, education, certifications, knowledge, capabilities, travel, work authorization.
- Then after qualifications, there is a paragraph about salary ranges, benefits, etc. That includes: "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. 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. Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M105ADV_2_26 KPMG offers a comprehensive compensation and benefits package."
Thus we have content about Pay (salary ranges) and Benefits (medical, dental, etc.) and Schedule (Personal Time Off, holidays, breaks). So we can include sections for Pay, Benefits, Schedule.
We also have "Skills" maybe not explicit; but qualifications include knowledge and capabilities. Could treat as Skills section. But we need to decide: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have About the role (intro), Responsibilities, Qualifications (maybe also Requirements?), Skills (maybe from qualifications), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". The posting does not have such filler.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details.
We must output only HTML fragment, no /, no markdown fences.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
Thus we need to convert the responsibilities list into
- items. The responsibilities are a long paragraph with semicolons separating items. We need to split into list items. Must preserve all info.
Similarly qualifications: we can make a list.
Benefits: list of benefits.
Pay: we have description about salary ranges but not actual numbers. The posting says "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 not a specific range; it's a statement about compliance and that ranges are displayed elsewhere. There's a link to salary ranges by city outside of CA. So we have some content about Pay: statement that salary ranges are displayed per location, link. That's substantive. We should include that as Pay section.
Schedule: includes Personal Time Off per fiscal year, calendar of holidays, two breaks each year (year end and around July 4th). That's schedule.
Benefits: medical/dental plans, vision, disability/life insurance, 401(k), personal well-being benefits, etc.
We also have "About the role": the introductory paragraph about KPMG Advisory practice, transformation, etc. That's prose.
We also have maybe "Requirements": but we have Qualifications covering requirements. Could treat Qualifications as Requirements. But we have both Qualifications and Skills headings possible. The posting includes qualifications (experience, education, certifications, knowledge, capabilities). Could split into Requirements (experience, education, certifications) and Skills (knowledge, capabilities). But we need to avoid thin sections. Might be better to have one Qualifications section that includes all. The instruction says we can use Qualifications heading. We'll use that.
We also have Skills heading optional; but we could omit if we put everything under Qualifications. However the posting includes "Strong knowledge of ITIL..." etc. That's more skill-like. But we can keep under Qualifications.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include Requirements if we don't have separate content.
Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove lines like "KPMG is an equal opportunity employer..." etc. Also remove "No phone calls or agencies please." etc. Also remove "Los Angeles County applicants: Material job duties..." etc. Also remove "KPMG recruits on a rolling basis." etc. Also remove "Candidates are encouraged to apply expeditiously..." etc. Also remove "KPMG offers a comprehensive compensation and benefits package." (maybe duplicate). Also remove "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's not boilerplate; it's about pay transparency, we keep as Pay.
We need to remove duplicated lines: there may be duplicate sentences about benefits etc. We'll deduplicate.
Now craft HTML.
We'll start with
About the role
then with the intro paragraph(s). The intro includes multiple sentences; we can combine into one
.
Then
Responsibilities
then - each responsibility item.
We need to split the responsibilities text into items. Let's parse the responsibilities block:
"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 (;). However there are some missing spaces after semicolons (e.g., "...actionsDesign" missing space). We'll need to handle that. We'll split by ";" and then trim.
Let's manually split:
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 actionsDesign and operate the governance framework, including decision rights, escalation paths, controls, meeting cadence, and action tracking
(Note: missing space before "Design". We'll treat as separate item: "convert client feedback into accountable improvement actions" and then "Design and operate the governance framework..." Actually the text: "...actionsDesign and operate the governance framework". So we need to split: "convert client
- for any list of duties/requirements/benefits, and
for prose. Thus we need to convert the responsibilities list into
- items. The responsibilities are a long paragraph with semicolons separating items. We need to split into list items. Must preserve all info.
Similarly qualifications: we can make a list.
Benefits: list of benefits.
Pay: we have description about salary ranges but not actual numbers. The posting says "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 not a specific range; it's a statement about compliance and that ranges are displayed elsewhere. There's a link to salary ranges by city outside of CA. So we have some content about Pay: statement that salary ranges are displayed per location, link. That's substantive. We should include that as Pay section.
Schedule: includes Personal Time Off per fiscal year, calendar of holidays, two breaks each year (year end and around July 4th). That's schedule.
Benefits: medical/dental plans, vision, disability/life insurance, 401(k), personal well-being benefits, etc.
We also have "About the role": the introductory paragraph about KPMG Advisory practice, transformation, etc. That's prose.
We also have maybe "Requirements": but we have Qualifications covering requirements. Could treat Qualifications as Requirements. But we have both Qualifications and Skills headings possible. The posting includes qualifications (experience, education, certifications, knowledge, capabilities). Could split into Requirements (experience, education, certifications) and Skills (knowledge, capabilities). But we need to avoid thin sections. Might be better to have one Qualifications section that includes all. The instruction says we can use Qualifications heading. We'll use that.
We also have Skills heading optional; but we could omit if we put everything under Qualifications. However the posting includes "Strong knowledge of ITIL..." etc. That's more skill-like. But we can keep under Qualifications.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include Requirements if we don't have separate content.
Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove lines like "KPMG is an equal opportunity employer..." etc. Also remove "No phone calls or agencies please." etc. Also remove "Los Angeles County applicants: Material job duties..." etc. Also remove "KPMG recruits on a rolling basis." etc. Also remove "Candidates are encouraged to apply expeditiously..." etc. Also remove "KPMG offers a comprehensive compensation and benefits package." (maybe duplicate). Also remove "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's not boilerplate; it's about pay transparency, we keep as Pay.
We need to remove duplicated lines: there may be duplicate sentences about benefits etc. We'll deduplicate.
Now craft HTML.
We'll start with
About the role
thenwith the intro paragraph(s). The intro includes multiple sentences; we can combine into one
. Then
Responsibilities
then- each responsibility item. We need to split the responsibilities text into items. Let's parse the responsibilities block: "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 (;). However there are some missing spaces after semicolons (e.g., "...actionsDesign" missing space). We'll need to handle that. We'll split by ";" and then trim. Let's manually split: 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 actionsDesign and operate the governance framework, including decision rights, escalation paths, controls, meeting cadence, and action tracking (Note: missing space before "Design". We'll treat as separate item: "convert client feedback into accountable improvement actions" and then "Design and operate the governance framework..." Actually the text: "...actionsDesign and operate the governance framework". So we need to split: "convert client
- items. The responsibilities are a long paragraph with semicolons separating items. We need to split into list items. Must preserve all info.
Similarly qualifications: we can make a list.
Benefits: list of benefits.
Pay: we have description about salary ranges but not actual numbers. The posting says "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 not a specific range; it's a statement about compliance and that ranges are displayed elsewhere. There's a link to salary ranges by city outside of CA. So we have some content about Pay: statement that salary ranges are displayed per location, link. That's substantive. We should include that as Pay section.
Schedule: includes Personal Time Off per fiscal year, calendar of holidays, two breaks each year (year end and around July 4th). That's schedule.
Benefits: medical/dental plans, vision, disability/life insurance, 401(k), personal well-being benefits, etc.
We also have "About the role": the introductory paragraph about KPMG Advisory practice, transformation, etc. That's prose.
We also have maybe "Requirements": but we have Qualifications covering requirements. Could treat Qualifications as Requirements. But we have both Qualifications and Skills headings possible. The posting includes qualifications (experience, education, certifications, knowledge, capabilities). Could split into Requirements (experience, education, certifications) and Skills (knowledge, capabilities). But we need to avoid thin sections. Might be better to have one Qualifications section that includes all. The instruction says we can use Qualifications heading. We'll use that.
We also have Skills heading optional; but we could omit if we put everything under Qualifications. However the posting includes "Strong knowledge of ITIL..." etc. That's more skill-like. But we can keep under Qualifications.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include Requirements if we don't have separate content.
Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove lines like "KPMG is an equal opportunity employer..." etc. Also remove "No phone calls or agencies please." etc. Also remove "Los Angeles County applicants: Material job duties..." etc. Also remove "KPMG recruits on a rolling basis." etc. Also remove "Candidates are encouraged to apply expeditiously..." etc. Also remove "KPMG offers a comprehensive compensation and benefits package." (maybe duplicate). Also remove "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's not boilerplate; it's about pay transparency, we keep as Pay.
We need to remove duplicated lines: there may be duplicate sentences about benefits etc. We'll deduplicate.
Now craft HTML.
We'll start with