Linux Network Engineer

We need to output HTML fragment with sections only if real content. Need to extract sections: About the role? The posting starts with description. We can treat "About the role" as heading with paragraph summarizing? But we must not invent content. We can use the first paragraph as prose under maybe no heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content for it. So we need to identify content that matches those headings. We have description: "Atlas Technologies... seeking a passionate...". That's about the role. Could be "About the role". Then responsibilities: list of duties (Networking, Linux Systems Engineering, Virtualization, Containerization Platforms, DevOps Concepts and Practices, Additional Duties). Those are responsibilities. Then requirements/qualifications: "You Have" list: ability to obtain clearance, min 3 years experience, Bachelor's degree, certifications, etc. That's qualifications/requirements. Skills: maybe list of specific technical skills (Web server, Subversion, protocols, backup, storage, Linux distro, virtualization, DBA, hardware, etc.) Could be under Skills. Benefits: mention "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." That's benefits. Pay: not specified specific number, just "competitive salary" - but we should not create Pay section if only vague "competitive salary" (which is not specific). The rule: 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. Benefits: they said "generous benefits package" - that's somewhat vague but still a statement of benefits. Is that considered real content? It's not specific but it's a statement. Might be okay. However they also said "competitive salary". That's vague. Might be considered filler. Safer to include Benefits section with the statement about generous benefits package and opportunity to make impact. Pay: we could omit because not specific. Schedule: not mentioned. So we omit Pay and Schedule. We need to preserve all substantive information; do not invent or summarize away detail. We need to keep details like specific tasks, certifications, etc. We need to use

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

  for prose. We need to avoid repeating job title as heading. No Job ID. We need to strip boilerplate: EEO, accessibility, accommodation contact, etc. Also remove duplicated lines, application instructions, "Want to hear more? Read on to see what our Team Members say about their experience:" and quotes? Those are testimonials; maybe we can keep as part of About the role? They are substantive? They are quotes from employees. Could be considered part of About the role. But they are not required; we could keep them as prose under About the role. However they are not mandatory; but we can keep them as they are substantive. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the quotes. We also need to remove "Accessibility & Accommodations" etc. Let's extract sections: About the role: first paragraph(s) up to "This is an onsite position in Charleston SC." plus maybe the quotes? Actually the quotes are after "Want to hear more? Read on to see what our Team Members say about their experience:" That's a prompt to read testimonials. We could include the quotes as part of About the role (maybe under a subsection? but we only have h3 headings). We could just include them as prose under About the role after the initial description. Responsibilities: The bullet-like sections: "You Will Networking (Cisco-focused)" etc. Those are responsibilities. We'll make a list. Qualifications/Requirements: "You Have Ability to obtain and maintain a Department of Defense (DoD) Secret level Security Clearance.Minimum of three years of relevant experience.Bachelor’s degree in Computer Science, Engineering or a related fieldCurrently hold at least ONE security related certification (Security+, CISSP, etc.) PLUS one OS related certification (Linux+, CCNA, etc.)Web server and application server configuration and scaling e.g., Apache HTTP server, IIS.Proven Systems Administration and Maintenance duties.Working knowledge of Subversion software versioning and revision control system.Understanding of core Internet protocols (HTTP, DNS, SMTP, etc.)Experience of backup and recovery best practices to ensure systems are protected from data loss.Experience with Storage Volume management (LVM, iSCSI, SMB, NFS).Experience with a major Linux distribution, e.g., Red Hat, CentOS, Debian.Experience with Virtual Environments e.g., VMware, Hyper-V, etc.Experience and DBA skills of at least one RDBMS, e.g., MySQL, Postgres, Oracle.Strong computer hardware and software background.Must be highly motivated and possess a mid-level skill set in Windows Systems Administration.Must possess strong troubleshooting, analytical skills.Excellent written and verbal communication skills.Strong attention to details.Strong work ethic and commitment to quality.Ability to work in a fast paced environment, multi-task and balance multiple goals and priorities.Ability to work with others in a highly collaborative environment, working with users and customers.Willingness to work overtime on an as needed basis." We can split into two sub-sections: Requirements (education, experience, certifications, clearance) and Skills (technical skills). But we only have headings: Requirements, Qualifications, Skills. We could combine Requirements and Qualifications into one heading "Requirements" (or "Qualifications") and then have Skills separate. Let's decide: Use "Requirements" for mandatory items (clearance, experience, degree, certifications). Use "Skills" for technical proficiencies. Benefits: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." We'll keep that as benefits. We must not create Pay section because salary is vague; but we included salary in benefits? Actually we said "competitive salary" inside benefits. That might be considered Pay content. But we are not making a separate Pay section; we are including it in Benefits. That's okay. Now we need to format. We'll output:

  About the role

  Atlas Technologies, a rapidly expanding company supporting the US Military and other Government entities, is seeking a passionate, flexible, highly motivated team player to join our group of Information Technology professionals. We are seeking a motivated, analytical, and detail-oriented Linux Network Engineer in Charleston SC to assist our Navy customer. This system administrator position performs systems administration of both Linux and Windows systems, general networking, disaster recover, and security for servers, desktops, mobile devices, routers and switches. In addition to server configuration, administration, and security, the candidate will support hundreds of users (including customers) with applications, resources and account issues. Experience with ancillary Navy and DoD functions such as NetWeb, SITC, DADMS, DRMO, etc. is a plus. The ideal candidate for this position will have proven system administration experience in a DoD environment, with customer-focused user support skills. This is an onsite position in Charleston SC.

  “With LEARNING as a core value, Atlas is constantly promoting ways to increase knowledge and stay at the forefront of the latest technology. Team members are regularly encouraged to continue learning and Atlas provides training resources and skills enhancement opportunities internally as well as education reimbursement if you prefer to obtain skills through outside resources or higher education.” - Wendy

  “I could not have asked for a better company to transition from Active-Duty military to civilian life. Atlas not only provides opportunities for professional growth, but it’s also highly encouraged. The passion and appreciation for what we do that is displayed every day, makes it exciting for me to come to work each day.” - Laurence

  Then Responsibilities:

  Responsibilities

  • Networking (Cisco-focused): Provide advanced support for Cisco-based networking environments across lab and C2OIX environments; serve as a strong secondary/backup network engineer for lab operations, troubleshooting, configuration, and maintenance; support design, implementation, and optimization of network infrastructure to ensure reliability and performance.
  • Linux Systems Engineering (Red Hat-focused): Design and build complex Red Hat–based systems, not just administer them; engineer solutions for isolated, fully air-gapped environments with no internet connectivity; create and maintain internal mirrors for Red Hat repositories and container registries; manage transfer and deployment into air-gapped labs; configure downstream systems to seamlessly use internal mirrors and repositories; develop scripts and tools to automate system tasks and maintain existing automation pipelines.
  • Virtualization: Deploy, configure, and maintain virtualization platforms including VMware and oVirt (RHEV free version); support virtualization lifecycle operations, performance tuning, and troubleshooting across lab environments.
  • Containerization Platforms: Build and maintain containerization infrastructure, including standing up OpenShift clusters from bare metal; manage long-term operations, upgrades, and reliability of container platforms and supporting services.
  • DevOps Concepts and Practices: Apply DevOps methodologies to enhance automation, scalability, and reliability across systems; support CI/CD concepts related to containerization, orchestration, and infrastructure management.
  • Additional Duties: Perform system administration on Windows and Linux systems in a virtual and physical environment with hands‑on approach in a R&D environment while supporting both development and production resources; install, maintain, and support all variants of Windows and Linux servers, workstations and the applications loaded on them; support users of a Linux based Help System; act as administrator of network assets in NetWeb ensuring an accurate accounting of all assets and their patch status is complete and up to date; troubleshoot basic end‑to‑end networking problems involving switches, routers, workstations, servers, VLANS, and other IT devices and or services; identify End‑of‑Life (EOL) issues, ensure all applications hosted on internal servers are approved in DADMS and upgrade as needed; provide user support including but not limited to: accounts, CACs, HBSS, printing, access, SITC, drive mapping, etc.; track and resolve local user hardware and software issues; perform regular maintenance duties such as patching, upgrades, and migrations; review/make recommended changes to Preventative Maintenance Plan.
  Then Requirements:

  Requirements

  • Ability to obtain and maintain a Department of Defense (DoD) Secret level Security Clearance.
  • Minimum of three years of relevant experience.
  • Bachelor’s degree in Computer Science, Engineering or a related field.
  • Currently hold at least ONE security related certification (Security+, CISSP, etc.) PLUS one OS related certification (Linux+, CCNA, etc.).
  Then Skills:

  Skills

  • Web server and application server configuration and scaling (e.g., Apache HTTP server, IIS).
  • Proven Systems Administration and Maintenance duties.
  • Working knowledge of Subversion software versioning and revision control system.
  • Understanding of core Internet protocols (HTTP, DNS, SMTP, etc.).
  • Experience with backup and recovery best practices to ensure systems are protected from data loss.
  • Experience with Storage Volume management (LVM, iSCSI, SMB, NFS).
  • Experience with a major Linux distribution (e.g., Red Hat, CentOS, Debian).
  • Experience with Virtual Environments (e.g., VMware, Hyper-V, etc.).
  • Experience and DBA skills of at least one RDBMS (e.g., MySQL, Postgres, Oracle).
  • Strong computer hardware and software background.
  • Must be highly motivated and possess a mid‑