MQ-9 Reaper Air Vehicle Pilot
for each section. Use - for lists. Use
for prose.
We must not repeat job title. No Job ID. Remove boilerplate like EEO etc. The posting includes an EEO statement at end: "AVIAN is a service-based organization. As an equal opportunity employer..." That's boilerplate; remove.
Also remove duplicated lines like "Responsibilities Responsibilities". We'll consolidate.
We need to preserve all substantive information. Let's extract sections:
Overview: The first paragraph(s) about company mission etc. Could be considered "About the role"? Actually there is an "Overview" then "About The Role". We could treat "Overview" as part of "About the role"? But the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have "About The Role" heading in source. We'll use that as
About the role
. Under that we put the prose describing the role: "AVIAN is seeking an MQ-9 Reaper Air Vehicle Pilot (AVP) to join the Navy/Marine Corps' premier UAS test squadron, UX-24, in Patuxent River, Maryland. Become part of a dynamic team of military, government, and contract support personnel that will continue to deliver new capability to the Marine Corps' MQ-9 Reaper air vehicles through the test and evaluation of cutting edge next-generation communication and SIGINT payloads. We are looking for a candidate with a strong background in MQ-9 operations, to include both C-band and SLR launch and recovery, who is familiar with the integration of new payloads and capabilities onto existing airframes. Prior operational or developmental test experience is a highly desired. In addition to piloting the MQ-9 air vehicle in support of developmental test events, you will work as a project officer within the UAS test squadron where you will manage diverse teams of aircrew and flight test engineers and work closely with those teams to apply real-world operational experience to the test program in an effort to ensure the highest quality product is delivered to support the warfighters needs."
That's the prose.
Then "Responsibilities" heading. The responsibilities list includes many items: test planning meetings, test plan development, event planning, test procedure and card development, flight briefings, test execution, post event support, test reporting, deficiency reporting, Act as Pilot-in-Command (PIC) of MQ-9 aircraft for launch and recovery efforts., Coordinate and actively participate in UAS ground and flight operations efforts; including mission planning, execution, briefing, debriefing, aircrew resource management, and safety., Define, plan, organize, and execute flight plans and schedules. Review maintenance logs, weather reports, and forecasts., Use Technical Orders, other documents, and reports to ascertain factors; such as aircraft weight and balance, fuel supply, route, schedule, and mechanical reliability., Maintain ability to travel to CONUS and OCONUS sites., Most work will be conducted on-site at NAS Patuxent River, MD, however, some domestic travel will be required in support of flight test activities.
We should put each as - . Some are sentences with semicolons; we can keep as is.
Then "Qualifications" heading. The posting has "Qualifications Required:" and then list. Also "Desired" items. We could combine required and desired under Qualifications. But we could also have separate "Requirements" and "Skills"? The instruction says we can use headings like Requirements, Qualifications, Skills. We have qualifications list; we could put under
Qualifications
. We'll include both required and desired items as list items.
Required list:
- Qualified MQ-9 Pilot with SLR experience
- 1000+ documented flight hours (manned/unmanned)
- Minimum 500 hours PIC in medium/high altitude long endurance UAS
- Active Secret clearance with the ability to attain a Top Secret clearance
- FAA Second Class Medical
- Must be able to obtain and maintain a Department of Defense security clearance.
- Due to the sensitivity of customer-related requirements, U.S. Citizenship is required.
Desired list:
- Manual Launch and Recovery experience / C-Band operations experience
- Graduate of full-length course of instruction from a recognized military test pilot school: e.g. USNTPS, USAFTPS, Empire, or EPNER. Pay differential for this experience will be applied.
- Operational test or payload integration experience
- 500 hours of MQ-9 experience highly desired
- Project officer experience
- Applicant must be adaptable, have good communication skills, and work well in a team environment.
We could also note "Salary range: $130,000 - $160,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)" That's Pay.
Benefits: as described.
We should not include Schedule.
We need to output only HTML fragment.
Let's construct:
About the role
... (prose)
Responsibilities
- ... each item
Qualifications
- ... required items
- ... desired items
Pay
Salary range: $130,000 - $160,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)
Benefits
- Comprehensive Benefits Package: Designed to support your health, financial security, and overall well-being, our health and wellness benefits include medical, dental, and vision coverage, along with telemedicine services and a TRICARE supplement for veterans.
- Flexible Leave Benefits: we prioritize a balanced, supportive environment that allows you to thrive both personally and professionally and offer flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, and military training leave.
We need to ensure no duplicate content. Also ensure we didn't include any boilerplate like EEO.
Check that we didn't inadvertently include "Overview" section; we omitted it but its content is somewhat generic about company mission. Could be considered part of "About the role"? The overview includes: "Join a Company Where You Can Make a Real Impact – and Own a Piece of the Future Are you energized by the idea of helping a company grow smarter, serve our customers better, and connect more deeply? Do you thrive in an environment where your ideas matter, your voice is heard, and your work drives real results? If so, we’d love to meet you. We’re a mid-sized, employee-owned company on a mission to create meaningful value for both our employees and our customers. That means we’re not just looking for someone to fill a seat — we’re looking for someone who wants to build, innovate, and evolve with us. Our company primarily serves the Navy and other Department of Defense clients, offering a dynamic environment where your expertise will make a difference."
That is substantive and not covered elsewhere. Should we include it? The instruction says include a section ONLY when the posting has real, specific content for it. The overview is about company culture/mission. Could be placed under "About the role" or maybe a separate section like "About the company". But allowed headings are limited to those listed; we could incorporate overview into About the role section as additional prose before the role specifics. That would be okay: we can have About the role section containing both overview and role details. However the source already has an "About The Role" heading; we could keep that heading and include overview as part of that section. That would preserve all info.
Thus About the role section will contain two paragraphs: first the overview paragraph(s), then the role specifics.
Let's combine.
Overview prose: "Join a Company Where You Can Make a Real Impact – and Own a Piece of the Future Are you energized by the idea of helping a company grow smarter, serve our customers better, and connect more deeply? Do you thrive in an environment where your ideas matter, your voice is heard, and your work drives real results? If so, we’d love to meet you. We’re a mid-sized, employee-owned company on a mission to create meaningful value for both our employees and our customers. That means we’re not just looking for someone to fill a seat — we’re looking for someone who wants to build, innovate, and evolve with us. Our company primarily serves the Navy and other Department of Defense clients, offering a dynamic environment where your expertise will make a difference."
Then role specifics as earlier.
We'll put them in separate tags under the same heading.
Now ensure we didn't include any duplicated lines like "Responsibilities Responsibilities". We'll just have one Responsibilities heading.
Now produce HTML.
Check for any leftover boilerplate: The "Why Join Us?" section includes bullet points about employee ownership etc. That's substantive; could be considered part of Benefits or maybe a separate section like "Why Join Us?" but not in allowed headings. Could incorporate into Benefits or maybe a separate section like "About Being a Part Of Team AVIAN". That section includes employee ownership description, culture, etc. That's substantive and not covered elsewhere. Should we include it? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have headings limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the "Why Join Us?" content under Benefits or maybe under About the role? But it's more about company culture and benefits beyond health. Could be considered part of Benefits (though benefits usually refer to health/leave). However the "Why Join Us?" includes Employee Ownership, Real Growth, Purpose-Driven Work, Culture of Collaboration. That's more about company value proposition. Could be placed under a section like "About the role" but that might be odd. Perhaps we could create a section "About Being a Part Of Team AVIAN" but not allowed heading. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." implying those are examples, not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings if they have content. If we have content that doesn't fit those, maybe we should not create a heading for it; we could incorporate into existing sections as prose.
Thus we can incorporate the "Why Join Us?" content into Benefits section as additional list items or prose. Or we could add a
under Benefits describing culture.
Let's add to Benefits section: after the two list items, add a
describing employee
for prose. We must not repeat job title. No Job ID. Remove boilerplate like EEO etc. The posting includes an EEO statement at end: "AVIAN is a service-based organization. As an equal opportunity employer..." That's boilerplate; remove. Also remove duplicated lines like "Responsibilities Responsibilities". We'll consolidate. We need to preserve all substantive information. Let's extract sections: Overview: The first paragraph(s) about company mission etc. Could be considered "About the role"? Actually there is an "Overview" then "About The Role". We could treat "Overview" as part of "About the role"? But the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "About The Role" heading in source. We'll use that as
About the role
. Under that we put the prose describing the role: "AVIAN is seeking an MQ-9 Reaper Air Vehicle Pilot (AVP) to join the Navy/Marine Corps' premier UAS test squadron, UX-24, in Patuxent River, Maryland. Become part of a dynamic team of military, government, and contract support personnel that will continue to deliver new capability to the Marine Corps' MQ-9 Reaper air vehicles through the test and evaluation of cutting edge next-generation communication and SIGINT payloads. We are looking for a candidate with a strong background in MQ-9 operations, to include both C-band and SLR launch and recovery, who is familiar with the integration of new payloads and capabilities onto existing airframes. Prior operational or developmental test experience is a highly desired. In addition to piloting the MQ-9 air vehicle in support of developmental test events, you will work as a project officer within the UAS test squadron where you will manage diverse teams of aircrew and flight test engineers and work closely with those teams to apply real-world operational experience to the test program in an effort to ensure the highest quality product is delivered to support the warfighters needs." That's the prose. Then "Responsibilities" heading. The responsibilities list includes many items: test planning meetings, test plan development, event planning, test procedure and card development, flight briefings, test execution, post event support, test reporting, deficiency reporting, Act as Pilot-in-Command (PIC) of MQ-9 aircraft for launch and recovery efforts., Coordinate and actively participate in UAS ground and flight operations efforts; including mission planning, execution, briefing, debriefing, aircrew resource management, and safety., Define, plan, organize, and execute flight plans and schedules. Review maintenance logs, weather reports, and forecasts., Use Technical Orders, other documents, and reports to ascertain factors; such as aircraft weight and balance, fuel supply, route, schedule, and mechanical reliability., Maintain ability to travel to CONUS and OCONUS sites., Most work will be conducted on-site at NAS Patuxent River, MD, however, some domestic travel will be required in support of flight test activities. We should put each asQualifications
. We'll include both required and desired items as list items. Required list: - Qualified MQ-9 Pilot with SLR experience - 1000+ documented flight hours (manned/unmanned) - Minimum 500 hours PIC in medium/high altitude long endurance UAS - Active Secret clearance with the ability to attain a Top Secret clearance - FAA Second Class Medical - Must be able to obtain and maintain a Department of Defense security clearance. - Due to the sensitivity of customer-related requirements, U.S. Citizenship is required. Desired list: - Manual Launch and Recovery experience / C-Band operations experience - Graduate of full-length course of instruction from a recognized military test pilot school: e.g. USNTPS, USAFTPS, Empire, or EPNER. Pay differential for this experience will be applied. - Operational test or payload integration experience - 500 hours of MQ-9 experience highly desired - Project officer experience - Applicant must be adaptable, have good communication skills, and work well in a team environment. We could also note "Salary range: $130,000 - $160,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)" That's Pay. Benefits: as described. We should not include Schedule. We need to output only HTML fragment. Let's construct:About the role
... (prose)
Responsibilities
- ... each item
Qualifications
- ... required items
- ... desired items
Pay
Salary range: $130,000 - $160,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)
Benefits
- Comprehensive Benefits Package: Designed to support your health, financial security, and overall well-being, our health and wellness benefits include medical, dental, and vision coverage, along with telemedicine services and a TRICARE supplement for veterans.
- Flexible Leave Benefits: we prioritize a balanced, supportive environment that allows you to thrive both personally and professionally and offer flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, and military training leave.
tags under the same heading. Now ensure we didn't include any duplicated lines like "Responsibilities Responsibilities". We'll just have one Responsibilities heading. Now produce HTML. Check for any leftover boilerplate: The "Why Join Us?" section includes bullet points about employee ownership etc. That's substantive; could be considered part of Benefits or maybe a separate section like "Why Join Us?" but not in allowed headings. Could incorporate into Benefits or maybe a separate section like "About Being a Part Of Team AVIAN". That section includes employee ownership description, culture, etc. That's substantive and not covered elsewhere. Should we include it? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have headings limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the "Why Join Us?" content under Benefits or maybe under About the role? But it's more about company culture and benefits beyond health. Could be considered part of Benefits (though benefits usually refer to health/leave). However the "Why Join Us?" includes Employee Ownership, Real Growth, Purpose-Driven Work, Culture of Collaboration. That's more about company value proposition. Could be placed under a section like "About the role" but that might be odd. Perhaps we could create a section "About Being a Part Of Team AVIAN" but not allowed heading. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." implying those are examples, not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings if they have content. If we have content that doesn't fit those, maybe we should not create a heading for it; we could incorporate into existing sections as prose. Thus we can incorporate the "Why Join Us?" content into Benefits section as additional list items or prose. Or we could add a
under Benefits describing culture. Let's add to Benefits section: after the two list items, add a
describing employee