HPC Linux Systems Engineer, Classified Environment

We need to output HTML fragment with sections: About the role? The posting includes Overview, Major Duties And Responsibilities, Basic Qualifications, Preferred Qualifications, Special Requirement, About ORNL, Why Join Us, etc. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Overview (intro) -> could be "About the role" (or maybe "Overview"). - Major Duties And Responsibilities -> "Responsibilities". - Basic Qualifications -> "Requirements" or "Qualifications". Since they have Basic Qualifications and Preferred Qualifications, we could combine into "Qualifications" with sub-sections? But we need to use

  for section headings only; we could have separate sections: "Basic Qualifications" and "Preferred Qualifications". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but suggests those as examples. We could still use "Basic Qualifications" and "Preferred Qualifications" as headings if they are meaningful. But they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those standard headings where applicable. However we can also use other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's implied to use those. However we need to preserve all substantive info. We could map Basic Qualifications to "Requirements" and Preferred Qualifications to "Qualifications" or "Skills". But we also have "Special Requirement" (SCI clearance) which is a requirement. Could be part of Requirements. We also have "About ORNL" and "Why Join Us" which could be "About the role"? Actually "About ORNL" is about the organization; "Why Join Us" is benefits/ culture. Could be "Benefits"? But they didn't list explicit benefits like health insurance etc. They have "Why Join Us" with collaborative environment, professional development, location quality of life. That could be considered "Benefits" or "About the role". The instruction says never create Benefits section unless posting actually states them. The posting does state reasons to join us, which are benefits/perks. So we could include a Benefits section with those points. We also have "Pay" and "Schedule": not mentioned. So we should not include those sections. We need to remove boilerplate: EEO, equal opportunity, application instructions (file types, email, etc.), navigation, cookie, legal, scam-warning. Also remove "This position will remain open for a minimum of 5 days after which it will close when a qualified candidate is identified and/or hired." That's application instruction? It's about posting duration; maybe we can drop as it's not substantive? It's not about role. Probably drop. Also remove "We accept Word (.doc, .docx), Adobe (unsecured .pdf), Rich Text Format (.rtf), and HTML (.htm, .html) up to 5MB in size. Resumes from third party vendors will not be accepted; these resumes will be deleted and the candidates submitted will not be considered for employment. If you have trouble applying for a position, please email ORNLRecruiting@ornl.gov." That's application instructions; drop. Also remove "ORNL is an equal opportunity employer..." etc. Drop. Also remove "UT-Battelle is an E-Verify employer." Drop. Also remove "All team members deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service." That's substantive? It's about core values; could be part of About ORNL or Why Join Us. Might keep as part of About ORNL. We need to preserve all substantive information: overview, duties, qualifications, special requirement, about ORNL, why join us. We need to format with

  headings and

  for prose,

  • for lists. We need to decide sections: - About the role (or Overview) -> combine overview paragraph(s). Could be "About the role". Use

    About the role

    then

    with overview text. - Responsibilities ->

    Responsibilities

    then
    • each duty. - Requirements -> could combine Basic Qualifications and Special Requirement (SCI clearance). Use

      Requirements

      then
      • each. - Qualifications/Skills -> Preferred Qualifications could be "Preferred Qualifications" or "Skills". Use

        Preferred Qualifications

        then
        • . - Benefits -> "Why Join Us" points: collaborate with diverse teams, grow career, enjoy life in East Tennessee, etc. Also maybe mention core values? Could be part of Benefits. Use

          Benefits

          then
          • . - About ORNL -> maybe "About ORNL" as a section. Use

            About ORNL

            then

            . We need to avoid thin sections: each should have substantive content. Let's extract content. Overview paragraph(s): "The Field Intelligence Operations Division invites candidates to apply to join our National Security Computing team to contribute to the design, implementation, and management of HPC systems within a classified environment. We are looking for candidates with experience in HPC architecture, cluster management, and parallel computing, with a proven ability to work within highly secure and regulated environments. This role involves close collaboration with security teams, scientists, and IT leadership to ensure that the HPC infrastructure meets the stringent performance, security, and compliance requirements necessary for classified work. As part of our team, you will be joining a vibrant group of professionals eager to provide premier customer service to ensure people and information technology remain secure. The team is collaborative and strives to ensure security practices and procedures are understood, implemented, and enforced." That's the overview. We could also include the sentence about evergreen posting representing multiple openings? That's metadata; maybe drop as not substantive? It's about multiple openings; could be considered part of overview but it's about the posting. Might drop as not essential. Major Duties And Responsibilities list: - Install, integrate, and administer Linux-based HPC clusters, storage systems, and high-speed networks. - Monitor and optimize system performance, reliability, and scalability for large-scale computational workloads. - Diagnose complex hardware and software issues, coordinating with vendors and internal engineering teams to implement solutions. - Participate in system design, deployment, acceptance testing, and upgrades for leadership-class and research computing systems. - Develop and maintain automation, configuration management, and monitoring solutions using tools such as Ansible, Puppet, Bash, or Python. - Collaborate with scientists, researchers, and technical staff to ensure HPC resources effectively support scientific and mission objectives. - Support identity management, authentication, and access control frameworks to maintain secure and compliant environments. - Document system architectures, processes, and best practices, and contribute to internal knowledge sharing. - Participate in on-call rotations and off-hours maintenance windows as required to support 24x7 operations. Basic Qualifications: - BS degree in computer science, engineering, or a related field. - A minimum of 5 years of experience in Linux systems administration, or an equivalent combination of education and experience. Preferred Qualifications: - Experience administering HPC clusters or large-scale Linux computing environments. - Familiarity with batch schedulers (e.g., SLURM, PBS, LSF) and parallel file systems (Lustre, GPFS/Spectrum Scale). - Experience implementing and managing automation and configuration management frameworks (Ansible, Puppet, Salt). - Proficiency in scripting or programming (Python, Bash, Go). - Understanding of networking fundamentals and high-speed interconnects (InfiniBand, Ethernet). - Experience deploying or supporting identity management and multi-factor authentication systems (PingFederate, RSA SecureID, Entra ID). - Familiarity with virtualization or containerization technologies (VMware, KVM, Podman, Apptainer). - Experience troubleshooting and tuning high-performance storage, networking, and computer systems. - Excellent communication, collaboration, and problem-solving skills. - Demonstrated ability to lead or contribute to complex technical projects with minimal supervision. Special Requirement: - SCI Clearance: This position requires the ability to obtain and maintain a Secret Compartmented Information (SCI) clearance from the Department of Energy. As such, this position is a Workplace Substance Abuse (WSAP) testing designated position. WSAP positions require passing a pre-placement drug test and participation in an ongoing random drug testing program. In addition, due to the SCI, you may also be subject to random polygraph testing. About ORNL: - As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive 80-year legacy of addressing the nation’s most pressing challenges. Our team is made up of over 7,000 dedicated and innovative individuals! Our goal is to create an environment where a variety of perspectives and backgrounds are valued, ensuring ORNL is known as a top choice for employment. These principles are essential for supporting our broader mission to drive scientific breakthroughs and translate them into solutions for energy, environmental, and security challenges facing the nation. Why Join Us: - Collaborate with diverse teams of scientists, engineers, and technologists from across the DOE complex and academia. - Grow your career in a mission-driven, innovation-focused environment with access to professional development and leadership opportunities. - Enjoy life in East Tennessee, with a thriving research community, scenic outdoor recreation, and a high quality of life. Also there is sentence about core values: "All team members deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service." Could be included in About ORNL or Benefits. Let's include in About ORNL paragraph. Now we need to format. We must not include job title heading. No job ID/requisition as heading. We need to output only HTML fragment. Let's craft:

            About the role

            ...overview...

            Responsibilities

            • ...
            ...

            Requirements

            • BS degree in computer science, engineering, or a related field.
            • A minimum of 5 years of experience in Linux systems administration, or an equivalent combination of education and experience.
            • Ability to obtain and maintain a Secret Compartmented