Developmental Test Project Officer / UAS Pilot
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include: About the role (description), Responsibilities (Essential Functions), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Desired Qualifications?), Skills (maybe from required/desired like technical writing etc), Benefits, Pay, Schedule.
But we must avoid thin sections. Let's see content:
About the role: description paragraph(s) about ABSI and mission. That's substantive.
Responsibilities: Essential Functions list (multiple items). Good.
Requirements: Could be "US Citizenship Required", "Clearance Type", maybe also "Work Schedule"? But those are more metadata. Could combine into a "Requirements" section with those items as list? But the rule: Use
- for any list of duties/requirements/benefits. So we can list citizenship, clearance, etc as list items.
Qualifications: Could be Required Qualifications and Desired Qualifications combined? Might be better to have a "Qualifications" section with both required and desired as sublists? But we need to follow rule: only include section when posting has real specific content. We have both required and desired qualifications. Could make two subsections? But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put qualifications under
Qualifications
and list both required and desired as items, maybe differentiate with bold? But we must preserve all substantive info; we can include both sets as list items.
Skills: Could extract from required/desired: "Strong technical writing, data-analysis, briefing, and presentation skills", "Ability to integrate competing technical, operational, schedule, safety, and stakeholder requirements", "Ability to work flexibly around test schedules", "Proficiency with Microsoft Office and web-based collaborative resources such as SharePoint and Microsoft Teams". Also "Ability to lead cross-functional technical or operational teams". Those are skills.
Benefits: "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 "excellent benefits" is vague but we have specifics: instant 401K vesting, full cafeteria plan. So we can list those.
Pay: "highly competitive salaries". Could be a sentence.
Schedule: "Work Schedule: Full Time, Exempt" and "flexible work schedules". Also "occasional travel as required". So schedule section can include full-time exempt, occasional travel, flexible work schedules.
We must not repeat job title. Not include headings for Job ID etc.
We must not include boilerplate like EEO etc. Remove that paragraph.
We must not include duplicated lines. Ensure we don't repeat same info.
Now craft HTML.
Structure:
About the role
... description ...
Responsibilities
- Lead the planning, coordination, execution, and reporting of developmental test events in support of program and test objectives.
- Serve as the primary interface among the test team, government program offices, aircrew, engineers, fleet representatives, and other participating organizations to maintain stakeholder alignment and enable successful execution.
- Lead and coordinate multi-domain cUAS and UART test activities, integrating technical, operational, schedule, resource, and mission requirements across participating teams.
- Develop and maintain test plans, test cards, mission requirements, schedules, readiness products, and other supporting documentation for developmental test activities.
- Provide hands-on leadership during test preparation and execution by coordinating personnel and resources, assigning and tracking action items, identifying dependencies, and managing risks to safe and efficient completion.
- Lead test team communications, coordination meetings, readiness reviews, mission briefs, debriefs, and follow-up activities.
- Monitor test execution, assess progress against objectives, elevate issues, and coordinate timely adjustments with technical and operational stakeholders.
- Analyze test data and aircraft or system performance; prepare technical reports, presentations, recommendations, and briefings that clearly document test results and conclusions.
- Apply applicable NAVAIR flight-test instructions, approved procedures, and operational risk-management practices throughout planning and execution.
- Obtain and maintain required Group 1-2 UAS qualifications and, as required, serve as an sUAS pilot or target operator in support of developmental test missions and associated flight operations.
- Perform other duties consistent with the position and program requirements, as assigned.
Requirements
- U.S. citizenship required.
- Ability to obtain and maintain a Secret security clearance.
- Full-time, exempt position.
- Occasional travel as required to support developmental test events.
- Reports to Director of Programs and Partnerships.
- Provides functional leadership to integrated test teams (no direct reports).
Qualifications
- Bachelor’s degree from an accredited institution with at least 8 years of relevant experience performing the essential functions.
- 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.
- Desired: Graduate of a recognized military or civilian Test Pilot School.
- Desired: Familiarity with the NAVAIR M-3905.1 Flight Test Manual series of instructions.
- Desired: Prior Navy aviation leadership experience at the O-3/O-4 level, or comparable military or civilian test-team leadership experience.
- Desired: Experience serving as a Project Officer, Test Director, Test Pilot, Test Naval Flight Officer, or lead flight test engineer for developmental test programs.
- Desired: Experience coordinating multi-domain cUAS testing, UART activities, UAS target operations, or related integrated test events.
- Desired: Current or prior qualification operating Group 1-2 UAS.
- Desired: Knowledge of NAVAIR developmental test processes and experience working with government program offices, test squadrons, operational aircrew, engineers, and fleet stakeholders.
- Desired: Proficiency with Microsoft Office and web-based collaborative resources such as SharePoint and Microsoft Teams.
But we might be duplicating some items already in Required Qualifications; we included them all. Might be okay.
Now Skills section: Could extract skills like leadership, technical writing, data analysis, briefing, presentation, integration, proficiency with MS Office, etc. However many of those already appear in Qualifications. To avoid duplication, maybe we can omit Skills section if content overlaps heavily. But rule: Prefer a few substantive sections over many thin ones. If we already have Qualifications covering skills, we could skip Skills. However the instruction says to use sections only when posting has real specific content for it. We have specific skills listed; we could still include Skills but risk duplication. Better to include Skills with items not already captured? But we already captured technical writing etc in Qualifications. Could still include but might be considered thin. I'd omit Skills section.
Benefits section: list items.
Benefits
- Highly competitive salaries.
- Flexible work schedules.
- Excellent benefits package including instant 401K vesting.
- Full cafeteria plan that employees can tailor to individual needs.
Pay section: maybe we already covered salary in Benefits; but Pay could be separate: "Highly competitive salaries." However we already have that in Benefits. To avoid duplication, we could combine Pay into Benefits or omit Pay. The rule: only include Pay if posting actually states them. It does state "highly competitive salaries". We could include Pay section with that sentence. But then Benefits also mentions salary; duplication. Better to have Pay section with "Highly competitive salaries." and Benefits section with other benefits (flexible schedules, 401K vesting, cafeteria plan). However flexible work schedules also appears in Schedule. Might duplicate.
Let's think: The posting says: "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." So we could parse:
- Pay: highly competitive salaries.
- Schedule: flexible work schedules (also full-time exempt).
- Benefits: excellent benefits, instant 401K vesting, full cafeteria plan.
Thus we can have three sections: Pay, Schedule, Benefits.
Schedule section also
for prose. We need to decide which sections to include: About the role (description), Responsibilities (Essential Functions), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Desired Qualifications?), Skills (maybe from required/desired like technical writing etc), Benefits, Pay, Schedule. But we must avoid thin sections. Let's see content: About the role: description paragraph(s) about ABSI and mission. That's substantive. Responsibilities: Essential Functions list (multiple items). Good. Requirements: Could be "US Citizenship Required", "Clearance Type", maybe also "Work Schedule"? But those are more metadata. Could combine into a "Requirements" section with those items as list? But the rule: Use
- for any list of duties/requirements/benefits. So we can list citizenship, clearance, etc as list items.
Qualifications: Could be Required Qualifications and Desired Qualifications combined? Might be better to have a "Qualifications" section with both required and desired as sublists? But we need to follow rule: only include section when posting has real specific content. We have both required and desired qualifications. Could make two subsections? But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put qualifications under
Qualifications
and list both required and desired as items, maybe differentiate with bold? But we must preserve all substantive info; we can include both sets as list items. Skills: Could extract from required/desired: "Strong technical writing, data-analysis, briefing, and presentation skills", "Ability to integrate competing technical, operational, schedule, safety, and stakeholder requirements", "Ability to work flexibly around test schedules", "Proficiency with Microsoft Office and web-based collaborative resources such as SharePoint and Microsoft Teams". Also "Ability to lead cross-functional technical or operational teams". Those are skills. Benefits: "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 "excellent benefits" is vague but we have specifics: instant 401K vesting, full cafeteria plan. So we can list those. Pay: "highly competitive salaries". Could be a sentence. Schedule: "Work Schedule: Full Time, Exempt" and "flexible work schedules". Also "occasional travel as required". So schedule section can include full-time exempt, occasional travel, flexible work schedules. We must not repeat job title. Not include headings for Job ID etc. We must not include boilerplate like EEO etc. Remove that paragraph. We must not include duplicated lines. Ensure we don't repeat same info. Now craft HTML. Structure:About the role
... description ...
Responsibilities
- Lead the planning, coordination, execution, and reporting of developmental test events in support of program and test objectives.
- Serve as the primary interface among the test team, government program offices, aircrew, engineers, fleet representatives, and other participating organizations to maintain stakeholder alignment and enable successful execution.
- Lead and coordinate multi-domain cUAS and UART test activities, integrating technical, operational, schedule, resource, and mission requirements across participating teams.
- Develop and maintain test plans, test cards, mission requirements, schedules, readiness products, and other supporting documentation for developmental test activities.
- Provide hands-on leadership during test preparation and execution by coordinating personnel and resources, assigning and tracking action items, identifying dependencies, and managing risks to safe and efficient completion.
- Lead test team communications, coordination meetings, readiness reviews, mission briefs, debriefs, and follow-up activities.
- Monitor test execution, assess progress against objectives, elevate issues, and coordinate timely adjustments with technical and operational stakeholders.
- Analyze test data and aircraft or system performance; prepare technical reports, presentations, recommendations, and briefings that clearly document test results and conclusions.
- Apply applicable NAVAIR flight-test instructions, approved procedures, and operational risk-management practices throughout planning and execution.
- Obtain and maintain required Group 1-2 UAS qualifications and, as required, serve as an sUAS pilot or target operator in support of developmental test missions and associated flight operations.
- Perform other duties consistent with the position and program requirements, as assigned.
Requirements
- U.S. citizenship required.
- Ability to obtain and maintain a Secret security clearance.
- Full-time, exempt position.
- Occasional travel as required to support developmental test events.
- Reports to Director of Programs and Partnerships.
- Provides functional leadership to integrated test teams (no direct reports).
Qualifications
- Bachelor’s degree from an accredited institution with at least 8 years of relevant experience performing the essential functions.
- 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.
- Desired: Graduate of a recognized military or civilian Test Pilot School.
- Desired: Familiarity with the NAVAIR M-3905.1 Flight Test Manual series of instructions.
- Desired: Prior Navy aviation leadership experience at the O-3/O-4 level, or comparable military or civilian test-team leadership experience.
- Desired: Experience serving as a Project Officer, Test Director, Test Pilot, Test Naval Flight Officer, or lead flight test engineer for developmental test programs.
- Desired: Experience coordinating multi-domain cUAS testing, UART activities, UAS target operations, or related integrated test events.
- Desired: Current or prior qualification operating Group 1-2 UAS.
- Desired: Knowledge of NAVAIR developmental test processes and experience working with government program offices, test squadrons, operational aircrew, engineers, and fleet stakeholders.
- Desired: Proficiency with Microsoft Office and web-based collaborative resources such as SharePoint and Microsoft Teams.
Benefits
- Highly competitive salaries.
- Flexible work schedules.
- Excellent benefits package including instant 401K vesting.
- Full cafeteria plan that employees can tailor to individual needs.