Security Program Oversight Manager
for sections like 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. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. No invented or summarized away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "How you’ll grow", "Benefits" maybe we have benefits content. There's a Benefits section with description. Also there is "Estimated Salary/Wage". So Pay section. No schedule info. So we may not include Schedule heading.
We need to parse the posting.
Let's extract sections:
- About the role: The initial paragraph after title: "Are you ready to enhance your skills and build your career in a rapidly evolving business climate? Are you looking for a career where professional development is embedded in your employer’s core culture? If so, Chenega Military, Intelligence & Operations Support (MIOS) could be the place for you! Join our team of professionals who support large-scale government operations by leveraging cutting-edge technology and take your career to the next level! We are seeking a highly experienced and strategic Security Program Oversight Manager to provide governance, track, and monitor the successful delivery of a portfolio of strategic initiatives. This role is responsible for managing the project governance lifecycle for cybersecurity efforts, from initiation through closeout, providing schedule control, formal risk management, and decision-ready reporting in partnership with the Lead Cybersecurity Execution Manager, who directs technical execution. This role Track and report RMF milestones, artifacts, and authorization timelines, and provides transparent accountability through schedule, milestone, and risk reporting. The Security Project Oversight Manager will act as a champion for delivery excellence by establishing and enforcing best practices, guiding project teams, and driving continuous improvement in project management processes."
We can treat that as About the role.
- Responsibilities: There's a "Responsibilities" heading in the posting, then bullet-like paragraphs: "Performance Monitoring & Risk Management:" then list of items each ending with colon? Actually they are sentences. We need to convert to
- . The content includes multiple bullet-like items separated by line breaks. We'll need to extract each duty.
Let's list them:
Performance Monitoring & Risk Management:
- Monitor a program-level dashboard for tracking key performance indicators (KPIs), milestones, and resource allocation across all projects.
- Implement and manage a program-level risk and dependency management process, identifying and escalating cross-project issues to senior leadership.
- Enforce project management standards and methodologies across the organization.
- Create and manage key project charters and plans to ensure they meet organizational standards for quality, completeness, and strategic fit.
- Conduct regular health checks and audits on key projects to ensure adherence to established standards and identify potential issues before they impact delivery.
- Maintain the IMS baseline and incorporate approved changes and ensure the integrity and accuracy of project data within Jira, leveraging it to generate program-level insights and reports.
- Track vendor deliverables, approvals, and schedule impacts; escalate performance concerns through the Portfolio Oversight chain.
Risk, Issue and Dependency Management:
- Maintain the formal risk register; track and report dependencies and issues; monitor mitigation plans owned by assigned risk owners.
- Manage formal deliverable review, acceptance, and completeness tracking.
Stakeholder Management & Communication:
- Serve as the central point of contact for senior leadership regarding the status and performance of the program.
- Coordinate with stakeholders to keep schedule, scope, and reporting consistent across projects
- Build and maintain strong relationships with senior stakeholders to foster trust, transparency, and effective governance.
Process Improvement & Team Enablement:
- Champion and drive the continuous improvement of project management, tooling, and reporting.
- Stay current on industry best practices and emerging trends, assessing their applicability to the organization to enhance efficiency and effectiveness.
- Other duties as assigned
We'll treat each bullet as
- .
- Qualifications: There's a "Qualifications" heading then bullet list:
Bachelor's degree in a related field (e.g., Computer Science, Business Administration).
7+ years of experience in project and portfolio management, with a strong focus on Agile methodologies.)
DoD Top Secret Clearance is required with the ability to obtain DoD TS/SCI
Proven experience governing multiple complex projects simultaneously.
Expert understanding of project management principles, portfolio management, and governance frameworks.
Experience with Agile frameworks (Scrum, Kanban, etc.) and principles at a portfolio or program level.
DoD Top Secret Clearance is required with the ability to obtain DoD TS/SCI (duplicate)
Probably we need to deduplicate duplicate lines.
Also there is "Preferred Qualifications" heading with list:
Certifications such as PMP, PgMP (Program Management Professional), PfMP (Portfolio Management Professional), or SAFe (Scaled Agile Framework)
Successfully pass background and drug screening
We could combine Qualifications and Preferred Qualifications into a Qualifications section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Qualifications heading; we can include both required and preferred under that, maybe separate subheadings? But we should not create extra headings not in list. Could embed preferred qualifications as part of Qualifications section using
- and maybe note "Preferred". But we must preserve all substantive info. We could include both required and preferred as separate
lists with headings? Not allowed to create extra headings beyond those list. However we could include a preceding the list indicating "Preferred qualifications:" but that's okay as prose. The heading remains Qualifications.
Thus under Qualifications we will have two
maybe: one for Required Qualifications, one for Preferred Qualifications. But we need to avoid extra headings; we can use to label.
- Knowledge, Skills And Abilities: This could map to Skills heading. The content is a list of KSAs. We'll treat as Skills.
- How you’ll grow: This is like professional development; could be considered Benefits? But we have a Benefits section later. The "How you’ll grow" is about professional development; we could include under Benefits? But we have a separate Benefits heading with description. The instruction: include a section ONLY when posting has real specific content. So we have Benefits section with description. We'll include that.
- Benefits: The posting has a Benefits heading with paragraphs about culture, corporate citizenship, news, tips, etc. We need to preserve all substantive info but remove boilerplate like navigation links? The Benefits section includes: "Learn more about what working at Chenega MIOS can mean for you." then paragraphs about culture, corporate citizenship, news, tips, etc. Also includes links. We should keep the descriptive text but maybe drop the links? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The links might be considered navigation? Probably we should drop the URLs as they are navigation. Keep the descriptive sentences.
Thus Benefits section: we will have
containing the descriptive text (maybe multiple
).
- Pay: There's "Estimated Salary/Wage USD $108,800.00/Yr. Up to USD $150,000.00/Yr." We'll create Pay section with that as
.
- Schedule: No schedule info, so omit.
- Requirements: There's no explicit Requirements heading separate from Qualifications; but we could treat Qualifications as Requirements. However we already have Qualifications. The instruction list includes Requirements as possible heading. We could map Qualifications to Requirements? But we have both Qualifications and Skills. The posting includes "Qualifications" and "Knowledge, Skills And Abilities". So we can have Qualifications (required + preferred) and Skills (KSAs). We'll not create Requirements heading unless we have content distinct. We'll skip Requirements.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
... (the about role paragraph)
Responsibilities
- ...
...
Qualifications
Required qualifications:
- ...
...
Preferred qualifications:
- ...
...
Skills
- ...
...
Benefits
...
...
...
Pay
Estimated Salary/Wage USD $108,800.00/Yr. Up to USD $150,000.00/Yr.
We must ensure no duplicated content. Remove duplicate DoD Top Secret line.
Let's extract exact text.
About the role paragraph: We'll copy the paragraph as is, maybe trim extra spaces.
Original: "Are you ready to enhance your skills and build your career in a rapidly evolving business climate? Are you looking for a career where professional development is embedded in your employer’s core culture? If so, Chenega Military, Intelligence & Operations Support (MIOS) could be the place for you! Join our team of professionals who support large-scale government operations by leveraging cutting-edge technology and take your career to the next level! We are seeking a highly experienced and strategic Security Program Oversight Manager to provide governance, track, and monitor the successful delivery of a portfolio of strategic initiatives. This role is responsible for managing the project governance lifecycle for cybersecurity efforts, from initiation through closeout, providing schedule control, formal risk management, and decision-ready reporting in partnership with the Lead Cybersecurity Execution Manager, who directs technical execution. This role Track and report RMF milestones, artifacts, and authorization timelines, and provides transparent accountability through schedule, milestone, and risk reporting. The Security Project Oversight Manager will act as a champion for delivery excellence by establishing and enforcing best practices, guiding project teams, and driving continuous improvement in project management processes."
Note there is a slight grammar issue: "This role Track" should be "This role tracks". We'll keep as is.
Now Responsibilities list items: We need to extract each bullet exactly as in text.
Let's rewrite each:
Performance Monitoring & Risk Management:
- Monitor a program-level dashboard for tracking key performance indicators (KPIs), milestones, and resource allocation across all projects.
- Implement and manage a program-level risk and dependency management process, identifying and escalating cross-project issues to senior leadership.
- Enforce project management standards and methodologies across the organization.
- Create and manage key project charters and plans to ensure they meet organizational standards for quality, completeness, and strategic fit.
- Conduct regular health checks and audits on key projects to ensure adherence to established standards and identify potential issues before they impact delivery.
- Maintain the IMS baseline and incorporate approved changes and ensure the integrity and accuracy of project data within Jira, leveraging it to generate program-level insights and reports.
- Track vendor deliverables, approvals, and schedule impacts; escalate performance concerns through the Portfolio Oversight chain.
Risk, Issue and Dependency Management:
- Maintain the formal risk register; track and report dependencies and issues; monitor mitigation plans owned by assigned risk owners.
- Manage formal deliverable review, acceptance, and completeness tracking.
Stakeholder Management & Communication:
- Serve as the central point of contact for senior leadership regarding the status and performance of the program.
- Coordinate with stakeholders to keep schedule, scope, and reporting consistent across projects
- Build and maintain strong relationships with senior stakeholders to foster trust, transparency, and effective governance.
Process Improvement & Team Enablement:
- Champion and drive the continuous improvement of project management, tooling, and reporting.
- Stay current on industry best practices and emerging trends, assessing their applicability to the organization
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. No invented or summarized away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "How you’ll grow", "Benefits" maybe we have benefits content. There's a Benefits section with description. Also there is "Estimated Salary/Wage". So Pay section. No schedule info. So we may not include Schedule heading. We need to parse the posting. Let's extract sections: - About the role: The initial paragraph after title: "Are you ready to enhance your skills and build your career in a rapidly evolving business climate? Are you looking for a career where professional development is embedded in your employer’s core culture? If so, Chenega Military, Intelligence & Operations Support (MIOS) could be the place for you! Join our team of professionals who support large-scale government operations by leveraging cutting-edge technology and take your career to the next level! We are seeking a highly experienced and strategic Security Program Oversight Manager to provide governance, track, and monitor the successful delivery of a portfolio of strategic initiatives. This role is responsible for managing the project governance lifecycle for cybersecurity efforts, from initiation through closeout, providing schedule control, formal risk management, and decision-ready reporting in partnership with the Lead Cybersecurity Execution Manager, who directs technical execution. This role Track and report RMF milestones, artifacts, and authorization timelines, and provides transparent accountability through schedule, milestone, and risk reporting. The Security Project Oversight Manager will act as a champion for delivery excellence by establishing and enforcing best practices, guiding project teams, and driving continuous improvement in project management processes." We can treat that as About the role. - Responsibilities: There's a "Responsibilities" heading in the posting, then bullet-like paragraphs: "Performance Monitoring & Risk Management:" then list of items each ending with colon? Actually they are sentences. We need to convert to
- . The content includes multiple bullet-like items separated by line breaks. We'll need to extract each duty. Let's list them: Performance Monitoring & Risk Management: - Monitor a program-level dashboard for tracking key performance indicators (KPIs), milestones, and resource allocation across all projects. - Implement and manage a program-level risk and dependency management process, identifying and escalating cross-project issues to senior leadership. - Enforce project management standards and methodologies across the organization. - Create and manage key project charters and plans to ensure they meet organizational standards for quality, completeness, and strategic fit. - Conduct regular health checks and audits on key projects to ensure adherence to established standards and identify potential issues before they impact delivery. - Maintain the IMS baseline and incorporate approved changes and ensure the integrity and accuracy of project data within Jira, leveraging it to generate program-level insights and reports. - Track vendor deliverables, approvals, and schedule impacts; escalate performance concerns through the Portfolio Oversight chain. Risk, Issue and Dependency Management: - Maintain the formal risk register; track and report dependencies and issues; monitor mitigation plans owned by assigned risk owners. - Manage formal deliverable review, acceptance, and completeness tracking. Stakeholder Management & Communication: - Serve as the central point of contact for senior leadership regarding the status and performance of the program. - Coordinate with stakeholders to keep schedule, scope, and reporting consistent across projects - Build and maintain strong relationships with senior stakeholders to foster trust, transparency, and effective governance. Process Improvement & Team Enablement: - Champion and drive the continuous improvement of project management, tooling, and reporting. - Stay current on industry best practices and emerging trends, assessing their applicability to the organization to enhance efficiency and effectiveness. - Other duties as assigned We'll treat each bullet as
- .
- Qualifications: There's a "Qualifications" heading then bullet list:
Bachelor's degree in a related field (e.g., Computer Science, Business Administration).
7+ years of experience in project and portfolio management, with a strong focus on Agile methodologies.)
DoD Top Secret Clearance is required with the ability to obtain DoD TS/SCI
Proven experience governing multiple complex projects simultaneously.
Expert understanding of project management principles, portfolio management, and governance frameworks.
Experience with Agile frameworks (Scrum, Kanban, etc.) and principles at a portfolio or program level.
DoD Top Secret Clearance is required with the ability to obtain DoD TS/SCI (duplicate)
Probably we need to deduplicate duplicate lines.
Also there is "Preferred Qualifications" heading with list:
Certifications such as PMP, PgMP (Program Management Professional), PfMP (Portfolio Management Professional), or SAFe (Scaled Agile Framework)
Successfully pass background and drug screening
We could combine Qualifications and Preferred Qualifications into a Qualifications section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Qualifications heading; we can include both required and preferred under that, maybe separate subheadings? But we should not create extra headings not in list. Could embed preferred qualifications as part of Qualifications section using
- and maybe note "Preferred". But we must preserve all substantive info. We could include both required and preferred as separate
- lists with headings? Not allowed to create extra headings beyond those list. However we could include a
- ... ...
- ... ...
- ... ...
- ... ...
preceding the list indicating "Preferred qualifications:" but that's okay as prose. The heading remains Qualifications. Thus under Qualifications we will have two
- maybe: one for Required Qualifications, one for Preferred Qualifications. But we need to avoid extra headings; we can use
to label. - Knowledge, Skills And Abilities: This could map to Skills heading. The content is a list of KSAs. We'll treat as Skills. - How you’ll grow: This is like professional development; could be considered Benefits? But we have a Benefits section later. The "How you’ll grow" is about professional development; we could include under Benefits? But we have a separate Benefits heading with description. The instruction: include a section ONLY when posting has real specific content. So we have Benefits section with description. We'll include that. - Benefits: The posting has a Benefits heading with paragraphs about culture, corporate citizenship, news, tips, etc. We need to preserve all substantive info but remove boilerplate like navigation links? The Benefits section includes: "Learn more about what working at Chenega MIOS can mean for you." then paragraphs about culture, corporate citizenship, news, tips, etc. Also includes links. We should keep the descriptive text but maybe drop the links? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The links might be considered navigation? Probably we should drop the URLs as they are navigation. Keep the descriptive sentences. Thus Benefits section: we will have
containing the descriptive text (maybe multiple
). - Pay: There's "Estimated Salary/Wage USD $108,800.00/Yr. Up to USD $150,000.00/Yr." We'll create Pay section with that as
. - Schedule: No schedule info, so omit. - Requirements: There's no explicit Requirements heading separate from Qualifications; but we could treat Qualifications as Requirements. However we already have Qualifications. The instruction list includes Requirements as possible heading. We could map Qualifications to Requirements? But we have both Qualifications and Skills. The posting includes "Qualifications" and "Knowledge, Skills And Abilities". So we can have Qualifications (required + preferred) and Skills (KSAs). We'll not create Requirements heading unless we have content distinct. We'll skip Requirements. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:
About the role
... (the about role paragraph)
Responsibilities
Qualifications
Required qualifications:
Preferred qualifications:
Skills
Benefits
...
...
...Pay
Estimated Salary/Wage USD $108,800.00/Yr. Up to USD $150,000.00/Yr.
We must ensure no duplicated content. Remove duplicate DoD Top Secret line. Let's extract exact text. About the role paragraph: We'll copy the paragraph as is, maybe trim extra spaces. Original: "Are you ready to enhance your skills and build your career in a rapidly evolving business climate? Are you looking for a career where professional development is embedded in your employer’s core culture? If so, Chenega Military, Intelligence & Operations Support (MIOS) could be the place for you! Join our team of professionals who support large-scale government operations by leveraging cutting-edge technology and take your career to the next level! We are seeking a highly experienced and strategic Security Program Oversight Manager to provide governance, track, and monitor the successful delivery of a portfolio of strategic initiatives. This role is responsible for managing the project governance lifecycle for cybersecurity efforts, from initiation through closeout, providing schedule control, formal risk management, and decision-ready reporting in partnership with the Lead Cybersecurity Execution Manager, who directs technical execution. This role Track and report RMF milestones, artifacts, and authorization timelines, and provides transparent accountability through schedule, milestone, and risk reporting. The Security Project Oversight Manager will act as a champion for delivery excellence by establishing and enforcing best practices, guiding project teams, and driving continuous improvement in project management processes." Note there is a slight grammar issue: "This role Track" should be "This role tracks". We'll keep as is. Now Responsibilities list items: We need to extract each bullet exactly as in text. Let's rewrite each: Performance Monitoring & Risk Management: - Monitor a program-level dashboard for tracking key performance indicators (KPIs), milestones, and resource allocation across all projects. - Implement and manage a program-level risk and dependency management process, identifying and escalating cross-project issues to senior leadership. - Enforce project management standards and methodologies across the organization. - Create and manage key project charters and plans to ensure they meet organizational standards for quality, completeness, and strategic fit. - Conduct regular health checks and audits on key projects to ensure adherence to established standards and identify potential issues before they impact delivery. - Maintain the IMS baseline and incorporate approved changes and ensure the integrity and accuracy of project data within Jira, leveraging it to generate program-level insights and reports. - Track vendor deliverables, approvals, and schedule impacts; escalate performance concerns through the Portfolio Oversight chain. Risk, Issue and Dependency Management: - Maintain the formal risk register; track and report dependencies and issues; monitor mitigation plans owned by assigned risk owners. - Manage formal deliverable review, acceptance, and completeness tracking. Stakeholder Management & Communication: - Serve as the central point of contact for senior leadership regarding the status and performance of the program. - Coordinate with stakeholders to keep schedule, scope, and reporting consistent across projects - Build and maintain strong relationships with senior stakeholders to foster trust, transparency, and effective governance. Process Improvement & Team Enablement: - Champion and drive the continuous improvement of project management, tooling, and reporting. - Stay current on industry best practices and emerging trends, assessing their applicability to the organization
- and maybe note "Preferred". But we must preserve all substantive info. We could include both required and preferred as separate