ME00684-System Engineer 1.5

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. Use

for headings. Use

• for lists. Use

  for prose. We need to parse the posting. Content: - Intro paragraph about company: "Momentum Engineering, Inc. fosters an employee-centric culture..." etc. That's about the role? Actually it's about the company. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under "About the role". Or maybe we could have a separate "About the company" but not allowed. So we put it under About the role. - Job Summary: "Seeking a Systems Engineer to support mission-critical operational systems and dataflow management within a dynamic technical environment This position directly contributes to mission success by helping ensure the reliability, scalability, and performance of systems that process and deliver critical mission data to end usersThe role supports modernization of dataflows and operational systems, including the transition of legacy capabilities into cloud-based environments while maintaining real-time mission supportThe ideal candidate has experience with mission systems, dataflow technologies, Linux environments, and tools such as Apache NiFi". That's prose. - Primary Responsibilities: list of bullet points. - Required Qualifications: list. - Desired Qualifications: list. - Exempt hourly position. 11 paid holidays, minimum of 3 weeks PTO, company sponsored group medical plan, company paid dental, vision, life insurance, and STD/LTD plans. Salary is dependent upon the candidate’s experience and qualifications. The Pay Range For This Role Is 130,000 - 180,000 USD per year(NBP). Thus we have Benefits: 11 paid holidays, min 3 weeks PTO, company sponsored group medical plan, company paid dental, vision, life insurance, STD/LTD plans. Pay: Salary range 130k-180k USD per year. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. Skills: Could be derived from Desired Qualifications? The instruction says we can have Skills section. But we need to decide if we have specific content for Skills. The posting includes Desired Qualifications which are essentially skills/experience. Could treat Desired Qualifications as Skills. But we also have Required Qualifications. Could combine Required and Desired under Requirements? The headings list includes Requirements and Qualifications separate. Usually Requirements = mandatory, Qualifications = desired? But they gave both Required Qualifications and Desired Qualifications. We could map Required Qualifications to Requirements section, and Desired Qualifications to Qualifications section. Or we could put Required under Requirements, Desired under Skills. But they have both Requirements and Qualifications headings. Let's interpret: Requirements = mandatory (Required Qualifications). Qualifications = desired (Desired Qualifications). Skills could be maybe omitted if not distinct. But we could also put Skills as a separate section if we have specific skills like Apache NiFi, Linux, etc. However those appear in both Required and Desired. To avoid duplication, we can follow the headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide content for each. - About the role: company intro + job summary? Could combine. - Responsibilities: list of Primary Responsibilities. - Requirements: Required Qualifications (must have active TS/SCI clearance, 10 years experience, bachelor's degree or substitution). - Qualifications: Desired Qualifications (experience with mission data formats, Linux, DMRs, Apache NiFi, analytical requirements, system architecture diagrams, experience with ZooKeeper, Elasticsearch, Grafana, Apache NiFi Registry). - Skills: maybe we could list specific technical skills: Apache NiFi, Linux, Apache ZooKeeper, Elasticsearch, Grafana, Apache NiFi Registry, dataflow management, system architecture diagramming, etc. But that would duplicate Qualifications. Better to not create Skills if content is thin. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if we already have Qualifications covering desired qualifications. But we need to see if we have any content that fits Skills but not covered elsewhere. The posting mentions "experience with mission systems, dataflow technologies, Linux environments, and tools such as Apache NiFi" in job summary. That's more of a skill. But we could incorporate that into About the role or Responsibilities. Probably better to omit Skills section to avoid thin. - Benefits: list. - Pay: salary range. - Schedule: none, omit. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now format. About the role: combine company paragraph and job summary into prose (

  ). Ensure we don't repeat job title. Use

  . Responsibilities:

  Responsibilities

  then
  • each bullet. Requirements:

    Requirements

    then
    • each bullet. Qualifications:

      Qualifications

      then
      • each bullet. Benefits:

        Benefits

        then
        • each bullet. Pay:

          Pay

          then

          salary range. Make sure to preserve all substantive information. Let's extract bullets. Primary Responsibilities list: - Review and process Dataflow Management Requests (DMRs) and implement efficient, reliable dataflow solutions - Create, configure, manage, and maintain dataflows using Apache NiFi - Manage and support operational systems that process, route, and maintain mission data - Evaluate existing dataflows and identify opportunities for modernization, optimization, and improved reliability - Support migration of dataflows from hardware-based environments to virtualized and cloud-based platforms - Develop technical requirements for new or modernized dataflow capabilities - Rebuild and validate dataflows in coordination with operations teams and other technical stakeholders - Support analytical requirements and evolving mission needs - Develop and maintain system architecture diagrams depicting software components, interfaces, dataflows, and system functions - Support Linux-based software configuration, maintenance, troubleshooting, and upgrades - Monitor and troubleshoot operational systems and dataflow performance - Coordinate with systems engineers, operations personnel, analysts, and mission stakeholders to ensure system availability and data delivery - Support continuous improvement of dataflow processes, system reliability, and operational effectiveness - Participate in on-call support after approximately six (6) months of on-the-job training Required Qualifications: - Must have active Top Secret/SCI clearance with NSA Full Scope Polygraph - Ten (10) years of experience as a Systems Engineer supporting programs and contracts of similar scope, type, and complexity - Bachelor’s degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related discipline from an accredited college or university - Five (5) additional years of Systems Engineering experience may be substituted for the bachelor’s degree Desired Qualifications: - Experience working with mission data formats - Familiarity with Linux operating systems and command-line interfaces for software configuration, maintenance, and upgrades - Familiarity with Dataflow Management Requests (DMRs) - Experience using Apache NiFi to build, configure, or manage dataflows - Experience managing analytical requirements and mission needs - Experience developing system architecture diagrams that depict software components and system functions - Experience with one or more of the following technologies: - Apache ZooKeeper - Elasticsearch - Grafana - Apache NiFi Registry Note: The last bullet includes a sublist. We'll need to represent that as nested list or as separate bullets. For simplicity, we can flatten: "Experience with Apache ZooKeeper", "Experience with Elasticsearch", "Experience with Grafana", "Experience with Apache NiFi Registry". Or keep as a bullet with sublist. Use

          • Experience with one or more of the following technologies:
            • Apache ZooKeeper
            • Elasticsearch
            • Grafana
            • Apache NiFi Registry
          . That's okay. Benefits: - 11 paid holidays - minimum of 3 weeks PTO - company sponsored group medical plan - company paid dental - vision - life insurance - STD/LTD plans Pay: - Salary range: 130,000 - 180,000 USD per year. Now About the role paragraph: combine company intro and job summary. Company intro: "Momentum Engineering, Inc. fosters an employee-centric culture. Our strength lies in our people. With a high percentage of employees holding advanced degrees in engineering, computer science, and related disciplines, we bring deep technical expertise to every mission. Our team includes professionals with security clearances and full-scope polygraphs, ensuring trusted, secure support for the most sensitive national security initiatives. Additionally, our workforce is equipped with industry-leading certifications, demonstrating a commitment to continuous learning and excellence. Most importantly, our exceptional employee retention rate reflects a culture of professional growth, mission focus, and dedication—ensuring long-term stability and expertise for our customers’ critical needs." Job summary: "Seeking a Systems Engineer to support mission-critical operational systems and dataflow management within a dynamic technical environment. This position directly contributes to mission success by helping ensure the reliability, scalability, and performance of systems that process and deliver critical mission data to end users. The role supports modernization of dataflows and operational systems, including the transition of legacy capabilities into cloud-based environments while maintaining real-time mission support. The ideal candidate has experience with mission systems, dataflow technologies, Linux environments, and tools such as Apache NiFi." Combine into one or two paragraphs. We'll put as

          maybe two

          but it's okay. Now ensure we don't include boilerplate like "Exempt hourly position." That's part of benefits? Actually "Exempt hourly position." is a classification; we could include in About the role or maybe as a note. But it's not benefits. Could include in About the role as a sentence. But it's minor. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." So "Exempt hourly position." is minor metadata; we can fold into a short

          maybe after About the role or before Benefits. But we could also drop it. However it's substantive? It's about FLSA status. Might be considered minor. I'd include it as a short

          after About the role maybe. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep "Exempt hourly position." somewhere. Could add a

          after About the role: "

          Exempt hourly position.

          " That's fine. Now ensure we don't repeat any content inadvertently. Now produce HTML fragment. Let's craft:

          About the role

          Momentum Engineering, Inc. fosters an employee-centric culture. Our strength lies in our people. With a high percentage of employees holding advanced degrees in engineering, computer science, and related disciplines, we bring deep technical expertise to every mission. Our team includes professionals with security clearances and full-scope polygraphs, ensuring trusted, secure support for the most sensitive national security initiatives. Additionally, our workforce is equipped with industry-leading certifications, demonstrating a commitment to continuous learning and excellence. Most importantly, our exceptional employee retention rate reflects a culture of professional growth, mission focus, and dedication—ensuring long-term stability and expertise for our customers’ critical needs.

          Seeking a Systems Engineer to support mission-critical operational systems and dataflow management within a dynamic technical environment. This position directly contributes to mission success by helping ensure the reliability, scalability, and performance of systems that process and deliver critical mission data to end