MCICOM Facilities Program Director

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have content: description about role (first paragraphs). Could map to "About the role". Then responsibilities list (Key Responsibilities). Then basic qualifications (maybe Requirements). Preferred qualifications maybe Qualifications? Skills maybe? Benefits present. Pay: salary range given. Schedule: not mentioned (Hybrid but location: Arlington, VA-Hybrid (Must be DMV Local). That's schedule? It's location/hybrid, not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive info, not invent. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to remove boilerplate: EEO, application instructions, etc. Also remove "Why CTC?" maybe considered boilerplate? It's promotional but maybe keep? It's not required but could be considered filler. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why CTC?" is promotional but not boilerplate; but could be considered fluff. Safer to keep? It's not required but we can keep as prose under maybe "About the role"? Might be considered filler. I'd keep it as part of About the role? But we need to preserve all substantive information; promotional content maybe not substantive but it's still part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. "Why CTC?" seems like marketing but not boilerplate. I'd keep it as a paragraph under About the role or separate section? There's no heading for it; we could incorporate into About the role. Also need to include Pay section: salary range. Also Benefits: list. Also maybe Skills: not explicitly listed; there is proficiency with Microsoft tools etc under Basic Qualifications. Could treat as Skills section? But we have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to Requirements, Preferred to Qualifications, Skills maybe from proficiency with Microsoft tools etc. However we must not create sections without real specific content. We have content for Requirements (basic qualifications). We have content for Qualifications (preferred). We have content for Skills? Could extract proficiency with Microsoft tools etc as skills. But they are already in Basic Qualifications. Might be redundant. Better to have Requirements (basic qualifications) and Qualifications (preferred). Skills maybe not needed. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have content for each: - About the role: description paragraphs about CTC, ERS Division, role purpose. Yes. - Responsibilities: Key Responsibilities list (many bullet-like sentences). We'll put as

  • . - Requirements: Basic Qualifications list (bullet). We'll put as
    • . - Qualifications: Preferred Qualifications list (bullet). We'll put as
      • . - Benefits: list. - Pay: salary range. We must not include Schedule. Now format: Use

        for each section heading. Then content. We must not include /. Just fragment. We need to ensure we don't duplicate lines. Let's extract text. About the role: combine first paragraphs up to "The ERS Division is seeking a qualified and proactive Program Director to provide strategic program leadership and enterprise-level oversight for Marine Corps Installations Command (MCICOM) Facilities Program." plus maybe following sentence about successful candidate will lead... Actually that is part of responsibilities? It says "The successful candidate will lead a multidisciplinary team providing strategic oversight of enterprise-level project management..." That seems like responsibilities. So About the role could be up to that sentence? But we can include that as part of About the role? Might be better to keep responsibilities separate. Let's parse: Paragraphs: "Concurrent Technologies Corporation Location: Arlington, VA-Hybrid (Must be DMV Local) Minimum Clearance Required: Secret Clearance Level Must Be Able to Obtain: Secret As a trusted partner and leader in providing energy and sustainability consulting services to the federal government, Concurrent Technologies Corporation (CTC) understands the increasing complexity of achieving energy security and climate resilience in a changing world. As part of the Energy, Resilience and Sustainability (ERS) Division, you will collaborate with experts to provide comprehensive policy, planning, and implementation services that deliver solutions addressing critical infrastructure resilience and security issues while supporting the military mission and reducing environmental impacts. We take our role seriously, as our efforts ensure our installations and assets are prepared for any operating environment, present and future. The ERS Division is seeking a qualified and proactive Program Director to provide strategic program leadership and enterprise-level oversight for Marine Corps Installations Command (MCICOM) Facilities Program. The successful candidate will lead a multidisciplinary team providing strategic oversight of enterprise-level project management, Integrated Master Schedule governance, capital investment tracking, engineering reviews, geospatial and property data integration, environmental/cultural resource technical support, installation-level coordination, and reporting across a global portfolio of MILCON, Unspecified Minor Military Construction, Facilities Sustainment, Restoration, and Modernization (FSRM), and demolition projects." That seems like a mix of role description and responsibilities. But we have a separate "Key Responsibilities" heading later. So we can treat the first part up to "The ERS Division is seeking a qualified and proactive Program Director to provide strategic program leadership and enterprise-level oversight for Marine Corps Installations Command (MCICOM) Facilities Program." as About the role. Then the sentence starting "The successful candidate will lead..." could be considered part of responsibilities but it's also a summary. However the Key Responsibilities list starts after that. To avoid duplication, we could include that sentence in About the role as it's describing the role. But then Responsibilities list will start with "Serve as the primary contractor interface..." etc. That's fine. Thus About the role: include paragraphs up to that point. Now Responsibilities: list each item after "Key Responsibilities". They are separated by periods but each starts with a verb. We'll make each as

        . List: - Serve as the primary contractor interface with the Government Contracting Officer's Representative (COR). - Provide strategic direction, establishes priorities, and ensures work products align with Marine Corps operational, installation, and Force Design goals. - Direct all programmatic, technical, engineering, and analytical support across HQ MCICOM and regional commands. - Oversee lifecycle management of contract deliverables and CDRLs, ensuring timely, accurate, and compliant submissions. - Lead development, maintenance, and quality control of the enterprise Integrated Master Schedule (IMS). - Supervise teams delivering on-site project reconnaissance, stakeholder coordination, facility assessments, schedule/cost tracking, and status reporting across multiple worldwide bases. - Guide development of financial metrics, execution reports, dashboards, and POM/IGCE support materials. - Manage enterprise engineering analysis for MILCON, FSRM, utilities, system planning, and constructability validation. - Oversee environmental risk assessments, permit package development, NEPA support, and regulatory compliance documentation. - Oversee GIS and iNFADS data reconciliation efforts to ensure authoritative alignment between spatial, real property, and infrastructure records. - Oversee enterprise and regional master planning support, including review and validation of Basic Facility Requirements (BFRs) and installation layout studies. - Oversee production of executive‑level briefing materials, decision packages, analytic reports, performance summaries, and policy drafts for senior Marine Corps leadership. - Direct development and maintenance of automated reporting solutions and dashboards that integrate financial, execution, and facilities data for senior leadership. Now Requirements (Basic Qualifications): - Bachelor’s degree in Engineering, Architecture, Construction Management, Program Management, Business, or related field. - Minimum 12 years of progressive experience in program/project management for large‑scale federal infrastructure, MILCON, FSRM, or similar engineering portfolios. - Experience leading large (40+) multi-disciplinary technical teams supporting federal agencies or DoD organizations. - Demonstrated expertise managing enterprise Integrated Master Schedules and large, multi-region infrastructure programs. - Strong analytical skills with experience evaluating complex data, developing recommendations, and producing executive-level briefings and reports. - Demonstrated ability to coordinate effectively across senior stakeholders, HQMC directorates, regional commands, installations, and external agencies. - Ability to oversee deliverable quality and ensure compliance with federal standards, audit requirements, and reporting protocols. - Proficiency with Microsoft tools, including MS Teams, Word, Excel, and PowerPoint. - PMP certification. Now Qualifications (Preferred Qualifications): - Master's degree in relevant discipline - Direct experience supporting Marine Corps installations facilities programs - Professional Engineer (PE) or Registered Architect (RA) credential, or equivalent technical licensure - Experience supporting MCICOM, NAVFAC, or other USMC facilities programs. - Experience directing global teams in multiple time zones and overseas locations (Japan, South Korea, Hawaii). - Prior leadership of MILCON design review processes and UFC compliance assessments. - Knowledge of UFC criteria, POM budget development, DoD real property systems (iNFADS, BUILDER SMS, Maximo), GIS tools, and MILCON/FSRM processes. - Familiarity with Design-Build and Design-Bid-Build (DB, DBB) project documentation development. - Geospatial and enterprise data integration experience (ESRI, GEOFidelis). - Demonstrated experience developing financial models, cost estimating, POM documentation, or budget exhibits. - Experience managing environmental planning, NEPA, permitting, and cultural/natural resource compliance. - Strong familiarity with Base Operating Support (BOS) metrics, public works operations, maintenance analytics, and FIAR audit readiness. Now Benefits: list: - Medical Insurance and Prescription - Dental Insurance - Vision Insurance - Life and AD&D Insurance - Short-Term/Long-Term Disability Insurance - Employee Assistance Program (EAP) - Voluntary Critical Illness and Accident Insurance - Tuition Reimbursement Assistance - Paid Leave - Paid Holidays - Bereavement Leave - Retirement Plan Also note: "The Concurrent Technologies Corporation pay range for this job level is a general guideline and not a guarantee of compensation or salary." That's a disclaimer; we can include as a

        after Pay maybe. Pay: salary range: "$185,000-$215,000". We'll put as

        . Now we need to ensure we don't include boilerplate like "Why CTC?" etc. We'll omit that. Also need to omit location line? Location is Arlington, VA-Hybrid (Must be DMV Local). That's not a heading; we could include as a short

        maybe under About the role? But location is metadata; instruction says fold minor metadata into a short

        or drop it. We could include a short paragraph with location and clearance. But we already have clearance in the location line? Actually location line includes clearance. We could include a short

        at top: "Location: Arlington, VA-Hybrid (Must be DMV Local). Minimum Clearance Required: Secret." But we must not repeat job ID etc. It's okay. We need to preserve ALL substantive information; location and clearance are substantive. So include them as a short

        before sections. Thus output:

        Location: Arlington, VA-Hybrid (Must be DMV Local). Minimum Clearance Required: Secret Clearance Level. Must Be Able to Obtain: Secret.

        Then

        About the role

        with paragraphs. We need to avoid duplication: The location line also appears in the posting; we included. Now About the role paragraph(s): combine the descriptive text up to the seeking sentence. Let's craft:

        As a trusted partner and leader in providing energy and sustainability consulting services to the federal government, Concurrent Technologies Corporation (CTC) understands the increasing complexity