ServiceNow Systems Specialist, Senior

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 with real content. We need to parse the posting. Job title: ServiceNow Systems Specialist, Senior (but we do not repeat as heading). Job Number: R0247641 (metadata, we can fold into short p or drop). We'll include maybe a short p with Job ID. We need sections: - About the role: The Opportunity paragraph(s). Could be "Your combination of people skills..." etc. We'll put that as

. - Responsibilities: The bullet list under "How You'll Contribute:" and subsequent paragraphs about leadership etc. We'll extract bullet points. - Requirements: The "You Have:" list. - Qualifications: maybe "Nice If You Have:" could be Qualifications or Skills? Usually Qualifications are required; Nice If You Have are preferred qualifications. Could treat as "Preferred Qualifications". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Requirements: required qualifications (You Have) - Qualifications: maybe combine Nice If You Have as "Preferred Qualifications" (still Qualifications heading) - Skills: maybe we could extract specific skills from requirements (like scripting languages, etc.) but we could also put under Skills heading if we have explicit skill list. The posting includes "Experience in ServiceNow scripting languages, such as JavaScript or GlideScript, and web technologies such as HTML, CSS, or AJAX". That's skill. Also "Knowledge of ITIL processes and ServiceNow best practices". Also "Ability to document requirements, support Agile processes, collaborate with stakeholders, and mentor staff". Also "TS/SCI clearance". Also certifications. Could treat as Skills. But we need to avoid duplication. Perhaps better: Use Requirements for mandatory experience/qualifications; Skills for technical skills; Qualifications for preferred/nice-to-have. Let's extract: About the role: The Opportunity paragraph(s) and maybe the paragraph after "How You'll Contribute:"? Actually "How You'll Contribute:" is responsibilities. So About the role: The Opportunity paragraph: "Your combination of people skills and Service Now expertise makes you the team hero, solving one problem after another. What if you could use those skills to improve the technology for our client? We’re looking for a ServiceNow Administrator to help us operate and maintain our client's ServiceNow platforms." We could also include the later paragraph about "We focus on growing as a team..." but that seems part of responsibilities/leadership. Might be better to include under Responsibilities. Responsibilities: bullet list under "How You'll Contribute:" plus the later paragraph about leadership/mentoring etc. Let's list responsibilities bullet points: - Create and maintain ServiceNow platform architecture and technical solutions, system configurations, processes, and procedures. - Support the implementation, configuration, and support of ServiceNow modules — including ITSM, ITOM, SecOps, and ITAM. - Develop and execute data migration and ETL strategies, including data validation and transformation mapping, while enforcing data integrity across the CMDB and related tables. - Integrate ServiceNow with enterprise technologies such as Splunk, Tanium, Active Directory, MFA, and authentication platforms, leveraging ServiceNow integration tools and APIs. - Configure RBAC, secure authentication, user access, and system security in accordance with DOW best practices. - Support deployments within secure and air-gapped federal environments, including on-prem ServiceNow instances. - Troubleshoot and resolve issues related to the ServiceNow platform, providing timely support to end users. - Collaborate and partner with government stakeholders and technical teams to define and document technical specifications and workflows. - Provide Operations & Maintenance (O&M) support including patching, monitoring, performance-metrics analysis, and platform optimization and make recommendations for improvements. - Support development and enforcement of ServiceNow best practices. Support the Platform Change Configuration Board - Provide training and mentorship to junior administrators, team members, and support user training on ServiceNow functionality and best practices. - Participate in Agile ceremonies, technical reviews, and testing, and stay current with ServiceNow updates, features, and industry trends, evaluating their potential impact on the organization. Then after that: "We focus on growing as a team, so you’ll share your expertise through leadership and mentoring as you help the team work through challenges and develop new methodologies. As leader, you’ll identify new opportunities to modernize the environment so your clients achieve their goals. Work with us and resolve daily challenges. Join us. The world can’t wait." We can include that as a paragraph under Responsibilities as well. Requirements (You Have): - 12+ years of experience in an IT field - 5+ years of experience as a ServiceNow Administrator, including implementations and management - Experience supporting ServiceNow security and secure, air-gapped federal environments - Experience in ServiceNow scripting languages, such as JavaScript or GlideScript, and web technologies such as HTML, CSS, or AJAX - Knowledge of ITIL processes and ServiceNow best practices - Ability to document requirements, support Agile processes, collaborate with stakeholders, and mentor staff - TS/SCI clearance - HS diploma or GED - DoD 8570 IAT II Certification - DoW 8140 compliant certification under the Work Role Code 451 at Intermediate level such as COMPTIA Cloud+, COMPTIA Security+, GIAC GICSP or GSEC, or (ISC)2 SSCP certification We might also include "Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; TS/SCI clearance is required." That's similar. Qualifications (Nice If You Have): - Experience with ServiceNow On-Prem instance implementation, management, and troubleshooting - Knowledge of database management and SQL MariaDB - Possession of excellent analytical and problem-solving skills - Possession of outstanding communication and interpersonal skills - Bachelor’s degree and 8+ years of experience in an IT field, or Master’s degree and 6+ years of experience in an IT field - ServiceNow Certified System Administrator (CSA) certification or other available ServiceNow certifications such as Certified Implementation Specialist Skills: Could be technical skills extracted: ServiceNow scripting languages (JavaScript, GlideScript), web technologies (HTML, CSS, AJAX), integration tools/APIs, RBAC, authentication, etc. But we already have many in Requirements. Might be redundant. Perhaps we can omit Skills section if not distinct. But we need to follow instruction: prefer a few substantive sections over many thin ones. We could combine Skills into Requirements or Qualifications. However the instruction says we can use headings for those sections only if there is real specific content. We could decide to not include Skills heading if we don't have a distinct list separate from Requirements. But we have some skill-like items: "Experience in ServiceNow scripting languages, such as JavaScript or GlideScript, and web technologies such as HTML, CSS, or AJAX". That's a skill. Could be placed under Skills heading. But we also have "Knowledge of ITIL processes and ServiceNow best practices" (knowledge). Could be skill. Maybe better to have: - About the role - Responsibilities - Requirements - Qualifications (Nice If You Have) - Skills (technical skills) - Benefits - Pay - Schedule (if any) We need to see if posting includes Benefits, Pay, Schedule. Benefits: There is a paragraph under "Compensation At Booz Allen..." describing benefits: health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program. Also mention eligibility for full-time/part-time employees working at least 20 hours a week. That's benefits content. Pay: There's a salary range: "$77,500.00 to $176,000.00 (annualized USD)". Also mention that salary determined by factors. That's pay. Schedule: Not explicitly mentioned. There's mention of remote/hybrid/onsite definitions but not a schedule for this role. No specific schedule like "Full-time", "Part-time". Could infer full-time but not explicitly stated. The benefits paragraph mentions full-time and part-time employees working at least 20 hours a week are eligible. But not a schedule for the role. So we should not create Schedule section unless posting actually states it. It does not state schedule for this role. So omit Schedule. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We need to include Job ID maybe as a short p at top:

  Job Number: R0247641

  . That's minor metadata. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, etc. We have to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Commitment to Non-Discrimination" etc. That's EEO boilerplate; we should remove. Also "Identity Statement", "Candidate AI Usage Policy", "Work Model", etc. Those are boilerplate; remove. Also "Clearance: Applicants selected will be subject to a security investigation..." is somewhat relevant but it's about clearance; we already have TS/SCI clearance in Requirements. Might be duplicate; we can keep only one mention. We'll keep the requirement. Now craft HTML. Structure:

  Job Number: R0247641

  About the role

  Your combination of people skills and Service Now expertise makes you the team hero, solving one problem after another. What if you could use those skills to improve the technology for our client? We’re looking for a ServiceNow Administrator to help us operate and maintain our client's ServiceNow platforms.

  Responsibilities

  • Create and maintain ServiceNow platform architecture and technical solutions, system configurations, processes, and procedures.
  • Support the implementation, configuration, and support of ServiceNow modules — including ITSM, ITOM, SecOps, and ITAM.
  • Develop and execute data migration and ETL strategies, including data validation and transformation mapping, while enforcing data integrity across the CMDB and related tables.
  • Integrate ServiceNow with enterprise technologies such as Splunk, Tanium, Active Directory, MFA, and authentication platforms, leveraging ServiceNow integration tools and APIs.
  • Configure RBAC, secure authentication, user access, and system security in accordance with DOW best practices.
  • Support deployments within secure and air-gapped federal environments, including on-prem ServiceNow instances.
  • Troubleshoot and resolve issues related to the ServiceNow platform, providing timely support to end users.
  • Collaborate and partner with government stakeholders and technical teams to define and document technical specifications and workflows.
  • Provide Operations & Maintenance (O&M) support including patching, monitoring, performance-metrics analysis, and platform optimization and make recommendations for improvements.
  • Support development and enforcement of ServiceNow best practices. Support the Platform Change Configuration Board
  • Provide training and mentorship to junior administrators, team members, and support user training on ServiceNow functionality and best practices.
  • Participate in Agile ceremonies, technical reviews, and testing, and stay current with ServiceNow updates, features, and industry trends, evaluating their potential impact on the organization.

  We focus on growing as a team, so you’ll share your expertise through leadership and mentoring as you help the team work through challenges and develop new methodologies. As leader, you’ll identify new opportunities to modernize the environment so your clients achieve their goals. Work with us and resolve daily challenges. Join us. The world can’t wait.

  Requirements