Lead Engineering Program Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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 parse the posting.
Key sections:
- Description: Leidos is seeking an experienced Lead Program Manager to lead complex, cross-functional programs and oversee a team of program managers. This role requires strategic vision, exceptional leadership skills, and a proven track record in delivering high-impact initiatives. The Lead Program Manager will drive program execution, align teams with organizational goals, and foster a culture of collaboration and excellence.
- Key Responsibilities: bullet list (Program Leadership, Team Management, Stakeholder Engagement, Process Optimization, Risk Management, Performance Tracking, Change Management). Each bullet includes description.
- Qualifications: Education: Bachelor’s degree in engineering or a related field. 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers. Proven success in delivering complex, cross-functional programs in a fast-paced environment. Exceptional leadership, communication, and interpersonal skills. Strong analytical and problem-solving abilities. Proficiency in program management tools (e.g., Jira, Asana, MS Project) and methodologies (e.g., Agile, Waterfall, PMI, NPI). Ability to influence and build relationships at all organizational levels. Certifications: PMP, PgMP, or equivalent certification is a plus.
- Desired Qualifications: Familiarity with radio frequency technologies or programs; Experience with aviation security technologies or programs; Experience with TSA, DHS or other government regulatory bodies.
- Then there is marketing fluff: "If you're looking for comfort, keep scrolling..." etc. That's boilerplate? It's not required content; we can remove as it's not substantive? It's more like marketing tagline. Probably remove.
- Original Posting date: September 16, 2026. That's metadata; we can drop or put in short p.
- For U.S. Positions: while subject to change... This is boilerplate about posting duration; we can drop.
- Pay Range: Pay Range $116,350.00 - $210,325.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered... This is pay info; we should include Pay section.
- About Leidos: description of company; could be considered "About the role"? Actually "About Leidos" is company overview; we could put under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "About the role" could include the description paragraph and maybe company overview? But we should not repeat job title. The description paragraph is about role. We'll put that under About the role.
- Pay And Benefits: section heading "Pay And Benefits" includes paragraph about compensation packages and benefits list: Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at link. This is benefits info. So we need Benefits section (list) and Pay section (range). The Pay And Benefits section includes both; we can split.
- Securing Your Data: scam warning boilerplate; remove.
- Commitment to Non-Discrimination: EEO boilerplate; remove.
Thus we need sections:
- About the role: includes the description paragraph (maybe also the "If you're looking for comfort..."? That's fluff; we should remove as not substantive. So just the description paragraph.
- Responsibilities: list of responsibilities.
- Requirements: maybe combine Qualifications and Desired Qualifications? The instruction has headings: Requirements, Qualifications, Skills. We need to decide what to put where. The posting has Qualifications (education, experience, skills, certifications) and Desired Qualifications (specific domain experience). We could put Qualifications section for the required qualifications, and Skills section for proficiencies (tools, methodologies). Or we could put Requirements for education/experience, Qualifications for certifications, Skills for tools. But we need to avoid thin sections. Prefer few substantive sections.
We could have:
- About the role (description)
- Responsibilities (list)
- Qualifications (education, experience, certifications, desired qualifications)
- Skills (tools, methodologies, abilities)
- Pay (range)
- Benefits (list)
Schedule: not mentioned, so omit.
We must not create sections with filler. So we will include only those with real content.
Now format:
About the role
Leidos is seeking an experienced Lead Program Manager to lead complex, cross-functional programs and oversee a team of program managers. This role requires strategic vision, exceptional leadership skills, and a proven track record in delivering high-impact initiatives. The Lead Program Manager will drive program execution, align teams with organizational goals, and foster a culture of collaboration and excellence.
Responsibilities
- Program Leadership: Define, plan, and execute large-scale programs, ensuring alignment with business objectives, timelines, and budgets.
- Team Management: Supervise and mentor a team of program managers, providing guidance, performance feedback, and professional development opportunities.
- Stakeholder Engagement: Collaborate with senior leadership, cross-functional teams, and external partners to drive consensus and resolve conflicts.
- Process Optimization: Develop and implement scalable program management frameworks, tools, and best practices to enhance efficiency and outcomes.
- Risk Management: Identify, assess, and mitigate program risks, ensuring proactive solutions to challenges.
- Performance Tracking: Establish KPIs, monitor program progress, and report outcomes to executives and stakeholders.
- Change Management: Lead teams through organizational changes, ensuring smooth transitions and adoption of new processes or technologies.
Qualifications
- Education: Bachelor’s degree in engineering or a related field.
- Experience: 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers.
- Proven success in delivering complex, cross-functional programs in a fast‑paced environment.
- Exceptional leadership, communication, and interpersonal skills.
- Strong analytical and problem‑solving abilities.
- Ability to influence and build relationships at all organizational levels.
- Certifications: PMP, PgMP, or equivalent certification is a plus.
- Desired qualifications: Familiarity with radio frequency technologies or programs; experience with aviation security technologies or programs; experience with TSA, DHS or other government regulatory bodies.
But we might want to separate Skills. However the Qualifications list includes skills like leadership, communication, analytical abilities. Could be considered Skills. But we already have Qualifications covering education, experience, certifications, desired qualifications. The instruction says we can have Skills section. Might be better to split: Qualifications for education/experience/certifications; Skills for tools, methodologies, leadership etc. But we need to avoid thin sections. Let's see if we can combine.
We have: "Proficiency in program management tools (e.g., Jira, Asana, MS Project) and methodologies (e.g., Agile, Waterfall, PMI, NPI)." That's a skill. Also "Exceptional leadership, communication, and interpersonal skills." and "Strong analytical and problem-solving abilities." and "Ability to influence and build relationships at all organizational levels." Those are skills/competencies.
Thus we could have a Skills section containing those bullet points.
Qualifications section could contain education, experience, certifications, desired qualifications.
Let's do:
Qualifications
- Education: Bachelor’s degree in engineering or a related field.
- Experience: 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers.
- Certifications: PMP, PgMP, or equivalent certification is a plus.
- Desired qualifications: Familiarity with radio frequency technologies or programs; experience with aviation security technologies or programs; experience with TSA, DHS or other government regulatory bodies.
Skills
- Proven success in delivering complex, cross‑functional programs in a fast‑paced environment.
- Exceptional leadership, communication, and interpersonal skills.
- Strong analytical and problem‑solving abilities.
- Proficiency in program management tools (e.g., Jira, Asana, MS Project) and methodologies (e.g., Agile, Waterfall, PMI, NPI).
- Ability to influence and build relationships at all organizational levels.
Now Pay:
Pay
Pay Range: $116,350.00 - $210,325.00 (Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary; additional factors considered include responsibilities, education, experience, knowledge, skills, abilities, internal equity, market data, applicable bargaining agreement, or other law.)
We need to preserve all substantive information; we included the note about guideline and factors.
Benefits:
From Pay And Benefits paragraph: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits."
We should make a Benefits section with list.
Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
More details: www.leidos.com/careers/pay-benefits
But we must not add extra info like link? The posting says "More details are available at www.leidos.com/careers/pay-benefits." We can keep as plain text or as a link. The instruction says preserve ALL substantive information; we can keep as plain text. Using is okay but might be considered adding markup not present; but it's still preserving the URL. Safer to keep as plain text.
Thus:
More details are available at www.leidos.com/careers/pay-benefits.
Now About Leidos company overview: Should we include? It's under "About Leidos". That could be considered "About the role"? But we already used About the role for description. The company overview is not about the role but about the employer. The instruction headings include "About the role". Not "About the company". So we might omit company overview as it's not required for the role? However it's substantive information about the employer; but the instruction says to include sections only when posting has real, specific content for it. The posting does have "About Leidos" paragraph. Should we include it? Possibly under About the role? But that heading is for role description.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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 parse the posting. Key sections: - Description: Leidos is seeking an experienced Lead Program Manager to lead complex, cross-functional programs and oversee a team of program managers. This role requires strategic vision, exceptional leadership skills, and a proven track record in delivering high-impact initiatives. The Lead Program Manager will drive program execution, align teams with organizational goals, and foster a culture of collaboration and excellence. - Key Responsibilities: bullet list (Program Leadership, Team Management, Stakeholder Engagement, Process Optimization, Risk Management, Performance Tracking, Change Management). Each bullet includes description. - Qualifications: Education: Bachelor’s degree in engineering or a related field. 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers. Proven success in delivering complex, cross-functional programs in a fast-paced environment. Exceptional leadership, communication, and interpersonal skills. Strong analytical and problem-solving abilities. Proficiency in program management tools (e.g., Jira, Asana, MS Project) and methodologies (e.g., Agile, Waterfall, PMI, NPI). Ability to influence and build relationships at all organizational levels. Certifications: PMP, PgMP, or equivalent certification is a plus. - Desired Qualifications: Familiarity with radio frequency technologies or programs; Experience with aviation security technologies or programs; Experience with TSA, DHS or other government regulatory bodies. - Then there is marketing fluff: "If you're looking for comfort, keep scrolling..." etc. That's boilerplate? It's not required content; we can remove as it's not substantive? It's more like marketing tagline. Probably remove. - Original Posting date: September 16, 2026. That's metadata; we can drop or put in short p. - For U.S. Positions: while subject to change... This is boilerplate about posting duration; we can drop. - Pay Range: Pay Range $116,350.00 - $210,325.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered... This is pay info; we should include Pay section. - About Leidos: description of company; could be considered "About the role"? Actually "About Leidos" is company overview; we could put under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "About the role" could include the description paragraph and maybe company overview? But we should not repeat job title. The description paragraph is about role. We'll put that under About the role. - Pay And Benefits: section heading "Pay And Benefits" includes paragraph about compensation packages and benefits list: Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at link. This is benefits info. So we need Benefits section (list) and Pay section (range). The Pay And Benefits section includes both; we can split. - Securing Your Data: scam warning boilerplate; remove. - Commitment to Non-Discrimination: EEO boilerplate; remove. Thus we need sections: - About the role: includes the description paragraph (maybe also the "If you're looking for comfort..."? That's fluff; we should remove as not substantive. So just the description paragraph. - Responsibilities: list of responsibilities. - Requirements: maybe combine Qualifications and Desired Qualifications? The instruction has headings: Requirements, Qualifications, Skills. We need to decide what to put where. The posting has Qualifications (education, experience, skills, certifications) and Desired Qualifications (specific domain experience). We could put Qualifications section for the required qualifications, and Skills section for proficiencies (tools, methodologies). Or we could put Requirements for education/experience, Qualifications for certifications, Skills for tools. But we need to avoid thin sections. Prefer few substantive sections. We could have: - About the role (description) - Responsibilities (list) - Qualifications (education, experience, certifications, desired qualifications) - Skills (tools, methodologies, abilities) - Pay (range) - Benefits (list) Schedule: not mentioned, so omit. We must not create sections with filler. So we will include only those with real content. Now format:
About the role
Leidos is seeking an experienced Lead Program Manager to lead complex, cross-functional programs and oversee a team of program managers. This role requires strategic vision, exceptional leadership skills, and a proven track record in delivering high-impact initiatives. The Lead Program Manager will drive program execution, align teams with organizational goals, and foster a culture of collaboration and excellence.
Responsibilities
- Program Leadership: Define, plan, and execute large-scale programs, ensuring alignment with business objectives, timelines, and budgets.
- Team Management: Supervise and mentor a team of program managers, providing guidance, performance feedback, and professional development opportunities.
- Stakeholder Engagement: Collaborate with senior leadership, cross-functional teams, and external partners to drive consensus and resolve conflicts.
- Process Optimization: Develop and implement scalable program management frameworks, tools, and best practices to enhance efficiency and outcomes.
- Risk Management: Identify, assess, and mitigate program risks, ensuring proactive solutions to challenges.
- Performance Tracking: Establish KPIs, monitor program progress, and report outcomes to executives and stakeholders.
- Change Management: Lead teams through organizational changes, ensuring smooth transitions and adoption of new processes or technologies.
Qualifications
- Education: Bachelor’s degree in engineering or a related field.
- Experience: 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers.
- Proven success in delivering complex, cross-functional programs in a fast‑paced environment.
- Exceptional leadership, communication, and interpersonal skills.
- Strong analytical and problem‑solving abilities.
- Ability to influence and build relationships at all organizational levels.
- Certifications: PMP, PgMP, or equivalent certification is a plus.
- Desired qualifications: Familiarity with radio frequency technologies or programs; experience with aviation security technologies or programs; experience with TSA, DHS or other government regulatory bodies.
Qualifications
- Education: Bachelor’s degree in engineering or a related field.
- Experience: 12+ years of program or project management experience, with at least 5 years in a leadership role managing other program managers.
- Certifications: PMP, PgMP, or equivalent certification is a plus.
- Desired qualifications: Familiarity with radio frequency technologies or programs; experience with aviation security technologies or programs; experience with TSA, DHS or other government regulatory bodies.
Skills
- Proven success in delivering complex, cross‑functional programs in a fast‑paced environment.
- Exceptional leadership, communication, and interpersonal skills.
- Strong analytical and problem‑solving abilities.
- Proficiency in program management tools (e.g., Jira, Asana, MS Project) and methodologies (e.g., Agile, Waterfall, PMI, NPI).
- Ability to influence and build relationships at all organizational levels.
Pay
Pay Range: $116,350.00 - $210,325.00 (Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary; additional factors considered include responsibilities, education, experience, knowledge, skills, abilities, internal equity, market data, applicable bargaining agreement, or other law.)
We need to preserve all substantive information; we included the note about guideline and factors. Benefits: From Pay And Benefits paragraph: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." We should make a Benefits section with list.Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
More details: www.leidos.com/careers/pay-benefits
But we must not add extra info like link? The posting says "More details are available at www.leidos.com/careers/pay-benefits." We can keep as plain text or as a link. The instruction says preserve ALL substantive information; we can keep as plain text. Using is okay but might be considered adding markup not present; but it's still preserving the URL. Safer to keep as plain text. Thus:More details are available at www.leidos.com/careers/pay-benefits.
Now About Leidos company overview: Should we include? It's under "About Leidos". That could be considered "About the role"? But we already used About the role for description. The company overview is not about the role but about the employer. The instruction headings include "About the role". Not "About the company". So we might omit company overview as it's not required for the role? However it's substantive information about the employer; but the instruction says to include sections only when posting has real, specific content for it. The posting does have "About Leidos" paragraph. Should we include it? Possibly under About the role? But that heading is for role description.