GSOC Communications Systems Operator

We need to output HTML fragment with sections for headings: 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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. Let's parse content. Job description: - Government Security Operations Center (GSOC) Communications Systems Operator (CSO) Liaison KeenLogic is seeking a Government Security Operations Center Communications Systems Operator Liaison to support the U.S. Air Force’s Executive Airlift Communications Network (EACN) at Joint Base Andrews, Maryland. EACN supports communications for senior U.S. Government leaders aboard executive aircraft. The GSOC, part of the 89th Communications Squadron, serves as the primary reporting office for SLC3S-A operational and maintenance issues, including communications outages, degradations, and deficiencies. This position will provide aircraft mission communications expertise and serve as a ground-based liaison between GSOC personnel and Communications Systems Operators aboard executive aircraft. The liaison will monitor and assist flights, respond to communications incidents, provide troubleshooting guidance, and support improvements to flight monitoring and trend analysis. - KeenLogic offers Fortune 500-level benefits, including health, dental, and vision insurance, PTO, paid federal holidays, 401(k), and life insurance. - Position Details Anticipated Start: January 2, 2027, with availability required for the beginning of phase-in. Contract Length: Anticipated phase-in from January 2–February 1, 2027, followed by a base period from February 2–September 30, 2027. Four one-year option periods may extend performance through September 30, 2031, with a potential six-month extension through March 31, 2032. Location: Joint Base Andrews, Maryland. Onsite Requirements: Onsite at the Government Security Operations Center. Schedule: Assigned shifts supporting 24-hour, 365-day coverage. Coverage includes nights, weekends, and federal holidays. Individual shift times, shift pattern, and weekly hours remain to be confirmed; the 24/7 requirement applies to team coverage, not one individual’s working hours. Clearance: Top Secret clearance. - Required Qualifications Top Secret security clearance. Subject matter expertise in the Mission Communications Systems of one or more of the following aircraft: C-32A, C-40B/C, and/or C-37A/B. Ability to work onsite at Joint Base Andrews and support an assigned schedule within a 24/7/365 operation. Ability to satisfy applicable Government facility-access, security training, and DoD workforce qualification requirements. - Job Expectations Ability to provide expert operational and troubleshooting guidance to airborne Communications Systems Operators. Ability to communicate clearly and accurately during mission communications anomalies, outages, and other time-sensitive situations. Ability to use command-and-control tools, chat applications, and commercial satellite communications monitoring resources. Ability to advise GSOC leadership on aircraft mission communications capabilities and operational issues. Ability to document incidents accurately and contribute to trend analysis and service improvement. - Key Responsibilities Track executive aircraft in flight and assist with communications issues affecting supported missions. Respond to incident calls and provide expert guidance during Mission Communications System anomalies or outages. Advise GSOC leadership on the operation of mission communications systems aboard C-32, C-40, and C-37 executive aircraft. Provide troubleshooting guidance directly to Communications Systems Operators aboard supported aircraft. Use Government command-and-control tools and chat software, such as Mattermost, to support airborne missions. Review the effectiveness of GSOC flight monitoring solutions and recommend improvements. Use relevant web-based tools provided by commercial satellite communications providers to support monitoring and troubleshooting. Support trend-analysis efforts related to communications performance and recurring operational issues. Create, update, and verify incident-management records, including accurate descriptions and resolution details. Support continuous mission-essential coverage in accordance with the assigned staffing schedule - Powered by JazzHR 4AA5gpcKG5 (boilerplate, remove) We need sections: About the role (intro), Responsibilities (Key Responsibilities), Requirements (maybe Required Qualifications?), Qualifications (maybe Job Expectations?), Skills (maybe abilities?), Benefits (benefits), Pay (none), Schedule (schedule). We must only include sections with real specific content. Pay: no mention of salary, so omit Pay section. Benefits: we have benefits described. Schedule: we have schedule details. About the role: we have introductory paragraph(s). Responsibilities: we have Key Responsibilities. Requirements: maybe "Required Qualifications" is requirements. Qualifications: maybe "Job Expectations" could be qualifications? But we need to differentiate. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can map content accordingly. We need to decide what goes where. - About the role: introductory description of role, mission, context. - Responsibilities: list of duties (Key Responsibilities). - Requirements: maybe "Required Qualifications" (clearance, expertise, ability to work onsite, satisfy facility-access etc.) - Qualifications: maybe "Job Expectations" (abilities to provide guidance, communicate, use tools, advise, document). Could also be considered skills. - Skills: maybe list of specific skills like command-and-control tools, Mattermost, web-based tools, etc. But we already have those in Job Expectations. Could split. But we must not create thin sections. Prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can omit sections if no real specific content. We need to include sections only when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly Skills if we have distinct skill list not covered elsewhere. But we could put skills under Qualifications or Requirements. Let's see. We have: - Required Qualifications (clearance, expertise, ability to work onsite, satisfy facility-access). That's Requirements. - Job Expectations (abilities to provide guidance, communicate, use tools, advise, document). That's more like Skills/Qualifications. Thus we can map: Requirements: Required Qualifications bullet list. Qualifications/Skills: Job Expectations bullet list (maybe call it Skills). But we have both Qualifications and Skills headings available. Could put Job Expectations under Qualifications, and maybe Skills under Skills (like specific tools). However we have limited distinct content. Better: Use Requirements for Required Qualifications. Use Qualifications for Job Expectations (abilities). Use Skills maybe empty -> omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Check each for substantive content. About the role: we have first paragraph(s) describing role, mission, GSOC, etc. That's substantive. Responsibilities: Key Responsibilities list. Requirements: Required Qualifications list. Qualifications: Job Expectations list. Benefits: KeenLogic offers Fortune 500-level benefits list. Schedule: Schedule details. We must not include Pay. Now format: Use

