Technical Project Manager - Senior

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. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove EEO line. Also remove "Application Statements" etc. Also remove "Details" maybe? But we need to capture Pay and Benefits sections if present. Pay: "Target Salary Range: $104,000 - $166,000." That's specific, so include Pay section. Benefits: they list benefits statement, include Benefits section. Schedule: they have "Work Location Preferred location: Herndon, VA Work arrangement: Primarily on-site; remote work options may be considered based on candidate qualifications and program requirements." That's schedule info (work arrangement). So include Schedule section. Now we need sections: About the role (intro paragraph). Responsibilities: list of duties from "In This Role, You Will" bullet points. Requirements: maybe the "Position Requirements:" list. Qualifications: maybe "Preferred Qualifications". Skills: maybe combine? But we have separate sections for Skills; we could put skills under Requirements or Qualifications. However we need to follow instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real specific content for it. So we need to decide what content goes where. We have: - About the role: The paragraphs after "About The Role" up to maybe before "Project Manager - Surveillance & Radar Systems". Actually the posting includes "About The Role Join Peraton..." then "Project Manager - Surveillance & Radar Systems Shape the Future...". We can treat that as About the role content. - Responsibilities: The bullet list under "In This Role, You Will". Those are duties. - Requirements: The "Position Requirements:" list (citizenship, clearance, education/experience, proven project leadership experience, FAA TechOps experience, etc). Those are mandatory requirements. - Qualifications: The "Preferred Qualifications" list. - Skills: Could be derived from requirements like "Strong communication and stakeholder management skills", "Demonstrated ability to drive alignment, manage competing priorities, and deliver results". But those are already in Requirements. Might be redundant. Could create Skills section for soft skills etc. But we need to avoid thin sections. Perhaps we can combine skills into Requirements or Qualifications. However instruction says we can have Skills section if there is real specific content. There is mention of skills: "Strong communication and stakeholder management skills", "Demonstrated ability to drive alignment, manage competing priorities, and deliver results". Also "Hands-on technical experience with airport surface surveillance/radar systems". Those are more like requirements/qualifications. Might be okay to put them under Requirements. But we need to decide. Given we already have Requirements and Qualifications sections, we could omit Skills to avoid thin section. But we need to check if any content not covered elsewhere: The "Hands-on technical experience with airport surface surveillance/radar systems, including architecture, hardware, software, system interfaces, maintenance, troubleshooting, and performance analysis." That's a requirement. So it's covered. Thus we can omit Skills section. Now Benefits: we have benefits statement. Pay: salary range. Schedule: work location and arrangement. Now we need to output HTML fragment with headings

and content in

or

