Senior Manager, Flight Operations

We need to output HTML fragment with headings

for 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 (EEO, etc). Must not create sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes "Standard work hours for this position are 8:30am-5:00pm with occasional overtime as operational needs demand." That's schedule info. So we can include Schedule section. Pay: posting says "Competitive salary, generous paid time off (PTO), and flexible leave options." That's compensation but not specific numbers. It says "Competitive salary" but no actual figure. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, "Competitive salary" is vague but still states something about pay. Is that considered filler? It's not a specific number but it's a statement about pay. The rule says avoid filler like "commensurate with experience". "Competitive salary" might be considered vague but still a statement. However they said never create Pay section unless posting actually states them. It does state "Competitive salary, generous paid time off (PTO), and flexible leave options." That's about compensation. So we could include Pay section with that sentence. But we also have Benefits section already covering benefits. The Benefits section includes many benefits listed. The Pay section could just be about salary. However they said prefer a few substantive sections over many thin ones. Could combine Pay and Benefits? But they want separate headings if content exists. We have Benefits content: comprehensive BCBS medical, dental, vision; Safe Harbor 401K; Paid Parental Leave; on-site gym; employer provided life insurance; EAP; work environment encourages teamwork; Competitive salary, generous PTO, flexible leave options. Actually the last part about competitive salary etc appears in Benefits paragraph. So we could put all compensation and benefits under Benefits section. Then we might not need separate Pay section. The rule: Prefer a few substantive sections over many thin ones. So we can omit Pay section and include salary info within Benefits. Schedule we have specific hours. So include Schedule. Now sections: About the role (intro paragraph), Responsibilities (the "What You’ll Do" bullet list), Requirements (the "Requirements" bullet list), Qualifications (the "Preferred Qualifications" maybe), Skills? Not explicitly listed; maybe we can combine Requirements and Qualifications. But we need to follow headings only if content exists. We have Requirements (mandatory) and Preferred Qualifications (preferred). Could treat both under Requirements? But they are separate sections in posting. We could have Requirements (mandatory) and Qualifications (preferred). Skills not explicitly listed; we could omit Skills. We need to preserve all substantive info. So we need to include the intro paragraph about PDW, mission, values, etc as About the role. Then Responsibilities: the bullet list under "What You’ll Do". Then Requirements: the bullet list under "Requirements". Then Qualifications: the bullet list under "Preferred Qualifications". Then Benefits: the bullet list under "Benefits". Then Schedule: the sentence about standard work hours. We must not include EEO statement, physical requirements, work environment? Those are substantive? They are part of posting but maybe considered boilerplate? Physical Requirements and Work Environment are specific details about job. Should we include? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements and Work Environment are not EEO; they are substantive job details. Should we keep them? Possibly yes, as they are part of job description. However they might be considered boilerplate but they are specific to role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep Physical Requirements and Work Environment. But we need to fit them into sections. Could create a section "Physical Requirements" or "Work Environment". But headings list only includes certain headings; we can use other headings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings for sections. It doesn't forbid other headings, but likely they expect only those. However we could incorporate Physical Requirements and Work Environment into existing sections like Requirements or Qualifications? Might be awkward. Better to add a section "Physical Requirements" and "Work Environment" as

even if not in the list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are typical but not exhaustive. But to be safe, we could add them as

with appropriate titles. However the instruction also says "Prefer a few substantive sections over many thin ones." Adding many sections may be thin. Physical Requirements and Work Environment are each a short paragraph; could be combined into a "Working Conditions" section. But not in list. Could we incorporate them into Requirements? They are not requirements but details about job. Might be okay to add a section "Working Conditions". However the instruction didn't forbid other headings; just gave examples. I'd include them as separate sections to preserve info. But we must not include boilerplate like EEO statement. So we remove that. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Schedule

Standard work hours for this position are 8:30am-5:00pm with occasional overtime as operational needs demand.

