Systems Administrator - 30425

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 where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, navigation, cookie, legal, etc. Also remove application instructions. Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes "Anticipated Salary Range: $65,592.00 - $94,000.00". So Pay section should be included with that info. Schedule: The posting mentions "Ability to work onsite at Dam Neck, Virginia Beach, VA hybrid schedule. Remote/telework is at the discretion of the government." Also "Expected travel up to 10-15% of time for approximately one week per trip". Also "Utilize SIPRnet access 25-60% of the time depending on specific system assignments." So schedule info includes hybrid schedule, remote/telework discretion, travel expectations. So we can include a Schedule section with that content. Benefits: The posting includes a paragraph about benefits: "We offer competitive benefits such as best-in-class medical, dental and vision plan choices; wellness resources; employee assistance programs; Savings Plan Options (401(k)); financial planning tools, life insurance; employee discounts; paid holidays and paid time off; tuition reimbursement; as well as early childhood and post-secondary education scholarships. Bonus/other non-recurrent compensation is occasionally offered..." So we can include Benefits section. About the role: There's a summary paragraph: "HII's Mission Technologies division is currently seeking two (2) System Administrators to support Naval Surface Warfare Center Dahlgren Division (NSWCDD) Dam Neck Activity (DNA) cybersecurity programs for Shore-Based Training Systems. These positions will provide system administration support for approximately 80 cloud and shore-based training systems requiring Risk Management Framework (RMF) compliance, security baseline maintenance, and continuous monitoring across PMS339, DRPM SUBS (SEA07TR), and RRL sponsors." Also earlier there is "Meet HII’s Mission Technologies Division Our team of more than 7,000 professionals worldwide delivers all-domain expertise..." That's more about the division. Could be included in About the role or maybe a separate "About the team". But we only have allowed headings list; we can use About the role for that content. Responsibilities: There's a "Key Job Responsibilities" list with many bullet points. We'll put those in

