ServiceNow - Senior Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Intro paragraphs: "ServiceNow Senior Manager Our Deloitte Cyber team ..." etc. This is about the role description. Could be "About the role" section. - "Recruiting for this role ends on 12/31/2026." That's metadata; we can fold into short

maybe. - "Key Responsibilities:" then bullet list (actually sentences). We'll create

• for each responsibility. - "The Team:" paragraph describing team. Could be part of About the role or separate? Could be "About the team" but not a required heading. Probably include under About the role or separate "Team". Since we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put team description under About the role. - "Qualifications:" then Required list and Preferred list. We'll put under Qualifications. - Skills: maybe we can extract from Preferred: documentation, presentation, communication, problem solving, etc. Could be a Skills section. But we need to decide if we have enough content. The posting includes many skill-like items under Preferred. Could create Skills section. - Pay: The wage range: "$175,300- $322,900." Also mention discretionary annual incentive program. So we have Pay section. - Benefits: Not explicitly listed besides incentive program? It mentions discretionary annual incentive program, but not benefits like health, retirement. Could treat incentive as part of Pay? Or Benefits? The instruction: include Benefits section only if posting actually states them. It mentions "You may also be eligible to participate in a discretionary annual incentive program". That's compensation, not benefits like health. So maybe not Benefits. - Schedule: Not mentioned (travel 50% mentioned under Qualifications). Travel is not schedule. No schedule info. So omit Schedule. - Requirements: Could be separate from Qualifications? Usually Requirements = required qualifications. But we have Qualifications heading already. Could combine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have both Required and Preferred under Qualifications. Could treat that as Qualifications. Could also have Requirements as a separate section for required experience/education. But we might duplicate. Better to follow typical: Responsibilities, Qualifications (which includes required and preferred), Skills, Pay. Since we have both Required and Preferred, we can put them under Qualifications. We need to preserve all substantive information. So we need to include the travel requirement, recruitment end date, etc. Let's extract sections: About the role: include introductory paragraphs up to "Recruiting for this role ends on 12/31/2026." plus The Team paragraph. Responsibilities: list each bullet after "Key Responsibilities:". Qualifications: include Required and Preferred bullet points. Skills: maybe extract from Preferred bullet points that are skill-oriented: "Exceptional documentation, presentation, and communication skills-both verbal and written-with the ability to collaborate effectively across geographically dispersed teams.", "Demonstrated adaptability in prioritizing and executing tasks, working closely with clients to identify and resolve key constraints, risks, and issues.", "Strong problem-solving, critical thinking, and logical structuring abilities.", "Hands-on experience defining epics and user stories, creating UI mock-ups, and a proactive, "roll-up-the-sleeves" approach to driving results.", "Expertise in developing business and technical design specifications for ServiceNow platform implementations.", "Skilled at leading technical design meetings, reviewing proposed solutions with stakeholders, and ensuring alignment with client objectives." Also maybe "Proven experience with ServiceNow Security and GRC modules..." is more qualification. But we can still include under Skills. Pay: include wage range and discretionary annual incentive program. We must not include boilerplate like EEO, etc. There's none. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's craft. Structure:

  About the role

  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. The Team: Our Cyber Strategy & Transformation offering develops and transforms cyber programs in line with a client's strategic objectives, regulatory requirements, and risk appetite. It keeps the enterprise a step ahead of the evolving threat landscape and gives stakeholders confidence in the organization's cyber posture. Includes design of the cyber organization, governance, and risk assessments.

  Recruiting for this role ends on 12/31/2026.

  Then Responsibilities:

  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:

  Qualifications

  Required:

  • 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:

  • ServiceNow Certified Master Architect (CMA) / ServiceNow Certified Technical Architect (CTA)
  • Proven experience with ServiceNow Security and GRC modules, with a strong understanding of platform capabilities and best practices.
  • Exceptional documentation, presentation, and communication skills-both verbal and written-with the ability to collaborate effectively across geographically dispersed teams.
  • Demonstrated adaptability in prioritizing and executing tasks, working closely with clients to identify and resolve key constraints, risks, and issues.
  • Strong problem-solving, critical thinking, and logical structuring abilities.
  • Hands-on experience defining epics and user stories, creating UI mock-ups, and a proactive, "roll-up-the-sleeves" approach to driving results.
  • Expertise in developing business and technical design specifications for ServiceNow platform implementations.
  • Skilled at leading technical design meetings, reviewing proposed solutions with stakeholders, and ensuring alignment with client objectives.
  Skills: maybe we can extract the skill bullet points from Preferred into a Skills section, but we already have them under Preferred. Could still create a Skills section to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put them under Qualifications Preferred, that's fine. We may not need separate Skills section. However we have a heading Skills in the list of allowed headings; we could create a Skills section pulling out the skill-oriented items. But that would duplicate content if we also keep them under Qualifications Preferred. Duplication is allowed? The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid redundancy. However we could move skill items to Skills and keep Qualifications for required/education/experience/certifications. Let's decide. We have Required items: degree, years experience, certifications, consulting, travel, sponsorship. Preferred items: certifications, experience with modules, skills (documentation, communication, adaptability, problem-solving, epics, expertise, leading meetings). It might be reasonable to split: Qualifications for required education/experience/certifications/travel/sponsorship; Skills for the skill-based preferred items; and maybe keep the preferred certifications and module experience under Qualifications as well? But that would split preferred across two sections. Could keep all preferred under Qualifications and not have Skills section. Simpler. Given the instruction to prefer a few substantive sections over many thin ones, we can avoid Skills section. Thus sections: About the role, Responsibilities, Qualifications, Pay. Pay section:

  Pay

  The wage range for this role 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.

  We need to preserve the note about geographic differential not adjusted, typical hiring not at top of range, etc. That's also substantive. Should we include? It's part of Pay description. Yes we should include all substantive info. So include those sentences. Thus Pay paragraph: include all sentences from "The wage range for this role takes into account..." through "Information for applicants with a need for accommodation:"? Actually that accommodation link is separate; it's not Pay or Benefits. It's a link for accommodation. Should we keep? It's substantive info about accommodation. Could be placed under a separate section? Not in headings list. Could fold into a short

  after Pay maybe. The instruction: do NOT include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accommodation link is not exactly boilerplate; it's info for applicants with