Developmental Test Project Officer / UAS Pilot

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO etc. Must not include placeholder sections. We need to parse the posting. Key info: - Primary Portfolio Assignment: Professional Services Division - Location: St. Inigoes, MD - US Citizenship Required: Yes - Clearance Type: Ability to obtain and maintain Secret clearance - Work Schedule: Full Time, Exempt - Reports to: Director of Programs and Partnerships - Positions Supervised: None; provides functional leadership to integrated test teams - Travel: Occasional travel as required to support developmental test events Description: about company, mission, etc. Essential Functions: list of responsibilities. Required Qualifications: bullet list. Desired Qualifications: bullet list. Benefits: mention "highly competitive salaries, flexible work schedules, excellent benefits, instant 401K vesting and a full cafeteria plan that employees can tailor to their individual needs." Pay: not explicitly given; only "highly competitive salaries" but no specific numbers. According to rule: do NOT create Pay section unless posting actually states them. "highly competitive salaries" is vague but still states that salaries are competitive; is that considered stating? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "highly competitive salaries" is a statement about pay, albeit not specific. Might be considered stating pay exists. However they also say "Prefer a few substantive sections over many thin ones." Could combine Benefits and Pay? But we need separate sections if content exists. The posting mentions "highly competitive salaries, flexible work schedules, excellent benefits, instant 401K vesting and a full cafeteria plan". So we have info about salary (competitive), benefits (excellent benefits, 401K vesting, cafeteria plan), schedule (flexible work schedules). So we could have Benefits section covering benefits, Pay section covering salary statement, Schedule section covering flexible work schedules. However we must avoid placeholder like "commensurate with experience". "highly competitive salaries" is not placeholder; it's a statement. So we can include Pay with that statement. Similarly Schedule: "flexible work schedules". Benefits: "excellent benefits, instant 401K vesting and a full cafeteria plan". Also mention "highly competitive salaries" maybe also part of Benefits? But we can separate. We also have Work Schedule: Full Time, Exempt (from metadata). That's also schedule info. So schedule section can include both Full Time, Exempt and flexible work schedules. We need to avoid duplication. Now sections: - About the role: could be description paragraph about company and role purpose. Use

About the role

then

with description. - Responsibilities: list of essential functions. Use

