Deputy Program Manager, NASA AEGIS Program
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: e.g., "assist the Program Manager with achieving financial, service delivery, customer satisfaction, and growth objectives." etc.
We need to include the details about location: "The position can be located onsite at any NASA Center."
Include AEGIS program description.
Include Primary Responsibilities bullet points exactly as given.
Include Planning, Governance & Integration bullet points.
Include Basic Qualifications bullet points.
Include Preferred Qualifications bullet points.
Include Clearance Requirements: U.S. Citizenship required; ability to obtain and maintain a security clearance ranging from a Public Trust, at minimum, up to a Top Secret clearance, as required.
Include Pay Range: $154,050.00 - $278,475.00 with note that it's a guideline.
Include Benefits: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at www.leidos.com/careers/pay-benefits.
We might also include About Leidos? Not required as a section; but could be part of About the role? Probably not needed. The instruction: "Prefer a few substantive sections over many thin ones." We could include About Leidos as part of About the role? But it's not about the role. Might be considered boilerplate? It's company description; maybe we can include as a short paragraph under About the role? But the instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Leidos is not boilerplate; it's substantive about the company. Could be included but not required as a section. Since we have limited sections, we could omit it to keep focused. However we must preserve ALL substantive information; does that mean we must include everything? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep all substantive info from the posting. However we are allowed to omit sections that are not requested? The output format only includes certain headings; but we can still include paragraphs under those headings that contain the info. If we omit About Leidos entirely, we would be dropping substantive info. So we need to include it somewhere. Perhaps we can include it under About the role as a brief paragraph about the company. Or we could add a separate section "About Leidos" but not in the list of allowed headings? The instruction says to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should not add other headings. So we must fit About Leidos into one of those sections. Probably under About the role we can include a sentence about Leidos being an industry and technology leader etc. That would preserve the info.
Similarly, we need to include the note about Pay Range being a guideline only and factors considered.
Also need to include the note about Pay and benefits: "Pay and benefits are fundamental to any career decision..." etc. That's substantive.
We also need to include the line about "Original Posting September 22, 2026" maybe? That's metadata; could be considered minor metadata and we can drop or fold into short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p with the original posting date maybe. But we might drop it as not essential. However it's substantive? It's just date; could be considered minor metadata. We'll drop.
Also "For U.S. Positions: While subject to change based on business needs, Leidos reasonably anticipates that this job requisition will remain open for at least 3 days with an anticipated close date of no earlier than 3 days after the original posting date as listed above." That's also metadata; we can drop.
Now we need to decide which info goes to which section.
Let's outline:
About the role
Combine overview and position summary and maybe About Leidos.
Responsibilities
- ... from Primary Responsibilities
- ... from Planning, Governance & Integration
Requirements
Basic Qualifications and Clearance Requirements maybe as list.
Could use for each.
Qualifications
Preferred Qualifications.
Skills
Technical knowledge areas: Network Solutions, Data Center Technologies, Cloud-based Architectures, Collaboration Services, plus leadership skills? Could list.
Benefits
Competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at www.leidos.com/careers/pay-benefits.
Pay
Pay Range $154,050.00 - $278,475.00 (guideline only; factors considered...).
We must not include Schedule.
Now we need to ensure we preserve all substantive info from Basic Qualifications, Preferred Qualifications, etc.
Let's extract Basic Qualifications bullet points:
- Bachelor's degree and 15+ years of prior relevant experience or Master's and 10+ years of prior relevant experience.
- Strong leadership abilities; detail-oriented; effective under deadlines.
- At least 7 years of experience with the management, manpower utilization, and supervision of employees (including subcontractors) of various labor categories and skills in projects.
- Proven Program Management experience across CPAF, and FFP contracts. This includes experience managing contract deliverable items, budgets, customer satisfaction.
- Proven experience and interaction with senior level customers (SES and above).
- Experience in effectively capturing on contract growth.
- Experience managing IT contracts with focus on Customer Relationship Management across multiple stakeholder communities.
- Demonstrated success building relationships with customers and teammates.
- Ability to effectively communicate when briefing Leidos and NASA senior leadership.
Preferred Qualifications bullet points:
- ITIL Certification.
- SAFe® Agile Product Manager or Lean Portfolio Manager.
- Project Management Professional (PMP)® Certification.
- Experience working with NASA or other federal agencies
- Technical knowledge across one or more of the following technologies:
- Network Solutions (e.g., LAN, WAN, SDA, SD-WAN)
- Data Center Technologies (e.g., Virtualization, Capacity Management, Data Backup)
- Cloud-based Architectures (e.g., AWS, Azure, GCP)
- Collaboration Services (e.g., Conferencing, VoIP)
Clearance Requirements:
- U.S. Citizenship is required.
- Must have the ability to obtain and maintain a security clearance ranging from a Public Trust, at minimum, up to a Top Secret clearance, as required.
Now we need to preserve all that.
Now we need to decide where to put each.
Requirements section: Could include Basic Qualifications and Clearance Requirements as a list.
Qualifications section: Preferred Qualifications.
Skills section: Could include the technical knowledge list from Preferred Qualifications (Network Solutions, Data Center Technologies, Cloud-based Architectures, Collaboration Services). Also maybe leadership skills? But leadership skills are in Basic Qualifications; we could keep them there.
But we must not duplicate info. If we put technical knowledge under Skills, we should not also repeat under Qualifications. However Preferred Qualifications includes both certifications and experience and technical knowledge. We could split: Qualifications section for certifications and experience (ITIL, SAFe, PMP, NASA experience). Skills section for technical knowledge.
But we need to preserve all substantive info; splitting is okay as long as we don't lose info.
Let's design:
About the role
The Digital Sector at Leidos currently has an opening for a Deputy Program Manager to help provide program leadership to NASA to support a complex set of enterprise IT services, including network infrastructure, data center operations, cloud computing and cybersecurity. In this position you will serve as a direct report to the Program Manager within Leidos for the NASA AEGIS Program
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: e.g., "assist the Program Manager with achieving financial, service delivery, customer satisfaction, and growth objectives." etc. We need to include the details about location: "The position can be located onsite at any NASA Center." Include AEGIS program description. Include Primary Responsibilities bullet points exactly as given. Include Planning, Governance & Integration bullet points. Include Basic Qualifications bullet points. Include Preferred Qualifications bullet points. Include Clearance Requirements: U.S. Citizenship required; ability to obtain and maintain a security clearance ranging from a Public Trust, at minimum, up to a Top Secret clearance, as required. Include Pay Range: $154,050.00 - $278,475.00 with note that it's a guideline. Include Benefits: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at www.leidos.com/careers/pay-benefits. We might also include About Leidos? Not required as a section; but could be part of About the role? Probably not needed. The instruction: "Prefer a few substantive sections over many thin ones." We could include About Leidos as part of About the role? But it's not about the role. Might be considered boilerplate? It's company description; maybe we can include as a short paragraph under About the role? But the instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Leidos is not boilerplate; it's substantive about the company. Could be included but not required as a section. Since we have limited sections, we could omit it to keep focused. However we must preserve ALL substantive information; does that mean we must include everything? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep all substantive info from the posting. However we are allowed to omit sections that are not requested? The output format only includes certain headings; but we can still include paragraphs under those headings that contain the info. If we omit About Leidos entirely, we would be dropping substantive info. So we need to include it somewhere. Perhaps we can include it under About the role as a brief paragraph about the company. Or we could add a separate section "About Leidos" but not in the list of allowed headings? The instruction says to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should not add other headings. So we must fit About Leidos into one of those sections. Probably under About the role we can include a sentence about Leidos being an industry and technology leader etc. That would preserve the info. Similarly, we need to include the note about Pay Range being a guideline only and factors considered. Also need to include the note about Pay and benefits: "Pay and benefits are fundamental to any career decision..." etc. That's substantive. We also need to include the line about "Original Posting September 22, 2026" maybe? That's metadata; could be considered minor metadata and we can drop or fold into short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p with the original posting date maybe. But we might drop it as not essential. However it's substantive? It's just date; could be considered minor metadata. We'll drop. Also "For U.S. Positions: While subject to change based on business needs, Leidos reasonably anticipates that this job requisition will remain open for at least 3 days with an anticipated close date of no earlier than 3 days after the original posting date as listed above." That's also metadata; we can drop. Now we need to decide which info goes to which section. Let's outline:
About the role
Combine overview and position summary and maybe About Leidos.
Responsibilities
- ... from Primary Responsibilities
- ... from Planning, Governance & Integration
Requirements
Basic Qualifications and Clearance Requirements maybe as list.
Could use- for each.
Qualifications
Preferred Qualifications.
Skills
Technical knowledge areas: Network Solutions, Data Center Technologies, Cloud-based Architectures, Collaboration Services, plus leadership skills? Could list.
Benefits
Competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at www.leidos.com/careers/pay-benefits.
Pay
Pay Range $154,050.00 - $278,475.00 (guideline only; factors considered...).
We must not include Schedule. Now we need to ensure we preserve all substantive info from Basic Qualifications, Preferred Qualifications, etc. Let's extract Basic Qualifications bullet points: - Bachelor's degree and 15+ years of prior relevant experience or Master's and 10+ years of prior relevant experience. - Strong leadership abilities; detail-oriented; effective under deadlines. - At least 7 years of experience with the management, manpower utilization, and supervision of employees (including subcontractors) of various labor categories and skills in projects. - Proven Program Management experience across CPAF, and FFP contracts. This includes experience managing contract deliverable items, budgets, customer satisfaction. - Proven experience and interaction with senior level customers (SES and above). - Experience in effectively capturing on contract growth. - Experience managing IT contracts with focus on Customer Relationship Management across multiple stakeholder communities. - Demonstrated success building relationships with customers and teammates. - Ability to effectively communicate when briefing Leidos and NASA senior leadership. Preferred Qualifications bullet points: - ITIL Certification. - SAFe® Agile Product Manager or Lean Portfolio Manager. - Project Management Professional (PMP)® Certification. - Experience working with NASA or other federal agencies - Technical knowledge across one or more of the following technologies: - Network Solutions (e.g., LAN, WAN, SDA, SD-WAN) - Data Center Technologies (e.g., Virtualization, Capacity Management, Data Backup) - Cloud-based Architectures (e.g., AWS, Azure, GCP) - Collaboration Services (e.g., Conferencing, VoIP) Clearance Requirements: - U.S. Citizenship is required. - Must have the ability to obtain and maintain a security clearance ranging from a Public Trust, at minimum, up to a Top Secret clearance, as required. Now we need to preserve all that. Now we need to decide where to put each. Requirements section: Could include Basic Qualifications and Clearance Requirements as a list. Qualifications section: Preferred Qualifications. Skills section: Could include the technical knowledge list from Preferred Qualifications (Network Solutions, Data Center Technologies, Cloud-based Architectures, Collaboration Services). Also maybe leadership skills? But leadership skills are in Basic Qualifications; we could keep them there. But we must not duplicate info. If we put technical knowledge under Skills, we should not also repeat under Qualifications. However Preferred Qualifications includes both certifications and experience and technical knowledge. We could split: Qualifications section for certifications and experience (ITIL, SAFe, PMP, NASA experience). Skills section for technical knowledge. But we need to preserve all substantive info; splitting is okay as long as we don't lose info. Let's design:About the role
The Digital Sector at Leidos currently has an opening for a Deputy Program Manager to help provide program leadership to NASA to support a complex set of enterprise IT services, including network infrastructure, data center operations, cloud computing and cybersecurity. In this position you will serve as a direct report to the Program Manager within Leidos for the NASA AEGIS Program