SSDS Software Engineer - JobID-0291
Innovative Defense Technologies (IDT) · Arlington, VA · 1 mo ago
On-siteEngineering$114k–$231k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Skills, Knowledge & Expertise), Benefits, Pay, Schedule maybe. Must include only sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, navigation, etc. Must preserve all substantive info.
We need to parse the posting.
Key parts:
- Department: Engineering (maybe not needed)
- Location: Arlington, VA (maybe not needed as heading)
- Compensation: $114,000 - $231,000 / year (but later they give two ranges: $114,000 - $184,000 or $135,000 - $231,000). We need to include Pay section only if posting actually states them. It does state pay ranges. So we can include Pay section with the ranges. Must not include filler like "commensurate with experience". We can include the ranges as given.
- Description About The Role: paragraph.
- Clearance & Location Requirements: active Secret clearance, fully on-site Arlington VA.
- Key Responsibilities: list of duties.
- Skills, Knowledge & Expertise: Who You Are (Required) list, plus What Makes You Stand Out list.
- Benefits: list of benefits.
- EEO statement: remove.
We need sections: About the role (maybe heading About the role), Responsibilities, Requirements (or Skills, Knowledge & Expertise), Benefits, Pay, Schedule? Schedule: they mention "9/80 optional schedule (2nd and 4th Friday off every month)" under benefits. That's schedule info. Could be part of Benefits or separate Schedule section. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if present. Since they mention 9/80 optional schedule, we can put Schedule section with that detail. But also benefits include many items; we could keep Benefits section with list of benefits, and Schedule separate.
We must not create sections with filler. So we need to ensure each section has real content.
Let's extract content:
About the role: paragraph after "Description About The Role:" includes: "Innovative Defense Technologies (IDT), a leading defense technology company, is seeking a SSDS Software Engineer to be part of our Advanced Capabilities team and based out of our Arlington, VA location. This SSDS Software Engineer will focus heavily on designing, developing, integrating, and testing tactical combat system software interfaces, specifically interacting with naval combatants (SSDS), fire control loops, and self-defense systems (RAM/CIWS). This role requires full-time presence on-site at our Arlington, VA office."
We can keep that.
Clearance & Location Requirements: maybe we can incorporate into About the role or Requirements? Could be part of Requirements (clearance, location). But we have a separate Requirements section maybe.
Responsibilities: list:
- Design, implement, and test high-performance tactical software components using modern C++ or Java.
- Integrate software components with complex Navy tactical combat systems, specifically developing interfaces and middleware wrappers for SSDS, RAM, or CIWS data streams.
- Build low-latency software interfaces to transport tactical messages across network protocols (TCP/UDP, DDS, ActiveMQ, Kafka).
- Prototype next-generation automated testing solutions and support integration within IDT labs and on-site Navy land-based test sites (LBTS).
- Translate complex tactical Navy weapon specifications and ICDs (Interface Control Documents) into functional, automated test scripts and software requirements.
Skills, Knowledge & Expertise:
Who You Are (Required):
- Bachelor's degree in engineering, computer science, mathematics, physics or other STEM field (or equivalent full-time professional experience)
- Minimum 5 years’ experience in the design, development, and management of complex software systems for the DoD.
- Ability to travel up to 10% of the time as needed
- Strong proficiency in programming languages such as C++ or Java, with an understanding of memory management and real-time execution constraints.
- Navy Combat Systems Exposure: Hands-on software development or integration experience supporting tactical Navy programs (such as SSDS, RAM, or CIWS).
- Tactical Networking: Experience with publish-subscribe middleware like DDS (Data Distribution Service) and standard network protocols.
- Development Workflow: Proficiency with Git/SVN, Jira, Confluence, and working within structured Software Development Life Cycles (SDLC).
What Makes You Stand Out:
- DevOps & Containers: Experience with containerization (Docker, Podman), orchestration (Kubernetes, Swarm), and deployment automation (Ansible, Salt, Terraform).
- CI/CD Tools: Experience with Jenkins, JFrog Artifactory, and GitLab CI pipelines.
- Infrastructure: Experience with virtualization (VMware ESXi) and configuring basic network topologies (VLANs, routing).
- Experience with Infrastructure as Code (IaC) and configuration management tools (e.g., Terraform, Ansible).
Benefits: list:
- Generous benefits package
- Competitive PTO
- Paid holidays
- 401(k) with immediate vesting and matching
- 9/80 optional schedule (2nd and 4th Friday off every month)
- Tuition Assistance Reimbursement Program
- Professional Development Resources
- Pre-Tax Commuter Benefits
- Organization-Wide Monthly Tech Connect Events
- Annual Employee Recognition Awards
- Regular Social Events and Catered Lunches
Pay: they gave two ranges: $114,000 - $184,000 or $135,000 - $231,000. Also note "This amount may not be reflective of actual compensation that may be earned as pay is dependent on a candidate’s experience, skills, and education. The posted range does not include bonuses, commissions, tips, or other benefits. IDT is often looking to place multiple candidates at various levels. Therefore, more than one pay range has been included, commensurate with experience." We should not include filler like "commensurate with experience". We can just list the ranges as given. Possibly combine: "$114,000 - $184,000 or $135,000 - $231,000 per year". We'll keep that.
Schedule: we have 9/80 optional schedule already in benefits; but we could still have a Schedule section with that detail. However that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we incorporate schedule into Benefits and not create separate Schedule section. Since schedule is a benefit, we can keep it under Benefits. So we may not need Schedule section.
Thus sections: About the role, Responsibilities, Requirements (or Skills, Knowledge & Expertise), Benefits, Pay.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if present. Since they mention 9/80 optional schedule, we can put Schedule section with that detail. But also benefits include many items; we could keep Benefits section with list of benefits, and Schedule separate.
We must not create sections with filler. So we need to ensure each section has real content.
Let's extract content:
About the role: paragraph after "Description About The Role:" includes: "Innovative Defense Technologies (IDT), a leading defense technology company, is seeking a SSDS Software Engineer to be part of our Advanced Capabilities team and based out of our Arlington, VA location. This SSDS Software Engineer will focus heavily on designing, developing, integrating, and testing tactical combat system software interfaces, specifically interacting with naval combatants (SSDS), fire control loops, and self-defense systems (RAM/CIWS). This role requires full-time presence on-site at our Arlington, VA office."
We can keep that.
Clearance & Location Requirements: maybe we can incorporate into About the role or Requirements? Could be part of Requirements (clearance, location). But we have a separate Requirements section maybe.
Responsibilities: list:
- Design, implement, and test high-performance tactical software components using modern C++ or Java.
- Integrate software components with complex Navy tactical combat systems, specifically developing interfaces and middleware wrappers for SSDS, RAM, or CIWS data streams.
- Build low-latency software interfaces to transport tactical messages across network protocols (TCP/UDP, DDS, ActiveMQ, Kafka).
- Prototype next-generation automated testing solutions and support integration within IDT labs and on-site Navy land-based test sites (LBTS).
- Translate complex tactical Navy weapon specifications and ICDs (Interface Control Documents) into functional, automated test scripts and software requirements.
Skills, Knowledge & Expertise:
Who You Are (Required):
- Bachelor's degree in engineering, computer science, mathematics, physics or other STEM field (or equivalent full-time professional experience)
- Minimum 5 years’ experience in the design, development, and management of complex software systems for the DoD.
- Ability to travel up to 10% of the time as needed
- Strong proficiency in programming languages such as C++ or Java, with an understanding of memory management and real-time execution constraints.
- Navy Combat Systems Exposure: Hands-on software development or integration experience supporting tactical Navy programs (such as SSDS, RAM, or CIWS).
- Tactical Networking: Experience with publish-subscribe middleware like DDS (Data Distribution Service) and standard network protocols.
- Development Workflow: Proficiency with Git/SVN, Jira, Confluence, and working within structured Software Development Life Cycles (SDLC).
What Makes You Stand Out:
- DevOps & Containers: Experience with containerization (Docker, Podman), orchestration (Kubernetes, Swarm), and deployment automation (Ansible, Salt, Terraform).
- CI/CD Tools: Experience with Jenkins, JFrog Artifactory, and GitLab CI pipelines.
- Infrastructure: Experience with virtualization (VMware ESXi) and configuring basic network topologies (VLANs, routing).
- Experience with Infrastructure as Code (IaC) and configuration management tools (e.g., Terraform, Ansible).
Benefits: list:
- Generous benefits package
- Competitive PTO
- Paid holidays
- 401(k) with immediate vesting and matching
- 9/80 optional schedule (2nd and 4th Friday off every month)
- Tuition Assistance Reimbursement Program
- Professional Development Resources
- Pre-Tax Commuter Benefits
- Organization-Wide Monthly Tech Connect Events
- Annual Employee Recognition Awards
- Regular Social Events and Catered Lunches
Pay: they gave two ranges: $114,000 - $184,000 or $135,000 - $231,000. Also note "This amount may not be reflective of actual compensation that may be earned as pay is dependent on a candidate’s experience, skills, and education. The posted range does not include bonuses, commissions, tips, or other benefits. IDT is often looking to place multiple candidates at various levels. Therefore, more than one pay range has been included, commensurate with experience." We should not include filler like "commensurate with experience". We can just list the ranges as given. Possibly combine: "$114,000 - $184,000 or $135,000 - $231,000 per year". We'll keep that.
Schedule: we have 9/80 optional schedule already in benefits; but we could still have a Schedule section with that detail. However that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we incorporate schedule into Benefits and not create separate Schedule section. Since schedule is a benefit, we can keep it under Benefits. So we may not need Schedule section.
Thus sections: About the role, Responsibilities, Requirements (or Skills, Knowledge & Expertise), Benefits, Pay.
We need to use for each section heading.
Inside sections: use
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc.
We must not include boilerplate like EEO.
We must preserve all substantive information. Ensure we include clearance requirement, location requirement (on-site Arlington VA). Where to put? Could be in About the role or Requirements. Since we have a Requirements section, we can include clearance and location there.
Let's craft:
About the role
Innovative Defense Technologies (IDT), a leading defense technology company, is seeking a SSDS Software Engineer to be part of our Advanced Capabilities team and based out of our Arlington, VA location. This SSDS Software Engineer will focus heavily on designing, developing, integrating, and testing tactical combat system software interfaces, specifically interacting with naval combatants (SSDS), fire control loops, and self-defense systems (RAM/CIWS). This role requires full-time presence on-site at our Arlington, VA office.
Responsibilities
- Design, implement, and test high-performance tactical software components using modern C++ or Java.
- Integrate software components with complex Navy tactical combat systems, specifically developing interfaces and middleware wrappers for SSDS, RAM, or CIWS data streams.
- Build low-latency software interfaces to transport tactical messages across network protocols (TCP/UDP, DDS, ActiveMQ, Kafka).
- Prototype next-generation automated testing solutions and support integration within IDT labs and on-site Navy land-based test sites (LBTS).
- Translate complex tactical Navy weapon specifications and ICDs (Interface Control Documents) into functional, automated test scripts and software requirements.
Requirements
All applicants must currently possess an active Secret U.S. Security Clearance. This is a fully on-site position based out of Arlington, VA.
- Bachelor's degree in engineering, computer science, mathematics, physics or other STEM field (or equivalent full-time professional experience)
- Minimum 5 years’ experience in the design, development, and management of complex software systems for the DoD.
- Ability to travel up to 10% of the time as needed
- Strong proficiency in programming languages such as C++ or Java, with an understanding of memory management and real-time execution constraints.
- Navy Combat Systems Exposure: Hands-on software development or integration experience supporting tactical Navy programs (such as SSDS, RAM, or CIWS).
- Tactical Networking: Experience with publish-subscribe middleware like DDS (Data Distribution Service) and standard network protocols.
- Development Workflow: Proficiency with Git/SVN, Jira, Confluence, and working within structured Software Development Life Cycles (SDLC).
What makes you stand out:
- DevOps & Containers: Experience with containerization (Docker, Podman), orchestration (Kubernetes, Swarm), and deployment automation (Ansible, Salt, Terraform).
- CI/CD Tools: Experience with Jenkins, JFrog Artifactory, and GitLab CI pipelines.
- Infrastructure: Experience with virtualization (VMware ESXi) and configuring basic network topologies (VLANs, routing).
- Experience with Infrastructure as Code (IaC) and configuration management tools (e.g., Terraform, Ansible).
Benefits
- Generous benefits package
- Competitive PTO
- Paid holidays
- 401(k) with immediate vesting and matching
- 9/80 optional schedule (2nd and 4th Friday off every month)
- Tuition Assistance Reimbursement Program
- Professional Development Resources
- Pre-Tax Commuter Benefits
- Organization-Wide Monthly Tech Connect Events
- Annual Employee Recognition Awards
- Regular Social Events and Catered Lunches
Pay
$114,000 - $184,000 or $135,000 - $231,000 per year
We must ensure we didn't include any filler like "commensurate with experience". We omitted that. Check for any duplicated lines: we have not included navigation etc. Check for any mention of "EEO Statement": removed. Check for any mention of "Job Benefits Why Work at Innovative Defense Technologies (IDT):" we turned into Benefits section. Check for any mention of "Clearance & Location Requirements": we incorporated into Requirements. Check for any mention of "Department: Engineering" and "Location: Arlington, VA" - we didn't include those as headings; location is in About the role and Requirements. Department not needed. Check for any mention of "Compensation: $11