Sr. Offensive Small Unmanned Aerial Systems (OsUAS) Project Leader

We need to output HTML fragment with sections: About the role? The posting includes intro about corporation, but we need to include sections only when posting has real specific content. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Intro about corporation (maybe "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content. We have: - About the role: description of role, what you'll be doing (the "What You'll Be Doing" bullet list). That's responsibilities. - Responsibilities: could be the bullet list under "What You'll Be Doing". That's responsibilities. - Requirements: "What You Need To Be Successful Minimum Requirements". That's requirements. - Qualifications: maybe "How You Can Stand Out" (preferred qualifications). Could be "Qualifications" or "Skills". The instruction includes Skills as a possible heading. We could put "Skills" for the standout items. - Benefits: The posting mentions "We offer a competitive compensation package..." and then later "Ways We Reward Our Employees" with benefits list. So we have benefits content. - Pay: The posting includes grade-based pay range: $155,900.00 - $233,900.00 Annual. So we have Pay. - Schedule: Not explicitly mentioned; there is mention of "Standard and alternate work schedules, including telework options" under benefits. That's schedule info but could be part of Benefits. There's no explicit schedule like full-time/part-time, but they said "selected candidate will be required to work full-time, on-site at our facility in Dayton, OH". That's schedule info (full-time, on-site). So we could include Schedule section with that detail. We must not create sections with filler. All these have real content. We need to remove boilerplate: EEO, equal opportunity, legal, etc. Also remove navigation, cookie, etc. Also remove duplicated lines. Also remove application instructions (like contact info for accommodation). Also remove "Equal Opportunity Commitment" paragraph. We need to preserve all substantive information. So we need to keep the description of corporation, DSG, etc? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However we also need to remove boilerplate. The introductory paragraphs about Aerospace Corporation, DSG, Joint and Multi-Domain Subdivision are substantive? They describe the organization and context. Likely we should keep them as part of "About the role" or maybe a separate "About the company". But the allowed headings list does not include About the company; only About the role. However we could incorporate that info into About the role section as a paragraph before responsibilities. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those. So we can put the introductory description under About the role. Thus structure:

About the role

... (intro about Aerospace Corporation, DSG, Joint and Multi-Domain Subdivision, role description)

Then responsibilities as

• ... under

  Responsibilities

  Then Requirements under

  Requirements

  with list. Then Skills (or Qualifications) under

  Skills

  for standout items. Then Benefits under

  Benefits

  with list. Then Pay under

  Pay

  with the range. Then Schedule under

  Schedule

  with full-time on-site. We must ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information: need to include details like "The Aerospace Corporation is the trusted partner..." etc. Also mention DSG description, Joint and Multi-Domain Subdivision, etc. Also mention "As a Senior Project Leader supporting the USAF Offensive Small Unmanned Aircraft Systems (OsUAS) Program Office, you will play a critical role..." etc. Also mention "The selected candidate will be required to work full-time, on-site at our facility in Dayton, OH". Also mention "What You'll Be Doing" bullet list. Also need to include "Minimum Requirements for Senior Project Leader – Enterprise Systems Engineering:" list. Also need to include "How You Can Stand Out" list. Also need to include benefits list: Comprehensive health care and wellness plans, Paid holidays, sick time, and vacation, Standard and alternate work schedules, including telework options, 401(k) Plan..., Flexible spending accounts, Variable pay program for exceptional contributions, Relocation assistance, Professional growth and development programs, Education assistance programs, An inclusive work environment built on teamwork, flexibility, and respect. Also mention "We offer a competitive compensation package where you’ll be rewarded based on your performance and recognized for the value you bring to our business. The grade-based pay range for this job is listed below. Individual salaries within that range are determined through a wide variety of factors including but not limited to education, experience, knowledge and skills. (Min - Max) $155,900.00 - $233,900.00 Pay Basis: Annual". Also maybe mention "Leadership Competitors" etc but that's maybe not needed. The "Leadership Competencies" and "Ways We Reward Our Employees" sections could be considered part of Benefits? But we already captured benefits list. The leadership competencies could be omitted? It's substantive but not a standard heading. Could we include under a separate heading like "Leadership Competencies"? Not in allowed list but maybe we can still use heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. Leadership competencies could be part of Benefits or maybe omitted? But we need to preserve ALL substantive information. If we omit leadership competencies, we lose info. Could we incorporate them into Benefits section as a bullet? They are not benefits but maybe we can put them under a separate heading like "Leadership Competencies" but that deviates from allowed headings. However the instruction says "e.g." meaning those are examples, not an exhaustive list. So we could add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate leadership competencies into Benefits or maybe into About the role. But better to keep them as a separate section if they are substantive. However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd stick to those to be safe. We can incorporate leadership competencies into Benefits as a bullet? Might be odd but acceptable. Or we could create a section "Leadership Competencies" as an h3; it's not prohibited. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings. It just gives examples. So we could add a heading for Leadership Competencies. However they also say "Prefer a few substantive sections over many thin ones." Adding many sections may be discouraged. Leadership Competencies is a thin section (just a list). Could combine with Benefits? But they are distinct. Maybe we can incorporate them into Benefits as a bullet "Leadership competencies: Operate Strategically, Lead Change, Engage with Impact, Foster Innovation, Deliver Results". That preserves info. Similarly "Ways We Reward Our Employees" is basically benefits list we already captured. Thus we can omit separate leadership competencies. Now we need to remove boilerplate: Equal Opportunity Commitment, contact info for accommodation, "Know Your Rights: Workplace Discrimination is Illegal." Also remove any duplicated lines. Also remove "We are all unique, from various backgrounds and all walks of life, yet one thing bonds all of us to each other—the belief that we can make a difference. This core belief empowers us to do our best work at The Aerospace Corporation." That's maybe boilerplate? It's a value statement; could be considered substantive? It's more of a fluff. Might be considered boilerplate but it's not EEO. It's a cultural statement. Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those. It's a value statement. Could keep but it's not essential. However to preserve ALL substantive information, we should keep it unless it's considered boilerplate. I'd keep it as part of About the role maybe. But we need to be careful not to include duplicated lines. The posting repeats some sentences? Not sure. Now craft HTML. We'll start with

  About the role

  then a paragraph containing the intro about Aerospace Corporation, DSG, Joint and Multi-Domain Subdivision, and the role description. Let's extract that text: "The Aerospace Corporation is the trusted partner to the nation’s space programs, solving the hardest problems and providing unmatched technical expertise. As the operator of a federally funded research and development center (FFRDC), we are broadly engaged across all aspects of space— delivering innovative solutions that span satellite, launch, ground, and cyber systems for defense, civil and commercial customers. When you join our team, you’ll be part of a special collection of problem solvers, thought leaders, and innovators. Join us and take your place in space. The Defense Systems Group (DSG) provides analysis-based decision support to senior leaders on space architectures, policy and strategy, technology development, warfighter capability enablers, systems integration, defense industrial base, and threat reduction to help shape existing and future space missions across the national security space (NSS) enterprise. DSG is unique at Aerospace as it not only directly supports major customers, including the U.S. Space Force, U.S. Space Command, Air Force Material Command, and senior leadership at the Pentagon, but also provides a broad range of technical support across the national space enterprise, maintaining vertical responsibilities with customers’ portfolios as well as horizontal, matrixed responsibilities across the corporation. Additionally, DSG provides deep technical expertise to the Space Force Space Systems Command (SSC) in the conception, design, acquisition, launch and operations of satellite, launch vehicle, ground control, and range systems. Aerospace’s Joint and Multi-Domain Subdivision supports a broad sponsor landscape, extending Aerospace’s space-based technical expertise to operational end users. With projects ranging from state of the art research and concept development, to prototyping, cutting-edge laboratory environments, fully integrated operational capabilities, and robust analytics and decision