Systems Engineer (Engineer Systems 2)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, accommodation, etc. Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also we should not include sections like "Benefits", "Pay", "Schedule" unless posting actually states them. The posting includes "Anticipated Salary Range: $75,867.00 - $108,381.00". That's pay info, so we can include a Pay section. It also includes "Required Travel: 0 - 10%" maybe could be under Schedule? Not exactly schedule. Travel is not schedule. There's no explicit schedule (e.g., full-time). It says Employment Type: Full Time/Salaried/Exempt. That could be considered schedule? Possibly we could include a Schedule section with "Full Time". But the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Employment Type: Full Time/Salaried/Exempt. That's schedule info. So we could include a Schedule section with that. Benefits: not mentioned. So we omit Benefits. We need sections: About the role (maybe from the descriptive paragraphs). Responsibilities (list). Requirements (list). Qualifications? Might be overlapping with Requirements. The posting includes "Requirements:" and "Preferred Requirements". Could treat Requirements as required qualifications, and Preferred as maybe Skills? But we have sections: Qualifications, Skills. We need to decide where to put content. The posting includes "Experience in various embedded programming languages..." etc under Requirements. Also "Preferred Requirements" list. Could map required requirements to Requirements section, and preferred to Skills or Qualifications. However we must not invent sections if content is thin. Let's see. We have: - About the role: The paragraph starting "This opportunity resides with Warfare Systems (WS)..." and subsequent paragraphs describing HII, leadership capabilities, etc. Also "Come Join HII! Where Hard Stuff is Done Right!" and description of role: "HII, Mission Technologies is seeking self-motivated, talented Systems Engineers to design, develop, and test command, control, and communications system for leading edge ISR, EW, and launcher DoD products." That's about the role. - Responsibilities: list after "Responsibilities:" includes bullet points (though not formatted as bullet but sentences). We need to extract each duty as

. The text: "I want to and can do that! Participate in all phases of system lifecycle, from requirements definition through design, development, integration, and test with minimal supervision. Be a big picture thinker and understand the impacts to the whole system. Guide customers and other engineers in formulating system/hardware/software requirements, advise on alternative approaches, and conduct feasibility studies, as required. Prepare and communicate daily status information in accordance with required development lifecycles. Independently derives requirements into actionable tasks. Follow all company policies and guidelines, including familiarity with company-wide engineering practices." We need to split into list items. Probably each sentence is a duty. We'll create

• for each. - Requirements: list after "Requirements:" includes: "2 years relevant experience with Bachelors in related field; 0 years experience with Masters in related field Experience in various embedded programming languages (e.g. Embedded C/C++, C/C++) Experience in industry-standard systems engineering documentation methods such as user stories, SYSML, Agile and supporting tools such as Doxygen, Bamboo, JIRA Knowledge in Model Based Systems Engineering. Use of tools such as Cameo, Doors, Rhapsody, etc. Must be a U.S. citizen. Ability to obtain and maintain a secret government security clearance." We'll make each as
• . - Preferred Requirements: list after "Preferred Requirements": "Currently hold a U.S. security clearance. Experience in the DoD contractor space, especially maritime. Experience with the C/C++/Python/Matlab programming Experience with Cameo and MBSE tools. Experience in leading junior software engineers. Passionate about protecting the American warfighter. Experience with RF communication links and/or radio systems" We could treat these as Skills or Qualifications. Since we have Skills section, we could put them there. Or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Preferred into one Requirements section? But they are distinct. Could have Requirements (required) and Skills (preferred). That seems reasonable. We also have Pay section: Anticipated Salary Range. Schedule section: Employment Type: Full Time/Salaried/Exempt. We should not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines. Also remove "Requisition Number: 30382 Required Travel: 0 - 10% Employment Type: Full Time/Salaried/Exempt Anticipated Salary Range: $75,867.00 - $108,381.00 Security Clearance: Ability to Obtain Level of Experience: Mid". We need to preserve substantive info: Required Travel (0-10%) maybe could be placed under Schedule or a separate section? There's no specific heading for Travel. Could include under Schedule as note? But schedule section is for work schedule; travel is not schedule. Could we create a separate section? Not in allowed headings list. The allowed headings are only those listed. So we must fold travel info into a short

  or drop it. Since we cannot create a new heading, we can include travel info in a paragraph under About the role or maybe under Schedule? Probably better to include in a short paragraph after the headings, maybe as a

  before sections. But the instruction: "fold minor metadata into a short

  or drop it." So we can create a

  that includes Requisition Number? Actually they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include Requisition Number, Required Travel, Employment Type, Anticipated Salary Range, Security Clearance, Level of Experience in a short paragraph. However we also need to include Pay and Schedule sections separately if they have real content. But we might duplicate if we also put them in the metadata paragraph. Better to extract Pay and Schedule into their own sections, and leave other metadata (Requisition Number, Required Travel, Security Clearance, Level of Experience) in a short

  . But note that Security Clearance is also mentioned in Requirements (Ability to obtain and maintain a secret government security clearance). So we might not need to duplicate. Let's decide: We'll create a short

  for metadata: "Requisition Number: 30382 | Required Travel: 0‑10% | Level of Experience: Mid". That's minor metadata. We'll not include Security Clearance there because it's covered in Requirements. We'll not include Employment Type there because we have Schedule section. We'll not include Salary there because we have Pay section. Now sections: - About the role: combine the descriptive paragraphs. We need to ensure we don't include boilerplate like "Leadership at HII – Mission Technologies HII’s Leadership Capability Framework Defines The Standard Of Excellence Expected Of All Leaders Across Mission Technologies. Leaders Are Accountable For Modeling These Capabilities And Building Them Within Their Teams Know & Grow Your People – Develop talent, empower teams, and build an inclusive environment.Build Relationships – Strengthen trust, collaboration, and cross-functional partnerships.Take Ownership – Drive accountability, execution excellence, and results.Customer First – Anticipate mission needs and deliver value to our partners.Shape the Future – Inspire innovation and align work with strategic priorities.Act with Urgency – Make informed decisions and move with purpose. These capabilities define how leaders inspire teams, deliver results, and shape the future of Mission". This is still part of the description about the company and leadership; it's substantive? It's generic but it's in the posting. We should preserve all substantive information; we cannot invent or summarize away detail. So we should keep it. However it's quite long and maybe considered boilerplate? It's not explicitly listed as boilerplate to remove (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). It's about leadership capabilities; it's part of the job posting. We'll keep it. But we need to be careful not to include duplicated lines. There's a duplicated phrase "Come Join HII! Where Hard Stuff is Done Right!" appears maybe once. We'll keep. Now Responsibilities: we need to list each duty as

