Linux Systems Administrator
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Include a section ONLY when posting has real, specific content for it. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info.
We need to parse the posting: It has Overview (description of PNNL, directorates, FIE). Then Responsibilities (list). Then Knowledge, Skills And Abilities (list). Then Qualifications (minimum and preferred). Then Hazardous Working Conditions/Environment Not Applicable (skip). Additional Information (security clearance details). About PNNL (benefits, location). Commitment to Excellence and Equal Employment Opportunity (EEO boilerplate - remove). Drug Free Workplace (boilerplate - remove). Security, Credentialing, And Eligibility Requirements (security clearance details - maybe keep as part of Additional Information? It's substantive about clearance). Mandatory Requirements (foreign gov affiliation - maybe keep? It's about eligibility). Rockstar Reward (maybe not substantive? Probably boilerplate). We need to keep substantive info: overview, responsibilities, knowledge/skills/abilities, qualifications, additional info (security clearance, drug testing, background investigation), about PNNL (benefits, location). Possibly also "About PNNL" includes benefits: health insurance, flexible work schedules, location details. That's substantive.
We should not include sections like Benefits unless posting actually states them. The About PNNL paragraph mentions benefits: health insurance, flexible work schedules. So we could include a Benefits section with that info. Also location details maybe under About the role? But we can put under About PNNL as a section maybe "About the organization". However instruction only lists certain headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings. We need to map content.
- About the role: could be overview of role? The posting has "Overview" describing PNNL and FIE, not exactly role. But we could treat that as About the role? Might be better to use "About the role" for a description of the position purpose. The posting includes "We are seeking a skilled and motivated Linux Systems Engineer to help design, operate, automate, and improve our Linux-based infrastructure." That's role description. So we can put that under About the role.
- Responsibilities: we have list.
- Requirements: maybe combine Knowledge, Skills And Abilities? Or Requirements could be the knowledge/skills/abilities. Qualifications separate.
- Qualifications: minimum and preferred.
- Skills: maybe we could split out but we already have Knowledge, Skills And Abilities. Could put under Skills.
- Benefits: from About PNNL: health insurance, flexible work schedules. Also maybe mention location? Could be under Benefits or About the role? We'll put under Benefits.
- Pay: not specified, so omit.
- Schedule: not specified, omit.
We must not include sections with placeholder text. So we will not include Pay or Schedule.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each bullet.
Let's extract content.
Overview / About the role: The paragraph: "We are seeking a skilled and motivated Linux Systems Engineer to help design, operate, automate, and improve our Linux-based infrastructure. This role is responsible for maintaining reliable, secure, and scalable systems across on-premises and/or cloud environments. The ideal candidate has several years of hands-on Linux administration experience, strong troubleshooting skills, and familiarity with automation, monitoring, networking, and cloud technologies. You will work closely with engineering, security, and operations teams to support production services and continuously improve platform reliability."
We can keep that as prose under About the role.
Responsibilities: list bullet points after "Responsibilities". There's a repeated "Responsibilities" heading then list. Let's capture each bullet:
- Administer, maintain, and troubleshoot Linux servers and services in production and non-production environments.
- Perform system provisioning, patching, upgrades, configuration management, and lifecycle maintenance.
- Monitor system performance, capacity, availability, and security; respond to alerts and incidents as needed.
- Investigate and resolve complex operating system, application, storage, networking, and performance issues.
- Develop and maintain automation for repetitive operational tasks using tools such as Ansible, Terraform, Bash, or Python.
- Support cloud and virtualized infrastructure, including environments such as AWS, Azure, GCP, VMware, KVM, or similar platforms.
- Manage core Linux services such as DNS, SSH, NTP, LDAP/Active Directory integration, web servers, file systems, and logging.
- Implement and maintain system hardening, access controls, vulnerability remediation, backups, and disaster recovery procedures.
- Partner with security teams to ensure systems meet organizational security and compliance requirements.
- Maintain technical documentation, including system configurations, runbooks, troubleshooting guides, and standard operating procedures.
- Collaborate with software engineering and DevOps teams to improve deployment processes, observability, and platform reliability.
Knowledge, Skills And Abilities: list bullet points after that heading. Let's capture:
- Experience administering Linux systems in an enterprise, cloud, SaaS, or high-availability environment.
- Strong working knowledge of Linux distributions such as Red Hat Enterprise Linux, Rocky Linux, AlmaLinux, Ubuntu, Debian, or SUSE.
- Experience with Linux system administration concepts, including:
- User and group management
- Filesystems, storage, LVM, and permissions
- Process and service management
- Package management
- System logging and troubleshooting
- Performance tuning and capacity management
- Proficiency with scripting or automation using Bash, Python, or a similar language.
- Experience with configuration management and infrastructure-as-code tools, such as Ansible, Puppet, Chef, Terraform, or similar.
- Familiarity with networking fundamentals, including TCP/IP, DNS, DHCP, routing, firewalls, load balancing, and TLS/SSL.
- Experience with monitoring and logging platforms such as Prometheus, Grafana, Nagios, Zabbix, Datadog, Splunk, ELK/OpenSearch, or similar tools.
- Familiarity with cloud infrastructure and services in AWS, Azure, GCP, or another major cloud provider.
- Strong analytical, troubleshooting, communication, and documentation skills.
- Ability to manage competing priorities and work effectively both independently and as part of a cross-functional team.
Qualifications: Minimum Qualifications: list of education/experience combos. Then Preferred Qualifications: list.
We need to preserve all detail. So we will output as
- each item.
Minimum Qualifications:
- BS/BA and 5 years of relevant experience
- OR MS/MA or higher and 3 years of relevant experience
- OR PhD and 1 year of relevant experience
- OR AA and 14 years of relevant experience
- OR HS/GED and 16 years of relevant experience
- Demonstrated experience applying theoretical/fundamental computer science concepts through the design, development, configuration, implementation, and maintenance of computer infrastructure and networks
Preferred Qualifications:
- CompTIA Security + Certification.
- Experience with SELinux policy management, troubleshooting, and security context labeling.
- Experience with AIDE for file integrity monitoring, database management, and security auditing.
- Experience with File Access Control Lists (FACLs) for managing granular file and directory permissions on Linux systems.
- Experience working with Docker/Podman.
- Experience working with nVidia/CUDA.
- Experience working with NFS Shares.
- Experience working with CIFS Shares.
- Familiarity with virtualization technologies.
- Familiarity with Tenable Security Center/Nessus.
- Familiarity with configuration baselines (DISA STIGs).
Additional Information: security clearance details. Let's extract substantive:
- This position requires the ability to obtain and maintain a federal security clearance.
- A security clearance background investigation includes review of your employment, education, financial, and criminal history, as well as interviews with you and your personal references, neighbors, and co-workers to determine trustworthiness, reliability, and loyalty to the United States.
- The investigation also examines your foreign connections, drug and alcohol use, foreign influence, and overall conduct.
- Requirements: U.S. Citizenship
- Background Investigation: Applicants selected will be subject to a Federal background investigation and must meet eligibility requirements for access to classified matter in accordance with 10 CFR 710, Appendix B.
- Drug Testing: All Security Clearance positions are Testing Designated Positions, which means that the applicant selected for hire is subject to pre-employment drug testing, and post-employment random drug testing. In addition, applicants must be able to demonstrate non-use of illegal drugs, including marijuana, for the 12 consecutive months preceding completion of the requisite Questionnaire for National Security Positions (QNSP).
- Note: Applicants will be considered ineligible for security clearance processing by the U.S. Department of Energy if non-use of illegal drugs, including marijuana, for 12 months cannot be demonstrated.
- Testing Designated Position: This position is a Testing Designated Position (TDP). The candidate selected for this position will be subject to pre-employment and random drug testing for illegal drugs, including marijuana, consistent with the Controlled Substances Act and the PNNL Workplace Substance Abuse Program.
We could put this under a section maybe "Requirements" or "Additional Information". Since we have headings list, we could use "Requirements" for security clearance? But we already used Requirements for knowledge/skills? Actually we have separate sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping.
We have:
- About the role: overview description.
- Responsibilities: list.
- Requirements: maybe the knowledge/skills/abilities? Or could be the security clearance requirements? But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should stick to those.
Thus we need to map content to those headings. Let's decide:
- About the role: description of role (as above).
- Responsibilities: list of duties.
- Requirements: maybe the knowledge, skills, abilities (since those are requirements). Could also include security clearance? But security clearance is more like eligibility/requirements. However we have Qualifications separate for education/experience. So Requirements could be the knowledge/skills/abilities (including security clearance?). But we also have Qualifications for education/experience and preferred qualifications. Skills could be maybe the technical skills? But we already have knowledge/skills/abilities includes skills. Might be redundant.
Better: Use Requirements for the knowledge, skills, abilities (including security clearance?). Use Qualifications for education/experience combos. Use Skills for maybe the specific technical skills like scripting, automation tools, etc. But that would split the list.
Given the instruction: "Prefer a few substantive sections over many thin ones." So we should not over-section. Maybe combine knowledge/skills/abilities and qualifications into one Requirements section? But they said use headings e.g. Requirements, Qualifications, Skills. So we can have all three if substantive.
Let's assign:
- About the role: role description.
- Responsibilities: duties list.
- Requirements: knowledge, skills, abilities (including security clearance? maybe not). We'll include the knowledge/skills/abilities list.
- Qualifications: minimum and preferred qualifications (education/experience, certifications).
- Skills: maybe we could list specific technical skills like scripting, automation, cloud, networking, monitoring, etc. But that overlaps with Requirements. Could
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each bullet. Let's extract content. Overview / About the role: The paragraph: "We are seeking a skilled and motivated Linux Systems Engineer to help design, operate, automate, and improve our Linux-based infrastructure. This role is responsible for maintaining reliable, secure, and scalable systems across on-premises and/or cloud environments. The ideal candidate has several years of hands-on Linux administration experience, strong troubleshooting skills, and familiarity with automation, monitoring, networking, and cloud technologies. You will work closely with engineering, security, and operations teams to support production services and continuously improve platform reliability." We can keep that as prose under About the role. Responsibilities: list bullet points after "Responsibilities". There's a repeated "Responsibilities" heading then list. Let's capture each bullet: - Administer, maintain, and troubleshoot Linux servers and services in production and non-production environments. - Perform system provisioning, patching, upgrades, configuration management, and lifecycle maintenance. - Monitor system performance, capacity, availability, and security; respond to alerts and incidents as needed. - Investigate and resolve complex operating system, application, storage, networking, and performance issues. - Develop and maintain automation for repetitive operational tasks using tools such as Ansible, Terraform, Bash, or Python. - Support cloud and virtualized infrastructure, including environments such as AWS, Azure, GCP, VMware, KVM, or similar platforms. - Manage core Linux services such as DNS, SSH, NTP, LDAP/Active Directory integration, web servers, file systems, and logging. - Implement and maintain system hardening, access controls, vulnerability remediation, backups, and disaster recovery procedures. - Partner with security teams to ensure systems meet organizational security and compliance requirements. - Maintain technical documentation, including system configurations, runbooks, troubleshooting guides, and standard operating procedures. - Collaborate with software engineering and DevOps teams to improve deployment processes, observability, and platform reliability. Knowledge, Skills And Abilities: list bullet points after that heading. Let's capture: - Experience administering Linux systems in an enterprise, cloud, SaaS, or high-availability environment. - Strong working knowledge of Linux distributions such as Red Hat Enterprise Linux, Rocky Linux, AlmaLinux, Ubuntu, Debian, or SUSE. - Experience with Linux system administration concepts, including: - User and group management - Filesystems, storage, LVM, and permissions - Process and service management - Package management - System logging and troubleshooting - Performance tuning and capacity management - Proficiency with scripting or automation using Bash, Python, or a similar language. - Experience with configuration management and infrastructure-as-code tools, such as Ansible, Puppet, Chef, Terraform, or similar. - Familiarity with networking fundamentals, including TCP/IP, DNS, DHCP, routing, firewalls, load balancing, and TLS/SSL. - Experience with monitoring and logging platforms such as Prometheus, Grafana, Nagios, Zabbix, Datadog, Splunk, ELK/OpenSearch, or similar tools. - Familiarity with cloud infrastructure and services in AWS, Azure, GCP, or another major cloud provider. - Strong analytical, troubleshooting, communication, and documentation skills. - Ability to manage competing priorities and work effectively both independently and as part of a cross-functional team. Qualifications: Minimum Qualifications: list of education/experience combos. Then Preferred Qualifications: list. We need to preserve all detail. So we will output as
- each item.
Minimum Qualifications:
- BS/BA and 5 years of relevant experience
- OR MS/MA or higher and 3 years of relevant experience
- OR PhD and 1 year of relevant experience
- OR AA and 14 years of relevant experience
- OR HS/GED and 16 years of relevant experience
- Demonstrated experience applying theoretical/fundamental computer science concepts through the design, development, configuration, implementation, and maintenance of computer infrastructure and networks
Preferred Qualifications:
- CompTIA Security + Certification.
- Experience with SELinux policy management, troubleshooting, and security context labeling.
- Experience with AIDE for file integrity monitoring, database management, and security auditing.
- Experience with File Access Control Lists (FACLs) for managing granular file and directory permissions on Linux systems.
- Experience working with Docker/Podman.
- Experience working with nVidia/CUDA.
- Experience working with NFS Shares.
- Experience working with CIFS Shares.
- Familiarity with virtualization technologies.
- Familiarity with Tenable Security Center/Nessus.
- Familiarity with configuration baselines (DISA STIGs).
Additional Information: security clearance details. Let's extract substantive:
- This position requires the ability to obtain and maintain a federal security clearance.
- A security clearance background investigation includes review of your employment, education, financial, and criminal history, as well as interviews with you and your personal references, neighbors, and co-workers to determine trustworthiness, reliability, and loyalty to the United States.
- The investigation also examines your foreign connections, drug and alcohol use, foreign influence, and overall conduct.
- Requirements: U.S. Citizenship
- Background Investigation: Applicants selected will be subject to a Federal background investigation and must meet eligibility requirements for access to classified matter in accordance with 10 CFR 710, Appendix B.
- Drug Testing: All Security Clearance positions are Testing Designated Positions, which means that the applicant selected for hire is subject to pre-employment drug testing, and post-employment random drug testing. In addition, applicants must be able to demonstrate non-use of illegal drugs, including marijuana, for the 12 consecutive months preceding completion of the requisite Questionnaire for National Security Positions (QNSP).
- Note: Applicants will be considered ineligible for security clearance processing by the U.S. Department of Energy if non-use of illegal drugs, including marijuana, for 12 months cannot be demonstrated.
- Testing Designated Position: This position is a Testing Designated Position (TDP). The candidate selected for this position will be subject to pre-employment and random drug testing for illegal drugs, including marijuana, consistent with the Controlled Substances Act and the PNNL Workplace Substance Abuse Program.
We could put this under a section maybe "Requirements" or "Additional Information". Since we have headings list, we could use "Requirements" for security clearance? But we already used Requirements for knowledge/skills? Actually we have separate sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping.
We have:
- About the role: overview description.
- Responsibilities: list.
- Requirements: maybe the knowledge/skills/abilities? Or could be the security clearance requirements? But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should stick to those. Thus we need to map content to those headings. Let's decide: - About the role: description of role (as above). - Responsibilities: list of duties. - Requirements: maybe the knowledge, skills, abilities (since those are requirements). Could also include security clearance? But security clearance is more like eligibility/requirements. However we have Qualifications separate for education/experience. So Requirements could be the knowledge/skills/abilities (including security clearance?). But we also have Qualifications for education/experience and preferred qualifications. Skills could be maybe the technical skills? But we already have knowledge/skills/abilities includes skills. Might be redundant. Better: Use Requirements for the knowledge, skills, abilities (including security clearance?). Use Qualifications for education/experience combos. Use Skills for maybe the specific technical skills like scripting, automation tools, etc. But that would split the list. Given the instruction: "Prefer a few substantive sections over many thin ones." So we should not over-section. Maybe combine knowledge/skills/abilities and qualifications into one Requirements section? But they said use headings e.g. Requirements, Qualifications, Skills. So we can have all three if substantive. Let's assign: - About the role: role description. - Responsibilities: duties list. - Requirements: knowledge, skills, abilities (including security clearance? maybe not). We'll include the knowledge/skills/abilities list. - Qualifications: minimum and preferred qualifications (education/experience, certifications). - Skills: maybe we could list specific technical skills like scripting, automation, cloud, networking, monitoring, etc. But that overlaps with Requirements. Could
- each item.
Minimum Qualifications:
- BS/BA and 5 years of relevant experience
- OR MS/MA or higher and 3 years of relevant experience
- OR PhD and 1 year of relevant experience
- OR AA and 14 years of relevant experience
- OR HS/GED and 16 years of relevant experience
- Demonstrated experience applying theoretical/fundamental computer science concepts through the design, development, configuration, implementation, and maintenance of computer infrastructure and networks
Preferred Qualifications:
- CompTIA Security + Certification.
- Experience with SELinux policy management, troubleshooting, and security context labeling.
- Experience with AIDE for file integrity monitoring, database management, and security auditing.
- Experience with File Access Control Lists (FACLs) for managing granular file and directory permissions on Linux systems.
- Experience working with Docker/Podman.
- Experience working with nVidia/CUDA.
- Experience working with NFS Shares.
- Experience working with CIFS Shares.
- Familiarity with virtualization technologies.
- Familiarity with Tenable Security Center/Nessus.
- Familiarity with configuration baselines (DISA STIGs).
Additional Information: security clearance details. Let's extract substantive:
- This position requires the ability to obtain and maintain a federal security clearance.
- A security clearance background investigation includes review of your employment, education, financial, and criminal history, as well as interviews with you and your personal references, neighbors, and co-workers to determine trustworthiness, reliability, and loyalty to the United States.
- The investigation also examines your foreign connections, drug and alcohol use, foreign influence, and overall conduct.
- Requirements: U.S. Citizenship
- Background Investigation: Applicants selected will be subject to a Federal background investigation and must meet eligibility requirements for access to classified matter in accordance with 10 CFR 710, Appendix B.
- Drug Testing: All Security Clearance positions are Testing Designated Positions, which means that the applicant selected for hire is subject to pre-employment drug testing, and post-employment random drug testing. In addition, applicants must be able to demonstrate non-use of illegal drugs, including marijuana, for the 12 consecutive months preceding completion of the requisite Questionnaire for National Security Positions (QNSP).
- Note: Applicants will be considered ineligible for security clearance processing by the U.S. Department of Energy if non-use of illegal drugs, including marijuana, for 12 months cannot be demonstrated.
- Testing Designated Position: This position is a Testing Designated Position (TDP). The candidate selected for this position will be subject to pre-employment and random drug testing for illegal drugs, including marijuana, consistent with the Controlled Substances Act and the PNNL Workplace Substance Abuse Program.
We could put this under a section maybe "Requirements" or "Additional Information". Since we have headings list, we could use "Requirements" for security clearance? But we already used Requirements for knowledge/skills? Actually we have separate sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping.
We have:
- About the role: overview description.
- Responsibilities: list.
- Requirements: maybe the knowledge/skills/abilities? Or could be the security clearance requirements? But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using other headings? It says use