Lead Program Manager - Space Electronics

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. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key content: - Summary: "AV has an immediate opening for a mid-career Lead Program Manager to support satellite electronics programs within its Space Technologies Division." - About AV: description of company, mission, etc. Could be "About the role" or "About AV"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Position Responsibilities: list of duties. - Basic Qualifications (Required Skills & Competencies): list. - Other Qualifications & Desired Competencies: list. - Physical Demands: ability to work in office environment, sit/stand, talk, hear, use hands. - Clearance Level: No Clearance - The Salary Range For This Role Is $101,000 - $154,000 - ITAR Requirement: description. - Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown. - About AV: description of company. - Also "Worker Type Regular Summary Job Description" maybe not needed. - "Principals only need apply. NO agencies please." That's application instruction, should be removed. - EEO statements removed. - "ITAR U.S. Citizenship required" at end. We need to include sections only if real specific content. Let's decide sections: - About the role: could include summary and maybe About AV? Actually "About the role" could be summary of role. We'll put the immediate opening sentence. - Responsibilities: the list under Position Responsibilities. - Requirements: could combine Basic Qualifications (Required Skills & Competencies) and Other Qualifications & Desired Competencies? But we have separate headings Requirements and Qualifications. Usually Requirements = basic qualifications, Qualifications = other/desired. We'll follow that. - Skills: maybe we can extract communication skills etc. But we already have them in qualifications. Could create Skills section from communication skills etc. But we might avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But we have headings list; we can include both if they have content. We'll include Requirements (basic qualifications) and Qualifications (other/desired). Skills maybe not needed separately if covered. - Benefits: we have benefits content. - Pay: we have salary range. - Schedule: we have 9/80 work schedule mentioned in benefits; also maybe schedule info elsewhere? The benefits mention a 9/80 work schedule. That's schedule info. Could also include schedule as separate section: mention 9/80 work schedule and paid holiday shutdown? Actually paid holiday shutdown is benefit. So schedule: 9/80 work schedule. - Also Physical Demands: maybe could be under Requirements? But we could add a section? Not in list. Could incorporate into Requirements or Qualifications? Probably better to include under Requirements as a bullet? But not typical. Could create a separate section? Not in allowed headings. So we might incorporate physical demands into Requirements or Qualifications as a bullet. - Clearance Level: No Clearance - maybe include under Requirements? Could be a note. - ITAR Requirement: maybe include under Requirements or Qualifications as a note. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details: responsibilities list, basic qualifications list, other qualifications list, physical demands, clearance level, salary range, ITAR requirement, benefits, about AV, worker type? Not needed. We must not include boilerplate like EEO, application instructions, etc. We need to output only HTML fragment, no markdown fences. Let's structure:

About the role

AV has an immediate opening for a mid-career Lead Program Manager to support satellite electronics programs within its Space Technologies Division.

AV provides a full suite of exquisite, space-qualified hardware trusted to fly in the most extreme environments space presents across GEO, MEO, LEO and Cislunar orbits. With hundreds of systems flying in space, our customers turn to AV when a mission can't fail.

That seems like About AV content but could be under About the role. However we also have separate About AV paragraph later. Might duplicate. Better to put company description under About the role? The instruction says About the role heading; we can include role summary and maybe company context. It's okay. Then Responsibilities:

Responsibilities

• Working with customers to understand forecasts and demand for the product
• Leading proposal development, ensuring stable product pricing
• Assisting contract management in negotiations related to cost, schedule, and risk posture
• Partnering with material managers and supply chain to ensure inventory of electronic components is available and suppliers are meeting commitments
• Leading the development of an integrated master schedule
• Leading a risk management process for the product
• Managing all assigned resources including people, facilities, budgets, and schedules to meet performance requirements and commitments
• Reporting on product/program status internally and externally
• Ensuring project team members' responsibilities, accountability and authority are clearly documented and understood
• Ensuring assigned individuals are executing the assigned tasks and providing appropriate tracking and reporting per plan
• Facilitating the resolution of program issues
• Partnering cross functionally on configuration management and associated deliveries of the product
• Performing project management activities in accordance with accepted project management standards in the industry (e.g., PMI, Project Management Body of Knowledge [PMBOK], ANSI, and ISO-standards)

