Software Integration Engineer 4 - Linux/Bash/Python/VMware/Ansible/Docker/Gitlab
headings and - for lists,
for prose.
We must not repeat job title as heading. Not include Job ID.
We need to preserve all substantive information.
Let's craft sections:
About the role: prose paragraph(s). Could combine the initial motivational sentences and the description.
Responsibilities: list of duties: test, evaluation, integration, troubleshooting of HPC software stack and related system issues.
Requirements: maybe security clearance and citizenship.
Qualifications: education/experience details.
Skills: Required Skills and Desired Skills maybe combined under Skills heading with subheadings? But we only allowed headings as per list; we could have Skills heading and then separate Required and Desired as or separate with note. Could also split into Required Skills and Desired Skills headings but those are not in allowed list; but we could still use them? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It doesn't forbid other headings, but better to stick to those. So we can have Skills heading and inside we can have two lists: Required Skills and Desired Skills, each preceded by a
or . That's okay.
Benefits: list.
Pay: maybe just salary.
We must not include sections with filler like "commensurate with experience". We have concrete salary range.
Now produce HTML.
Let's draft:
About the role
Build to something to be proud of. Captivation has built a reputation on providing customers exactly what is needed in a timely manner. Our team of engineers take pride in what they develop and constantly innovate to provide the best solution. Captivation is looking for software developers who can get stuff done while making a difference in support of the mission to protect our country. Captivation Software is looking for a senior level software integration engineer who shall be responsible for the test, evaluation, integration, and troubleshooting of the HPC software stack and related system issues.
But note that the last sentence is also responsibilities; maybe we should separate.
Better: About the role: first paragraph about company and mission. Responsibilities: list.
Thus:
About the role
Build to something to be proud of. Captivation has built a reputation on providing customers exactly what is needed in a timely manner. Our team of engineers take pride in what they develop and constantly innovate to provide the best solution. Captivation is looking for software developers who can get stuff done while making a difference in support of the mission to protect our country.
Responsibilities
- Test, evaluate, integrate, and troubleshoot the HPC software stack and related system issues.
Requirements
- Must currently hold a Top Secret/SCI U.S. Government security clearance with a favorable Polygraph.
- U.S. citizenship (required for the clearance).
Qualifications
- Bachelor's Degree in Computer Science or related field and at least ten (10) years of demonstrable experience with integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment.
- Five (5) years full‑time Computer Science directly related work can be substituted for the degree, while still requiring at least ten (10) years of demonstrable experience.
- An industry‑recognized professional certification (as defined in the TT0s) may substitute for one (1) year of experience.
- A Master's Degree in Computer Science or related field may substitute for two (2) years of experience.
Skills
Required Skills:
- Experience with the Linux CLI and Linux tools
- Extensive recent experience using Bash/Python to develop scripts
- Solid understanding of the Slurm resource management and job scheduling tool
- Experience with integration, evaluation, and system administration of HPC systems
- Experience troubleshooting HPC system problems, including basic system administration tasks, software stack issues, and hardware issues
- Experience with IaC principles and automation tools such as Salt and Ansible
- Familiar with HPC shared file systems such as Lustre, GPFS, and Panasas
- Familiar with system monitoring tools such as Ganglia and Nagios
- Familiar with acceleration technologies such as GPU, FPGA, and ASICs
- Familiar with high-speed network interconnect technologies such as InfiniBand and Slingshot
- Familiar with open-source industry-standard HPC benchmark tooling
- Ability to troubleshoot problems with a rigorous, analytical approach that enables diagnosis of root causes and discovery of mitigation/solution paths
Desired Skills:
- Experience with the Atlassian Tool Suite (JIRA, Confluence)
- Experience supporting HPC large-scale systems and customers
Benefits
- Up to 20% 401k contribution (No Matching Required and Vested from Day 1)
- Above Market Hourly Rates
- $3,600 HSA Contribution
- 6 Weeks Paid Time Off
- Company Paid Employee Medical/Dental/Vision Insurance/Life Insurance/Short-Term & Long-Term Disability/AD&D
Pay
Annual Salary: $130,000 - $270,000 (Depends on the Years of Experience)
We should not include Schedule.
Check for any missing substantive info: The description also said "This position is open for direct hires only. We will not consider candidates from third party staffing/recruiting firms." That's substantive but maybe could be included under Requirements or a separate note. It's not a heading but we could add a under Requirements or a separate section like "Notes". But we have no heading for that. Could add a
under Requirements after list. Or we could add a
under About the role. Better to add a note under Requirements as a paragraph.
Add after Requirements list:
This position is open for direct hires only; candidates from third‑party staffing or recruiting firms will not be considered.
Also "Annual Salary: $130,000 - $270,000 (Depends on the Years of Experience)" we have.
Also "Up to 20% 401k contribution (No Matching Required and Vested from Day 1)" we have.
Also "Above Market Hourly Rates" we have.
Also "$3,600 HSA Contribution" we have.
Also "6 Weeks Paid Time Off" we have.
Also "Company Paid Employee Medical/Dental/Vision Insurance/Life Insurance/Short-Term & Long-Term Disability/AD&D" we have.
Check for any other: "Minimum Qualifications: Bachelor's Degree..." we captured.
Also "The individual shall have five (5) years full time Computer Science directly related work that can be substituted for a degree and have at least ten (10) years of demonstrable experience." captured.
Also "An industry recognized professional certification, as defined in the TT0s, may substitute as one (1) year experience." captured.
Also "A Master's Degree in Computer Science or related field may substitute for two (2) years' experience." captured.
Also "Required Skills: Experience with the Linux CLI, and Linux toolsExtensive recent experience using Bash/Python to develop scriptsSolid understanding of the Slurm resource management and job scheduling toolExperience with integration, evaluation, and system administration of HPC systemsExperience troubleshooting HPC system problems, including basic system administration tasks, including software stack issues and hardware issuesExperience with IaC principles and automation tools such as Salt and AnsibleF
for prose.
We must not repeat job title as heading. Not include Job ID.
We need to preserve all substantive information.
Let's craft sections:
About the role: prose paragraph(s). Could combine the initial motivational sentences and the description.
Responsibilities: list of duties: test, evaluation, integration, troubleshooting of HPC software stack and related system issues.
Requirements: maybe security clearance and citizenship.
Qualifications: education/experience details.
Skills: Required Skills and Desired Skills maybe combined under Skills heading with subheadings? But we only allowed headings as per list; we could have Skills heading and then separate Required and Desired as or separate or . That's okay.
Benefits: list.
Pay: maybe just salary.
We must not include sections with filler like "commensurate with experience". We have concrete salary range.
Now produce HTML.
Let's draft:
Build to something to be proud of. Captivation has built a reputation on providing customers exactly what is needed in a timely manner. Our team of engineers take pride in what they develop and constantly innovate to provide the best solution. Captivation is looking for software developers who can get stuff done while making a difference in support of the mission to protect our country. Captivation Software is looking for a senior level software integration engineer who shall be responsible for the test, evaluation, integration, and troubleshooting of the HPC software stack and related system issues. Build to something to be proud of. Captivation has built a reputation on providing customers exactly what is needed in a timely manner. Our team of engineers take pride in what they develop and constantly innovate to provide the best solution. Captivation is looking for software developers who can get stuff done while making a difference in support of the mission to protect our country. Required Skills: Desired Skills: Annual Salary: $130,000 - $270,000 (Depends on the Years of Experience) under Requirements or a separate section like "Notes". But we have no heading for that. Could add a under Requirements after list. Or we could add a under About the role. Better to add a note under Requirements as a paragraph.
Add after Requirements list: This position is open for direct hires only; candidates from third‑party staffing or recruiting firms will not be considered. with note. Could also split into Required Skills and Desired Skills headings but those are not in allowed list; but we could still use them? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It doesn't forbid other headings, but better to stick to those. So we can have Skills heading and inside we can have two lists: Required Skills and Desired Skills, each preceded by a
About the role
About the role
Responsibilities
Requirements
Qualifications
Skills
Benefits
Pay