• . Requirements: There's "What You Must Have" list. That's qualifications/requirements. Could be Requirements section. Qualifications: There's "Preferred Qualifications". Could be Qualifications section. Skills: Could be derived from requirements but we might not need separate Skills if we already have Requirements and Qualifications. But we can include Skills if there is specific skill list separate. The posting includes "Proficiency with Windows and/or Linux operating systems." etc. That's within requirements. Might be okay to not have separate Skills. We must not repeat job title. Must not include requisition number etc. Must drop boilerplate like EEO, legal, accommodation contact etc. Also remove "Find the role that’s right for you. Apply today. We look forward to meeting you." etc. Also remove "To learn more about Mission Technologies, click here for a short video: ..." etc. Also remove "Leadership Mindset at HII – Mission Technologies Role Leadership at HII is a mindset..." That's maybe not boilerplate but could be considered part of About the role? It's about leadership mindset. Could be included in About the role or maybe separate but we can include it in About the role as it's substantive. However we need to avoid duplication. We'll include relevant content. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are not boilerplate. That includes the leadership mindset paragraph, the summary, responsibilities, what you must have, preferred qualifications, physical requirements, benefits, etc. Also the "Physical Requirements Adequate visual acuity and manual dexterity for meeting the requirements of the Systems Analyst discipline." That's substantive; we could include in a Requirements or maybe a separate section but we don't have a heading for Physical Requirements. Could fold into Requirements or Qualifications. Probably include in Requirements as a bullet. Also "The listed salary range for this role is intended as a good faith estimate..." That's about salary; we can include in Pay section maybe as a note. Also "When extending an offer, HII's Mission Technologies division takes a variety of factors into consideration..." That's also about salary; we can include in Pay. Also "HII is more than a job - it’s an opportunity to build a new future." That's fluff but maybe considered boilerplate? It's generic marketing; but it's substantive? It's not specific to role. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories. It's more marketing fluff. Might be okay to keep? But we should aim to keep substantive info about the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep everything that is not explicitly boilerplate categories. The marketing fluff about building a new future is not EEO etc. It's still part of posting. I'd keep it maybe in About the role. But we must avoid creating sections with filler like "commensurate with experience". Not present. Now structure:

  About the role

  ... (include division description, leadership mindset, summary)

  Responsibilities

  • ... each responsibility

  Requirements

  • ... each must have

  Preferred Qualifications

  • ... each preferred

  Benefits

  ... benefits paragraph

  Pay

  ... salary range and note about factors

  Schedule

  ... hybrid schedule, remote/telework discretion, travel expectations, SIPRnet usage

  We need to ensure we don't include duplicated lines. Also we need to remove "Physical Requirements Adequate visual acuity and manual dexterity for meeting the requirements of the Systems Analyst discipline." We'll include that as a bullet in Requirements. Also need to include "Ability to work onsite at Dam Neck, Virginia Beach, VA hybrid schedule. Remote/telework is at the discretion of the government." That's schedule. Also "Utilize SIPRnet access 25-60% of the time depending on specific system assignments." schedule. Also "Expected travel up to 10-15% of time for approximately one week per trip to support on-site system installations, assessments, or technical coordination." schedule. Now let's extract details. Division description: "Meet HII’s Mission Technologies Division Our team of more than 7,000 professionals worldwide delivers all-domain expertise and advanced technologies in service of mission partners across the globe. Mission Technologies is leading the next evolution of national defense – the data evolution - by accelerating a breadth of national security solutions for government and commercial customers. Our capabilities range from C5ISR, AI and Big Data, cyber operations and synthetic training environments to fleet sustainment, environmental remediation and the largest family of unmanned underwater vehicles in every class. Find the role that’s right for you. Apply today. We look forward to meeting you. To learn more about Mission Technologies, click here for a short video: https://vimeo.com/732533072" We should remove the "Find the role that’s right for you. Apply today. We look forward to meeting you." and the video link? The video link is maybe not boilerplate but it's a call to action; could be considered application instruction? It's not exactly application instructions but it's a promotional link. Might be considered extraneous. The instruction says remove application instructions. The video link is not exactly an application instruction but it's a call to learn more. Might be considered non-essential. Safer to remove it. Also remove "Find the role that’s right for you. Apply today. We look forward to meeting you." as it's generic. Leadership Mindset paragraph: Keep. Summary: "HII's Mission Technologies division is currently seeking two (2) System Administrators to support Naval Surface Warfare Center Dahlgren Division (NSWCDD) Dam Neck Activity (DNA) cybersecurity programs for Shore-Based Training Systems. These positions will provide system administration support for approximately 80 cloud and shore-based training systems requiring Risk Management Framework (RMF) compliance, security baseline maintenance, and continuous monitoring across PMS339, DRPM SUBS (SEA07TR), and RRL sponsors." Now responsibilities list: Let's copy each bullet: - Administer and support daily operational requirements of computer network systems including workstations, file servers, web servers, and cloud-based training system infrastructure. - Install, configure, and maintain hardware, software, system upgrades, network accounts, and security configurations in support of RMF-compliant baselines (step 0-6). - Establish, update, and maintain security baselines for cloud instances and containerized environments, ensuring configurations remain compliant with required security controls. - Implement and maintain network security tools including firewalls, anti-virus, intrusion detection services, and security monitoring solutions. - Conduct Security Technical Implementation Guide (STIG) compliance testing using Evaluate-STIG; create and maintain STIG checklist files for assigned systems. - Execute Assured Compliance Assessment Solution (ACAS) vulnerability scans; coordinate scan scheduling and results processing with cybersecurity team. - Monitor system configuration (hardware and software) to ensure compliance with approved security baselines and Configuration Management Plans. - Support vulnerability remediation activities including patch management, configuration changes, and security updates. - Maintain documentation of system configurations, network architectures, and security baselines for RMF authorization packages. - Support Annual Security Reviews (ASR) by conducting security control testing and providing technical evidence of control implementation. - Assist in preparation of technical artifacts for RMF packages including hardware/software inventories, network diagrams, and system architecture documentation. - Troubleshoot system issues, identify security violations, and coordinate incident response activities. - Support contingency plan testing and system recovery procedures. - Attend Configuration Control Board (CCB) meetings to provide technical input on infrastructure and network upgrade proposals. - Transfer security artifacts and test results between NIPR and SIPR networks as required. - Train users on security-related software and procedures applicable to their positions. - Assist customers with information technology issues and security compliance questions. - Support cross-sponsor activities for PMS339, SUBS, and RRL programs as workload demands. - Utilize SIPRnet access 25-60% of the time depending on specific system assignments. - Expected travel up to 10-15% of time for approximately one week per trip to support on-site system installations, assessments, or technical coordination. Note: Some of these are also schedule items (SIPRnet, travel). But they appear in responsibilities list; we could keep them there and also maybe mention in schedule. To avoid duplication, we could keep them only in responsibilities and not repeat in schedule. However schedule section expects schedule info; we could still include schedule info separate but ensure not duplicate exact sentences. Might be okay to mention schedule in its own section summarizing hybrid schedule, remote/telework discretion, travel expectations, SIPRnet usage. But those are already in responsibilities; duplication may be considered duplicated lines. The instruction says remove duplicated lines. So we should avoid repeating the same sentences. So we should either keep them in responsibilities and not include schedule section, or include schedule section but paraphrase. Since schedule is a requested heading, we need to include schedule if posting actually states them. The posting does