ServiceNow - Senior Manager
Deloitte · Raleigh, NC · 3 wk ago
Hybrid$175k–$323k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We need to parse the posting and extract content.
The posting:
"ServiceNow Senior Manager Our Deloitte Cyber team understands the unique challenges and opportunities businesses face in cybersecurity. Join our team to deliver powerful solutions to help our clients navigate the ever-changing threat landscape. Through powerful solutions and managed services that simplify complexity, we enable our clients to operate with resilience, grow with confidence, and proactively manage to secure success. We are seeking a Senior Manager to join our team and play a pivotal role in advancing Deloitte's Cyber Strategy Technology Risk & Solution Management. In this role, you will leverage your expertise in cyber strategy, technology risk, and solution management to guide client teams in defining and executing their Cyber Tech Risk programs-shaping strategy, optimizing operations, and leading the selection, deployment, and ongoing management of technology solutions. As an internal solution architect, you will drive the definition, design, and implementation of innovative services that strengthen our clients' cyber risk posture and support their business objectives. Recruiting for this role ends on 12/31/2026."
That's introductory description. Could be "About the role". We'll put that in
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We need to parse the posting and extract content.
The posting:
"ServiceNow Senior Manager Our Deloitte Cyber team understands the unique challenges and opportunities businesses face in cybersecurity. Join our team to deliver powerful solutions to help our clients navigate the ever-changing threat landscape. Through powerful solutions and managed services that simplify complexity, we enable our clients to operate with resilience, grow with confidence, and proactively manage to secure success. We are seeking a Senior Manager to join our team and play a pivotal role in advancing Deloitte's Cyber Strategy Technology Risk & Solution Management. In this role, you will leverage your expertise in cyber strategy, technology risk, and solution management to guide client teams in defining and executing their Cyber Tech Risk programs-shaping strategy, optimizing operations, and leading the selection, deployment, and ongoing management of technology solutions. As an internal solution architect, you will drive the definition, design, and implementation of innovative services that strengthen our clients' cyber risk posture and support their business objectives. Recruiting for this role ends on 12/31/2026."
That's introductory description. Could be "About the role". We'll put that in About the role
with
containing that paragraph(s). Remove recruiting end date? It's substantive; keep. Then "Key Responsibilities:" list bullet points. So
Responsibilities
with- each bullet.
Then "The Team:" paragraph. Could be part of About the role or separate? Could be "About the team". But we only have allowed headings; we could include it under About the role or maybe "Qualifications"? Not exactly. The instruction: use those headings only when posting has real specific content. We could create a section "About the team" but not in list; better to incorporate into About the role or maybe omit separate heading. Since we have limited headings, we could add a paragraph under About the role that includes the team description. Or we could create a separate heading "About the team" but not allowed. So we incorporate.
Then "Qualifications:" with Required and Preferred bullet lists. That's qualifications. We'll put
Qualifications
with- for each required and preferred? Could separate Required and Preferred as subheadings? Not allowed; we can just list all items. But we need to preserve required vs preferred distinction maybe via text. We'll include as list items with indication.
Then "Skills:" maybe not explicitly listed but there are skills mentioned in Preferred: documentation, presentation, communication, adaptability, problem solving, etc. Could create Skills section. But we need to see if there is explicit skills list. The posting includes "Exceptional documentation, presentation, and communication skills..." etc. That's skills. Could create Skills section.
Then Pay: there is wage range $175,300- $322,900 and mention of discretionary annual incentive. So we can create Pay section with that info.
Benefits: not mentioned explicitly besides maybe discretionary annual incentive (which is compensation). No explicit benefits like health, retirement. So we should not create Benefits section unless posting actually states them. It does not. So omit Benefits.
Schedule: mentions ability to travel 50%, on average. That's schedule/travel. Could be considered Schedule? The instruction: Schedule section only if posting actually states them. It mentions travel expectation. Could be considered schedule. We'll include Schedule section with travel expectation.
Also there is recruitment end date; we could keep in About the role.
We must not include boilerplate like EEO, accommodation link? The accommodation link is at end: "Information for applicants with a need for accommodation: https://..." That's boilerplate? It's specific accommodation info; but it's likely considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accommodation link is not exactly EEO but could be considered legal? It's about accommodation for disabled applicants; might be considered EEO/legal. Safer to remove it. Also remove the "#knowledgecyber2026" tag.
Also remove the line about "The wage range for this role takes into account..." that's part of Pay; we keep that.
We must not repeat job title as heading.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- Develop and execute strategies for integrated risk management (IRM), governance, risk, and compliance (GRC), and Security Operations (SecOps) leveraging the ServiceNow platform.
- Design and implement enterprise risk and compliance frameworks aligned with industry standards (e.g., ISO 27001, NIST, COBIT, PCI, HIPAA) using ServiceNow GRC and SecOps modules.
- Oversee the delivery of ServiceNow-based cyber risk solutions, ensuring alignment with best practices and evolving client needs.
- Lead the assessment, configuration, and deployment of ServiceNow IRM, GRC, and SecOps modules, including ITSM, ITAM, CMDB, and automation workflows.
- Drive continuous improvement by applying industry-leading practices and ServiceNow capabilities to enhance cyber risk management and service delivery.
- Serve as a trusted advisor to executive stakeholders, translating business requirements into effective ServiceNow technical solutions.
- Contribute to practice development by creating go-to-market strategies and innovative ServiceNow-based solutions for client cyber risk challenges.
- Provide thought leadership on ServiceNow GRC and SecOps trends and evaluate emerging requirements and technologies.
- Lead and mentor global teams to ensure high-quality delivery of ServiceNow cyber risk management services.
Qualifications
- BA/BS Degree in Computer Science, Cyber Security, Information Security, Engineering, Information Technology, Finance, Business or related field
- 10+ years of hands-on experience on Tech Risk technology solution designs and architect, including but not limited to: IT Operations Management (ITOM) IT Asset Management (ITAM) Integrated Risk Management (IRM) Security Operations (SecOps) Third-Party Risk Management (TPRM)
- 10+ years of demonstrated deep technical expertise in ServiceNow, typically evidenced by advanced ServiceNow certifications (e.g., Certified Application Developer, Certified Implementation Specialist, Certified Technical Architect, Certified Master Architect) and hands-on experience designing, configuring, and integrating complex ServiceNow solutions.
- 10+ years of experience leading ServiceNow implementations including solution design and technical architecture
- Previous consulting or Big 4 experience
- Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve
- Limited immigration sponsorship may be available
Preferred Qualifications
but not allowed headings; we could just continue list with note "Preferred:" inside list items. Or we could create a Skills section for those soft skills. Let's think: The preferred items include certifications, experience with ServiceNow Security and GRC modules, documentation/presentation/communication skills, adaptability, problem-solving, defining epics/user stories, UI mock-ups, business/technical design specifications, leading technical design meetings. Those are a mix of qualifications and skills. We could split: Qualifications for required; Skills for preferred soft skills; and maybe keep certifications etc under Qualifications as well. Simplify: Keep Qualifications section for required only; then Skills section for preferred soft skills and technical skills like certifications? But the instruction: prefer few substantive sections over many thin ones. We could combine required and preferred into Qualifications, with sub-bullets indicating Preferred. That's okay. Thus Qualifications section will have list items, some marked "(Preferred)" at end. Let's craft list: - BA/BS Degree in Computer Science, Cyber Security, Information Security, Engineering, Information Technology, Finance, Business or related field (Required) - 10+ years of hands-on experience on Tech Risk technology solution designs and architect, including but not limited to: IT Operations Management (ITOM) IT Asset Management (ITAM) Integrated Risk Management (IRM) Security Operations (SecOps) Third-Party Risk Management (TPRM) (Required) - 10+ years of demonstrated deep technical expertise in ServiceNow, typically evidenced by advanced ServiceNow certifications (e.g., Certified Application Developer, Certified Implementation Specialist, Certified Technical Architect, Certified Master Architect) and hands-on experience designing, configuring, and integrating complex ServiceNow solutions. (Required) - 10+ years of experience leading ServiceNow implementations including solution design and technical architecture (Required) - Previous consulting or Big 4 experience (Required) - Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve (Required) - Limited immigration sponsorship may be available (Required) - ServiceNow Certified Master Architect (CMA) / ServiceNow Certified Technical Architect (CTA) (Preferred) - Proven experience with ServiceNow Security and GRC modules, with a strong understanding of platform capabilities and best practices. (Preferred) - Exceptional documentation, presentation, and communication skills-both verbal and written-with the ability to collaborate effectively across geographically dispersed teams. (Preferred) - Demonstrated adaptability in prioritizing and executing tasks, working closely with clients to identify and resolve key constraints, risks, and issues. (Preferred) - Strong problem-solving, critical thinking, and logical structuring abilities. (Preferred) - Hands-on experience defining epics and user stories, creating UI mock-ups, and a proactive, "roll-up-the-sleeves" approach to driving results. (Preferred) - Expertise in developing business and technical design specifications for ServiceNow platform implementations. (Preferred) - Skilled at leading technical design meetings, reviewing proposed solutions with stakeholders, and ensuring alignment with client objectives. (Preferred) That seems comprehensive. Now Pay section:Pay
The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $175,300- $322,900. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
Schedule section:Schedule
Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve.
We already included travel in qualifications; but schedule section can mention travel expectation. It's okay to have some overlap? Might be duplicate but okay. However we might avoid duplication by moving travel to schedule only and
- for each required and preferred? Could separate Required and Preferred as subheadings? Not allowed; we can just list all items. But we need to preserve required vs preferred distinction maybe via text. We'll include as list items with indication.
Then "Skills:" maybe not explicitly listed but there are skills mentioned in Preferred: documentation, presentation, communication, adaptability, problem solving, etc. Could create Skills section. But we need to see if there is explicit skills list. The posting includes "Exceptional documentation, presentation, and communication skills..." etc. That's skills. Could create Skills section.
Then Pay: there is wage range $175,300- $322,900 and mention of discretionary annual incentive. So we can create Pay section with that info.
Benefits: not mentioned explicitly besides maybe discretionary annual incentive (which is compensation). No explicit benefits like health, retirement. So we should not create Benefits section unless posting actually states them. It does not. So omit Benefits.
Schedule: mentions ability to travel 50%, on average. That's schedule/travel. Could be considered Schedule? The instruction: Schedule section only if posting actually states them. It mentions travel expectation. Could be considered schedule. We'll include Schedule section with travel expectation.
Also there is recruitment end date; we could keep in About the role.
We must not include boilerplate like EEO, accommodation link? The accommodation link is at end: "Information for applicants with a need for accommodation: https://..." That's boilerplate? It's specific accommodation info; but it's likely considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accommodation link is not exactly EEO but could be considered legal? It's about accommodation for disabled applicants; might be considered EEO/legal. Safer to remove it. Also remove the "#knowledgecyber2026" tag.
Also remove the line about "The wage range for this role takes into account..." that's part of Pay; we keep that.
We must not repeat job title as heading.
Now craft HTML.
Structure: