ServiceNow - Senior Manager

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. We have content: description (intro) could be About the role. Responsibilities: list of key responsibilities. Qualifications: required and preferred. Skills: maybe we can extract skills from qualifications? But we have Qualifications section already; we could treat Qualifications as heading. Skills maybe not separate; we could combine. Benefits: not mentioned except discretionary annual incentive program maybe considered benefit? It mentions "You may also be eligible to participate in a discretionary annual incentive program". That's a benefit. Also maybe immigration sponsorship limited. But we need to include Benefits only if posting actually states them. It does mention discretionary annual incentive program. So we can include Benefits section with that. Pay: wage range given $175,300- $322,900. So include Pay section. Schedule: not mentioned (travel 50% maybe schedule? Not exactly schedule). No explicit schedule. So omit Schedule. We must not repeat job title as heading. Do not put Job ID. Remove boilerplate like recruiting end date? That's metadata; we could fold into short p or drop. The posting includes "Recruiting for this role ends on 12/31/2026." That's minor metadata; we can put in a p maybe under About the role or separate? Probably fold into a short p. We must preserve all substantive information; not invent or summarize away detail. Must not omit details like responsibilities list items. Must keep all bullet points. We need to use

• for any list of duties/requirements/benefits. For qualifications, we have required and preferred lists; we can make ul. We must not create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no html/body tags, no markdown fences. Let's craft:

  About the role

  ServiceNow Senior Manager ... (the introductory paragraphs up to "Recruiting for this role ends on 12/31/2026.") maybe include that sentence as part of About the role.

  Then

  Responsibilities

  • ... each responsibility.
  Then

  Qualifications

  Maybe split into Required and Preferred? Could have subheadings? But only allowed headings are those listed; we could still include

  Qualifications

  and then within that have

  Required:

  ... and

  Preferred:

  . That's okay. Then

  Benefits

  • Discretionary annual incentive program (eligibility based on individual and organizational performance).
  Maybe also mention limited immigration sponsorship? Could include as benefit. Then

  Pay

  The wage range for this role is $175,300‑$322,900.

  We must not include schedule. Check we didn't miss any substantive info: The Team paragraph about Cyber Strategy & Transformation offering. Should we include that? It's substantive. Could be part of About the role or maybe a separate section like "About the team". But only allowed headings are those listed; we could incorporate into About the role paragraph. Also "The Team: Our Cyber Strategy & Transformation offering..." is substantive; we should preserve. So include in About the role. Also "The wage range for this role takes into account ..." includes more detail about compensation decisions; we should preserve that too. So Pay section could have multiple paragraphs. Also "At Deloitte, it is not typical for an individual to be hired at or near the top of the range..." etc. Keep. Also "Information for applicants with a need for accommodation: URL". That's maybe not substantive? It's a link for accommodation; could be considered boilerplate? It's not EEO but it's accommodation info. Might be considered useful; but it's a link. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accommodation info might be considered legal? Not sure. Safer to keep? It's not EEO; it's accommodation. Might be okay to keep as a p under Benefits or separate? But it's not a benefit. Could be placed under About the role as a note. However it's a link; maybe we keep it as a p. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Accommodation info is not exactly those; it's more about accessibility. I'd keep it. We also have "#knowledgecyber2026" tag; that's likely metadata; drop. Now craft HTML. Need to ensure we don't duplicate content. Let's draft:

  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 list. Let's copy responsibilities exactly: - 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. Make each
  • . Qualifications: Required and Preferred. Required list: - 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 list: - 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. We need to preserve bullet points exactly. Benefits: discretionary annual incentive program, limited immigration sponsorship maybe already in qualifications; but we can still list benefit: discretionary annual incentive program (eligibility based on individual and organizational performance). Also maybe mention limited immigration sponsorship as benefit? It's already in qualifications; but we can keep. Pay: include detailed paragraph about wage range and notes. Let's craft 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.

    We could also include the accommodation link maybe under Benefits or separate? But we already put incentive program in Pay; maybe better to put accommodation link under Benefits? Actually accommodation link is not a benefit; it's info. Could be placed under About the role as a note. But we already have a lot in About the role; we could add a p at end:

    Information for applicants with a need for accommodation: https://www2.deloitte.com/us/en/pages/careers/articles/join-deloitte-assistance-for-disabled-applicants.html

    But the instruction says remove boilerplate; accommodation info might be considered legal? Not sure. I'd keep it as it's substantive for applicants. Now ensure no duplicate content: we mentioned discretionary annual incentive program both in Pay and maybe Benefits; we should not duplicate. We'll keep it only in Pay section (as part of compensation). Benefits section could be empty then; better to omit Benefits if no distinct benefit besides that. But we have limited immigration sponsorship maybe as benefit; but it's already in qualifications. So maybe we skip Benefits section entirely. The instruction: "Prefer