Linux/HPC System Administrator
Argonne National Laboratory · Lemont, IL · 3 wk ago
Information Technology$86k–$135k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Key parts:
Intro: "The APS Engineering Support Division (AES) provides reliable operations and technical support to the Advanced Photon Source user community. AES works to ensure that the Advanced Photon Source maintains its status as a preeminent scientific user facility. We are seeking a highly skilled and motivated Linux/HPC System Administrator to manage and support the onsite HPC resources, beamline systems, and beamline services. Our administrators design, install, implement, and manage services running on Linux systems within our dynamic environment. The role involves maintaining and optimizing four unique HPC clusters, Globus data transfer nodes, GPU nodes, monitoring systems, IBM Storage Scale appliances, PBS Pro scheduler, and the support of data control and acquisition systems operating beamline experiments. The ideal candidate will ensure the reliability, performance, and scalability of our HPC and beamline infrastructure to support advanced computational workloads."
That's about the role. Could be "About the role" section.
Then "Key Responsibilities" with bullet list:
- GPU Nodes Administration: Configure and maintain GPU nodes for computational workloads. Optimize GPU utilization for machine learning, AI, and other GPU-intensive applications.
- Storage Management: Administer IBM Storage Scale 6K appliances and Spectrum Scale to ensure high availability and performance. Administer Nvidia InfiniBand switches and IB network to ensure high availability. Monitor storage usage and plan for capacity upgrades as needed.
- Beamline Support: Provide advanced level support to Advanced Photon Source Xray Science Division beamline computers, storage, and their associated networking on Linux. Provide second level technical assistance for beamline user support and problem resolution. Implement software and hardware installation and configuration for computers along with network troubleshooting.
- Monitoring & Visualization: Maintain monitoring tools such as Grafana to track system health and performance.
- Job Scheduling: Manage and optimize PBS Pro scheduler installations for efficient job queuing and resource allocation. Troubleshoot scheduling issues and implement policies to improve throughput.
- Documentation & Reporting: Maintain detailed documentation of system configurations, processes, and procedures. Generate regular reports on system performance, utilization, and incidents.
- Collaboration & Support: Work closely with researchers, developers, and other stakeholders to understand their computational and experimental needs. Provide technical support and training to users of the HPC systems.
- Security & Compliance: Implement security best practices to protect sensitive data and computational resources. Ensure compliance with organizational policies, industry standards, and government regulations.
Then "Position Requirements" includes: "May be required to perform other duties as assigned." Then "To perform the essential functions of this position, successful applicants must provide proof of U.S. citizenship, which is required to comply with federal regulations and contract." Then "Minimum Education and Experience Requirements: Bachelors and 4+ years’ experience, Masters and 2+ years’ experience, or equivalent Bachelor's degree in Computer Science, Information Technology, or a related field. 2+ years of experience in HPC systems administration or a similar role. Proficiency in Linux/Unix system administration. Experience with Globus, GPU nodes, and HPC cluster management. Experience with IBM Storage Scale or GPFS. Familiarity with PBS Pro scheduler and job queuing systems. Hands-on experience with monitoring tools like Grafana. Excellent problem-solving and analytical skills. Ability to work independently and manage multiple priorities. Attention to detail and commitment to quality. Ability to model Argonne’s core values of impact, safety, respect, integrity, and teamwork. Interpersonal skills, oral and written communication skills, and ability to interact with people at all levels both within and outside the laboratory."
Then "Preferred Knowledge, Skills, And Experience": Master's degree in a relevant field. Certifications in HPC, Linux, or storage technologies. Experience with scripting languages (e.g., Python, Bash) for automation. Knowledge of networking protocols and security practices.
Then "Work Environment": Office-based with on-site work at HPC facilities. May require after-hours support for critical issues.
Then "Job Family Professional Technical (PT) Job Profile Systems Integration Admin/Support 3 Worker Type Regular Time Type Full time"
Then "The expected hiring range for this position is $86,299.00 - $134,626.05. Please note that the pay range information is a general guideline only. The pay offered to a selected candidate will be determined based on factors such as, but not limited to, the scope and responsibilities of the position, the qualifications of the selected candidate, business considerations, internal equity, and external market pay for comparable jobs."
Then "Additionally, comprehensive benefits are part of the total rewards package. Click here to view Argonne employee benefits!"
Then a lot of EEO etc which we must remove.
Thus we need sections: About the role (intro), Responsibilities (the bullet list), Requirements (minimum education/experience and citizenship etc), Qualifications (maybe preferred?), Skills (maybe combine?), Benefits (mention comprehensive benefits), Pay (salary range), Schedule (maybe work environment includes after-hours support; but schedule not explicitly given; we have "Work Environment Office-based with on-site work at HPC facilities. May require after-hours support for critical issues." That's more about work environment, not schedule. There's no explicit schedule like full-time etc. There's "Time Type Full time". That is schedule info. So we can include Schedule section with "Full time". Also maybe mention "Office-based with on-site work at HPC facilities. May require after-hours support for critical issues." Could be part of Schedule or Work Environment but we only have allowed sections; we could put that under Schedule? But schedule is about time; we have full-time and after-hours support. Could include both.
We must not create sections with filler text. So we need to ensure each section has substantive content.
Let's plan:
About the role
... (intro paragraph)
Responsibilities
- ... each bullet as
- with its content.
Requirements
... include citizenship requirement, minimum education/experience, etc.
Maybe also include "Qualifications" for preferred knowledge? But we could combine preferred into Requirements or Skills. The instruction: Use sections only when posting has real specific content. We have both minimum and preferred. Could split: Requirements (minimum) and Qualifications (preferred). Or Skills (technical skills). Let's decide. We have: - Minimum Education and Experience Requirements: Bachelors and 4+ years’ experience, Masters and 2+ years’ experience, or equivalent; Bachelor's degree in Computer Science, Information Technology, or a related field; 2+ years of experience in HPC systems administration or a similar role; Proficiency in Linux/Unix system administration; Experience with Globus, GPU nodes, and HPC cluster management; Experience with IBM Storage Scale or GPFS; Familiarity with PBS Pro scheduler and job queuing systems; Hands-on experience with monitoring tools like Grafana; Excellent problem-solving and analytical skills; Ability to work independently and manage multiple priorities; Attention to detail and commitment to quality; Ability to model Argonne’s core values; Interpersonal skills, oral and written communication skills, and ability to interact with people at all levels both within and outside the laboratory. - Preferred Knowledge, Skills, And Experience: Master's degree in a relevant field; Certifications in HPC, Linux, or storage technologies; Experience with scripting languages (e.g., Python, Bash) for automation; Knowledge of networking protocols and security practices. We could put Requirements for minimum, Qualifications for preferred, Skills maybe for technical proficiencies? But we already have many technical skills in Requirements. Could combine. Better: Use Requirements for minimum, Qualifications for preferred, Skills for technical proficiencies like Linux, Globus, GPU nodes, IBM Storage Scale, PBS Pro, Grafana, scripting, networking, security. But that duplicates. Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section that includes both minimum and preferred. Or we could have "Requirements" for minimum, "Preferred Qualifications" for preferred. But that's two sections. We also need Benefits, Pay, Schedule. Benefits: "Additionally, comprehensive benefits are part of the total rewards package. Click here to view Argonne employee benefits!" That's substantive enough for Benefits. Pay: salary range. Schedule: "Work Environment Office-based with on-site work at HPC facilities. May require after-hours support for critical issues." plus "Time Type Full time". So schedule: Full-time, office-based, on-site, may require after-hours support. Thus we can create sections: About the role Responsibilities Requirements (minimum) Qualifications (preferred) Benefits Pay Schedule That's 7 sections. All have content. We must not include fluff like "May be required to perform other duties as assigned." That's part of responsibilities? Could include under Responsibilities as a bullet? It's generic; maybe we can include but it's not specific. Might be considered filler. Better to omit. We must not include boilerplate like EEO etc. Now produce HTML fragment. We need to wrap each section:About the role
...
etc. For lists:- ...