Requirements (basic qualifications):

Requirements

• Bachelor's degree in Project Management, Business Administration, Systems Engineering, or a related technical field and 8+ years of relevant experience within aerospace or a technical field as a project or program manager
• Thorough knowledge and proficiency in all project management areas in accordance with Industry project management standards
• Ability to lead and direct the activities and resources within and across the organization
• Excellent written and verbal communication skills with ability to listen, assimilate, evaluate, and summarize. Sound ability to communicate with the customer at all levels
• Knowledge of the Project Lifecycle from requirements definition, proposal preparation and negotiation and project implementation through to completion
• Strong initiative in defining, proposing, implementing, and communicating schedule metrics that support informed decision-making
• Ability to obtain and maintain a DoD security clearance
• Physical demands: Ability to work in an office environment; required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent)
• Clearance Level: No Clearance
• ITAR Requirement: This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants must qualify as a U.S. person under the ITAR and the EAR, or a person to be approved for an export license by the governing agency whose technology comes under its jurisdiction. Any job offer that requires approval of an export license will be conditional on AeroVironment’s determination that it will be able to obtain an export license in a time frame consistent with AeroVironment’s business requirements. A “U.S. person” according to the ITAR definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee or asylee. Some positions will require current U.S. Citizenship due to contract requirements.

Qualifications (other/desired):

Qualifications

• Master's degree in Project Management, Business Administration, Systems Engineering, or a related technical field and 10+ years of relevant experience within aerospace or a technical field as a project or program manager
• Project Management Professional (PMP) certification

Skills: maybe we could combine communication skills etc but already in Requirements. Could skip Skills section. Benefits:

Benefits

• Medical, dental, vision
• 401K with company matching
• 9/80 work schedule
• Paid holiday shutdown

Pay:

Pay

The salary range for this role is $101,000 - $154,000.

Schedule: we already included 9/80 work schedule in benefits; but we could also have a Schedule section referencing that. However to avoid duplication, we could keep schedule in benefits and not create separate Schedule section. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does mention 9/80 work schedule under benefits. So we could keep schedule as part of benefits. No need separate Schedule. But we might still include Schedule section referencing the 9/80 work schedule and maybe mention that it's a 9/80 schedule. However that would duplicate content. Better to keep only Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other content like "Worker Type Regular Summary Job Description" - ignore. Check for duplicated lines: we have not included navigation etc. Check for boilerplate: removed EEO, application instructions, etc. Check for placeholders: we have no "commensurate with experience" etc. Now ensure we preserve all substantive information: - Summary: included in About the role paragraph. - Company description: included in About the role paragraph (the second paragraph about AV providing hardware etc). Good. - Responsibilities: all bullets captured. - Basic Qualifications: all captured. - Other Qualifications: captured. - Physical Demands: captured as bullet in Requirements. - Clearance Level: captured. - ITAR Requirement: captured as bullet in Requirements (long text). Good. - Salary Range: captured in Pay. - Benefits: medical, dental, vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown. Captured. - About AV description: we used the paragraph about AV providing hardware etc. Also there is a longer "About AV" section later describing company heritage, mission, etc. Did we include that? We included only the first paragraph about AV providing hardware. The later "About AV" section includes more detail: "AV isn’t for everyone...". That is substantive information about company culture, mission, etc. We should preserve that as well. Could be part of About the role or maybe a separate section? But we only have headings list; we could include it under About the role as additional paragraphs. Thus we need to incorporate the later About AV text. Let's capture that: "AV isn’t for everyone. We hire the curious, the relentless, the mission-obsessed. The best of the best. We don’t just build defense technology—we redefine what’s possible. As the premier autonomous systems company in the U.S., AV delivers breakthrough capabilities across air, land, sea, space, and cyber. From AI-powered drones and loitering munitions to integrated autonomy and space resilience, our technologies shape the future of warfare and protect those who serve. Founded by legendary innovator Dr. Paul MacCready, AV has spent over 5