Installation Support Division Chief, S4O

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - The United States Space Force (USSF) Headquarters Space Force Command (HQSF) at The Pentagon in Arlington, Virginia is searching for an Installation Support Division Chief to support S4O (NH-0343-04, GS 14/15 equivalent). - Description: We are seeking an experienced leader who can navigate the complexities of installation management and base operating support at the strategic level, while remaining operationally engaged enough to drive execution, resolve friction and deliver mission ready results. This individual is a leader who thrives on transformation and is able to lead organizational change from concept to execution, turning vision into lasting operational impact. As the principal installations and base operating support advisor, this position will direct a diverse team of military and civilian professionals to ensure the resiliency, protection, and vital operational support of Space Force Bases, Stations and Geographically Separated Units (GSUs) worldwide. The successful candidate will drive enterprise basing decisions, integrate complex inter-service support agreements, and steward resources to guarantee uninterrupted mission execution across the globe. - Ideal Candidate: Possess a robust background in Base Operating Support (BOS) within the Department of the Air Force. Educationally, this individual should hold a bachelor’s degree with a master’s degree highly preferred. Minimum of 10 years of progressive senior leadership experience directing complex, multi-disciplinary, installation operations, successfully executing multi-million-dollar budgets and managing diverse, integrated teams of military and civilian professionals at the group or wing level of leadership. The ideal candidate has an in-depth knowledge of enterprise protection programs (Integrated Base Defense, CBRN, EOD, Fire & Emergency Services) and core BOS functions (Medical, Force Support, Contracting). The candidate must have familiarity with developing and negotiating inter-service support agreements (ISSAs) and sustaining Geographically Separated Units (GSUs) in remote or austere environments. - Key Skills and Abilities: list 1-5. - Requirements: list 1-8 (including PCS/Incentive funding, closing after 5 business days or 75 applications, subject to TDY 30 days a year). Also note: "May be required to travel by military or commercial aircraft in the performance of TDY assign." (typo assign). Also "Eligible for situational telework only, including Emergency and OPM prescribed “Unscheduled Telework”." Also "May be required to work overtime on an unscheduled or emergency basis." Also "PCS / Incentive funding is available and may be offered." Also "This position will close after 5 business days or 75 applications, whichever comes first." Also "Subject to Temporary Duty Assignment (TDY): 30 days a year." We need to decide sections: About the role (description), Responsibilities (maybe from description?), Requirements (list), Qualifications (maybe ideal candidate?), Skills (Key Skills and Abilities), Benefits (maybe PCS/Incentive funding?), Pay (not mentioned), Schedule (maybe situational telework, travel, overtime, TDY). Since Pay not mentioned, we should not create Pay section. Schedule: we have situational telework, travel, overtime, TDY. That's schedule-related info. Benefits: PCS/Incentive funding maybe considered benefit. Also maybe "Eligible for situational telework only" is schedule not benefit. We'll include Benefits section for PCS/Incentive funding. Also maybe "Eligible for situational telework only" could be schedule. We must not create sections with placeholder text like "commensurate with experience". Not present. We need to use

