Contract Project Manager
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes description, responsibilities, requirements, qualifications, schedule, location, availability, clearance, security requirement, certification, experience. Also benefits? Not mentioned. Pay? Not mentioned. So we should not include Pay or Benefits sections. Schedule is present: "Full-time, generally Monday-Friday, 8:00 AM-5:00 PM ET". Also availability: "Must be available to the COR by telephone between 8:00 AM and 5:00 PM ET, Monday-Friday, and respond to requests for discussion or problem resolution within 3 hours". That could be part of schedule or separate? Probably schedule section includes both. We'll include Schedule section with that info. Location: "Arlington, VA / Hybrid - on-site at CISA facilities as needed; telework the remainder of the time". Could be part of About the role or separate? Not a heading. We'll embed in About the role paragraph. We need to avoid repeating job title as heading. So no heading for job title. We need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine with Qualifications?), Qualifications (maybe separate), Skills (maybe list of skills). The posting has "What You'll Do" which is responsibilities. Then "Required WHAT YOU BRING" which is requirements/qualifications. Then "Preferred" which is preferred qualifications. Could treat Requirements as required qualifications, and Preferred as separate maybe under Qualifications? But we have headings: Requirements, Qualifications, Skills. We need to decide mapping. We could have: - About the role: description paragraph. - Responsibilities: list from "What You'll Do". - Requirements: list of required experience (10+ years, etc.) maybe bullet list. - Qualifications: list of preferred qualifications? Or we could combine required and preferred under Requirements and Qualifications respectively. - Skills: maybe list of skills like executive presence, communication, judgment, facilitation, etc. Could be extracted from required section. But we must not create sections with filler. Ensure each section has substantive content. Let's extract content. About the role: The first paragraph(s) describing the role: "Blue Sky Innovative Solutions LLC is seeking an experienced Contract Project Manager to support a high-visibility organizational transformation initiative for the Department of Homeland Security (Client) Cybersecurity and Infrastructure Security Agency (CISA). The program will help CISA strengthen how it operates in its role as the National Coordinator for the Security and Resilience of U.S. Critical Infrastructure, assess its current operating model, implement approved transformation priorities, and sustain effective execution across the effort. This is a senior, hands-on leadership role combining program management with deep subject-matter leadership in organizational transformation. The Contract Project Manager will lead the Operational Assessment and Implementation workstreams, guide the team's analytical and transformation methods, shape recommendations, and ensure findings move effectively into implementation. The successful candidate must be able to engage senior Government leaders as a trusted advisor, direct experienced consultants and analysts, challenge weak analysis, connect findings across the enterprise, and maintain disciplined control of performance, schedule, staffing, quality, risks, dependencies, deliverables, and Government communications." We can put that in
. Location and schedule maybe separate but schedule section will contain schedule and availability. Responsibilities: list from "What You'll Do" bullet points. Let's extract each bullet: - Lead the Operational Assessment and Implementation workstreams, providing both subject-matter direction and program leadership across the transformation effort. - Direct the team's approach to current-state assessment, organizational and operational analysis, stakeholder engagement, synthesis, future-state operating-model design, prioritization, and implementation planning. - Guide development of findings and recommendations related to organizational roles and interfaces, governance, decision rights, authorities, cross-functional processes, information flows, culture, performance drivers, dependencies, and measures of effectiveness. - Lead senior-level working sessions, reviews, and decision discussions with CISA leaders, Government Task Leads, Federal sponsors, subject-matter experts, and other stakeholders. - Review and challenge analytical work to ensure conclusions are evidence-based, enterprise-aware, practical, and sufficiently developed to support Government decisions. - Translate assessment findings into actionable transformation priorities, implementation activities, work packages, governance mechanisms, and measurable outcomes. - Ensure assessment and implementation remain tightly connected so mature findings can move into action while additional analysis continues. - Serve as the primary program management point of contact for the CISA Contracting Officer and Contracting Officer's Representative (COR). - Lead program planning and control for technical performance, schedule, staffing, quality, risk, cost awareness, deliverables, and Government communications. - Establish and maintain the Program Management Plan, Integrated Master Schedule, management rhythms, status reporting, risk and issue controls, decision tracking, and other mechanisms needed to maintain visibility and accountability. - Track contractual commitments and deliverables, anticipate schedule or performance risk, and drive timely corrective action before issues affect Government outcomes. - Maintain clear visibility into cross-task dependencies, decisions, and implementation barriers and elevate matters requiring Government action at the appropriate time. - Lead kickoff, progress reviews, status meetings, and other program forums; ensure agendas, decisions, actions, owners, and follow-up are clear and timely. - Provide concise, decision-ready reporting on progress, planned work, staffing, risks, issues, mitigation actions, dependencies, and matters requiring Government attention. - Manage staffing continuity, workforce readiness, resource allocation, and performance across the team; engage Blue Sky corporate resources when recruiting, security, HR, contracts, finance, or quality support is needed. - Ensure work products receive appropriate technical and quality review and that deliverables are accurate, internally consistent, timely, and responsive to CISA priorities. - Build an integrated team culture in which analysts and implementation personnel share evidence, test conclusions, surface dependencies, and maintain accountability for results. That's a lot; we can keep as
- .
Requirements: from "Required WHAT YOU BRING" bullet list.
Let's extract each bullet:
- 10+ years of progressively responsible experience leading Federal programs, management consulting engagements, organizational transformation initiatives, or comparable complex mission work.
- Substantial hands-on experience in organizational transformation, operating-model design, business process reengineering, organizational design, governance, or closely related transformation disciplines.
- Demonstrated ability to lead both the substantive work and the delivery of a complex consulting or transformation engagement, including directing analysis, shaping recommendations, and guiding implementation.
- Experience conducting or leading current-state assessments and developing future-state recommendations for complex organizations, operating models, or cross-functional processes.
- Demonstrated experience serving as the primary client-facing program or engagement leader for a Federal contract, task order, or major Federal initiative.
- Experience leading multidisciplinary teams and integrating work across multiple functional areas, stakeholders, workstreams, or organizational boundaries.
- Ability to evaluate the quality of analytical work, identify unsupported conclusions or gaps, and coach teams toward stronger, evidence-based recommendations.
- Experience facilitating senior-level discussions involving competing priorities, organizational sensitivities, ambiguous requirements, or significant operational change.
- Demonstrated responsibility for program performance, schedules, staffing, deliverables, risks, quality, customer relationships, and issue resolution.
- Experience developing and using program management plans, integrated schedules, status reporting, action tracking, risk/issue management, and performance controls.
- Strong executive presence and the ability to communicate credibly and concisely with senior Government leaders, Contracting Officers, CORs, and experienced subject-matter experts.
- Excellent judgment and the ability to distinguish issues the team should resolve independently from matters requiring Government decision or escalation.
- Proactive leadership style with strong ownership, accountability, and follow-through; able to anticipate problems and act before they become performance issues.
- Ability to lead effectively in an ambiguous, rapidly evolving environment where priorities, stakeholder needs, and implementation sequencing may change.
- Strong facilitation, negotiation, and conflict-resolution skills and the ability to build alignment across stakeholders with different priorities or perspectives.
- Excellent written communication skills and the ability to produce and review concise, executive-ready analyses, recommendations, program information, and decision-support materials.
- Ability to work on-site in Arlington, Virginia, as required and successfully complete Client personnel security and fitness processing.
We can put these as
- under Requirements.
Qualifications: maybe we can list certifications and preferred? The posting includes "Certification: PMP strongly preferred; other relevant organizational transformation, business process, change management, or Agile credentials are a plus". Also "Preferred" section list.
We could treat Qualifications as the certification and preferred qualifications. But we already used Requirements for required experience. Qualifications could include certification and preferred items.
Let's extract Preferred bullet list:
- Direct experience supporting CISA, Client, or another national security or critical-infrastructure mission organization.
- Experience leading enterprise organizational transformation involving operating-model design, business process reengineering, organizational design, governance, culture, or transformation implementation.
- Experience supporting Sector Risk Management Agency, critical-infrastructure, cybersecurity, resilience, or cross-agency coordination missions.
- Experience translating statutory authorities, policy, strategy, or mission responsibilities into organizational roles, governance, processes, decision rights, and operating practices.
- Experience managing complex Federal portfolios or transformation efforts with multiple concurrent deliverables, senior stakeholders, and cross-organizational dependencies.
- Experience managing Firm-Fixed-Price Federal service contracts and balancing performance, staffing, schedule, quality, and cost considerations.
- Project Management Professional (PMP) certification.
- Relevant business process management, organizational development, change management, Lean Six Sigma, Certified ScrumMaster, or comparable credential.
- Recent favorable Client Fitness Determination.
We could put these under Qualifications.
Skills: maybe we could extract some skill-based items like executive presence, communication, judgment, facilitation, negotiation, conflict-resolution, written communication, etc. But those are already in Requirements. To avoid duplication, we could omit Skills section or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Qualifications. That's four sections. Schedule we could embed in About the role or maybe separate Schedule section. Since schedule is specific, we could add Schedule section.
But we must not create sections with filler. Schedule has concrete info: "Full-time, generally Monday-Friday, 8:00 AM-5:00 PM ET Availability: Must be available to the COR by telephone between 8:00 AM and 5:00 PM ET, Monday-Friday, and respond to requests for discussion or problem resolution within 3 hours". That's substantive.
Thus we can have Schedule section.
Location maybe we can include in About the role paragraph.
Clearance and Security Requirement: "No active security clearance required Security Requirement: Must be able to obtain and maintain the required Client Fitness Determination and access authorization; a recent favorable Client Fitness Determination is preferred". This is also substantive; could be part of Requirements or Qualifications. But we already have Requirements and Qualifications; maybe we add a Clearance section? But we have no heading for Clearance in allowed list; only allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit clearance into one of those. Probably Requirements or Qualifications. Since it's about clearance, maybe under Requirements (as a requirement). We'll add a bullet under Requirements: "No active security clearance required; must be able to obtain and maintain the required Client Fitness Determination and access authorization; a recent favorable Client Fitness Determination is preferred."
Now Benefits and Pay not present, so we omit those sections.
Skills section maybe we could include some skill items not covered elsewhere, but we already have many skill-like items in Requirements. To avoid thin section, we could omit Skills.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Now produce HTML fragment: use
for each heading, then content:
for prose,
- for lists.
We need to ensure we don't repeat job title as heading. No heading for job title.
We'll output:
About the role
... (including location)
Res
- for lists.
We need to ensure we don't repeat job title as heading. No heading for job title.
We'll output:
- under Requirements.
Qualifications: maybe we can list certifications and preferred? The posting includes "Certification: PMP strongly preferred; other relevant organizational transformation, business process, change management, or Agile credentials are a plus". Also "Preferred" section list.
We could treat Qualifications as the certification and preferred qualifications. But we already used Requirements for required experience. Qualifications could include certification and preferred items.
Let's extract Preferred bullet list:
- Direct experience supporting CISA, Client, or another national security or critical-infrastructure mission organization.
- Experience leading enterprise organizational transformation involving operating-model design, business process reengineering, organizational design, governance, culture, or transformation implementation.
- Experience supporting Sector Risk Management Agency, critical-infrastructure, cybersecurity, resilience, or cross-agency coordination missions.
- Experience translating statutory authorities, policy, strategy, or mission responsibilities into organizational roles, governance, processes, decision rights, and operating practices.
- Experience managing complex Federal portfolios or transformation efforts with multiple concurrent deliverables, senior stakeholders, and cross-organizational dependencies.
- Experience managing Firm-Fixed-Price Federal service contracts and balancing performance, staffing, schedule, quality, and cost considerations.
- Project Management Professional (PMP) certification.
- Relevant business process management, organizational development, change management, Lean Six Sigma, Certified ScrumMaster, or comparable credential.
- Recent favorable Client Fitness Determination.
We could put these under Qualifications.
Skills: maybe we could extract some skill-based items like executive presence, communication, judgment, facilitation, negotiation, conflict-resolution, written communication, etc. But those are already in Requirements. To avoid duplication, we could omit Skills section or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Qualifications. That's four sections. Schedule we could embed in About the role or maybe separate Schedule section. Since schedule is specific, we could add Schedule section.
But we must not create sections with filler. Schedule has concrete info: "Full-time, generally Monday-Friday, 8:00 AM-5:00 PM ET Availability: Must be available to the COR by telephone between 8:00 AM and 5:00 PM ET, Monday-Friday, and respond to requests for discussion or problem resolution within 3 hours". That's substantive.
Thus we can have Schedule section.
Location maybe we can include in About the role paragraph.
Clearance and Security Requirement: "No active security clearance required Security Requirement: Must be able to obtain and maintain the required Client Fitness Determination and access authorization; a recent favorable Client Fitness Determination is preferred". This is also substantive; could be part of Requirements or Qualifications. But we already have Requirements and Qualifications; maybe we add a Clearance section? But we have no heading for Clearance in allowed list; only allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit clearance into one of those. Probably Requirements or Qualifications. Since it's about clearance, maybe under Requirements (as a requirement). We'll add a bullet under Requirements: "No active security clearance required; must be able to obtain and maintain the required Client Fitness Determination and access authorization; a recent favorable Client Fitness Determination is preferred."
Now Benefits and Pay not present, so we omit those sections.
Skills section maybe we could include some skill items not covered elsewhere, but we already have many skill-like items in Requirements. To avoid thin section, we could omit Skills.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Now produce HTML fragment: use