Regional Desk Officer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. The posting includes description of company, role, location, clearance, responsibilities, qualifications. No explicit benefits, pay, schedule. So we should not include those sections. Also no Skills section unless present; not explicit. So we will have About the role (maybe combine company description and role?), Responsibilities, Requirements, Qualifications. Possibly also a short paragraph for location/clearance metadata. The instruction: do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

for location and clearance. We need to preserve all substantive information. Remove boilerplate: EEO, ADA, accommodation contact, general disclaimer, at-will employment, etc. Also remove duplicated lines. Also remove navigation/cookie/legal etc (none present). So we keep company description, role description, responsibilities list, qualifications list. We need to use

for section headings. Use

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

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's extract content: Company description: "Endurion is a mission integrator built by and for the Special Operations community, providing end-to-end solutions across intelligence, operations, and technology. Founded and led by former Special Operations Forces operators and mission experts, the organization is rooted in firsthand experience with complex operational environments and high-stakes missions. Endurion partners closely with its customers to understand their unique challenges and deliver tailored, mission-focused capabilities. Team members join a culture that values adaptability, operational excellence, and innovation in support of critical national security objectives." Role: "Endurion is currently searching for a Regional Desk Officer to join our team in the Tampa, FL area to support the Joint Special Operations University (JSOU) mission in support of United States Special Operations Command (USSOCOM). Clearance: TOP SECRET clearance required; SCI eligible. Location: JSOU Campus, MacDill AFB, FL" Responsibilities: bullet list from "Plan, coordinate, and track international education programs..." etc. Let's extract each sentence as a bullet. List: - Plan, coordinate, and track international education programs in support of the Theater Special Operations Commands (TSOC) and regional Combatant Commands. - Develop and maintain international education network with emphasis on TSOC and Security Cooperation Organization (SCO) relationships to meet Special Operations education requirements. - Coordinate JSOU international engagement activities with all USSOCOM stakeholders through participation at security cooperation education & training working groups, regional education and training conferences, and other security cooperation conferences and workshops. - Provides periodic briefs to JSOU leadership. - Submit APACS, coordinate visas, and establish cross org for government travelers. - For International METs, responsible for the entire MET process from inception to completion including extensive coordination with the SCO, AFSAT case manager, DSCA, JSOU instructors & staff, IMSO, hotel staff, IT, and interpreter company/interpreters. - Works directly with these stakeholders to complete the following tasks: * With SCO: Complete MET worksheet to determine requirements. Coordinate in-country approvals and funding sources. Submit request to AFSAT, via DD Form 2964 * With AFSAT Case Manager: Confirm vetting of DD Form 2964 and checks status of form Build WCN Obtain FBO approval * With JSOU instructors & staff: Conduct initial IPR Identify venue requirements Submit ERW; FDO requirements; translation and printing requirements for processing. Review and post CONOPS package (agenda, risk assessment matrix, storyboard) Assist with course critique, demographic sheets, graduation certificates, and certificates of appreciation. Coordinate photographer, travel arrangements for team, arrival messages, student rosters, tent cards, refreshments, classroom layout, breakrooms, lodging procedures, interpreter guidelines and After-Action Reports (AARs). * With IMSO: Coordinate completion of student handbook/welcome guide (including translation) Plan social events Coordinate in processing/out-processing We could flatten sub-bullets but spec says use

  • for any list of duties/requirements/benefits. Could nest lists? Probably okay but simpler to keep each as separate
  • . Might be long but okay. Qualifications: list: - TOP SECRET clearance required; SCI eligible. - BS/BA in any field* - 2 years’ experience as a security cooperation planner with assignment as a SCO or in support of a TSOC, Regional Combatant Command (RCC) or at Special Operations Component level. - 5 years’ recent experience (within 2-3 years of start date) in one of the principal SOF personnel categories: SF, SEAL, Special Boat, CA, MISO, Special Operations Aviation, Combat Aviation Advisor, AFSOC Special Tactics, MARSOC, Ranger. - 3 years’ experience in a Special Operations environment as an enabler. - OR 3 years’ experience in a previous assignment to the SOCOM/SOF Component HQ staff. - 2 years of practical experience planning security cooperation activities with assignment or in support of TSOC, Regional Combatant Command (RCC), Special Operations Component, or Joint Special Operations University. - Complete Defense Security Cooperation level 2 training within 1 year of employment. We need to preserve the asterisk note? It says BS/BA in any field* maybe footnote but we keep as is. We should not include EEO etc. We'll create sections:

    About the role

    with paragraph(s) containing company description and role location/clearance. Maybe split: first paragraph company description, second paragraph role specifics. Then

    Responsibilities

    with
    • ... etc. Then

      Requirements

      maybe not needed because qualifications cover? The posting has "Requirements:" section before qualifications. Actually they have "Requirements:" then list of duties? Wait they had "Requirements:" then list of duties? Actually after location they wrote "Requirements:" then list of duties (plan, coordinate...). Then later "Qualifications:" list. So we need separate sections: Responsibilities (the duties) and Requirements (maybe the qualifications? But they label "Requirements:" as duties list. However typical job postings: Responsibilities = duties, Requirements = qualifications. But here they used "Requirements:" for duties list and "Qualifications:" for qualifications. To follow instruction: we should include sections only when posting has real specific content. We have both sections: Responsibilities (duties) and Requirements (maybe the qualifications?). But they also have a "Qualifications:" section. So we need three sections: Responsibilities, Requirements, Qualifications. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Qualifications. Thus: - About the role: company description + role location/clearance. - Responsibilities: the list of duties (the "Requirements:" block). - Requirements: maybe we could treat as the qualifications? But they have separate Qualifications. Actually the posting has "Requirements:" then duties, then "Qualifications:" then qualifications. So we need to map: Responsibilities = duties? Or Requirements = duties? Usually Responsibilities = duties, Requirements = qualifications. But the posting uses "Requirements:" for duties and "Qualifications:" for qualifications. To avoid confusion, we can follow the posting's headings: Responsibilities (maybe we could rename? but instruction says use those headings exactly). We could treat the duties as Responsibilities, and the qualifications as Requirements? But then we would lose the Qualifications section. However we have both sections in posting; we should reflect both. So we need to map: Responsibilities = duties (the list after "Requirements:"); Requirements = maybe the qualifications? But then we lose Qualifications heading. But we could also include Qualifications as separate section with the qualifications list. That would duplicate content? Actually we would have both Requirements and Qualifications sections with same content if we map incorrectly. Better to follow the posting: Responsibilities = duties (the list after "Requirements:"); Requirements = maybe the qualifications? But then we need also Qualifications section? The posting has both "Requirements:" and "Qualifications:" headings. So we should have both sections: Responsibilities (maybe we could treat as duties) and Requirements (maybe we could treat as qualifications) and Qualifications (maybe we could treat as something else?). But that seems redundant. Let's re-examine the posting text: "Endurion is currently searching for a Regional Desk Officer to join our team in the Tampa, FL area to support the Joint Special Operations University (JSOU) mission in support of United States Special Operations Command (USSOCOM). Clearance: TOP SECRET clearance required; SCI eligible. Location: JSOU Campus, MacDill AFB, FL Requirements: Plan, coordinate, and track international education programs in support of the Theater Special Operations Commands (TSOC) and regional Combatant Commands. Develop and maintain international education network with emphasis on TSOC and Security Cooperation Organization (SCO) relationships to meet Special Operations education requirements. Coordinate JSOU international engagement activities with all USSOCOM stakeholders through participation at security cooperation education & training working groups, regional education and training conferences, and other security cooperation conferences and workshops. Provides periodic briefs to JSOU leadership. Submit APACS, coordinate visas, and establish cross org for government travelers. For International METs, responsible for the entire MET process from inception to completion including extensive coordination with the SCO, AFSAT case manager, DSCA, JSOU instructors & staff, IMSO, hotel staff, IT, and interpreter company/interpreters. Works directly with these stakeholders to complete the following tasks: With SCO: Complete MET worksheet to determine requirements. Coordinate in-country approvals and funding sources. Submit request to AFSAT, via DD Form 2964 With AFSAT Case Manager: Confirm vetting of DD Form 2964 and checks status of form Build WCN Obtain FBO approval With JSOU instructors & staff: Conduct initial IPR Identify venue requirements Submit ERW; FDO requirements; translation and printing requirements for processing. Review and post CONOPS package (agenda, risk assessment matrix, storyboard) Assist with course critique, demographic sheets, graduation certificates, and certificates of appreciation. Coordinate photographer, travel arrangements for team, arrival messages, student rosters, tent cards, refreshments, classroom layout, breakrooms, lodging procedures, interpreter guidelines and After-Action Reports (AARs). With IMSO: Coordinate completion of student handbook/welcome guide (including translation) Plan social events Coordinate in processing/out-processing Qualifications: TOP SECRET clearance required; SCI eligible. BS/BA in any field* 2 years’ experience as a security cooperation planner with assignment as a SCO or in support of a TSOC, Regional Combatant Command (RCC) or at Special Operations Component level. 5 years’ recent experience (within 2-3 years of start date) in one of the principal SOF personnel categories: SF, SEAL, Special Boat, CA, MISO, Special Operations Aviation, Combat Aviation Advisor, AFSOC Special Tactics, MARSOC, Ranger. 3 years’ experience in a Special Operations environment as an enabler. OR 3 years’ experience in a previous assignment to the SOCOM/SOF Component HQ staff. 2 years of practical experience planning security cooperation activities with assignment or in support of TSOC, Regional Combatant Command (RCC), Special Operations Component, or Joint Special Operations University. Complete Defense Security Cooperation level 2 training within 1 year of employment." Thus after location they wrote "Requirements:" then the duties list. Then after that they wrote "Qualifications:" then qualifications list. Thus we should have: - About the role: company description