• . For About the role: likely a paragraph(s). Could be multiple paragraphs but we can combine into one

  with line breaks? Better to keep as

  for prose. If multiple paragraphs, we could have multiple

  under same heading? The instruction: Use

  for section headings,

  • for any list,

    for prose. It doesn't forbid multiple

    under a heading. We'll output multiple

    if needed. Responsibilities: list of duties from bullet points. We'll make

    • each. Requirements: list of position requirements. We'll make
      • . Qualifications: list of preferred qualifications.
        • . Benefits: list of benefits. Could be
          • each benefit. Pay: maybe

            with salary range. Schedule: maybe

            with work location and arrangement. Now we need to remove boilerplate: EEO line, application statements, etc. Also remove duplicated lines like "About Peraton" maybe? The "About Peraton" paragraph at start is boilerplate? It's about company description. Might be considered boilerplate but it's substantive? It's generic company overview. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Peraton" is not explicitly listed as boilerplate but could be considered generic marketing. However it's part of the job posting; but we might keep it as part of About the role? The instruction says "Preserve ALL substantive information". The company overview may be considered substantive? It's not specific to the role. Might be considered boilerplate but not explicitly listed. Safer to keep it? The instruction about sections: About the role heading should contain role-specific content, not generic company description. The "About Peraton" is not about the role. Could be omitted as it's not role-specific. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

            or drop it." It doesn't say to drop company overview. But we need to decide. Given the goal is to reformat a job posting into clean semantic HTML, likely they'd want the About the role section to contain the role description, not the generic company blurb. The "About Peraton" could be considered boilerplate but not explicitly listed. I'd keep it maybe as a short paragraph under About the role? But that would mix company description with role description. Might be okay. But we can also treat the initial "About Peraton" as a separate section? Not in allowed headings. So we could incorporate it into About the role as a brief intro. However the instruction says "include a section ONLY when the posting has real, specific content for it". The About the role section definitely has specific content (the role description). Adding extra generic company description may dilute but not violate. I'll include the role-specific paragraphs after "About The Role". I'll omit the initial "About Peraton" paragraph to keep focused. Now let's extract content. About the role: The text after "About The Role Join Peraton in advancing the safety, efficiency, and modernization of the National Airspace System (NAS) through the FAA's Brand New Air Traffic Control System (BNATCS) contract. As a trusted partner to the Federal Aviation Administration, Peraton helps deliver the systems and services that keep our nation's skies safe and connected. We're looking for innovative professionals who thrive in mission-critical environments and are passionate about shaping the future of air traffic management. This is your chance to make an impact on one of the world's most vital transportation infrastructures, working alongside leaders in aviation, engineering, data science, and systems integration. At Peraton, you won't just support the mission - you'll define it." Then there is a heading "Project Manager - Surveillance & Radar Systems Shape the Future of Air Traffic Management with Peraton Join a team dedicated to protecting the safety, efficiency, and integrity of U.S. air travel. At Peraton, we partner with the Federal Aviation Administration (FAA) to support and modernize the systems that keep the National Airspace System (NAS) operating safely and efficiently. Peraton is seeking dynamic, technically focused Project Managers to join our team of talented and diverse professionals. In this role, you will provide leadership across critical Surveillance and Radar Systems initiatives, guiding planning, prioritization, stakeholder engagement, and execution to ensure program objectives are achieved. Whether you are leading multidisciplinary engineering teams, coordinating safety and validation activities, or supporting major FAA modernization initiatives, your work will have a direct impact on the systems relied upon by millions of passengers, aviation professionals, and communities every day. This is an opportunity to bring your project leadership expertise to a mission where the work you do truly matters." We could combine both paragraphs as About the role. Now Responsibilities: bullet list under "In This Role, You Will". Let's extract each bullet: - Lead the planning and execution of multidisciplinary workstreams supporting Surveillance and Radar Systems and related engineering activities. - Establish priorities, coordinate resources, and ensure work remains aligned with program objectives, schedules, and stakeholder expectations. - Lead and motivate high-performing teams, fostering collaboration, accountability, and a culture focused on mission success. - Engage with stakeholders to understand requirements, manage expectations, communicate priorities, and provide clear and timely program updates. - Monitor program performance, schedules, and delivery metrics to identify risks, remove roadblocks, and drive continuous improvement. - Collaborate with product owners, system vendors, developers, FAA facilities, engineering teams, and leadership to maintain alignment and deliver mission value. - Develop and maintain roadmaps, status reports, action items, and program documentation to provide visibility and support informed decision-making. - Identify emerging challenges and opportunities, develop mitigation strategies, and help teams navigate complex technical and organizational issues. - Support change management and communications to facilitate the successful adoption of new technologies, processes, and tools. - Promote effective cross-functional collaboration while ensuring deliverables meet program, technical, quality, and mission requirements. Now Requirements: "Position Requirements:" list: - U.S. Citizenship required. - Ability to obtain and maintain a Public Trust clearance. - Bachelor's degree with 8 years of experience, Master's with 6 years, Associate's with 10 years, or HS diploma/equivalent with 12 years of relevant experience. - Proven project leadership experience supporting Surveillance and/or Radar Systems, including surface surveillance, sensor data feeds, multi-sensor fusion, primary/secondary radar, SSR, ASR, or similar systems. - FAA Technical Operations (TechOps) experience required, with demonstrated experience maintaining and supporting mission-critical NAS systems. - Direct experience with FAA Technical Services Operations Group (TSOG) or as an Airway Transportation Systems Specialist (ATSS) supporting NAS infrastructure. - Hands-on technical experience with airport surface surveillance/radar systems, including architecture, hardware, software, system interfaces, maintenance, troubleshooting, and performance analysis. - Experience coordinating site and facility activities, including installation, modification, system acceptance, and field deployment. - Strong communication and stakeholder management skills, including experience working with senior leadership and cross-functional teams. - Demonstrated ability to drive alignment, manage competing priorities, and deliver results in dynamic, mission-critical environments. Now Qualifications (Preferred Qualifications): - FAA TechOps, TSOG, or ATSS experience, with SMR/ASDE experience highly desirable. - Experience supporting FAA NextGen, NAS modernization, or federal aviation programs. - Experience managing federal modernization programs or large-scale enterprise initiatives. - Familiarity with FAA standards, facility directives, and compliance requirements. - Knowledge of risk management, budgeting, and program governance. Now Benefits: "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." We'll list each benefit as

          • . Now Pay: "Target Salary Range: $104,000 - $166,000. 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