We might also add Physical Requirements and Work Environment sections if we decide. Let's extract content. About the role: The first paragraph(s) up to "Now, we’re entering a new phase of growth and are looking for a Senior Manager, Flight Operations who will own the safe, compliant, and scalable execution of PDW flight activities across production, engineering development, qualification, regression, performance, demonstration, and customer/program support." That's basically the intro. We'll capture everything before "What You’ll Do". Let's copy: "Performance Drone Works (PDW) is building the next generation of tactical robotic systems used across defense, national security, and public safety missions. We are building a new center of engineering excellence to design our new category of tactical robotic systems and the industrial capacity to deliver them, bringing decisive airpower into the hands of every operator. We are not here to make promises; we are here to deliver real systems with real capabilities for real missions. You will join a team of operators, engineers, and builders who solve hard problems with humility and focus. We design and produce multi-mission aerial systems that operators trust to perform in real-world conditions, reliably, repeatedly, and at scale. Our approach is grounded in operator-centered design, rapid iteration from field use, and U.S.-based manufacturing. We operate by a clear set of values: Mission First, Aim Farther, Own It, Win Together. This is how we build advantage and how we help protect our service members, our communities, and our country. Now, we’re entering a new phase of growth and are looking for a Senior Manager, Flight Operations who will own the safe, compliant, and scalable execution of PDW flight activities across production, engineering development, qualification, regression, performance, demonstration, and customer/program support." That's the About the role. Responsibilities: The bullet list under "What You’ll Do". Let's capture each line: - Own the strategy, capacity, operating model, and continued development of PDW Flight Operations in support of production, research and development, qualification, regression, performance, demonstration, and customer/program flight activities. - Lead, develop, and scale the Flight Operations organization through workforce planning, clear accountability, performance management, succession planning, and development of pilots, supervisors, and support personnel. - Establish and govern flight-safety policy, operational-risk controls, emergency procedures, stop-work authority, and compliance with applicable FAA, FCC, range, export-control, customer, and company requirements. - Develop and govern pilot qualification, aircraft-specific authorization, recurrent training, competency evaluation, and flight-currency programs, including authority to approve, restrict, or suspend operational privileges. - Direct flight-test planning, readiness reviews, prioritization, scheduling, and execution against approved test plans, procedures, test cards, configurations, and acceptance criteria. - Partner with Engineering, Manufacturing, Quality, Product Management, and Program Management to resolve readiness constraints, communicate operational risk, and convert flight results and anomalies into accountable actions. - Ensure the operational fleet is maintained, configured, registered, tracked, and released for flight with complete maintenance, configuration, software, battery, and flight records. - Manage flight facilities, airspace authorizations and waivers, range coordination, external service providers, field deployments, and other resources required to support PDW flight activities. - Own departmental headcount, equipment, schedule, and performance metrics, including safety performance, pilot currency, fleet availability, test completion, data quality, and operational cycle time. - Lead response to flight incidents, test anomalies, and operational-performance issues, ensuring immediate containment, objective investigation, root-cause ownership, corrective action, and verification of effectiveness. We'll put each as

. Requirements: bullet list under "Requirements". Let's capture: - 8+ years of progressive experience in UAS, aviation flight operations, flight testing, or a comparable aerospace operational environment, including production and developmental flight activities. - 5+ years leading a flight-operations or flight-test organization, with demonstrated success developing leaders, scaling teams, managing budgets and resources, and improving operational performance - Bachelor’s degree in aviation, engineering, business, safety, or a related discipline, or an equivalent combination of education and directly relevant experience. - FAA Remote Pilot Certificate with a small UAS rating. Demonstrated experience with FAA operating requirements, airspace authorizations, waivers, LAANC, Remote ID, and applicable FCC or range requirements. - Demonstrated success establishing or managing flight-safety programs, operational-risk assessments, emergency-response procedures, incident investigations, and corrective actions. - Ability to travel and support off-site operations, field deployments, and nonstandard flight schedules as operational needs require. - Must have the ability to obtain and maintain a U.S. Security Clearance. We'll put each as

. Qualifications: bullet list under "Preferred Qualifications". Capture: - A pilot certificate issued under 14 CFR part 61, military aviation leadership, or formal flight-test education. - Experience supporting Department of Defense customers, classified programs, or production-rate UAS operation. - Experience implementing a Safety Management System or leading an aviation quality or regulatory audit. - Advanced competency in acceptance, regression, qualification, performance, and developmental flight-test methodologies, including readiness reviews, data integrity, and anomaly resolution. - Experience in an AS9100, ISO 9001, aerospace, defense, or similarly controlled environment requiring disciplined document, configuration, test-record, and quality controls. We'll put each as

. Benefits: bullet list under "Benefits". Capture: - Comprehensive BCBS medical, dental, and vision coverage; 80% sponsored by the company. - Safe Harbor 401(K