Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Opportunity PeopleTec is currently seeking a Software Engineer to support our Huntsville, AL location. The candidate will serve as a Software Engineer within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will review contract deliverables, provide recommendations, and provide technical management of the supplier's software development process and products across the system lifecycle, collaborating with product, design, security, operations, and other stakeholders to deliver scalable, secure, and user-focused technical solutions. The candidate will prepare and present software engineering findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of software engineering technical and programmatic objectives." Then "Duties" list: bullet points. Then "Qualifications" section: "Required Skills/Experience: 5+ years of relevant experience. Additional education may be substituted for years of experience. Demonstrated experience in software engineering, particularly within defense or aerospace industries. Knowledge of Agile software development and open standards software development. Strong knowledge of industry standards and defense requirements. Excellent communication and presentation skills. Ability to lead and work within a multidisciplinary team. Previous experience working in a U.S. Government Program Office (required). Travel: 25% Must be a U.S. Citizen An active DoD Secret clearance is required to perform this work. Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment. Education Requirements Bachelor's degree in Software Engineering (or related technical discipline). Desired Skills Top Secret clearance preferred" Then "Overview People First. Technology Always. PeopleTec, Inc. is an employee-owned small business founded in Huntsville, AL that provides exceptional customer support by employing and retaining a highly skilled workforce. Culture: The name "PeopleTec" was deliberately chosen to remind us of our core value system - our people. Our company's foundation was built on placing our employees and customers first. With an award-winning atmosphere, we have matured into a company that boasts the best and brightest across multiple technical fields. Career: At PeopleTec, we value your long-term goals. Whether it's through our continuing-education opportunities, our robust training programs, or our "People First" benefits package, PeopleTec truly believes that our best investments are our people. Come Experience It. #cjpost #dpost" Then EEO etc. We need to extract sections: - About the role: Could be the introductory paragraph(s) describing role. Could be "Opportunity PeopleTec...". We'll put that as About the role. - Responsibilities: The Duties list (the bullet points). Also maybe some responsibilities from earlier paragraphs (like reviewing contract deliverables, providing recommendations, technical management, preparing reports, leading team, interfacing). But we have a Duties section that enumerates them. We'll treat Duties as Responsibilities. - Requirements: Could be the qualifications (required skills/experience). Might be separate from Qualifications? The posting has "Qualifications" heading. We'll map that to Qualifications section. Also maybe "Education Requirements" is part of Qualifications. - Skills: Could be "Desired Skills Top Secret clearance preferred". Also maybe "Excellent communication and presentation skills" etc. But those are in qualifications. We could separate Skills as desired skills (Top Secret clearance). But we need to avoid thin sections. Might combine Skills into Qualifications? The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (which includes required skills/experience, education, desired skills). Benefits, Pay, Schedule: we need to see if any info present. Benefits: The overview mentions "People First" benefits package but not specific. It says "our 'People First' benefits package". That's vague but it's a mention of benefits. However it's not specific detail; it's just a phrase. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "People First" benefits package is a mention but not specific. Is that enough? It's not a specific benefit like health insurance, 401k, etc. It's vague. Likely we should not create Benefits section because no concrete benefits listed. Similarly Pay: no salary info. Schedule: no schedule info (maybe travel 25% but that's travel, not schedule). So we omit Benefits, Pay, Schedule. Thus we will have sections: About the role, Responsibilities, Qualifications. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, legal, application instructions, cookie/navigation, duplicated lines. We need to include the content exactly as given but maybe rephrase? We must preserve all substantive information; we can keep the same sentences but we can format. We need to ensure we don't repeat job title as heading. The job title is Software Engineer; we won't put that as heading. We need to not put Job ID/requisition numbers as headings (none present). We need to output only HTML fragment. Let's craft:

  About the role

  PeopleTec is currently seeking a Software Engineer to support our Huntsville, AL location. The candidate will serve as a Software Engineer within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will review contract deliverables, provide recommendations, and provide technical management of the supplier's software development process and products across the system lifecycle, collaborating with product, design, security, operations, and other stakeholders to deliver scalable, secure, and user-focused technical solutions. The candidate will prepare and present software engineering findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of software engineering technical and programmatic objectives.

  Then Responsibilities:

  Responsibilities

  • Provide technical support and leadership in software engineering across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment).
  • Author software requirements for placement on contract and maintain traceability through delivery.
  • Review software contract deliverables (CDRLs) and provide technical recommendations for Government acceptance.
  • Define and validate requirements for a single pane of glass, enabling one fire control system to manage many sensors and effectors.
  • Ensure developer APIs and SDKs for third-party sensor/effector vendor integration are specified, delivered, and validated.
  • Establish and develop the Glueware interfaces needed to support open systems and prevent Government vendor lock.
  • Oversee sprint execution and assess delivered increments against the open systems architecture enabling rapid integration of sensors and effectors.
  • Evaluate automation approaches that reduce operator cognitive load, improving kill chain actions and time to engage.
  • Ensure compliance with defense and industry standards by managing software engineering processes effectively.
  • Interface with internal teams and external organizations to coordinate software engineering objectives and strategies.
  • Prepare and present software engineering findings, reports, and improvement plans to senior management and stakeholders.
  • Conduct strategic planning and coordination to support program objectives.
  • Provide technical guidance and leadership to peer and subordinate engineers within the software engineering team.
  • Use digital tools and methodologies to manage cost, schedule, and performance for assigned activities.
  • Perform other tasks as assigned by the Chief Engineer and/or Product Manager.
  Qualifications: We need to include required skills/experience, education, desired skills (Top Secret clearance preferred). Also travel 25%, US Citizen, active DoD Secret clearance required, ability to maintain clearance. We should format as

  for prose, but we have list-like items. Could use

  for required skills/experience list. The instruction: Use
  • for any list of duties/requirements/benefits. So we can list qualifications as list. Let's extract: - 5+ years of relevant experience. Additional education may be substituted for years of experience. - Demonstrated experience in software engineering, particularly within defense or aerospace industries. - Knowledge of Agile software development and open standards software development. - Strong knowledge of industry standards and defense requirements. - Excellent communication and presentation skills. - Ability to lead and work within a multidisciplinary team. - Previous experience working in a U.S. Government Program Office (required). - Travel: 25% - Must be a U.S. Citizen - An active DoD Secret clearance is required to perform this work. - Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment. - Education Requirements: Bachelor's degree in Software Engineering (or related technical discipline). - Desired Skills: Top Secret clearance preferred. We could combine some sentences. We'll output:

    Qualifications

    • 5+ years of relevant experience; additional education may be substituted for years of experience.
    • Demonstrated experience in software engineering, particularly within defense or aerospace industries.
    • Knowledge of Agile software development and open standards software development.
    • Strong knowledge of industry standards and defense requirements.
    • Excellent communication and presentation skills.
    • Ability to lead and work within a multidisciplinary team.
    • Previous experience working in a U.S. Government Program Office (required).
    • Travel: 25%.
    • Must be a U.S. Citizen.
    • An active DoD Secret clearance is required to perform this work; candidates must have an active Secret clearance upon hire and maintain it during employment.
    • Education: Bachelor's degree in Software Engineering (or related technical discipline).
    • Desired: Top Secret clearance preferred.
    We should ensure we didn't lose any substantive info: The overview about PeopleTec culture etc. That's not required for sections; we could include as About the role? Already we have introductory paragraph. The overview about PeopleTec is more about company; could be considered "About the company" but we don't have a heading for that. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We could add an "About the company" section but not requested headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not add extra headings. The overview about PeopleTec could be considered part of About the role? It's not about the role but about company. However we might incorporate it into About the role as extra prose