• . Let's split sentences: 1. Participate in all phases of system lifecycle, from requirements definition through design, development, integration, and test with minimal supervision. 2. Be a big picture thinker and understand the impacts to the whole system. 3. Guide customers and other engineers in formulating system/hardware/software requirements, advise on alternative approaches, and conduct feasibility studies, as required. 4. Prepare and communicate daily status information in accordance with required development lifecycles. 5. Independently derives requirements into actionable tasks. 6. Follow all company policies and guidelines, including familiarity with company-wide engineering practices. Note: "Independently derives" maybe grammar but keep. Now Requirements: list each: 1. 2 years relevant experience with Bachelors in related field; 0 years experience with Masters in related field 2. Experience in various embedded programming languages (e.g. Embedded C/C++, C/C++) 3. Experience in industry-standard systems engineering documentation methods such as user stories, SYSML, Agile and supporting tools such as Doxygen, Bamboo, JIRA 4. Knowledge in Model Based Systems Engineering. Use of tools such as Cameo, Doors, Rhapsody, etc. 5. Must be a U.S. citizen. 6. Ability to obtain and maintain a secret government security clearance. Now Skills (preferred): list: 1. Currently hold a U.S. security clearance. 2. Experience in the DoD contractor space, especially maritime. 3. Experience with the C/C++/Python/Matlab programming 4. Experience with Cameo and MBSE tools. 5. Experience in leading junior software engineers. 6. Passionate about protecting the American warfighter. 7. Experience with RF communication links and/or radio systems Now Pay: we have Anticipated Salary Range: $75,867.00 - $108,381.00. We'll put in

  maybe. Schedule: Employment Type: Full Time/Salaried/Exempt. We'll put in

  . Now About the role: we need to include paragraphs. Let's extract the relevant descriptive text before Responsibilities. From the posting: "This opportunity resides with Warfare Systems (WS), a business group within HII’s Mission Technologies division. Warfare Systems comprises cyber and mission IT; electronic warfare; and C5ISR systems. HII works within our nation’s intelligence and cyber operations communities to defend our interests in cyberspace and anticipate emerging threats. Our capabilities in cybersecurity, network architecture, reverse engineering, software and hardware development uniquely enable us to support sensitive missions for the U.S. military and federal agency partners. Leadership at HII – Mission Technologies HII’s Leadership Capability Framework Defines The Standard Of Excellence Expected Of All Leaders Across Mission Technologies. Leaders Are Accountable For Modeling These Capabilities And Building Them Within Their Teams Know & Grow Your People – Develop talent, empower teams, and build an inclusive environment.Build Relationships – Strengthen trust, collaboration, and cross-functional partnerships.Take Ownership – Drive accountability, execution excellence, and results.Customer First – Anticipate mission needs and deliver value to our partners.Shape the Future – Inspire innovation and align work with strategic priorities.Act with Urgency – Make informed decisions and move with purpose. These capabilities define how leaders inspire teams, deliver results, and shape the future of Mission Come Join HII! Where Hard Stuff is Done Right!