• each. - Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate sections: Requirements and Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We have Required Qualifications (education, experience, etc.) and Desired Qualifications (additional). Could put Required Qualifications under Requirements heading, and Desired Qualifications under Qualifications heading. Or we could put all under Qualifications. But we have both headings available; better to use Requirements for mandatory, Qualifications for desired/preferred. Skills: maybe extract skills like technical writing, data analysis, briefing, presentation, ability to lead cross-functional teams, etc. Could be under Skills. But we must not invent sections if no specific content. We have skills content: "Strong technical writing, data-analysis, briefing, and presentation skills, including the ability to communicate test results and recommendations to technical and senior audiences". Also "Ability to integrate competing technical, operational, schedule, safety, and stakeholder requirements and drive actions to closure." Also "Ability to work flexibly around test schedules and mission requirements, including occasional travel and work outside standard business hours when required." Also "Ability and willingness to complete required training and qualification to operate Group 1-2 UAS and to perform flight-line or field duties in support of test events." Also "Demonstrated ability to lead cross-functional technical or operational teams in a hands-on test, flight, field, or mission environment." So we can put these under Skills. Now Benefits: we have "highly competitive salaries, flexible work schedules, excellent benefits, instant 401K vesting and a full cafeteria plan that employees can tailor to their individual needs." Also maybe mention "highly competitive salaries" could be Pay. But we can put salary under Pay, benefits under Benefits, schedule under Schedule. Pay: "highly competitive salaries". Could also mention nothing else. So Pay section with that statement. Schedule: we have "Work Schedule: Full Time, Exempt" and "flexible work schedules" and "occasional travel as required to support developmental test events" and "Ability to work flexibly around test schedules and mission requirements, including occasional travel and work outside standard business hours when required." So schedule section can include Full Time, Exempt; flexible work schedules; occasional travel; work outside standard business hours as needed. Now About the role: we can summarize the description: company mission, divisions, role purpose. Must preserve all substantive information; we cannot invent or summarize away detail. But we can condense while preserving meaning? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we should keep them. However we can rephrase but must keep all info. That's tricky: we need to include all details from the description. The description includes: ABSI Aerospace & Defense is a mission-driven, veteran-led company headquartered in the St. Mary’s County Innovation District in Southern Maryland. Through three integrated divisions—Professional Services, Flight Services, and Aerial Targets—ABSI delivers test and evaluation, training and logistics support, uncrewed systems operations, low-cost aerial targets, and counter-UAS training and field support to the Department of Defense and allied partners. Our success depends on employing and retaining world-class subject matter experts and personnel equally committed to our mission. To support our workforce, ABSI offers highly competitive salaries, flexible work schedules, excellent benefits, instant 401K vesting and a full cafeteria plan that employees can tailor to their individual needs. ABSI is seeking a hands-on Developmental Test Project Officer / UAS Pilot to support UX-24 developmental test activities. This position leads the planning, coordination, execution, and reporting of complex test events and serves as the primary interface among the test team, government program offices, aircrew, engineers, and fleet representatives. The Project Officer provides deckplate leadership in the test environment, coordinates multi-domain cUAS and UART test activities, and keeps stakeholders, resources, risks, and technical objectives aligned. As required, the employee will qualify to operate Group 1-2 UAS as test targets; flight duties support, but do not define, the position's primary project leadership role. We need to keep all that info. So About the role section can be a paragraph containing all that. Might be long but okay. Now Responsibilities: list of essential functions (the bullet list). We'll output each as
• . Now Requirements: Required Qualifications bullet list. Now Qualifications: Desired Qualifications bullet list. Now Skills: we can extract skills from Required and Desired qualifications that are skill-based. But we might duplicate. Better to put skill-based statements under Skills heading, and keep qualifications under Requirements/Qualifications for education/experience. However we risk duplicating content. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to avoid duplication by placing each piece only once. So we need to decide where each piece belongs. Let's parse Required Qualifications: - Bachelor’s degree from an accredited institution with at least 8 years of relevant experience performing the essential functions listed above. - Technical background demonstrated through relevant education, military training, professional credentials, or progressively responsible experience in aviation, engineering, flight test, UAS, or a closely related field. - Aviation experience as a pilot, Naval Flight Officer, Air Vehicle Pilot, flight test engineer, aerospace engineer, or in a comparable technical aviation role. - Demonstrated ability to lead cross-functional technical or operational teams in a hands-on test, flight, field, or mission environment. - Experience planning, coordinating, executing, and documenting complex test events, flight operations, demonstrations, or comparable technical activities. - Ability to integrate competing technical, operational, schedule, safety, and stakeholder requirements and drive actions to closure. - Strong technical writing, data-analysis, briefing, and presentation skills, including the ability to communicate test results and recommendations to technical and senior audiences - Ability and willingness to complete required training and qualification to operate Group 1-2 UAS and to perform flight-line or field duties in support of test events. - Ability to work flexibly around test schedules and mission requirements, including occasional travel and work outside standard business hours when required. - S. citizenship and the ability to obtain and maintain the security clearance, base access, and credentials required for assigned work. Desired Qualifications: - Graduate of a recognized military or civilian Test Pilot School. - Familiarity with the NAVAIR M-3905.1 Flight Test Manual series of instructions. - Prior Navy aviation leadership experience at the O-3/O-4 level, or comparable military or civilian test-team leadership experience. - Experience serving as a Project Officer, Test Director, Test Pilot, Test Naval Flight Officer, or lead flight test engineer for developmental test programs. - Experience coordinating multi-domain cUAS testing, UART activities, UAS target operations, or related integrated test events. - Current or prior qualification operating Group 1-2 UAS. - Knowledge of NAVAIR developmental test processes and experience working with government program offices, test squadrons, operational aircrew, engineers, and fleet stakeholders. - Proficiency with Microsoft Office and web-based collaborative resources such as SharePoint and Microsoft Teams. Now Skills: we could pull out skill statements like "Strong technical writing, data-analysis, briefing, and presentation skills", "Ability to integrate competing technical, operational, schedule, safety, and stakeholder requirements and drive actions to closure", "Demonstrated ability to lead cross-functional technical or operational teams", "Ability and willingness to complete required training and qualification to operate Group 1-2 UAS", "Ability to work flexibly around test schedules and mission requirements", "Proficiency with Microsoft Office and web-based collaborative resources". But many of these are already in Required/Desired qualifications. If we put them under Skills, we would be duplicating. Perhaps better to not have a separate Skills section; instead put skill statements under Requirements or Qualifications. But the instruction says we can use Skills heading if there is real specific content. We have skill content; we could put them under Skills and keep Requirements/Qualifications for education/experience only. However that would mean moving some items from Required/Desired to Skills, which is okay as long as we preserve all info (just re-categorized). The instruction does not forbid re-categorizing; just says preserve all substantive information. So we can reorganize. Thus: - Requirements: education and experience requirements (Bachelor's degree + 8 years experience, technical background, aviation experience). Possibly also citizenship and clearance? Those are more like mandatory requirements but could be under Requirements as well. However citizenship and clearance are also mandatory; we could put them under Requirements. - Qualifications: desired qualifications (preferred). Could also include some skill-based desired like proficiency with MS Office. - Skills: skill-based abilities (leadership, technical writing, data analysis, integrating requirements, ability to complete UAS training, flexible work, proficiency with MS Office). But note proficiency with MS Office is also in desired qualifications; we could keep it there. We need to avoid duplication. Let's decide: Requirements (mandatory): - Bachelor’s degree from an accredited institution with at least 8 years of relevant experience performing