Senior Program Manager USN/USMC
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings, but we should follow. Could have Qualifications heading and then list required and preferred within maybe separate? But better to have two sections: Required Qualifications and Preferred Qualifications? The examples didn't list those exactly but we can still use Qualifications heading and then separate lists? However instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide.
We have content for: Summary (About the role). Responsibilities. Required Qualifications. Preferred Qualifications. Benefits. Pay (salary range). Clearance Requirements (maybe not a standard heading but we could include as a section? Not in the list but could be considered as "Requirements"? Might be better to include as a separate section like "Clearance Requirements" but not in the given list; but we could treat as part of Requirements? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we can add other headings if needed, but better to stick to those. Clearance Requirements could be under Requirements or Qualifications. Work Environment maybe not needed.
We have Pay: salary range given. So we need a Pay section.
We have Benefits: list.
We have Schedule? Not mentioned. So omit.
We have Skills? Not explicit; could be under Qualifications.
Thus sections: About the role (from Summary), Responsibilities, Qualifications (maybe split Required and Preferred as subheadings? Could do Qualifications
then Required:
... then Preferred:
... but that might be okay. Or we could have two sections: Required Qualifications and Preferred Qualifications. The instruction didn't forbid that; they gave examples but not exclusive. I'd produce separate headings for Required Qualifications and Preferred Qualifications to keep clarity.
Also include Pay section.
Benefits section.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should omit the EEO statement, Clearance Requirements? That is not boilerplate; it's specific. Keep it maybe as a section "Clearance Requirements". Work Environment maybe not needed but could be included as a section? It's specific but not in list; but we could include as "Work Environment". However instruction says prefer few substantive sections over many thin ones. Might be better to omit Work Environment and Clearance Requirements? But they are substantive. However we could incorporate Clearance Requirements into Qualifications or Requirements. The posting says "Clearance Requirements This position may require access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). To comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify a US person’s status under the ITAR and the EAR." That's a requirement. Could be placed under Qualifications or Requirements. I'd add a subsection under Qualifications: Clearance.
Similarly Work Environment could be omitted as not required.
Thus final HTML:
About the role
... summary text ...
Responsibilities
... each responsibility as li . The responsibilities list is a paragraph with many sentences separated by periods. We need to split them into items. Ensure we keep all details.
Let's extract responsibilities sentences:
"Serves as the Redwire face to the customer for all post-award activites."
"Serves as point of contact for customer field issues and coordinates engineering responses including Air Worthiness Directives, Service Bulletins, field repairs, and troubleshooting."
"Provides critical input to cross-functional engineering teams during proposal, design, manufacturing, and delivery phases of products in development and production phases."
"Anticipates and stays ahead of stakeholder expectations; including internal and external customer suppliers, and ensures leadership is up to date on progress of work assigned."
"Tracks and reports on program performance metrics including schedule and performance."
"Leads failure root cause analysis and corrective actions as needed."
"Establishes milestones and monitors adherence to master plans and schedules."
"Tracks and manages issues/risks by working with internal and external team members and stakeholders to determine appropriate mitigation and containment actions."
"Participates in CCB and ECB activities across engineering and manufacturing groups."
"Proactively manages budget; holding teams responsible to program P&Ls."
"Manages timing and scope through proactively leading internal processes working closely with Program Engineering teams."
"Performs as the primary point of contact with the immediate customer and program office leadership."
"Coordinates training requests and activities."
"Travels to support assigned programs and teams as required."
Check for duplicates: none.
Now Required Qualifications list: need to split each bullet.
Required Qualifications text:
"8+ years of Program or Project Management experience or similar (e.g. Lead IPT (Integrated Product Team), or APM (Assistant Program Manager)."
"Experience working with Naval Air Systems Command (NAVAIR) program offices, ideally with the Aircraft Program Management Office (AIR PMO) formerly known as the Navy and Marine Corps Small Technical Unmanned Aircraft Systems Program Office (PMA-263)."
"Experience with full life-cycle Program Management, from design for manufacturing to transition to production programs."
"Experience with Department of Defense Acquisition Life-Cycle policies and processes."
"Experience in Defense, Government contracting and Aerospace, preferably in the UAV market."
"Earned Value Management experience."
"Demonstrated strong customer support experience."
"Strong interpersonal, communication and presentation skills."
"Ability to lead in a matrixed organization including getting things done through influence and collaboration."
"Proven analytical, technical, strategic and problem-solving skills."
"Strong sense for self-direction with the ability to work under limited supervision."
"Proficiency with Microsoft Office Suite."
Make each as - .
Preferred Qualifications list:
"BS or MS degree in engineering or technical discipline."
"Gated design development experience (PDR, CDR, MS-A, MS-B, etc.)."
"FAR Part 12 acquisition experience."
"Private industry experience."
"Navy or Marine Corps experience."
"PMP or similar Project Management/Continuous Process Improvement certification."
Benefits list:
"Matching 401(k)"
"Paid PTO"
"Paid holidays"
"Medical, vision, and dental insurance"
"Group Short-Term & Long-Term Disability"
"HSA and FSA Options"
"Critical Care Plan"
"Accident Care Plan"
"Employee Stock Purchase Plan"
Pay section: include salary range.
We need to include the salary range sentence: "The anticipated salary range for this role $159,700 – $209,000 annually. This range reflects a good faith estimate based on the targeted level for the role and typical compensation benchmarks across U.S. locations. Actual compensation may vary depending on the selected candidate’s qualifications, experience, geographical location, and internal alignment."
We should keep that as
under Pay heading.
Now About the role: The summary paragraph:
"The Senior Program Manager is a critical professional position that supports prime contracts with the United States Navy and Marine Corps (USN/USMC). The Senior Program Manager leads a portfolio that is complex in nature. The Senior Program Manager is responsible for the timing, cost and budget performance of assigned engineering projects that may vary in size from very large to multiple smaller programs. The Senior Program Manager leads the customer relationship and acts is the primary point of contact for our customers, briefing them regularly on project schedule/delivery status, aftermarket repairs status and actions, training, and all technical notifications such as Customer Change Notifications, Air Worthiness Directives, and Service Bulletins. The Senior Program Manager role requires strong leadership, communication, influence, relationship building, and management skills, coupled with Technical Project Management expertise. The Senior Program Manager role is remote; however, the selected candidate must reside in Maryland due to the need for regular travel to the customer site."
We need to preserve all info. Note there is a typo "acts is". We keep as is.
Now we need to ensure we don't include any boilerplate like EEO, etc. Also we should not include "Work Environment And Physical Requirements" nor "Clearance Requirements" as separate sections; we could incorporate clearance into Qualifications maybe as a note. But we already have Required and Preferred qualifications; we could add a bullet under Required Qualifications about clearance? However the clearance requirement is not a qualification but a requirement; we could add a separate section "Clearance Requirements" but that might be considered a section. The instruction says we can use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Clearance could be under Requirements. But we didn't include a Requirements section; we have Required Qualifications and Preferred Qualifications. Perhaps better to have a "Requirements" section that includes both required qualifications and clearance. But we already have Required Qualifications; we could rename that to "Requirements". However the instruction's examples include Requirements and Qualifications separate. Might be okay to have both.
Simplify: Use sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Under Requirements we can put the clearance requirement plus maybe the "must reside in Maryland" (that's from summary). Actually the Maryland residence is in summary; we could keep it there.
Under Qualifications we can put Required and Preferred as subheadings? Or we could just list all qualifications under Qualifications with required and preferred distinguished? But we need to preserve all info; we can separate.
Let's do:
About the role
... summary ...
Responsibilities
...
Requirements
Clearance: This position may require access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). To comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify a US person’s status under the ITAR and the EAR.
Qualifications
Required
... required qualifications ...
Preferred
... preferred qualifications ...
Benefits
... benefits ...
Pay
... salary range ...
We used for subheadings; the instruction only said use for section headings. It didn't forbid other headings, but to be safe we could avoid and instead use
bold? But we can keep
as it's still a heading; but they said use for section headings (e
Qualifications
thenRequired:
- ... then
- .
Preferred Qualifications list:
"BS or MS degree in engineering or technical discipline."
"Gated design development experience (PDR, CDR, MS-A, MS-B, etc.)."
"FAR Part 12 acquisition experience."
"Private industry experience."
"Navy or Marine Corps experience."
"PMP or similar Project Management/Continuous Process Improvement certification."
Benefits list:
"Matching 401(k)"
"Paid PTO"
"Paid holidays"
"Medical, vision, and dental insurance"
"Group Short-Term & Long-Term Disability"
"HSA and FSA Options"
"Critical Care Plan"
"Accident Care Plan"
"Employee Stock Purchase Plan"
Pay section: include salary range.
We need to include the salary range sentence: "The anticipated salary range for this role $159,700 – $209,000 annually. This range reflects a good faith estimate based on the targeted level for the role and typical compensation benchmarks across U.S. locations. Actual compensation may vary depending on the selected candidate’s qualifications, experience, geographical location, and internal alignment."
We should keep that as
under Pay heading. Now About the role: The summary paragraph: "The Senior Program Manager is a critical professional position that supports prime contracts with the United States Navy and Marine Corps (USN/USMC). The Senior Program Manager leads a portfolio that is complex in nature. The Senior Program Manager is responsible for the timing, cost and budget performance of assigned engineering projects that may vary in size from very large to multiple smaller programs. The Senior Program Manager leads the customer relationship and acts is the primary point of contact for our customers, briefing them regularly on project schedule/delivery status, aftermarket repairs status and actions, training, and all technical notifications such as Customer Change Notifications, Air Worthiness Directives, and Service Bulletins. The Senior Program Manager role requires strong leadership, communication, influence, relationship building, and management skills, coupled with Technical Project Management expertise. The Senior Program Manager role is remote; however, the selected candidate must reside in Maryland due to the need for regular travel to the customer site." We need to preserve all info. Note there is a typo "acts is". We keep as is. Now we need to ensure we don't include any boilerplate like EEO, etc. Also we should not include "Work Environment And Physical Requirements" nor "Clearance Requirements" as separate sections; we could incorporate clearance into Qualifications maybe as a note. But we already have Required and Preferred qualifications; we could add a bullet under Required Qualifications about clearance? However the clearance requirement is not a qualification but a requirement; we could add a separate section "Clearance Requirements" but that might be considered a section. The instruction says we can use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Clearance could be under Requirements. But we didn't include a Requirements section; we have Required Qualifications and Preferred Qualifications. Perhaps better to have a "Requirements" section that includes both required qualifications and clearance. But we already have Required Qualifications; we could rename that to "Requirements". However the instruction's examples include Requirements and Qualifications separate. Might be okay to have both. Simplify: Use sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Under Requirements we can put the clearance requirement plus maybe the "must reside in Maryland" (that's from summary). Actually the Maryland residence is in summary; we could keep it there. Under Qualifications we can put Required and Preferred as subheadings? Or we could just list all qualifications under Qualifications with required and preferred distinguished? But we need to preserve all info; we can separate. Let's do:
About the role
... summary ...
Responsibilities
- ...
Requirements
Clearance: This position may require access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). To comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify a US person’s status under the ITAR and the EAR.
Qualifications
Required
- ... required qualifications ...
Preferred
- ... preferred qualifications ...
Benefits
- ... benefits ...
Pay
... salary range ...
We usedfor subheadings; the instruction only said use
for section headings. It didn't forbid other headings, but to be safe we could avoid
and instead use
bold? But we can keep
as it's still a heading; but they said use
for section headings (e
Preferred:
- ... but that might be okay. Or we could have two sections: Required Qualifications and Preferred Qualifications. The instruction didn't forbid that; they gave examples but not exclusive. I'd produce separate headings for Required Qualifications and Preferred Qualifications to keep clarity.
Also include Pay section.
Benefits section.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should omit the EEO statement, Clearance Requirements? That is not boilerplate; it's specific. Keep it maybe as a section "Clearance Requirements". Work Environment maybe not needed but could be included as a section? It's specific but not in list; but we could include as "Work Environment". However instruction says prefer few substantive sections over many thin ones. Might be better to omit Work Environment and Clearance Requirements? But they are substantive. However we could incorporate Clearance Requirements into Qualifications or Requirements. The posting says "Clearance Requirements This position may require access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). To comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify a US person’s status under the ITAR and the EAR." That's a requirement. Could be placed under Qualifications or Requirements. I'd add a subsection under Qualifications: Clearance.
Similarly Work Environment could be omitted as not required.
Thus final HTML:
About the role
... summary text ...
Responsibilities
- ... each responsibility as li . The responsibilities list is a paragraph with many sentences separated by periods. We need to split them into items. Ensure we keep all details.
Let's extract responsibilities sentences:
"Serves as the Redwire face to the customer for all post-award activites."
"Serves as point of contact for customer field issues and coordinates engineering responses including Air Worthiness Directives, Service Bulletins, field repairs, and troubleshooting."
"Provides critical input to cross-functional engineering teams during proposal, design, manufacturing, and delivery phases of products in development and production phases."
"Anticipates and stays ahead of stakeholder expectations; including internal and external customer suppliers, and ensures leadership is up to date on progress of work assigned."
"Tracks and reports on program performance metrics including schedule and performance."
"Leads failure root cause analysis and corrective actions as needed."
"Establishes milestones and monitors adherence to master plans and schedules."
"Tracks and manages issues/risks by working with internal and external team members and stakeholders to determine appropriate mitigation and containment actions."
"Participates in CCB and ECB activities across engineering and manufacturing groups."
"Proactively manages budget; holding teams responsible to program P&Ls."
"Manages timing and scope through proactively leading internal processes working closely with Program Engineering teams."
"Performs as the primary point of contact with the immediate customer and program office leadership."
"Coordinates training requests and activities."
"Travels to support assigned programs and teams as required."
Check for duplicates: none.
Now Required Qualifications list: need to split each bullet.
Required Qualifications text:
"8+ years of Program or Project Management experience or similar (e.g. Lead IPT (Integrated Product Team), or APM (Assistant Program Manager)."
"Experience working with Naval Air Systems Command (NAVAIR) program offices, ideally with the Aircraft Program Management Office (AIR PMO) formerly known as the Navy and Marine Corps Small Technical Unmanned Aircraft Systems Program Office (PMA-263)."
"Experience with full life-cycle Program Management, from design for manufacturing to transition to production programs."
"Experience with Department of Defense Acquisition Life-Cycle policies and processes."
"Experience in Defense, Government contracting and Aerospace, preferably in the UAV market."
"Earned Value Management experience."
"Demonstrated strong customer support experience."
"Strong interpersonal, communication and presentation skills."
"Ability to lead in a matrixed organization including getting things done through influence and collaboration."
"Proven analytical, technical, strategic and problem-solving skills."
"Strong sense for self-direction with the ability to work under limited supervision."
"Proficiency with Microsoft Office Suite."
Make each as