Software Integrator
Scientific Research Corporation · North Charleston, SC · 3 wk ago
Full-time
We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About Us" maybe? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have posting content: first paragraph: "Supporting the planning, coordination, and execution of system and software integration, qualification, and regression testing ..." etc. That's responsibilities.
Then "Requirements" section: list of requirements.
Then "Desired Skills" maybe qualifies as Skills or Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: Responsibilities, Requirements, Qualifications (maybe desired skills), Skills (maybe desired skills?), Benefits (we have benefits info in About Us: "SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more." That's benefits.
Pay: Not specified. So we should NOT include Pay section because no specific pay info.
Schedule: Travel Requirements 5% maybe schedule? It says Travel Requirements 5% - that's travel, not schedule. No schedule info. So we omit Schedule.
About the role: Could be a brief summary? The posting does not have an explicit "About the role" heading, but we could create one from the introductory paragraph? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could include About the role if we have content. The first paragraph(s) could be considered About the role. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role as a heading with a paragraph summarizing the role. The initial sentences: "Supporting the planning, coordination, and execution of system and software integration, qualification, and regression testing Configuring and operating virtualized test environments (e.g., VMware) that simulate target operational baselines, including installation of fully compliant IA software Integrating new software baselines, capability enhancements, and patches on engineering systems while ensuring compatibility with existing hardware, sensors, and C5ISR interfaces Supporting development, integration, and testing of interfaces enabling data sharing between USMC C5ISR systems, Fires systems, and Naval/Joint C2/Fires systems Executing Nessus/ACAS scans during integration activities; analyze results, support remediation actions, and verify closure of vulnerabilities in coordination with cybersecurity engineering personnel Maintaining authorized software baselines by applying security patches, updates, and configuration changes consistent with ATO requirements and RMF artifacts Developing and maintaining STPs, test procedures, and test reports for each software build and system release, accurately capturing test configurations, standardized results, and defect status for Government review Producing and updating technical documentation, including software installation guides, build plans, build lists, version descriptions, configuration/user guides, and baseline comparison matrices Reproducing, thoroughly documenting, and tracking defects found during integration and test events, providing clear steps to reproduce, relevant logs, and environment details Collaborating closely with software developers, systems engineers, and cybersecurity personnel to analyze root cause, verify corrective actions, and re‑test fixes as part of regression testing Supporting configuration management activities for integration and test artifacts, ensuring accurate status accounting of software loads, configurations, and test results within CMPro and other program repositories"
That is a long list of responsibilities. So we could treat that as Responsibilities section. Then About the role could be a brief overview: maybe the first sentence? But we risk duplication. Better to treat the initial block as Responsibilities. Then we could omit About the role if we don't have distinct content. However instruction says "Prefer a few substantive sections over many thin ones." So we could have Responsibilities, Requirements, Qualifications (maybe desired skills), Skills (maybe desired skills?), Benefits. But we need to avoid thin sections.
We have Requirements (mandatory). Desired Skills could go under Qualifications or Skills. The instruction lists Qualifications and Skills as separate possible headings. We could put desired skills under Qualifications (like education, experience) and maybe Skills under Skills (like specific tools). But we have both mandatory and desired. Could combine: Requirements (mandatory) and Qualifications (desired). Or we could have Requirements and Skills (desired). Let's decide: Use Requirements for mandatory items. Use Qualifications for desired education/experience (Bachelor of science, more than two years experience supporting DoD C5ISR, familiarity with TAK, Agile/SCRUM, TEMP development). Use Skills for desired technical skills (TAK/WinTAK/ATAK, biometric/exploitation tools, etc). But there is overlap.
Better: Use Requirements for mandatory. Use Qualifications for desired education and experience (Bachelor's, >2 years DoD C5ISR, familiarity with TAK, Agile/SCRUM, TEMP). Use Skills for desired technical skills (TAK/WinTAK/ATAK, biometric/exploitation tools, etc). However many of those are also skills.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section called Qualifications (or Skills). But the instruction says we can use those headings if we have content. We can choose to have only Responsibilities, Requirements, Benefits. That's three substantive sections. That might be enough. The desired skills could be included under Requirements? But they are desired, not required. However we could still include them under Requirements as "Preferred qualifications". But the instruction says we must preserve ALL substantive information; we cannot omit desired skills. So we need to include them somewhere.
We could have a section "Qualifications" that includes both education and desired experience. Or we could have "Skills" for desired technical skills. Let's produce sections: Responsibilities, Requirements, Qualifications, Benefits. That's four sections.
Now we need to format:
. Must preserve all substantive information.
Let's extract responsibilities from the block:
- Supporting the planning, coordination, and execution of system and software integration, qualification, and regression testing
- Configuring and operating virtualized test environments (e.g., VMware) that simulate target operational baselines, including installation of fully compliant IA software
- Integrating new software baselines, capability enhancements, and patches on engineering systems while ensuring compatibility with existing hardware, sensors, and C5ISR interfaces
- Supporting development, integration, and testing of interfaces enabling data sharing between USMC C5ISR systems, Fires systems, and Naval/Joint C2/Fires systems
- Executing Nessus/ACAS scans during integration activities; analyze results, support remediation actions, and verify closure of vulnerabilities in coordination with cybersecurity engineering personnel
- Maintaining authorized software baselines by applying security patches, updates, and configuration changes consistent with ATO requirements and RMF artifacts
- Developing and maintaining STPs, test procedures, and test reports for each software build and system release, accurately capturing test configurations, standardized results, and defect status for Government review
- Producing and updating technical documentation, including software installation guides, build plans, build lists, version descriptions, configuration/user guides, and baseline comparison matrices
- Reproducing, thoroughly documenting, and tracking defects found during integration and test events, providing clear steps to reproduce, relevant logs, and environment details
- Collaborating closely with software developers, systems engineers, and cybersecurity personnel to analyze root cause, verify corrective actions, and re‑test fixes as part of regression testing
- Supporting configuration management activities for integration and test artifacts, ensuring accurate status accounting of software loads, configurations, and test results within CMPro and other program repositories
That's 11 items.
Now Requirements (mandatory):
- Must possess an active CompTIA Security+ certification or obtain the credential within the first six months of employment
- At least five years of IT professional experience supporting the full lifecycle of hybrid software, web, and hardware systems, from requirements and design through integration, testing, deployment, and sustainment, including operating system, application, and hardware integration
- Demonstrated experience integrating and validating complex tactical or intelligence systems, including:
- Planning and executing system/software integration test events (e.g., IV&V, FAIT, PAT, FVT, system/subsystem testing) in laboratory environments
- Reproducing, documenting, and troubleshooting defects identified during integration and test
- Hands-on experience configuring, securing, and maintaining Windows- and Linux-based test environments using virtual machines to emulate operational baselines, including installation of IA-compliant software and support for ongoing developmental and functional testing
- Working knowledge of DoD cybersecurity requirements, including application of DISA STIGs, patching, and vulnerability management in support of RMF compliance
- Experience using SCAP, Nessus, and/or ACAS to assess system configurations against DoD cybersecurity requirements and document results for accreditation and ATO support
- Experience supporting patch installation, security updates, and maintenance of software baselines, including coordination of recurring 30‑day (or similar) security update cycles
- Experience developing or contributing to technical documentation such as test plans, test reports, installation procedures, software installation guides, software build lists (SBLs), and configuration/user documentation
- Familiarity with configuration management tools and processes (e.g., CMPro, JIRA) to manage baselines, issues, and change documentation
- Strong analytical, communication, and documentation skills with a proven ability to collaborate effectively with systems engineers, software developers, cybersecurity personnel, logisticians, and Government stakeholders
We need to preserve the bullet structure. The original had a paragraph then a list with colon and sub-items. We'll represent as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could include About the role if we have content. The first paragraph(s) could be considered About the role. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role as a heading with a paragraph summarizing the role. The initial sentences: "Supporting the planning, coordination, and execution of system and software integration, qualification, and regression testing Configuring and operating virtualized test environments (e.g., VMware) that simulate target operational baselines, including installation of fully compliant IA software Integrating new software baselines, capability enhancements, and patches on engineering systems while ensuring compatibility with existing hardware, sensors, and C5ISR interfaces Supporting development, integration, and testing of interfaces enabling data sharing between USMC C5ISR systems, Fires systems, and Naval/Joint C2/Fires systems Executing Nessus/ACAS scans during integration activities; analyze results, support remediation actions, and verify closure of vulnerabilities in coordination with cybersecurity engineering personnel Maintaining authorized software baselines by applying security patches, updates, and configuration changes consistent with ATO requirements and RMF artifacts Developing and maintaining STPs, test procedures, and test reports for each software build and system release, accurately capturing test configurations, standardized results, and defect status for Government review Producing and updating technical documentation, including software installation guides, build plans, build lists, version descriptions, configuration/user guides, and baseline comparison matrices Reproducing, thoroughly documenting, and tracking defects found during integration and test events, providing clear steps to reproduce, relevant logs, and environment details Collaborating closely with software developers, systems engineers, and cybersecurity personnel to analyze root cause, verify corrective actions, and re‑test fixes as part of regression testing Supporting configuration management activities for integration and test artifacts, ensuring accurate status accounting of software loads, configurations, and test results within CMPro and other program repositories"
That is a long list of responsibilities. So we could treat that as Responsibilities section. Then About the role could be a brief overview: maybe the first sentence? But we risk duplication. Better to treat the initial block as Responsibilities. Then we could omit About the role if we don't have distinct content. However instruction says "Prefer a few substantive sections over many thin ones." So we could have Responsibilities, Requirements, Qualifications (maybe desired skills), Skills (maybe desired skills?), Benefits. But we need to avoid thin sections.
We have Requirements (mandatory). Desired Skills could go under Qualifications or Skills. The instruction lists Qualifications and Skills as separate possible headings. We could put desired skills under Qualifications (like education, experience) and maybe Skills under Skills (like specific tools). But we have both mandatory and desired. Could combine: Requirements (mandatory) and Qualifications (desired). Or we could have Requirements and Skills (desired). Let's decide: Use Requirements for mandatory items. Use Qualifications for desired education/experience (Bachelor of science, more than two years experience supporting DoD C5ISR, familiarity with TAK, Agile/SCRUM, TEMP development). Use Skills for desired technical skills (TAK/WinTAK/ATAK, biometric/exploitation tools, etc). But there is overlap.
Better: Use Requirements for mandatory. Use Qualifications for desired education and experience (Bachelor's, >2 years DoD C5ISR, familiarity with TAK, Agile/SCRUM, TEMP). Use Skills for desired technical skills (TAK/WinTAK/ATAK, biometric/exploitation tools, etc). However many of those are also skills.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section called Qualifications (or Skills). But the instruction says we can use those headings if we have content. We can choose to have only Responsibilities, Requirements, Benefits. That's three substantive sections. That might be enough. The desired skills could be included under Requirements? But they are desired, not required. However we could still include them under Requirements as "Preferred qualifications". But the instruction says we must preserve ALL substantive information; we cannot omit desired skills. So we need to include them somewhere.
We could have a section "Qualifications" that includes both education and desired experience. Or we could have "Skills" for desired technical skills. Let's produce sections: Responsibilities, Requirements, Qualifications, Benefits. That's four sections.
Now we need to format: About the role
maybe not needed. We'll skip About the role if we don't have distinct summary. But we could include a brief overview as About the role: maybe a sentence summarizing the role: "The role involves planning, coordinating, and executing system and software integration, qualification, and regression testing; configuring virtualized test environments; integrating software baselines; supporting interface development; performing vulnerability scans; maintaining baselines; developing test procedures; documenting defects; collaborating with teams; and supporting configuration management." That's essentially the responsibilities. If we put that in About the role, then Responsibilities would be duplicate. Better to not have About the role.
Thus we will output:
Responsibilities
- ... each responsibility as
- items.
We need to break the long paragraph into list items. Each sentence or clause can be an
- ... maybe nested lists. We'll keep the main items as
- and sub-items as nested
- . Now Qualifications (desired): - Bachelor of science in computer science, computer engineering, or systems engineering - More than two years of experience supporting DoD C5ISR, intelligence, or tactical communications programs, ideally with NIWC Atlantic or Marine Corps Systems Command - Familiarity with TAK/WinTAK/ATAK, biometric/exploitation tools, and C5ISR integration with Naval and Joint C2/Fires systems - Experience working within Agile/SCRUM environments, supporting sprint test planning, execution, and build/release demonstrations - Prior experience supporting TEMP development, authoring test documentation (plans, procedures, reports), and participating in T&E WIPTs and TRBs Now Benefits: From About Us: "SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick