Senior Program Manager

We need to output HTML fragment with sections: About the role (maybe from first paragraph?), Responsibilities (list of duties), Requirements (list of qualifications), Benefits (if present), Pay (if present), Schedule (if present). Also maybe Skills? The posting includes "What We Expect Of You" which is requirements. Also "What You Will Do" is responsibilities. Also "About Us" is company description but not needed? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: - About the role: The first paragraph describing role: "The Senior Program Manager leads the planning, coordination, and execution of complex programs in support of Marine Corps Installations Command (MCICOM), including Military Construction (MILCON) and Installation Communication Grid (ICG) initiatives. This role is responsible for managing the full lifecycle of infrastructure and telecommunications programs, ensuring alignment with mission requirements, technical standards, and program objectives. The Senior Program Manager serves as a key interface with senior stakeholders while driving cross-functional collaboration to successfully deliver large-scale programs." We can put that as

  About the role

  ...

  - Responsibilities: The bullet list under "What You Will Do". It's a long list of sentences, each starting with a verb. We need to put them as
  • each item. Should we split each sentence? Likely each line is a duty. The text includes many sentences separated by line breaks? In the provided posting, after "What You Will Do" there is a paragraph with many sentences separated by spaces. We need to parse them into list items. We'll split by sentences that start with a capital verb? Let's manually list: 1. Manage MILCON and ICG programs from initiation through planning, execution, and closeout, ensuring alignment with mission requirements and Marine Corps standards 2. Lead program planning and execution activities across multiple initiatives supporting MCICOM 3. Oversee scheduling and milestone management, including development and maintenance of Integrated Master Schedules (IMS) 4. Provide schedule oversight to ensure alignment of project milestones, deliverables, and critical path activities 5. Coordinate planning across engineering, logistics, financial, and operational teams 6. Manage cross-program resource allocation to optimize personnel, funding, and materials 7. Identify program risks and support development of mitigation strategies and risk management plans 8. Oversee program performance tracking, including metrics development, analysis, and reporting 9. Partner with engineering teams and SMEs to ensure technical alignment and successful delivery 10. Lead stakeholder engagement with Marine Corps leadership, installation personnel, and external partners 11. Support change management activities impacting program execution 12. Oversee project validation and prioritization to align initiatives with mission and strategic objectives 13. Coordinate requirements development and ensure alignment with operational and infrastructure needs 14. Support issue resolution to maintain timelines and ensure successful execution 15. Develop program roadmaps, including long-range planning and capability development 16. Provide milestone and deliverable forecasting to support leadership decision-making 17. Conduct or support risk assessments and integrate findings into program planning 18. Support resource planning and cross-functional coordination across all program elements 19. Assist in development of Concepts of Operations (CONOPS) and future system requirements 20. Provide input into long-term budgeting and outyear planning efforts 21. Ensure effective stakeholder coordination across all supported installations We'll output each as
  • . - Requirements/Qualifications: The "What We Expect Of You" section includes many bullet-like sentences. We'll treat as requirements. Also there are "plus" items. We'll include all as list items. Let's extract: - Bachelor’s degree in Engineering, Business Administration, Program Management, or a related field and Minimum of 15 years of experience in program or project management supporting federal or defense programs OR 10 years with a Project Management Professional (PMP) certification - Demonstrated experience managing MILCON and/or ICG programs with end-to-end lifecycle ownership - Extensive experience with scheduling, milestone tracking, and Integrated Master Schedule (IMS) oversight - Strong background in risk management, resource allocation, and performance tracking - Experience coordinating across engineering, logistics, financial, and operational teams - Familiarity with Department of Defense processes and infrastructure program management - Experience engaging with senior-level stakeholders in a federal or defense environment - Proven ability to manage competing priorities across multiple complex programs - Strong leadership, organizational, and decision-making capabilities - Excellent written and verbal communication skills, including executive-level briefings - Active Secret clearance required - Must be a U.S. Citizen - Project Management Professional (PMP) certification is a plus - Master’s degree in Program Management, Business Administration, Engineering, or related field is a plus - Experience supporting Marine Corps Installations Command (MCICOM) is a plus - Strong familiarity with Installation Communication Grid (ICG) architecture and telecommunications infrastructure programs is a plus - Experience supporting MILCON programs, including DD Form 1391 development and infrastructure modernization initiatives is a plus - Knowledge of Planning, Programming, Budgeting, and Execution (PPB&E) processes is a plus - Experience developing program roadmaps, CONOPS, and long-term capability strategies is a plus - Experience working with NAVFAC, USACE, DISA, or other Department of Defense stakeholders is a plus We could separate into Requirements and Qualifications but instructions allow using either. We'll just have a section "Requirements" (or "Qualifications") containing all. Since they said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll choose "Requirements" for the mandatory items and maybe "Qualifications" for plus items? But they said prefer few substantive sections over many thin ones. Could combine all into one Requirements section. However they also have "Skills" maybe we could separate skills but not needed. We'll just have one section "Requirements" containing all items (both mandatory and plus). That's okay. - Pay: The posting includes "Pay range: $180,000 – $240,000 depending on experience and skill set." Also "Salary ranges may be subject to geographic differentials." That's pay info. So we need a Pay section with that info. According to rules, we should include Pay section only if posting actually states them. Yes. We'll output

    Pay

    Pay range: $180,000 – $240,000 depending on experience and skill set. Salary ranges may be subject to geographic differentials.

    - Benefits: The posting includes "Benefits overview: CDW Benefits". That's vague. It says "Benefits overview: CDW Benefits". No specifics. That's not substantive detail; it's just a placeholder. According to rule: 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. The benefits overview is just "CDW Benefits" with no detail. That's likely filler. So we should NOT create a Benefits section. - Schedule: Not mentioned. So no Schedule section. - About Us: Not required; we can omit as it's company description not required. The instructions say to remove boilerplate, duplicated lines, application instructions. About Us is not required but could be considered boilerplate? It's not EEO but it's company description. The instruction says to include sections only when posting has real, specific content for it. The "About Us" is not a standard heading list but we could include as a paragraph if we want to preserve substantive info? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Us paragraph as prose, maybe under a heading? But they didn't list About Us as a heading option. They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. We could include the About Us content as a

    without a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. Probably we should not include About Us as a separate heading; we could just include it as a

    after the sections? But they said output ONLY the HTML fragment. It didn't say we must include all content; we must preserve ALL substantive information. So we need to include the About Us paragraph somewhere. Could we put it under a generic

    without heading? That seems acceptable. The instruction about headings is for section headings; we can have prose paragraphs outside headings. So we will output:

    About the role

    ...

    Responsibilities

    ...

    Requirements

    ...

    Pay

    ...

    About Us paragraph...

    We must also include the "About Us" paragraph exactly as given (maybe trimmed). Let's copy: "About Us CDW is a Fortune 500 technology solutions provider that helps businesses, government, education, and healthcare organizations achieve what’s possible through technology. What makes CDW different isn’t just what we do—it’s how we do it. At CDW we act as one—building trust, speaking candidly, and working together to achieve more. We play to win—focusing on what matters most and delivering for our customers. And we think forward—staying curious, moving fast, and continuously learning. We believe meaningful work happens when people feel supported, heard, and empowered to contribute. That’s why we think of ourselves as coworkers, not just employees—working together to solve complex challenges and deliver real impact for our customers and communities. As a full‑stack, full‑lifecycle technology partner, CDW brings deep expertise, strong relationships, and broad industry knowledge to help turn ideas into outcomes. When you join CDW, you become part of a collaborative environment where your work matters, your growth is supported, and your contributions help shape what’s next. Together, we deliver the full promise of what technology can do. Together, we Make Amazing Happen." We should preserve that exactly. Also there is EEO statement at end: "CDW is an equal opportunity employer...". That's boilerplate to remove per instructions: remove EEO/equal-opportunity/scam-warning boilerplate. So we drop that. Also there is lines about "CDW Benefits Salary ranges may be subject to geographic differentials." Actually that's part of benefits overview line: "Benefits overview: CDW Benefits Salary ranges may be subject to geographic differentials." We already used the salary range in Pay section; the "Benefits overview: CDW Benefits" is filler; we drop. Also there is lines about AI-fluent organization etc. That