IT Program Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (About the role) and responsibilities, qualifications (required and desired). Also target salary range. No explicit benefits or schedule beyond "Full-Time Shift Day". Schedule: Full-Time Shift Day is given. Should we include Schedule section? The posting says Schedule Full-Time Shift Day. That's specific content. So include Schedule section with that info. Benefits: none mentioned. So omit Benefits. Pay: target salary range given. So include Pay section with that range. Skills: maybe we can extract from qualifications? But we have Qualifications section already; Skills could be separate but we might combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have About the role (description). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (maybe desired?). Could combine required and desired under Qualifications. But we have both Required Qualifications and Desired Qualifications. Could put them under Qualifications with subheadings? But we must only use

for section headings, not subheadings. Could we include both Required and Desired as separate sections? The list includes Requirements and Qualifications as separate possible headings. We could treat Requirements as required qualifications, and Qualifications as desired qualifications. Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine required and desired into Qualifications section. But we also have Skills heading; we could put leadership & soft skills there. However the posting includes "Leadership & Soft Skills" under Desired Qualifications. Could treat that as Skills section. Let's think. We need to preserve all substantive information. We can structure:

About the role

...

Responsibilities

• ... each responsibility

Qualifications

maybe split into Required and Desired? Could use

for prose but we need to preserve details. Could do

Required Qualifications

and

Desired Qualifications

but those are not in the allowed list? The allowed list includes Requirements and Qualifications. Could use Requirements for required, Qualifications for desired. That seems okay. Thus:

Requirements

• ... required qualifications list

Qualifications

• ... desired qualifications list
Requirements (required qualifications)

Qualifications

(desired qualifications excluding leadership & soft skills? but we could include them there)

Skills

