Linux Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key content: - Intro about Accenture Federal Services (mission, etc). Could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Description: At Accenture Federal Services... (mission). Could be "About the role" (or maybe "About the company"? but we follow headings list). We'll put an

About the role

with paragraph(s) summarizing the mission and team. - Responsibilities: list bullet points. - Qualifications: includes Bachelor's degree, 5 years military/industry experience, must possess DoD 8140/8570 compliant certification, 5 years professional experience in any of the following: Linux engineering, Hybrid infrastructure, HPC/AI cluster operations, virtualization, Experience supporting secure government systems in accordance with DoD/IC policies. - Preferred Qualifications: Experience with VAST Data, Liqid composability, GPU architectures, HPC pipelines; scripting experience Python, Bash, PowerShell; DevSecOps or CI/CD automation exposure; VMware, KVM, Nutanix expertise; Experience applying DISA STIGs, CIS Benchmarks, RMF controls. - Clearance: An active TS/SCI is required for this role. - Pay: The base pay range for this position in these locations is shown below. Then later: The pay range for the states ... is: $119,300—$165,100 USD. Also mention compensation varies depending on factors. So we have pay info. - Benefits: "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." That's vague but it's a statement about benefits. It's not specific details, but it's still content about benefits. The instruction: 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. The posting does state benefits exist, but not specifics. Is that considered filler? It says "offers a wide variety of benefits. You can find more information on benefits here." That's somewhat generic but still states that benefits exist. Might be acceptable to include Benefits section with that sentence. However they said prefer a few substantive sections over many thin ones. Could include Benefits with that sentence. - Schedule: The role is fully onsite. That's schedule info. So we can include Schedule section with "Fully onsite." - Also there is "As required by local law, Accenture Federal Services provides reasonable ranges of compensation for hired roles based on labor costs in the states..." That's part of pay. - Also there is "We accept applications on an on-going basis and there is no fixed deadline to apply." That's application instruction, which we should remove. - Also there is "What We Believe" etc. That's boilerplate about EEO etc. Should be removed. - Also there is "Equal Employment Opportunity Statement" etc. Remove. - Also there is "Other Employment Statements" etc. Remove. - Also there is "Requesting An Accommodation" etc. Remove. - Also there is "California requires additional notifications..." Remove. Thus we need to output HTML fragment with sections: About the role, Responsibilities, Qualifications (maybe combine Requirements and Qualifications? The headings list includes Requirements and Qualifications separate. We have qualifications content; we could put Requirements as maybe same as Qualifications? But we have both "Qualifications" and "Preferred Qualifications". Could treat "Qualifications" as required qualifications, and "Skills" maybe for preferred? But we have also "Skills" heading. Could put preferred qualifications under Skills. Or we could have Requirements (required) and Qualifications (preferred). The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide mapping. We have required qualifications: Bachelor's degree, 5 years military/industry experience, DoD 8140/8570 certification, 5 years professional experience in any of the following: Linux engineering, Hybrid infrastructure, HPC/AI cluster operations, virtualization, Experience supporting secure government systems per DoD/IC policies. Preferred qualifications: Experience with VAST Data, Liqid composability, GPU architectures, HPC pipelines; scripting experience Python, Bash, PowerShell; DevSecOps or CI/CD automation exposure; VMware, KVM, Nutanix expertise; Experience applying DISA STIGs, CIS Benchmarks, RMF controls. Clearance: TS/SCI required. We could put Clearance under Requirements or Qualifications. Probably under Requirements as it's a requirement. Thus: - About the role: intro paragraph(s). - Responsibilities: list. - Requirements: required qualifications (degree, experience, certification, secure gov experience, TS/SCI). - Qualifications: maybe "Preferred Qualifications"? Or we could put "Qualifications" for required and "Skills" for preferred? But we already used Requirements for required. Could use Qualifications for preferred qualifications. And Skills for technical skills like scripting, hypervisor expertise, etc. But we have overlapping. Better: Use Requirements for mandatory (degree, experience, certification, clearance). Use Qualifications for preferred qualifications (VAST, Liqid, GPU, scripting, DevSecOps, VMware/KVM/Nutanix, STIGs etc). Use Skills for maybe technical skills like Linux, hypervisors, Docker/Kubernetes, HPC/storage, etc? But those are in responsibilities. Might be redundant. Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But headings list includes both; we could omit one if not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we could include only those sections that have substantive content. If we think Requirements and Qualifications overlap, we could combine them into a single "Qualifications" section covering both required and preferred. But we need to follow headings list; we can omit sections if not needed. So we could have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's six sections. That seems reasonable. Thus: - About the role: paragraph(s) about Accenture Federal Services mission, Tampa engineering team, role description. - Responsibilities: ul li list. - Qualifications: include required and preferred qualifications, maybe split into sub-sections? But we can just list all qualifications (required and preferred) as bullet points. However we need to preserve all substantive info; we can separate required vs preferred with headings inside? Not allowed to add extra headings beyond h3? We could use

to note "Required:" and "Preferred:" but that's okay. - Benefits: statement about wide variety of benefits. - Pay: pay range statement. - Schedule: fully onsite. We must not include boilerplate like "We accept applications..." etc. Now craft HTML. We need to ensure we don't repeat job title as heading. No job title appears. We'll output:

About the role

...

Responsibilities

• ...
...

Qualifications

Required: ...

Preferred: ...

Alternatively we could use ul for each. But we need to preserve all specifics: Bachelor’s degree in Computer Science, Engineering, or equivalent; 5 years of military/industry experience; Must possess and maintain DoD 8140/8570 compliant certification (e.g., Security+, CISSP, CCSP, CAP, CASP+, or other aligned baseline certs); 5 years of professional experience in any of the following: Linux engineering, Hybrid infrastructure, HPC/AI cluster operations, virtualization; Experience supporting secure government systems in accordance with DoD/IC policies; Active TS/SCI clearance. Preferred: Experience with VAST Data, Liqid composability, GPU architectures, and HPC pipelines; Scripting experience: Python, Bash, PowerShell; DevSecOps or CI/CD automation exposure (nice to have); VMware, KVM, Nutanix expertise; Experience applying DISA STIGs, CIS Benchmarks, RMF controls. We'll include those. Benefits: "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." Pay: "The base pay range for this position in these locations is $119,300—$165,100 USD. Compensation varies depending on office location, role, skill set, and level of experience." Schedule: "The role is fully onsite." Now ensure we removed all boilerplate: The intro about Accenture Federal Services mission etc we keep as About the role. We need to preserve all substantive information: The mission statement, the 13,000+ people, Glassdoor Top 100 Best Place to Work, collaborative community, hands-on experience, certifications, industry training, drive positive lasting change, support high tempo mission critical operations, Tampa engineering team works across advanced HPC and GPU compute environments, hybrid infrastructures, secure Linux platforms, emerging AI/ML workflows, Linux Engineer will operate within mission focused ecosystem, architecting and maintaining high-performance Linux systems, containerized workloads, virtualization stacks, HPC/GPU platforms, secure storage solutions, role fully onsite supports classified systems ensuring reliability, compliance, delivery of advanced compute capabilities essential to federal missions. We need to include all that in About the role paragraph(s). Could be multiple paragraphs. Let's craft About the role:

At Accenture Federal Services, the mission is to help the US federal government make the nation stronger and safer and improve life for people. With over 13,000 employees united in pursuing the limitless potential of technology and ingenuity for defense, national security, public safety, civilian, and military health clients, the company offers a collaborative and caring community where you can grow, learn, and thrive through hands‑on experience, certifications, industry training, and more. Recognized as a Glassdoor Top 100 Best Place to Work, Accenture Federal Services empowers employees to drive positive, lasting change that moves missions and the government forward.

The Tampa engineering team works across advanced HPC and GPU compute environments, hybrid infrastructures, secure Linux platforms, and emerging AI/ML workflows. As a Linux Engineer, you will operate directly within this mission‑focused ecosystem, architecting and maintaining high‑performance Linux systems, containerized workloads, virtualization stacks, HPC/GPU platforms, and secure storage solutions. The role is fully onsite and supports classified systems, ensuring reliability, compliance, and the delivery of advanced compute capabilities essential to federal missions.

That covers. Now Responsibilities list: from posting: - Deploy, configure, secure, and maintain RHEL, Rocky Linux, and Ubuntu systems. - Administer ESXi and other hypervisors; troubleshoot full stack issues from bare metal through OS and application layers. - Maintain system hardening, patching, and audit readiness aligned with operational requirements. - Build and orchestrate workloads using Docker and Kubernetes. - Support containerized AI/ML pipelines and HPC aligned job scheduling workflows. - Support HPC/AI cluster operations including Kubernetes, GPU compute, and performance tuning. - Align responsibilities directly with HPC operations and optimization requirements. - Manage high performance storage systems including VAST NFS/S3 and Liqid composability platforms. - Optimize data flows, dedu