GEOINT Systems Integrator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, there is an "About Peraton" intro, but we should not repeat job title as heading. The page already shows it. We need to include sections only when there is real content. We have "About The Role" content: paragraphs describing role. That's content for About the role. We have "Key Responsibilities" with bullet points (actually paragraphs with bullet-like lines). We need to extract list items. We have "Qualifications" section with Required and Desired bullet points. We have "Details" includes Target Salary Range and Benefits Statement. We have location line: "Location: This position is fully onsite in either Chantilly or Springfield, VA". That could go into a short

maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is metadata; we can include as a short

maybe after About the role. We need Benefits: The posting includes "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits." Thus we have Benefits content. Pay: "Target Salary Range: $146,000 - $234,000." plus description. So we have Pay content. Schedule: Not mentioned. So we should not include Schedule section. Skills: Not explicit separate section; but qualifications include skills. Could combine under Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include Skills if there is specific content. The posting includes "Strong verbal and written communication skills..." etc under Desired. That's skills. Could create Skills section. But we already have Qualifications covering required and desired. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine qualifications and skills into Qualifications. But we have both Required and Desired; we can keep Qualifications section with sublists. We need to output only HTML fragment, no /. 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. So we need to keep all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO line etc. Remove that. Also remove "Application Statements:" etc. Also remove "Details" heading? We'll incorporate salary and benefits. We need to keep location line as short

  . Let's extract content: About The Role paragraph(s): "We are seeking an Expert-Level GEOINT System Integrator with hands-on experience across the Systems Engineering and Integration Lifecycle, including architecture, requirements, CONOPS, integration, testing, and transition, to support enterprise transformation initiatives across GEOINT mission systems and projects. The ideal candidate brings deep expertise in NGA and Mission Partner GEOINT Tasking, Collection, Processing, Exploitation, and Dissemination (TCPED) Architecture, with significant experience focused on GEOINT metadata standards. This role requires a critical-thinking mindset and the ability to lead strategic enterprise architecture, technical planning, engineering analysis, and cross-organizational coordination and integration activities to modernize GEOINT architecture and advance mission capabilities. The Expert-Level GEOINT System Integrator will lead large-scale, multi-phase integration efforts spanning multiple agencies and the broader GEOINT community to drive enterprise readiness and transition. As a member of the Enterprise Engineering & Architecture Division's Integration Team, you will serve as a key SME leading agency and joint transition planning and readiness for the adoption of next-generation GEOINT data standards. You will serve as a trusted advisor to the customer, identifying and mitigating integration and transition risks while guiding complex, high-visibility initiatives from project planning through Transition to Operations (TTO)." That's prose. Key Responsibilities: list items: - Enterprise Integration & Transition - Lead enterprise transition planning and readiness for the adoption of modernized GEOINT data standards across the NSG. - Develop Plans of Action and Milestones (POA&Ms) for enterprise architecture, engineering, integration, testing, and transition activities. - Conduct Analysis of Alternatives (AoAs) and develop dual-operations transition architectures. - Develop and manage multi-phase enterprise transition roadmaps. - Provide SME expertise in the development of enterprise and program requirements. - Lead strategy development for joint baseline management updates, enterprise test planning, and joint transition planning. - Lead end-to-end coordination for readiness milestones. - Develop community outreach plans and messaging. - Lead end-to-end integration and transition efforts between NGA and Mission Partners. - Systems Engineering & Technical Analysis - Lead and participate in analyses including: - Architecture Gap Analysis - Enterprise Requirements Analysis - Analysis of Alternatives (AoAs) - Courses of Action (CoAs) - Trade Studies - Risk Analysis - Critical Path Analysis - Enterprise Technical Impact Analysis - Develop recommendations for transition architectures and investment decisions. - Leverage knowledge of the Joint Enterprise Ground and Space Architecture and GEOINT data standards to inform technical planning and integration. - Define modernized system integration processes that enhance adoption of Agile, Digital Engineering, Model-Based Systems Engineering (MBSE), and AI while introducing process efficiencies. - Facilitate development of integrated project plans, requirements, epics, target-state architectures, CONOPS, and roadmaps within NGA's Digital Engineering Environment. - Program & Stakeholder Leadership - Establish and lead Integrated Project Teams (IPTs) and working groups across multiple organizations, agencies, and stakeholders. - Lead preparations for NGA and Joint Agency engineering boards and working groups. - Participate in NGA and Joint Governance, Configuration Management, and Risk Management processes. - Identify risks, issues, and opportunities and develop associated mitigation or exploitation plans. - Provide thought leadership by identifying opportunities to expand team scope and developing project plans that define tasking, deliverables, and execution timelines. - Lead and participate in cross-organizational IPTs focused on Analytic, Collection Management, Data Services, Foundation GEOINT, and Information Technology modernization. - Provide technical leadership and ensure integrated solutions and capability deliveries. - Engineering Innovation & Team Leadership - Help drive adoption of Digital Engineering, MBSE, Automation, and AI to modernize engineering processes and products. - Mentor Senior-, Mid-, and Junior-Level GEOINT Systems Engineers and Integrators. - Provide task management oversight for engineering teammates. - Work collaboratively with Senior, Mid-, and Junior-Level Engineers and Integrators to execute complex enterprise initiatives. We need to decide how to structure lists. Could have a top-level

  with each responsibility as
  • containing sublists? The instruction: Use
    • for any list of duties/requirements/benefits. So we can flatten all bullet points into a single list, but that loses grouping. However we can nest lists; still each list uses
      • . That's fine. We'll produce

        Responsibilities

        then
        with each main bullet as
        • and sub-items as nested
          . Qualifications: Required and Desired. Required: - Master's degree in Engineering, Computer Science, Information Technology, Management Information Systems, or a related STEM discipline, or equivalent expert-level experience as a Systems Integrator. - 18+ years' of relevant experience may be considered in lieu of a degree. - Experience integrating solutions using cloud-based technologies, including: - Service-Oriented Architecture (SOA) - On-demand self-service - Broad network access - Resource pooling - Rapid elasticity - Measured service - Software as a Service (SaaS) - Platform as a Service (PaaS) - Infrastructure as a Service (IaaS) - Demonstrated hands-on experience architecting and building large-scale, service-oriented software products. - Active TS/SCI clearance or the ability to obtain SCI eligibility and successfully pass a polygraph. Desired: - Significant experience and working knowledge of GEOINT TCPED Architecture, including data providers, systems/services, interfaces, and data flows. - Significant experience leading complex, multi-organization, multi-agency, and multi-stakeholder initiatives, including: - Establishing and leading IPTs - Developing transformation roadmaps - Developing dual-operations architectures - End-to-end transition and readiness planning - Demonstrated knowledge of the current NSG/ASG and NRO enterprises. - Demonstrated knowledge of current and legacy GEOINT metadata standards, including Commercial, NITF, Still, Motion, and related standards, as well as an understanding of their limitations. - Demonstrated knowledge of transformational initiatives, including Automation, Artificial Intelligence, and/or Multi-Cloud Architectures. - Experience authoring Requests for Change (RFCs) and leading enterprise impact coordination. - Experience with Agile project management tools such as Jira and Confluence. - Strong verbal and written communication skills. - Strong customer relationship and engagement skills. - Strong technical mentorship skills for engineering teammates. - Experience with or working knowledge of Model-Based Systems Engineering (MBSE) processes, tools, and languages. We can put these as lists. Benefits: list of benefits: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. Also note link. We'll output as
          • each. Pay: Salary range: $146,000 - $234,000. plus description: "This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay." We'll put that as prose

            . Location: short

            : "Location: This position is fully onsite in either Chantilly or Springfield, VA." We need to ensure we don't repeat job title as heading. Not needed. We must not include sections with filler like "commensurate with experience". Not present. We must not include Pay/Schedule/Benefits unless posting actually states them. We have Pay and Benefits. No Schedule. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills? But we have Qualifications covering skills; we could add Skills but would be thin. Better to omit Skills. We need to output only HTML fragment. Let's craft. We'll start with

            About the role

            then

            ... (the paragraph). Might need to split into multiple paragraphs if there are natural breaks. The original has multiple sentences; we can keep as one

            or split. We'll keep as one

            . Then location

            . Then

            Responsibilities

            then
            with nested lists. Then

            Qualifications

            then
            with required and desired maybe separated with headings inside? Could use
            • with Required etc. But we need to