for each section heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like dates, locations, etc. Let's extract each piece. About the role prose: Combine sentences: "Government Security Operations Center (GSOC) Communications Systems Operator (CSO) Liaison KeenLogic is seeking a Government Security Operations Center Communications Systems Operator Liaison to support the U.S. Air Force’s Executive Airlift Communications Network (EACN) at Joint Base Andrews, Maryland. EACN supports communications for senior U.S. Government leaders aboard executive aircraft. The GSOC, part of the 89th Communications Squadron, serves as the primary reporting office for SLC3S-A operational and maintenance issues, including communications outages, degradations, and deficiencies. This position will provide aircraft mission communications expertise and serve as a ground-based liaison between GSOC personnel and Communications Systems Operators aboard executive aircraft. The liaison will monitor and assist flights, respond to communications incidents, provide troubleshooting guidance, and support improvements to flight monitoring and trend analysis." We should keep as is, maybe split into paragraphs but okay. Responsibilities list: each bullet from Key Responsibilities. Let's list them: - Track executive aircraft in flight and assist with communications issues affecting supported missions. - Respond to incident calls and provide expert guidance during Mission Communications System anomalies or outages. - Advise GSOC leadership on the operation of mission communications systems aboard C-32, C-40, and C-37 executive aircraft. - Provide troubleshooting guidance directly to Communications Systems Operators aboard supported aircraft. - Use Government command-and-control tools and chat software, such as Mattermost, to support airborne missions. - Review the effectiveness of GSOC flight monitoring solutions and recommend improvements. - Use relevant web-based tools provided by commercial satellite communications providers to support monitoring and troubleshooting. - Support trend-analysis efforts related to communications performance and recurring operational issues. - Create, update, and verify incident-management records, including accurate descriptions and resolution details. - Support continuous mission-essential coverage in accordance with the assigned staffing schedule We need to keep exact phrasing. Requirements list (Required Qualifications): - Top Secret security clearance. - Subject matter expertise in the Mission Communications Systems of one or more of the following aircraft: C-32A, C-40B/C, and/or C-37A/B. - Ability to work onsite at Joint Base Andrews and support an assigned schedule within a 24/7/365 operation. - Ability to satisfy applicable Government facility-access, security training, and DoD workforce qualification requirements. Qualifications list (Job Expectations): - Ability to provide expert operational and troubleshooting guidance to airborne Communications Systems Operators. - Ability to communicate clearly and accurately during mission communications anomalies, outages, and other time-sensitive situations. - Ability to use command-and-control tools, chat applications, and commercial satellite communications monitoring resources. - Ability to advise GSOC leadership on aircraft mission communications capabilities and operational issues. - Ability to document incidents accurately and contribute to trend analysis and service improvement. Benefits list: - health, dental, and vision insurance - PTO - paid federal holidays - 401(k) - life insurance But the text: "KeenLogic offers Fortune 500-level benefits, including health, dental, and vision insurance, PTO, paid federal holidays, 401(k), and life insurance." We'll make list items. Schedule details prose: "Assigned shifts supporting 24-hour, 365-day coverage. Coverage includes nights, weekends, and federal holidays. Individual shift times, shift pattern, and weekly hours remain to be confirmed; the 24/7 requirement applies to team coverage, not one individual’s working hours." We can put as

  . Also we might include Position Details like Anticipated Start, Contract Length, Location, Onsite Requirements, Clearance. Those are not covered in sections yet. Where to put? Could be part of About the role or maybe a separate section like "Position Details". But headings limited to given list. Could incorporate into About the role or Requirements? The instruction: "Prefer a few substantive sections over many thin ones." So we could incorporate those details into About the role or maybe a separate section like "Position Details" not in allowed headings, so we should fold them into existing sections. Where to put Anticipated Start, Contract Length, Location, Onsite Requirements, Clearance? Clearance is already in Requirements (Top Secret clearance). Location and Onsite Requirements could go in About the role or maybe a separate paragraph under About the role. Anticipated Start and Contract Length could go in About the role as well. Thus About the role paragraph can be expanded to include those details. Let's craft About the role prose to include: - Position: Government Security Operations Center Communications Systems Operator