for each section heading. Use

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

  for prose. We need to preserve all substantive info; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So we won't put a heading for the job title. We need to not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

  or drop it. The posting includes "S4O (NH-0343-04, GS 14/15 equivalent)". That's minor metadata; we can include in a short

  maybe under About the role. We need to output only HTML fragment. Let's structure:

  About the role

  The United States Space Force (USSF) Headquarters Space Force Command (HQSF) at The Pentagon in Arlington, Virginia is searching for an Installation Support Division Chief to support S4O (NH-0343-04, GS 14/15 equivalent). We are seeking an experienced leader who can navigate the complexities of installation management and base operating support at the strategic level, while remaining operationally engaged enough to drive execution, resolve friction and deliver mission ready results. This individual is a leader who thrives on transformation and is able to lead organizational change from concept to execution, turning vision into lasting operational impact. As the principal installations and base operating support advisor, this position will direct a diverse team of military and civilian professionals to ensure the resiliency, protection, and vital operational support of Space Force Bases, Stations and Geographically Separated Units (GSUs) worldwide. The successful candidate will drive enterprise basing decisions, integrate complex inter-service support agreements, and steward resources to guarantee uninterrupted mission execution across the globe.

  Maybe we could split responsibilities into a separate section? The description already covers responsibilities. Could have Responsibilities section with bullet list of duties: drive enterprise basing decisions, integrate complex inter-service support agreements, steward resources, direct diverse team, ensure resiliency, protection, vital operational support. But we must not invent or summarize away detail; we can extract from description. The description already includes those duties; we could keep as prose. The instruction: Use
  • for any list of duties/requirements/benefits. If we have a list, we should use list. The description is prose; we could keep as

    . That's fine. Next:

    Qualifications

    maybe for Ideal Candidate (education, experience). Or we could have Requirements separate. Let's decide sections: - About the role (description) - Qualifications (ideal candidate background, education, experience, knowledge) - Skills (Key Skills and Abilities) - Requirements (citizenship, clearance, drug testing, telework, travel, overtime, PCS funding, closing, TDY) - Benefits (PCS/Incentive funding) maybe but that's already in Requirements; we could treat PCS/Incentive funding as benefit. But we already have it in Requirements; maybe better to have Benefits section for PCS/Incentive funding and maybe other benefits (none). However we must not create thin sections; we could combine PCS/Incentive funding into Requirements or Benefits. Since we already have Requirements section with many items, we can keep PCS/Incentive funding there. Benefits section maybe not needed if only that. But we could still include Benefits if we have content. Let's see: The posting mentions "PCS / Incentive funding is available and may be offered." That's a benefit. Also maybe "Eligible for situational telework only" is schedule not benefit. So we could have Benefits section with that line. But we already have Requirements section; we could move PCS/Incentive funding to Benefits. However the instruction: Prefer a few substantive sections over many thin ones. If we create Benefits with just one line, that's thin. Might be better to incorporate into Requirements or maybe into a general "Additional Information" but we don't have that heading. We could incorporate into Requirements as a line item; that's fine. Schedule: we have situational telework, travel, overtime, TDY. That's schedule-related. Could create Schedule section with those items. That's substantive enough (multiple items). So we will have Schedule section. Thus sections: About the role, Qualifications, Skills, Requirements, Schedule. We must not create Pay or Benefits unless posting actually states them. Benefits: PCS/Incentive funding is a benefit; but we could treat as part of Requirements or Schedule? It's not schedule. Could be part of Requirements (miscellaneous). We'll keep it in Requirements. Now we need to ensure we use
    • for any list of duties/requirements/benefits. For Qualifications we have a list of items (education, experience, knowledge). We'll make a
      . For Skills we have numbered list; we can make
      . For Requirements we have numbered list; we can make
      . For Schedule we have bullet points (telework, travel, overtime, TDY). We'll make
      . We need to preserve all substantive info; do not invent or summarize away detail. So we need to include each item exactly as stated, maybe rephrase slightly but keep meaning. We should not omit any detail. Let's extract each piece. About the role paragraph: we already captured. Qualifications (Ideal Candidate): - Possess a robust background in Base Operating Support (BOS) within the Department of the Air Force. - Educationally, this individual should hold a bachelor’s degree with a master’s degree highly preferred. - Minimum of 10 years of progressive senior leadership experience directing complex, multi-disciplinary, installation operations, successfully executing multi-million-dollar budgets and managing diverse, integrated teams of military and civilian professionals at the group or wing level of leadership. - The ideal candidate has an in-depth knowledge of enterprise protection programs (Integrated Base Defense, CBRN, EOD, Fire & Emergency Services) and core BOS functions (Medical, Force Support, Contracting). - The candidate must have familiarity with developing and negotiating inter-service support agreements (ISSAs) and sustaining Geographically Separated Units (GSUs) in remote or austere environments. We'll put each as
      • . Skills (Key Skills and Abilities): 1. Expert knowledge of Base Operating Support (BOS) frameworks, policies, and directives governing military installations, facility sustainment, and municipal-level emergency services (Fire, EMS, and Base Defense). 2. In-depth understanding of Geographically Separated Unit (GSU) support mechanisms, including the development, negotiation, and administration of Inter-Service Support Agreements (ISSAs), Memorandums of Agreement (MOAs), and Host-Tenant Support Agreements. 3. Comprehensive knowledge of military readiness and protection programs, specifically including Chemical, Biological, Radiological, and Nuclear (CBRN) defense, Explosive Ordnance Disposal (EOD), and Integrated Base Defense (IBD) operations in a contested environment. 4. Familiarity with federal budget formulation, contracting regulations, and the PPBE lifecycle required to validate facility requirements and advocate for installation-level resources within the Program Objective Memorandum (POM). 5. Knowledge of federal civilian personnel management principles, OPM supervisory regulations, and merit system protocols required to effectively lead, evaluate, and develop a diverse, multi-functional installations division. We'll put as
      • . Requirements: 1. Must be a U.S. Citizen. 2. Must be able to obtain and maintain a Top-Secret security clearance with SCI access. 3. This is a drug testing designated position. The incumbent is subject to pre-employment drug testing as a condition of employment, and participation in random drug testing. 4. Eligible for situational telework only, including Emergency and OPM prescribed “Unscheduled Telework”. 5. May be required to travel by military or commercial aircraft in the performance of TDY assign. 6. May be required to work overtime on an unscheduled or emergency basis. 7. PCS / Incentive funding is available and may be offered. 8. This position will close after 5 business days or 75 applications, whichever comes first