(leadership & soft skills) But that splits desired qualifications into two sections, which may be thin. However leadership & soft skills is a substantive set of bullet points. Could be its own section. Alternatively, we could combine desired qualifications and leadership & soft skills under Qualifications, and not have Skills section. The instruction says prefer few substantive sections over many thin ones. So better to combine. Thus we will have: - About the role - Responsibilities - Requirements (required qualifications) - Qualifications (desired qualifications + leadership & soft skills) - Pay (salary range) - Schedule (Full-Time Shift Day) We must not include Benefits as none. Now we need to format lists: each duty/requirement/benefit as
• . For prose, use

  . We need to preserve all substantive information, not invent or summarize away detail. So we must include each bullet point exactly as given, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the content, but we can format as list items. It's okay to keep the same wording. We need to extract the responsibilities list from the "Key Responsibilities" section. It has subheadings: Program Leadership & Management, Technical Integration & Delivery, Agile Program Execution, Customer & Stakeholder Engagement, Risk, Financial, and Contract Management. Each has multiple sentences. We need to turn each duty into list items. Should we keep the subheadings as list items? Probably each sentence becomes a list item. We'll need to capture all responsibilities. Let's list them: Program Leadership & Management: - Provide overall leadership, direction, and accountability for a large IT program including software engineering, platform integration, cybersecurity, and operations. - Lead and mentor a team of ~70 personnel, including systems administrators, network administrators, Tier 2 Help Desk, C2, core applications, and test/validation teams. - Establish and maintain program vision, objectives, and performance metrics aligned with customer requirements and contract commitments. - Develop and manage program plans, schedules, staffing plans, and resource allocations to meet demanding integration and deployment timelines. - Ensure effective coordination and collaboration across multiple functional teams, subcontractors, and stakeholders. Technical Integration & Delivery: - Oversee integration, testing, and deployment of COTS/GOTS applications and systems into U.S. Government on‑premise and cloud environments. - Manage technical baselines and configuration control for systems deployed across 26 global instances. - Ensure solutions meet performance, security, interoperability, and sustainment requirements within Air Force operational environments, particularly Air Operations Centers (AOCs). - Champion best practices in systems engineering, cybersecurity, IT service management, and continuous integration/continuous delivery (CI/CD) where applicable. Agile Program Execution: - Implement and refine Agile methodologies at the program level (e.g., Scrum, Kanban, SAFe-like constructs) to support iterative development and integration. - Coordinate Agile ceremonies across multiple teams (PI planning, sprint planning, reviews, retrospectives) to ensure alignment with program-level objectives and milestones. - Monitor Agile metrics (velocity, throughput, defect trends) and adjust plans and priorities based on data-driven insights. Customer & Stakeholder Engagement: - Serve as the primary interface with Air Force program overseers and other Government stakeholders. - Represent the program in technical and programmatic reviews, readiness assessments, working groups, and governance forums. - Communicate program status, risks, issues, and mitigation strategies clearly and effectively to senior Government and corporate leadership. - Build and maintain strong relationships with customer counterparts, ensuring high levels of satisfaction and trust. Risk, Financial, and Contract Management: - Identify, assess, and manage program risks, issues, and dependencies; develop and execute mitigation plans. - Oversee program budget, forecasts, and financial performance, ensuring delivery within cost and schedule constraints. - Ensure compliance with contract requirements, SLAs, and performance standards; support contract modifications and proposals as needed. - Maintain adherence to quality standards, cybersecurity policies, and relevant DoD and Air Force regulations. Now Required Qualifications list: - Bachelor’s degree in Program Management, Information Technology, Computer Science, Engineering, Systems Management, or related discipline. - PMP (Project Management Professional); Security+ (or equivalent DoD 8570/8140 baseline certification); CSM (Certified ScrumMaster) or equivalent Agile certification; Other industry certifications in IT, Cloud, etc. - 10–15 years of progressively responsible IT program or project management experience. - Demonstrated experience managing large, complex IT programs involving software engineering, platform integration, and cybersecurity. - Proven experience leading multi‑disciplinary technical teams (50+ personnel) in a DoD, Federal, or similarly complex environment. - Experience overseeing operations teams including systems and network administration, Tier 2 Help Desk, and application support. - Hands-on experience delivering integrated COTS/GOTS solutions into secure on‑premise and cloud environments. - Demonstrated success managing demanding technical integration and deployment schedules across multiple sites or global instances. - Experience working directly with Government program offices or similar oversight organizations. - Practical experience leading programs using Agile methodologies (Scrum, Kanban, or scaled Agile frameworks) in a multi-team environment. Desired Qualifications list (excluding leadership & soft skills? We'll include them later maybe): - Master’s degree in Information Systems, Engineering, Business, Management, or related field. - Experience supporting U.S. Air Force programs, with a strong preference for Air Operations Centers (AOCs) or similar C2 environments. - Understanding of Air Force systems sustainment processes, including lifecycle management, configuration management, and sustainment planning. - Familiarity with DoD cyber and accreditation processes (e.g., RMF, ATO/ATO with conditions) and secure system deployment. - Experience managing or integrating C2 systems and core mission applications in operational environments. - Knowledge of ITIL/IT service management practices supporting Tier 2/3 operations and global enterprise environments. - Leadership & Soft Skills - Strong leadership, team-building, and mentoring skills with the ability to inspire and guide a diverse technical workforce. - Excellent communication skills, capable of presenting complex technical and programmatic information to senior leadership and non-technical stakeholders. - Proven ability to operate effectively in high-tempo, mission-critical environments with competing priorities and evolving requirements. - Strong negotiation, conflict resolution, and stakeholder management skills. We could keep Leadership & Soft Skills as a subsection under Qualifications, but we need to use only

  headings. Could we embed a

  ? Not allowed. So we could either keep them as list items under Qualifications, with the phrase "Leadership & Soft Skills" as a list item? That would be weird. Better to have a separate Skills section for those bullet points. That would be a substantive section. Thus we will have: - About the role - Responsibilities - Requirements (required qualifications) - Qualifications (desired qualifications excluding leadership & soft skills) - Skills (leadership & soft skills) - Pay - Schedule That's 7 sections, each substantive. Now we need to ensure we don't include any boilerplate like Job ID, Location, Date Posted, Category, Subcategory, Shift, Travel, Clearance, Potential for Remote Work, ORA_ON_SITE, etc. Those are minor metadata; we should fold them into a short

  or drop them. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short paragraph at the top with location, date posted, etc. But we could also drop them. The instruction says "fold minor metadata into a short