Systems Engineer - JobID-0196

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 remove boilerplate. We need to parse the posting. Key sections: - About The Role: description paragraph(s). We'll put under

About the role

with

content. - Responsibilities: "Key Responsibilities What You Will Do:" then list bullet points. We'll put under

Responsibilities

with

• each. - Skills, Knowledge & Expertise: "Who You Are (Required):" list of required qualifications, then "What Makes You Stand Out:" list of preferred. Could combine into Requirements section. Use

  Requirements

  maybe. Must include both required and preferred? Could separate but we can combine into one list? Better to separate required and preferred as subheadings? But spec says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have Requirements and maybe Qualifications. But we need to avoid filler. We'll include a Requirements section with required items, and maybe a Qualifications section for preferred? However spec says prefer few substantive sections over many thin ones. Could combine required and preferred into one Requirements section with sub-bullets? Might be okay. We also have Benefits: list under "Why Work at IDT:" bullet list. Pay: we have Pay Range* line. Must include Pay section only if posting actually states them. It does: "$74,000 - $184,000 / year". Also note about range not reflective etc. We'll include Pay section with that info. Schedule: mention "9/80 optional schedule (2nd and 4th Friday off every month)" under Benefits? Actually it's listed under Benefits bullet list. Could also be Schedule section. Since schedule info present, we could create Schedule section with that detail. But spec says prefer few sections; we could include schedule under Benefits. However they said include a section ONLY when posting has real, specific content for it. Benefits already includes schedule bullet. So we can keep Benefits and not create separate Schedule. We must not include cookie/navigation/legal/EEO etc. Remove EEO statement. Now craft HTML. Structure:

  About the role

  ...

  Responsibilities

  • Design, implement, and test complex software in C, C++, Python, JavaScript, and Java within various development environments.
  • Analyze legacy monolithic software programs, recompiling them, and incrementally apply refactoring to modernize the software using the “brownfield” and “greenfield” methodologies.
  • Technical assessment and deconstruction of Navy tactical system code for Surface Navy Combat systems.
  • Explore and prototype next-generation solutions using artificial intelligence/machine learning, distributed processing, and modeling.
  • Interact with customers to elicit requirements and document agreements.
  • Present to organization leadership on project cost, schedule, and technical progress.
  • Software architecture development including hardware and software interfaces between software components.
  • Assist in developing user, functional, and technical requirements for tactical systems.
  • Participate and provide feedback for design & code/peer reviews.
  • Integrate individual software components into complex software environments.
  • Support test and integration activities at IDT labs and government Land Based Test Sites (LBTS).

  Requirements

  We need to include required qualifications bullet list. Required: - Bachelor’s degree in Systems Engineering or a related field, or equivalent full-time professional experience. - 0-5 years of full time professional experience. - Ability to travel up to 10% of the time, as needed. - Familiarity with combat system design and software. - Familiarity and experience with developing tactical systems software on DOD programs. - Experience with C, C++, Python, and/or Java programming languages. - Adept with developing in Linux OS environments, including shell scripting. - Ability to decompose and document requirements and specifications. - Understanding of distributed systems, algorithms, data structures and software design patterns, especially the Strangler Pattern. - Experience with Agile software development processes. - Proficiency working within a Git CM environment. - Comfortable with DevSecOps best practices. - Ability to convert vague customer requirements into a refined vision. - Ability to identify and describe algorithmic complexity. - Ability to work on-site with potential hybrid flexibility. Preferred (What Makes You Stand Out): - Up to 5 years of full-time professional experience. (actually same as required? but okay) - Familiarity with the AEGIS Weapon System Common Source Library (CSL), ideally, or Ship Self Defense System (SSDS) Single Source Library (SSL). - Experience with AEGIS, ideally, or SSDS tactical systems. - Experience utilizing Make build system, Maven, and Ant scripting. - Experience with X-Windows. - Familiar with Model Based System Engineering (MBSE) methodologies. - Experience with Jenkins, Jira, and the Atlassian tool suite. - Familiarity with foundational networking concepts such as routing, switching, identity services, intrusion detection, and firewall. - Familiarity deploying virtual machines in VMWare vSphere environments including networking configuration. - Familiarity designing complex software development environments including submodules, remote dependencies, and mixed-code deployments. - Familiarity deploying virtual machines and/or containers into Azure cloud environments including networking configuration. - Solid analytical abilities, coupled with a strong sense of ownership, urgency, and drive. - Problem-solving skills with the ability to navigate ambiguous situations. - Excellence in oral, written, and technical communication with peers and non-technical cohorts. - Initiative, creativity, reliability, teamwork. - Strong organization and planning skills. - Attention to detail while ability to see and understand the big picture. We could combine required and preferred into one list but maybe better to separate with subheadings? But spec only allows headings for sections; we could have

  Required Qualifications

  and

  Preferred Qualifications

  but those aren't in the allowed list? The allowed list includes Requirements, Qualifications, Skills. We could use Qualifications for required and maybe Skills for preferred? But better to keep one Requirements section with both required and preferred, maybe label within

  or . However spec says use

  • for any list of duties/requirements/benefits. So we can have two lists under same heading? Could do

    Requirements

    then

    Required:

    ... then

    Preferred:

    ... That's acceptable. Now Benefits:

    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:

    Pay

    $74,000 - $184,000 per year (actual compensation dependent on experience, skills, and education; does not include bonuses, commissions, tips, or other benefits).

    We should not include the note about "This amount may not be reflective..." but we can summarize. It's okay to include that detail as it's substantive. We'll include the sentence. Now ensure we didn't include any boilerplate like EEO, etc. Check for duplicate lines: we removed "Job Benefits Why Work at Innovative Defense Technologies (IDT):" we turned into Benefits. Check for location: we didn't include location as heading; but location info is in description maybe not needed. The posting includes Department, Location, Compensation. We already have Pay. Location could be included in About the role paragraph? The About the role paragraph currently only includes description; we could add location info there. But spec says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep location info (Arlington, VA or Mount Laurel, NJ). Also department Engineering. Should we include that? It's substantive. Could add to About the role paragraph: "Innovative Defense Technologies (IDT), a leading defense technology company, is seeking a Systems Engineer to be part of our Warfare Systems team and based out of our Arlington, VA or Mount Laurel, NJ location." That's already in the description. We'll keep that. Also compensation line: we already have Pay. Now ensure we didn't include "Department: Engineering" etc. Could add a short paragraph about department? Might be okay to include in About the role: "Department: Engineering". But we can incorporate. Let's craft About the role paragraph: "Innovative Defense Technologies (IDT), a leading defense technology company, is seeking a Systems Engineer to be part of our Warfare Systems team and based out of our Arlington, VA or Mount Laurel, NJ location. The Systems Engineer will work as a critical part of a multi-discipline team focused on the DOD’s initiatives in support of tactical capability development for Navy surface and unmanned (UxVs) platforms. The Warfare Systems project domains include real-time automated test and analysis, virtual computing environments, Artificial Intelligence (AI) & Machine Learning (ML) based data analytics, cybersecurity, as well as backfit and forward-fit tactical solutions. The successful candidate will be fiercely accountable for the delivery of uncompromisingly punctual and fiscally disciplined solutions that not only meet but go above and beyond the expectations of every customer." We could also add department: Engineering. Maybe add at start: "Department: Engineering". But that's minor; we can include as part of paragraph. Now ensure we didn't include any fluff like "Clearance & Location Requirements:" we need to keep clearance requirement: "All applicants must be able to obtain/maintain an active Secret U.S. Security Clearance. This is an on-site position. Requiring at least 4 days in office, based out of our Arlington, VA and Mount Laurel, NJ locations." This is substantive; we should include it somewhere. Could add to About the role or a separate section like "Clearance & Location". But we don't have a heading for that; we could incorporate into About the role paragraph after description. Or we could add a

    Clearance & Location

    but not in allowed list. Better to fold into About the role or maybe a

    under About the role. We'll add a paragraph after the role description: "All applicants must be able to obtain/maintain an active Secret U.S. Security Clearance. This is an on‑site position requiring at least 4 days in the office, based out of the Arlington, VA and Mount Laurel, NJ locations." Now ensure we didn't repeat location multiple times; it's okay. Now check for any other substantive info: "If you see yourself reflected in this role and are excited about the impact you could make, we encourage you to apply! If you know someone who may be a great fit, please feel free to share this opportunity with your network." That's application encouragement; we should remove as per instruction: remove application instructions. So we remove that. Also "Pay Range*: $74,000 - $184,000 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